media type in the manifest

[rubeus]

Sigil is doing that correct. But there are a lot of converters or other programs doing it not correct.

Doitso: thx but this is only working for octet-stream, there are some other media-types out there.

@Diap: yes, thats what i'm looking for. But to achieve this i need to know how Sigil is doinf that to do it the same way. Now i need to have a look in the Sigil-Python-API to find out what is available to achieve this. Getting the fonts is easy, i've done that creating the Stylesheet. But now i need the way back

Edit: just read the API documentation and as far as i can see there is no method to write something to the manifest.

[KevinH]

Hi,

Edit: just read the API documentation and as far as i can see there is no method to write something to the manifest.

I am not sure what you are trying to do. Where did the incorrect media type come from? Upon import if you load an epub, it will use the media-type from the incoming content.opf otherwise it will use the file extension to look up the media-type per the map I posted a link to.

In a plugin, you can walk all of the fonts (or even all of the files in the manifest) using the api and then add new files for any with the wrong media-type and then remove the incorrect ones.

So, yes this is easily doable via a plugin. If you want more information about how to understand the plugin api, just ask in the Sigil plugin developers thread so that any answers can be kept in one place to help future plugin developers.

KevinH

[Doitsu]

Originally Posted by KevinH

In a plugin, you can walk all of the fonts (or even all of the files in the manifest) using the api and then add new files for any with the wrong media-type and then remove the incorrect ones.

If I understand you correctly, there's no way to directly manipulate manifest entries or rewrite the manifest section only. The following code seems to work, but, IMHO, it'd be much easier if the Plugin Runner code allowed for direct manifest entry value changes.

#!/usr/bin/env python
 # -*- coding: utf-8 -*-
import os
 
def run(bk):

    # read manifest items
    for id in sorted(bk._w.id_to_mime):
        mime = bk._w.id_to_mime[id]
        href = bk._w.id_to_href[id]
            
        # check for invalid MIME types
        if href.endswith('tf') and mime not in ('application/x-font-ttf', 'application/vnd.ms-opentype') :
            data = bk.readfile(id)
            bk.deletefile(id)
            if href.endswith('ttf'):
                bk.addfile(id, os.path.basename(href), data, 'application/x-font-ttf')
            else:
                bk.addfile(id, os.path.basename(href), data, 'application/vnd.ms-opentype')
            print 'MIME type updated: ' + os.path.basename(href)

def main():
    print 'I reached main when I should not have\n'
    return -1

if __name__ == "__main__":
    sys.exit(main())

BTW, for Sigil 0.9.0 you could theoretically use application/font-sfnt for both .ttf and .otf files, since both epubcheck 3.0.1 and epubcheck 4.x accept all font mimetypes that start with "font" or "x-font."

[rubeus]

Hi doitso

thats exactly what i'm currently testing, i'm only using the font iterator. Is there a way to get the sigil version in a plugin?

But maybe we should really move this to plugin develop forum.

[Doitsu]

Originally Posted by rubeus

thats exactly what i'm currently testing, i'm only using the font iterator.

My code uses parts of the font iterator code and should behave exactly the same.

Originally Posted by rubeus

Is there a way to get the sigil version in a plugin?

For all intents and purposes my code pretty much mimics what Sigil does when fonts are added.

Originally Posted by rubeus

But maybe we should really move this to plugin develop forum.

I agree. Can a moderator please move this thread to the Plugin section?

[DiapDealer]

Originally Posted by Doitsu

If I understand you correctly, there's no way to directly manipulate manifest entries or rewrite the manifest section only. The following code seems to work, but, IMHO, it'd be much easier if the Plugin Runner code allowed for direct manifest entry value changes.

#!/usr/bin/env python
 # -*- coding: utf-8 -*-
import os
 
def run(bk):

    # read manifest items
    for id in sorted(bk._w.id_to_mime):
        mime = bk._w.id_to_mime[id]
        href = bk._w.id_to_href[id]
            
        # check for invalid MIME types
        if href.endswith('tf') and mime not in ('application/x-font-ttf', 'application/vnd.ms-opentype') :
            data = bk.readfile(id)
            bk.deletefile(id)
            if href.endswith('ttf'):
                bk.addfile(id, os.path.basename(href), data, 'application/x-font-ttf')
            else:
                bk.addfile(id, os.path.basename(href), data, 'application/vnd.ms-opentype')
            print 'MIME type updated: ' + os.path.basename(href)

def main():
    print 'I reached main when I should not have\n'
    return -1

if __name__ == "__main__":
    sys.exit(main())

Not that it matters a lot in this instance/example, but you may just want to use the manifest_iter method of the bookcontainer (bk) class instead of calling the underlying wrapper methods and properties directly.

for id, href, mime in bk.manifest_iter()

[KevinH]

Hi,

Yes, DiapDealer is correct. Calling the wrapper routines directly in your plugin is NOT supported. The wrapper routines are subject to change at any time. You should be using the iterators in the bookcontainer class. The bookcontainer class is the public API for the edit plugins.

Given the design uses the content.opf to derive the interface itself and tries to protect the content.opf from being incorrectly changed, directly changing the media-types will not be supported. It should not be needed if font files are added in Sigil as Sigil will assign the correct media-type.

Hope this explains things.

KevinH

[rubeus]

There are books created outside Sigil and often they do have an incorrect media type. Sigil itself does not offer any help here, it only flags the error and i need to manipulate the content.opf manually. I guess i was telling this more than three times, why is there always the hint that Sigil is inserting fonts correctly? I never said that Sigil is inserting fonts incorrectly. But others do. At least one person out of 8 billion would like to have something helpful here. thats why i created this plugin.

[KevinH]

No, you are incorrect ...

If you load an epub into Sigil that has bad media types it may end up storing the file in the incorrect location for an epub in Sigil. Or it may place it in the correct place but with an incorrect media- type. If either of these happen, the user can do one of two things depending on their skill level.

1) Delete the font files in Sigil and re-add them and Sigil will automatically put them in the right place (as I repeatedly have pointed out).

OR

2) Use CodeView to directly edit the content.opf and change just the media-types.


If you want to accomplish something similar in the plugin, simply use the correct bookcontainer API calls as directed earler.

No one is saying the problem does not exist. We are simply pointing out that if you add fonts using Sigil, they will be assigned the correct media-types which in turn leads directly to approach 1) above and the API approach we pointed out in the plugin.

Hope this makes things clearer.

KevinH

Originally Posted by rubeus

There are books created outside Sigil and often they do have an incorrect media type. Sigil itself does not offer any help here, it only flags the error and i need to manipulate the content.opf manually. I guess i was telling this more than three times, why is there always the hint that Sigil is inserting fonts correctly? I never said that Sigil is inserting fonts incorrectly. But others do. At least one person out of 8 billion would like to have something helpful here. thats why i created this plugin.

[rubeus]

*sigh* nuff said