Bookshelf | Reports | Community | KDP Select

Home » Amazon KDP Support » Ask the Community » Formatting

Thread: Kindle Previewer errors; any suggestions welcome


This question is answered.

Reply to this Thread Reply to this Thread Search Forum Search Forum Back to Thread List Back to Thread List

Permlink Replies: 5 - Pages: 1 - Last Post: Nov 7, 2017 5:41 AM Last Post By: Babu
david101727

Posts: 46
Registered: 05/04/12
Kindle Previewer errors; any suggestions welcome
Posted: May 30, 2012 9:37 AM
 
Click to report abuse...   Click to reply to this thread Reply
Hi,

I'm a newbie. I'm working on formatting my first Kindle title which is a children's picture book. I have already successfully produced fixed layout iPad titles. I'm in the UK and just received a Kindle Fire in the post today, so that's what I'll be testing on.

When I run Kindle Previewer much of the file is okay until the end where I still have a number of errors:

**************************************************
  • Amazon.com kindlegen(Windows) V2.4 build 69900 *
  • A command line e-book compiler *
  • Copyright Amazon.com 2012 *
**************************************************

Info:I9014:option: -verbose: Verbose output

(Removed for space saving)

Info(prcgen):I1002: Parsing files 0000020

Info(prcgen):I1003: Parsing file URL: Cover.xhtml

Info(prcgen):I1003: Parsing file URL: page02.xhtml

(Removed for space saving)

Info(prcgen):I1003: Parsing file URL: page20.xhtml

Info(prcgen):I1015: Building PRC file

Info(prcgen):I1006: Resolving hyperlinks

Info(prcgen):I1010: Writing hyperlinks

Warning(prcgen):W14001: Hyperlink not resolved: C:\DOCUME~1\David\LOCALS~1\Temp\mbp_7DC_5_1E_11_14_1D4_14E8_4D8_1\html\page02.html

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.

Info(prcgen):I1049: Building table of content URL: C:\DOCUME~1\David\LOCALS~1\Temp\mbp_7DC_5_1E_11_14_1D4_14E8_4D8_1\toc.ncx

Error(prcgen):E24010: Hyperlink not resolved in toc:C:\DOCUME~1\David\LOCALS~1\Temp\mbp_7DC_5_1E_11_14_1D4_14E8_4D8_1\Cover.xhtml#

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

Info(prcgen):I1038: MOBI file could not be generated because of errors!

  • - -

I realise that these are likely to be simple problems, but I'm right at the start of my learning curve, so any suggestions or pointers would be very welcome.

Thanks
mrlasers

Posts: 1,633
Registered: 07/06/11
Re: Kindle Previewer errors; any suggestions welcome
Posted: May 30, 2012 9:51 AM   in response to: david101727 in response to: david101727
Correct
Click to report abuse...   Click to reply to this thread Reply
This error occurs when the reference to a file within the NCX, or a named location within that file, can not be found. This is called "resolution," which you'll see mentioned in the error message.

Error(prcgen):E24010: Hyperlink not [b]resolved[/b] in toc:C:\DOCUME~1\David\LOCALS~1\Temp\mbp_7DC_5_1E_11_14_1D4_14E8_4D8_1\Cover.xhtml#

What this means for you is that your files are either not named as you have specified in your OPF and NCX files, or (possibly more likely) they are simply not in the expected location relative to each other.

Make sure that the relative path from the OPF file to every file referenced within is correct. Then check the same for NCX. Should be able to clear it up. Also, if you do have a reference to "Cover.xhtml#" you can drop the hash as this is only necessary when specifying a named location within that file, like "Cover.xhtml#title" or whatever.

--
MrLasers
eBook Formatting & Production
http://www.mrlasers.com
david101727

Posts: 46
Registered: 05/04/12
Re: Kindle Previewer errors; any suggestions welcome
Posted: May 31, 2012 4:59 AM   in response to: mrlasers in response to: mrlasers
 
Click to report abuse...   Click to reply to this thread Reply
Thanks mrlasers.

I followed your advice and finally found a reference with the wrong path.

Fixing that allowed me to make a mobi file (still with warnings). I'll keep going on the warnings.

My mobi file is displaying pages much larger than the Fire view port. I'll try to fix this, but it may be that I open up another post asking for help if I don't make any progress.

Thanks!
Kin Wilson

Posts: 1
Registered: 09/26/12
Re: Kindle Previewer errors; any suggestions welcome
Posted: Sep 26, 2012 12:44 PM   in response to: david101727 in response to: david101727
 
Click to report abuse...   Click to reply to this thread Reply
Watch out when copying code. I copied ncx code from Amazon Kindle Publishing Guidelines and found one of the quotation marks was typographic not the upright ascii kind. Took a while :(
booknookbiz

Posts: 4,009
Registered: 03/04/10
Re: Kindle Previewer errors; any suggestions welcome
Posted: Sep 26, 2012 6:54 PM   in response to: david101727 in response to: david101727
 
Click to report abuse...   Click to reply to this thread Reply
David:

Are you attempting to use the iBooks version (ePUB) of the file to create the MOBI? That won't work well. K8 fixed-format books require their own coding, so that you don't have viewport issues, which will cause the book to fail intake. May I ask how you made the source file (epub, html, etc.)? Or did you simply recapture the html and endeavor to reuse it? Did you make your iBooks version in code or with iBooks Author?

Hitch
We produce ebooks
Listed as an Amazon Professional Conversion Service: http://bit.ly/uFwMwb
An INScribe Preferred Conversion Partner
http://www.booknook.biz/
Follow me on Twitter: @BookNookBiz
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur."
  • Red Adair
Babu

Posts: 1
Registered: 11/07/17
Re: Kindle Previewer errors; any suggestions welcome
Posted: Nov 7, 2017 5:37 AM   in response to: david101727 in response to: david101727
 
Click to report abuse...   Click to reply to this thread Reply
Hi,

The anchor ID's should be sequence in the toc.ncx, nav.xhtml and content page. Also in the XHTML files.

e.g.

filename.xhtml#f1
filename.xhtml#f2
filename.xhtml#f3

Not like this:

filename.xhtml#f2
filename.xhtml#f1
filename.xhtml#f2

Thank you.

Regards,
Babu

Edited by: Babu on Nov 7, 2017 5:40 AM
Legend
Helpful Answer
Correct Answer

Point your RSS reader here for a feed of the latest messages in all forums