IngramSpark Help Center home page Submit a request

Deciphering cryptic error messages

Comments

9 comments

  • Erik Istrup Publishing

    Hi, Richard.

    In InDesign, go to the menu File > File Info... and add info in the first tab (Description), these data will be transferred to the epub file.

    I always have to tweak a few things in the epub file (using Sigel) anyway. It is the Font Obfuscation set to None, and the "Media-type" set to "application/x-font-ttf" in the content.opf. There may also be a thing with the bookid. This also in respect to the toc.ncx.

    Does the FlightCrew plugin in Sigil help you. Maybe showing you a line number to refer to?

    I can't attach an epub file here, but you can ask to see one of mine: eip@erikistrup.dk

    0
    Comment actions Permalink
  • Richard McGuire

    Hi Erik,

    Thanks very much for your reply. I fear some of this is over my head and I still don't understand what the error messages mean.

    I followed your advice about filling in the File Info data in InDesign first. But my book is a Book in InDesign with 26 chapters, each chapter being its own InDesign file. I completed the File Info in one of the chapters, but it does not synchronize this information into the other chapters. I can't find a way to copy the information into the other chapters, and entering it all manually is a big job. Does every file need this File Info?

    The other two errors would appear to be in toc.ncx and it looks like the same error in both. Would your advice on Font Obfuscation and Media-type apply to this?

    I'm new to Sigil and am unfamiliar with FlightCrew, but I will check this out. (Added: I just installed FlightCrew, and the book failed because it says FlightCrew only supports ePub 2 and my book is in ePub 3).

    Your help is very much appreciated, but if you or anyone else can provide further clarification on the above points it would help a lot. Thanks very much.

    1
    Comment actions Permalink
  • Erik Istrup Publishing

    I have never worked with individual files for each chapter. I use Document and not Book if I start a new book.

    I assume the epub file you generate is ONE file. I also assume the file info does not reflect into the epub file. If you put the (few) info material into any file for copy/paste, you can have this file open and  paste it into each InDesign file.

    I had not had the other error, but an error from IngramSpark, if the fonts are not Obfuscationed.

    I am sure the FlightCrew plugin will help you. https://github.com/Sigil-Ebook/flightcrew/releases 

     

     

    0
    Comment actions Permalink
  • Richard McGuire

    Hi Erik,

    Thanks for your reply. As I added to my note above, I tried FlightCrew, but it only works with ePub 2. IngramSpark requires ePub 3.

    I will try creating and validating an ePub 2 file in the hopes that FlightCrew can identify the error, but I'll still need to upload an ePub 3 file.

    Hopefully someone can tell me what the "[ERROR]OEBPS/toc.ncx: External DTD entities are not allowed. Remove the DOCTYPE." means and how to fix it.

    Thanks again.

    0
    Comment actions Permalink
  • Erik Istrup Publishing

    I generate and upload epub 2 files to IS and always have!

     

    0
    Comment actions Permalink
  • Richard McGuire

    Hi Erik,

    I believe IS now requires ePub 3 and this change may be recent.

    I reexported my book as an ePub 2 and ran it through FlightCrew validation. It gave me two errors, both in content.opf.

    Both errors give the message:

    Error OPF bad item media type value: The <item> element's "media-type" attribute has value "application/vnd.ms-opentype", but the file's media type is "application/x-font-ttf". near column 105 (near column 109 in the second error)

    The offending lines are:

    <item id="Cambria-Italic.ttf" href="Fonts/Cambria-Italic.ttf" media-type="application/vnd.ms-opentype"/>

    <item id="Cambria.ttc" href="Fonts/Cambria.ttc" media-type="application/x-font-ttf"/>

    I'm not sure how to fix these.

    I found another plug-in called "ePub3-itizer" that is supposed to convert an ePub2 to ePub3, so if I can solve the problems in ePub2 and then convert to ePub3, I might be able to get IS to validate the file.

    Any help you or anyone else can give me on how to revise those two lines would be much appreciated. Thanks!

    1
    Comment actions Permalink
  • Erik Istrup Publishing

    This program checks epub2 and 3 files: https://github.com/w3c/epubcheck 
    Download here: https://github.com/w3c/epubcheck/releases 

    Prepare an InDesign document for EPUB output: https://helpx.adobe.com/indesign/how-to/indesign-prepare-document-for-epub.html

    InDesign Kindle plug-in:https://www.amazon.com/gp/feature.html?ie=UTF8&docId=1000765271&tag=viglink121320-20

    When I got this one:

    "Error OPF bad item media type value: The <item> element's "media-type" attribute has value "application/vnd.ms-opentype", but the file's media type is "application/x-font-ttf". near column 105 (near column 109 in the second error)"

    I simply change the media type to "application/x-font-ttf" as FlightCrew suggested.

    The second one: I can only guess that Cambria.ttc should be Cambria.ttf unless you have the file type, ttc (which I don't know).

    Sounds great with the ePub2 to 3!

    0
    Comment actions Permalink
  • Richard McGuire

    Thanks again for all your help Erik,

    Fingers crossed, but I finally got IS to validate my ePub file.

    I generated an ePub 2 file in InDesign, then ran it through FlightCrew in Sigil, making the media type changes as you suggested. Then I ran it through the ePub3-itizer plugin to convert it to ePub 3.

    This messed up the HTML in content.opf, notably removing the closing tag on the "spine" attribute. I had to use Calibre to fix this.

    Anyway, IS finally accepted it.

    I very much appreciate your help on this.

    1
    Comment actions Permalink
  • Erik Istrup Publishing

    Super, that you didn't give up, and ended up with fixing it!

    Thanks for the feedback on how you did it!

    0
    Comment actions Permalink

Please sign in to leave a comment.

Support