Thread: Troubleshooting Send to Kindle issues and findings
View Single Post
Old 04-27-2023, 06:41 PM   #5
tomsem
Grand Sorcerer
tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.
 
Posts: 6,959
Karma: 27060153
Join Date: Apr 2009
Location: USA
Device: iPhone 15PM, Kindle Scribe, iPad mini 6, PocketBook InkPad Color 3
That said, I'm now getting the same error with another book. Originally ePub (one of Tor's free book of the month). No longer have the source files, and apparently didn't have backup in calibre (this goes back 6 years, before I got serious). I downloaded it to my Kindle, imported it to calibre, converted to ePub3. epubcheck passes, no errors or warnings. But Kindle Previewer 3 throws the 'Hyperlink not resolved in toc' error, and S2K rejects it (probably the same code).

I tried one of the online converters and the result didn't pass epubcheck. Also tried the ^^tool and it made changes, but it broke epubcheck.

So it again comes down to resolving:

Quote:
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/1c/s6n482rn5fs_ls6v8cdnqr5r0000gr/T/0bf4418c-75c0-48fe-a8bf-342aa3c493ac/cTemp/mTemp/mobi-76dTK3/text/part0001.html#UGI0-51bae2eb2418443c8e37a3f2d3286faf
It seems Kindle Create is tripping over toc references that include ID in the url after hash (#).

/text/part0001.html#UGI0-51bae2eb2418443c8e37a3f2d3286fa

I removed the hash and ID (there were two TOC entries in this case), and now Kindle Create and S2K accept it.

All's well that ends well, but it kinda looks like bug in the Kindle Create (and presumably Send to Kindle) validation code.

Can someone explain why a publisher would be using this URL form? Visually it doesn't seem different, or I'm not noticing anything.

Okay, I found the original .ePub and .mobi files from Tor. It seems the hash style is used in the .mobi, but not in the .epub. When I convert .mobi/.azw3 to .epub, it carries over this hash style that Kindle Create doesn't like. But if I convert the original .ePub to epub3 there are no hash style TOC URLs.

I wonder if calibre's conversion to ePub should dispense with carrying over the hash style tags or at least offer option to just leave the hash part off.

In any case, I'll start making use of the original epub (having found them all) rather than downloading to kindle and using that for source for adding to calibre.

Last edited by tomsem; 04-27-2023 at 07:45 PM.
tomsem is offline   Reply With Quote