Trouble with compile to Ebook and Kindle

Hi,
I’m having trouble with compile for ebooks and KIndle.

  1. Ebooks - there are a few chapters in the MS, when viewed on iBook, contain an error message followed by the first few sentences of the chapter. Here is the error message:

“This page contains the following errors:

error on line 19 at column 114: Opening and ending tag mismatch: div line 0 and p
Below is a rendering of the page up to the first error.”

I don’t know what to do about this. The chapter looks the same in the file as all the other chapters.

  1. Kindle - I’m getting the same error message as others have posted about before: “KindleGen failed to generate a mobi file at the specified location.” A solution to this was given as making sure you have the latest Scrivener version (which I do) and making sure to download Kindle Previewer 3, which is what I have. I’ve never used KindleGen. But I still get the error. I’ve pasted below the detailed log of the error.

Anyone have any help for this? It looks like perhaps a problem with the hyperlinks from the TOC to the MS?

Any advice on either of these errors appreciated!

Lisa


Amazon kindlegen(MAC OSX) V2.9 build 0000-kdevbld
A command line e-book compiler
Copyright Amazon.com and its Affiliates 2015


Info(prcgen):I1047: Added metadata dc:Title “BOUND-Book Two of the Traveller’s Path, FINAL FOR COMPILE (june 2020)”
Info(prcgen):I1047: Added metadata dc:Creator “L.A. Smith”
Info(prcgen):I1002: Parsing files 0000070
Info(prcgen):I1015: Building PRC file
Info(prcgen):I1006: Resolving hyperlinks
Warning(prcgen):W14001: Hyperlink not resolved: /private/var/folders/lh/61nh9gb57tx2ldngt4js85_c0000gn/T/EBOOK_TEMP/BOUND-Book Two of the Traveller’s Path, FINAL FOR COMPILE (june 2020)#1 MOBI/contents.xhtml
Warning(prcgen):W14001: Hyperlink not resolved: /private/var/folders/lh/61nh9gb57tx2ldngt4js85_c0000gn/T/EBOOK_TEMP/BOUND-Book Two of the Traveller’s Path, FINAL FOR COMPILE (june 2020)
#1 MOBI/body1.xhtml
Warning(prcgen):W14001: Hyperlink not resolved: /private/var/folders/lh/61nh9gb57tx2ldngt4js85_c0000gn/T/EBOOK_TEMP/BOUND-Book Two of the Traveller’s Path, FINAL FOR COMPILE (june 2020)_
Warning(prcgen):W14002: Some hyperlinks could not be resolved.
Info(prcgen):I1008: Resolving start reading location
Warning(prcgen):W14003: The start reading location could not be resolved.
Error(prcgen):E24010: Hyperlink not resolved in toc (One possible reason can be that the link points to a tag with style display:none):/private/var/folders/lh/61nh9gb57tx2ldngt4js85_c0000gn/T/EBOOK_TEMP/BOUND-Book Two of the Traveller’s Path, FINAL FOR COMPILE (june 2020)#1 MOBI/body.xhtml#
Error(prcgen):E24001: The table of content could not be built.
Info(prcgen):I1016: Building enhanced PRC file
Error(prcgen): Hyperlink not resolved in toc (One possible reason can be that the link points to a tag with style display:none):/private/var/folders/lh/61nh9gb57tx2ldngt4js85_c0000gn/T/EBOOK_TEMP/BOUND-Book Two of the Traveller’s Path, FINAL FOR COMPILE (june 2020)
#1 MOBI/body.xhtml#

Info(prcgen):I1007: Resolving mediaidlinks
Info(prcgen):I1011: Writing mediaidlinks
Info(prcgen):I1009: Resolving guide items
Info(prcgen):I1038: MOBI file could not be generated because of errors!

These sorts of errors are usually indicative of an incorrectly formatted Contents page, which is a bit strict given how ePub and Amazon formatting guidelines are described. The warning signs are highlighted:

Warning(prcgen):W14001: Hyperlink not resolved: /private/var/folders/lh/61nh9gb57tx2ldngt4js85_c0000gn/T/EBOOK_TEMP/BOUND-Book Two of the Traveller’s Path, FINAL FOR COMPILE (june 2020)_#1 MOBI/contents.xhtml

And toward the bottom:

Error(prcgen):E24001: The table of content could not be built.

So when you encounter a warning or error like the first one, most of the path to the file can be ignored—that’s just where Scrivener was working from while it was putting your book together. The important stuff is at the end, and in this case you can see that it is the contents file itself that had errors. If it is another file, like “body23.xhtml”, then you know the problem is in a certain file and the best thing to do is open the .epub in Sigil or Calibre to edit it, and look up that file, along with the line number the error report gives you. That can usually lead you to precisely where the problem is in the text editor, back in Scrivener.

But for this, we can see at the end of the log that it eventually gave up entirely, probably on account of these other warnings.

Make sure you are following the advice given in the user manual for constructing a custom ebook ToC, in §22.2, Contents in Ebooks, the big yellow warning box toward the bottom of page 553. As a secondary test, temporarily move the custom contents section out of the Draft or Front Matter folder and let Scrivener automatically generate one. That will also clue you in on whether the problem is larger, or something with this one file.

Okay. Thank you…I will do my best to follow this (gulp)…I’m not a programmer so these kinds of things seem very intimidating to me but I’ll take it step by step and will see how I go. I will report back once I’ve given it a try. I don’t have much confidence in myself that I’ll get it figured out in one shot but I will see! :slight_smile: I’ll start with the advice in the user manual!

Thanks again,

Lisa

Fortunately the fix shouldn’t involve any programming! :slight_smile: Most likely you just need to delete a title from this file or style is properly—or maybe shuffle some text around. Like I say, a good first test will be compiling without the contents file, otherwise you might spend a while trying to fix something that isn’t broken.

Ok. I deselected the option to create a HTML table of content in the Compile settings…the same error came up. :frowning:

In looking through the Manual where you suggested, it seems like that part of the Manual is talking about creating a custom table of contents. Just for clarity, I did not do so for this project, nor do I want to, if possible.

Stumped.

Lisa

The checkbox itself may not actually dodge the problem, as there will always be a table of content—whether there is a visible one in the book that people can page to is what the “HTML” version is. So the question then would be, do you by happenstance of a chapter or section anywhere in the Draft folder that is named “Contents”? If so, and it needs to be that way, maybe change the setting in the compiler to read “Table of Contents” instead.

If that doesn’t work, it may work best to get in touch with tech support and send a copy of the project so they can take a look for you. Without HTML experience, it may be hard to say what is going on. You really kind of have to look at the book itself against the error log to know what’s going on in some cases.

No I don’t have any chapter or section with the title of Contents. Drat. Looks like not an easy fix. I will contact tech support and see if they can help.

Thanks for your help, much appreciated!

Lisa

Hi,

I’m just a user and have less than 10% of Ioa’s Scrivener-fu, but while reading the thread, I wonder if “Zap Gremlins”—it’s somewhere in the “Edit” menu, at the bottom; I’m not at my Mac at the moment to check—would make any difference … that there’s some kind of code remnant in there causing the problem.

Just an idea, possibly useless.

:slight_smile:

Mark