01-16-2015, 03:17 PM
|
#16 | |
|
Member
 Posts: 13
Karma: 10
Join Date: Nov 2011
Device: Kindle
|
Quote:
First I was hoping there was just something obvious people would see that I'm not. But this appears to be a thing they will just have to fix. The entire content.opf is below: Code:
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<package xmlns="http://www.idpf.org/2007/opf" unique-identifier="PrimaryID" version="2.0">
<metadata xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:opf="http://www.idpf.org/2007/opf">
<dc:identifier id="PrimaryID">urn:isbn: 9781483543888</dc:identifier>
<dc:title>3 Poetry Books in 1, vol III</dc:title>
<dc:language>en-US</dc:language>
<dc:creator opf:file-as="Fernandez-Reyes, Ynez" opf:role="aut">Ynez Fernandez-Reyes</dc:creator>
<dc:date opf:event="publication">2014-01-01</dc:date>
<meta content="MyCoverimage" name="cover" />
<meta content="0.7.4" name="Sigil version" />
<dc:date opf:event="modification">2015-01-15</dc:date>
</metadata>
<manifest>
<item href="toc.ncx" id="ncx" media-type="application/x-dtbncx+xml" />
<item href="Styles/stylesheet.css" id="css" media-type="text/css" />
<item href="Text/cover.xhtml" id="cover" media-type="application/xhtml+xml" />
<item href="Text/title.xhtml" id="title" media-type="application/xhtml+xml" />
<item href="Text/copy.xhtml" id="copy" media-type="application/xhtml+xml" />
<item href="Text/fm.xhtml" id="fm" media-type="application/xhtml+xml" />
<item href="Text/book01.xhtml" id="book01" media-type="application/xhtml+xml" />
<item href="Text/toc.xhtml" id="toc" media-type="application/xhtml+xml" />
<item href="Text/chap01.xhtml" id="chap01" media-type="application/xhtml+xml" />
<item href="Text/chap02.xhtml" id="chap02" media-type="application/xhtml+xml" />
<item href="Text/chap03.xhtml" id="chap03" media-type="application/xhtml+xml" />
<item href="Text/chap04.xhtml" id="chap04" media-type="application/xhtml+xml" />
<item href="Text/chap05.xhtml" id="chap05" media-type="application/xhtml+xml" />
<item href="Text/chap06.xhtml" id="chap06" media-type="application/xhtml+xml" />
<item href="Text/chap07.xhtml" id="chap07" media-type="application/xhtml+xml" />
<item href="Text/chap08.xhtml" id="chap08" media-type="application/xhtml+xml" />
<item href="Text/chap09.xhtml" id="chap09" media-type="application/xhtml+xml" />
<item href="Text/chap10.xhtml" id="chap10" media-type="application/xhtml+xml" />
<item href="Text/book02.xhtml" id="book02" media-type="application/xhtml+xml" />
<item href="Text/toc01.xhtml" id="toc01" media-type="application/xhtml+xml" />
<item href="Text/chapp01.xhtml" id="chapp01" media-type="application/xhtml+xml" />
<item href="Text/chapp02.xhtml" id="chapp02" media-type="application/xhtml+xml" />
<item href="Text/chapp03.xhtml" id="chapp03" media-type="application/xhtml+xml" />
<item href="Text/chapp04.xhtml" id="chapp04" media-type="application/xhtml+xml" />
<item href="Text/chapp05.xhtml" id="chapp05" media-type="application/xhtml+xml" />
<item href="Text/chapp06.xhtml" id="chapp06" media-type="application/xhtml+xml" />
<item href="Text/chapp07.xhtml" id="chapp07" media-type="application/xhtml+xml" />
<item href="Text/chapp08.xhtml" id="chapp08" media-type="application/xhtml+xml" />
<item href="Text/chapp09.xhtml" id="chapp09" media-type="application/xhtml+xml" />
<item href="Text/chapp10.xhtml" id="chapp10" media-type="application/xhtml+xml" />
<item href="Text/fm1.xhtml" id="fm1" media-type="application/xhtml+xml" />
<item href="Text/book03.xhtml" id="book03" media-type="application/xhtml+xml" />
<item href="Text/toc02.xhtml" id="toc02" media-type="application/xhtml+xml" />
<item href="Text/chappp01.xhtml" id="chappp01" media-type="application/xhtml+xml" />
<item href="Text/chappp02.xhtml" id="chappp02" media-type="application/xhtml+xml" />
<item href="Text/chappp03.xhtml" id="chappp03" media-type="application/xhtml+xml" />
<item href="Text/chappp04.xhtml" id="chappp04" media-type="application/xhtml+xml" />
<item href="Text/chappp05.xhtml" id="chappp05" media-type="application/xhtml+xml" />
<item href="Text/chappp06.xhtml" id="chappp06" media-type="application/xhtml+xml" />
<item href="Text/chappp07.xhtml" id="chappp07" media-type="application/xhtml+xml" />
<item href="Text/chappp08.xhtml" id="chappp08" media-type="application/xhtml+xml" />
<item href="Text/chappp09.xhtml" id="chappp09" media-type="application/xhtml+xml" />
<item href="Text/chappp10.xhtml" id="chappp10" media-type="application/xhtml+xml" />
<item href="Text/aut.xhtml" id="aut" media-type="application/xhtml+xml" />
<item href="Images/cover.jpg" id="MyCoverimage" media-type="image/jpeg" />
<item href="Images/img.jpg" id="img" media-type="image/jpeg" />
<item href="Images/img1.jpg" id="img1" media-type="image/jpeg" />
<item href="Images/img2.jpg" id="img2" media-type="image/jpeg" />
<item href="Images/img3.jpg" id="img3" media-type="image/jpeg" />
<item href="Images/title.jpg" id="title.jpg" media-type="image/jpeg" />
</manifest>
<spine toc="ncx">
<itemref idref="cover" linear="yes" />
<itemref idref="title" linear="yes" />
<itemref idref="copy" linear="yes" />
<itemref idref="fm" linear="yes" />
<itemref idref="book01" linear="yes" />
<itemref idref="toc" linear="yes" />
<itemref idref="chap01" linear="yes" />
<itemref idref="chap02" linear="yes" />
<itemref idref="chap03" linear="yes" />
<itemref idref="chap04" linear="yes" />
<itemref idref="chap05" linear="yes" />
<itemref idref="chap06" linear="yes" />
<itemref idref="chap07" linear="yes" />
<itemref idref="chap08" linear="yes" />
<itemref idref="chap09" linear="yes" />
<itemref idref="chap10" linear="yes" />
<itemref idref="book02" linear="yes" />
<itemref idref="toc01" linear="yes" />
<itemref idref="chapp01" linear="yes" />
<itemref idref="chapp02" linear="yes" />
<itemref idref="chapp03" linear="yes" />
<itemref idref="chapp04" linear="yes" />
<itemref idref="chapp05" linear="yes" />
<itemref idref="chapp06" linear="yes" />
<itemref idref="chapp07" linear="yes" />
<itemref idref="chapp08" linear="yes" />
<itemref idref="chapp09" linear="yes" />
<itemref idref="chapp10" linear="yes" />
<itemref idref="fm1" linear="yes" />
<itemref idref="book03" linear="yes" />
<itemref idref="toc02" linear="yes" />
<itemref idref="chappp01" linear="yes" />
<itemref idref="chappp02" linear="yes" />
<itemref idref="chappp03" linear="yes" />
<itemref idref="chappp04" linear="yes" />
<itemref idref="chappp05" linear="yes" />
<itemref idref="chappp06" linear="yes" />
<itemref idref="chappp07" linear="yes" />
<itemref idref="chappp08" linear="yes" />
<itemref idref="chappp09" linear="yes" />
<itemref idref="chappp10" linear="yes" />
<itemref idref="aut" linear="yes" />
</spine>
<guide>
<reference href="Text/cover.xhtml" title="Cover Page" type="cover" />
<reference href="Text/toc.xhtml" title="Contents" type="toc" />
</guide>
</package>
|
|
|
|
|
01-16-2015, 03:21 PM
|
#17 |
|
Grand Sorcerer
 
