Fixing an epub from KindleImport

[dhdurgee]

I am working on fixing errors in an epub that I created via KindleImport and given my lack of experience in this area am unsure of the appropriate way to do so. The F7 FlightCrew validation yields two types of errors. The first is:

OEBPS/content.opf - 30 - The <item> element's "media-type" attribute has value "application/x-font-opentype", but the file's media type is "application/vnd.ms-opentype".

Am I correct in assuming the proper way to fix this is to adjust the media-type attribute in content.opf?

The second type of error is:

OEBPS/Styles/&quot;fonts/Fort-Book.otf&quot; - N/A -This resource is reachable but not present in the OPF <manifest>. "Reachable" means that a reference of some kind that points to this resource exists in the epub.

Tracking this down I find the Fort-Book.otf reference in Style0002.css which is used only in part0147.xhtml in the document. As the error notes, the font is not present in the epub. Is the appropriate fix to replace it with one of the fonts present? Is it possible that the font was in the original azw3 and KindleImport had problems with it? Is the font file available somewhere and can I incorporate it into the document?

Thanks for any assistance or guidance you can give.

Dave

[DiapDealer]

Originally Posted by dhdurgee

I am working on fixing errors in an epub that I created via KindleImport and given my lack of experience in this area am unsure of the appropriate way to do so. The F7 FlightCrew validation yields two types of errors. The first is:



Am I correct in assuming the proper way to fix this is to adjust the media-type attribute in content.opf?

Yes. You're correct. Changing the media type in the opf manifest is the way to fix this.

And for future reference, you may want to drop the "F7" from your references to "F7 FlightCrew Validation." In the latest versions of Sigil, "F7" is no longer associated with FlightCrew (like it is in your older Sigil). FlightCrew is now a separate Validation plugin. So just referring to it as "FlightCrew" will probably help avoid any confusion.

Originally Posted by dhdurgee

The second type of error is:



Tracking this down I find the Fort-Book.otf reference in Style0002.css which is used only in part0147.xhtml in the document. As the error notes, the font is not present in the epub. Is the appropriate fix to replace it with one of the fonts present? Is it possible that the font was in the original azw3 and KindleImport had problems with it? Is the font file available somewhere and can I incorporate it into the document?

I saw that one, myself. Not really sure what to make of it actually. My guess is that it was messed up when it went into Kindlegen, because filenames simply don't come back out of a KindleBook binary that way. Because filenames don't actually exist in a KF8 Kindlebook.

But regardless, a search of that (and the other css file) shows that a font family named "Fort-Book" is never assigned to any elements via css. Further searching shows that all 6 of the fonts included in the epub (the font folder) all have corresponding @font-face declarations somewhere in the two css files. So it seems in this case that this css @font-face is unused and unneeded. I'd frankly just delete that @font-face { } statement from the css and move on.