Posts: 12,166
Karma: 73448616
Join Date: Nov 2007
Location: Toronto
Device: Nexus 7, Clara, Touch, Tolino EPOS
|
Any chance you could actually supply a book showing this error? Maybe replace all the text by Lorem Ipsum text...
|
|
|
|
| Advert | |
|
|
|
01-16-2015, 04:06 PM
|
#18 | ||
|
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
Quote:
I'm with Pete: can you lorem ipsum us these books? Or a sample? I realize you'd have to lorem ipsume them all, but we'd only need one paragraph of lorem per section to enable us to work it... Hitch |
||
|
|
|
|
01-20-2015, 12:21 PM
|
#19 |
|
Member
Posts: 13
Karma: 10
Join Date: Nov 2011
Device: Kindle
|
Ok, well the issue was solved. And yes, it was obvious.
Calibre appears to avoid this issue, but basically the TOC order didn't match the spine order. I wasn't aware this was an issue to be honest. Thanks all! |
|
|
|
|
01-20-2015, 01:49 PM
|
#20 | |
|
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
Hitch |
|
|
|
|
| Advert | |
|
|
|
01-20-2015, 04:07 PM
|
#21 |
|
Member
Posts: 13
Karma: 10
Join Date: Nov 2011
Device: Kindle
|
The order of the TOC.NCX didn't match the order of the spine. I've verified this with other books with more blantantly obvious examples. The TOC.html doesn't matter it seems.
One being a book which decided to link a chapter that was in the back of the book, long before it totally out of order (the TOC.NCX was created based on the source document) On top of that, I think Calibre just ignores this error and makes the MOBI anyway. But when you submit that mobi to KDP, KDP does not accept it. It would appear if you want a proper mobi to be submitted to amazon, the spine needs to be in order with the TOC. I honestly didn't know this was a thing until now. It answers a lot of "why this mobi won't be accepted" questions. The TOC.NCX isn't used in Kindle devices that are common, but it IS used in some of the apps for other devices. |
|
|
|
|
01-20-2015, 04:49 PM
|
#22 | |
|
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
Honestly, if I had known that your spine and the NCX were out of sequence, I would have told you that that was the problem. When you said, TOC, I thought you meant the TOC. Sorry about that. That really has almost nothing to do with the "Amazon won't accept..." error, because most people don't have the wherewithal to make a book in which the spine and the NCX aren't in the same order. The vast majority of those rejections are either a) Calibre bookmaking or b) simple incompetence, the usual errors. I don't think we ever saw the NCX, did we? I'm glad it is resolved for you. Hitch |
|
|
|
|
|
01-20-2015, 04:55 PM
|
#23 |
|
Member
Posts: 13
Karma: 10
Join Date: Nov 2011
Device: Kindle
|
Well I just fixed a book that was horribly out of order, which was not convertible by Kindlegen, but was convertible by Calibre, just not acceptable by KDP.
I just fix that EPUB and re-converted in both formats. The kindlegen converts successfully, and Calibre converts AND is accepted by KDP. So based on that, the TOC.NCX being in order of the spine is something that is required for KDP. |
|
|
|
|
01-20-2015, 05:34 PM
|
#24 | |
|
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
If you are making a MOBI only, generally, yes, it will be accepted. It seems to be the KF8 versions that have an exceedingly high failure rate. The older, KF7-format seems to go through without huge issues. And, sure: Calibre doesn't care about that. It's not checking your work, vis-a-vis NCX versus Spine. Hitch |
|
|
|
|
|
01-20-2015, 05:43 PM
|
#25 |
|
Member
Posts: 13
Karma: 10
Join Date: Nov 2011
Device: Kindle
|
I don't think there is a correlation with versions of Kindlegen (KF7/8). I think it's a correlation with Amazon itself, and the devices that are out. This wasn't an issue until Amazon changed a few things.
I just didn't know it was due to the TOC/spine error because they tell you nothing. |
|
|
|
|
08-21-2016, 08:32 AM
|
#26 |
|
Member
Posts: 86
Karma: 12586
Join Date: Nov 2012
Device: Ipad and Kindle Fire
|
TOC section scope is not included in the parent chapter
I received this error message when converting a verified ePub file with Kindlegen (I still can't get KindlePreviewer to work on my iMac). It mentioned the parent chapter's file name, which was not the chapter containing the doc. I then used www.online-convert.com, and it worked fine. I had converted an earlier version of this file with Kindle Previewer (when it was working) and there had been no problem. Don't know what the issue was with Kindlegen.
|
|
|
|
|
08-21-2016, 09:11 AM
|
#27 | |
|
Resident Curmudgeon
Posts: 73,966
Karma: 128903250
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
|
|
|
|
|
|
08-30-2016, 07:08 AM
|
#28 |
|
Member
Posts: 86
Karma: 12586
Join Date: Nov 2012
Device: Ipad and Kindle Fire
|
'TOC scope error when using Kindlegen'
I received this error message when using KINDLEGEN with a validated EPUB file. Having read online that this could be caused by there being more than two levels in the NCX, which may confuse KindleGen. I tried simplifying the NCX, without solving the problem. I then removed the extra levels in the toc.html file, so there was only one level. I could then generate a MOBI file with Kindlegen without errors. |
|
|
|
|
08-30-2016, 09:04 AM
|
#29 |
|
Grand Sorcerer
Posts: 6,496
Karma: 84420419
Join Date: Nov 2011
Location: Tampa Bay, Florida
Device: Kindles
|
I have seen this error occur when there are multiple levels of TOC nesting and the order of links in the TOC does not match the order of the targets within the book's structure. Specifically in cases where there links to different id's in the same html file that are not all sequential within the TOC or the TOC has entries with links to other html files between them.
Last edited by jhowell; 08-30-2016 at 09:23 AM. |
|
|
|
|
06-27-2023, 01:30 AM
|
#30 |
|
Connoisseur
Posts: 57
Karma: 2378
Join Date: Jul 2018
Location: CA, USA.
Device: Kindle Paperwhite Signature Edition and Samsung 10.1 tablet
|
if you use calibre and get that TOC scope error from converting epub to KFX, I was able to fix it simple by converting the epub file or an azw3 file to HTMLZ format in calibre, then from the HTMLZ to KFX it seems to work and not get the TOC Scope error, that the easiest way I was able to fix it, since KFX output plugin uses kindle previewer 3 which also uses Kindlegen within kindle previewer 3 to make KFX DRM free based ebooks from my public domain ebooks from project Gutenberg website, in any case its sort of related to that TOC error that both software has kindle previewer 3 and kindlegen with a few ebooks I don't see the problem much, but I found that ZIP output format doesn't look right to KFX or azw3 but if you take either azw3 or epub to kfx without first converting it to HTMLZ format for ones that get this error, it does seem to fix it for one ebook, in any case if that information helps, I wanted to share it. if your using your ebooks with calibre 64bit - E-book management, which I use for my kindle paperwhite device.
|
|
|
|
 |
«
Previous Thread
|
Next Thread
»
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| KindleGen error message: E1003 Unknown error in class String. | Doitsu | Kindle Formats | 1 | 06-25-2014 12:29 PM |
| toc.ncx okay in calibre, missing after kindlegen...? | GeoffRussell | Kindle Formats | 2 | 01-31-2014 04:10 PM |
| Creating an HTML TOC for kindlegen | MrB | Kindle Formats | 2 | 10-28-2012 02:53 PM |
| kindlegen epub to mobi - TOC intention level incorrect | vogella | Kindle Formats | 3 | 11-04-2011 04:02 AM |
| Troubleshooting TOC fails in Kindlegen 1.1, not Kindlegen 1.0 | cyberbaffled | Amazon Kindle | 3 | 12-25-2010 05:21 PM |
All times are GMT -4. The time now is 11:42 AM.