View Single Post
Old 06-26-2015, 06:13 AM   #2
Doitsu
Grand Sorcerer
Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.
 
Doitsu's Avatar
 
Posts: 5,737
Karma: 24031401
Join Date: Dec 2010
Device: Kindle PW2
Quote:
Originally Posted by GrannyGrump View Post
So is this just a known problem with the azw3 format, or am I doing something wrong in my code?
I've just tested a KindleGen generated .azw3 file of The Wouldbegoods on my PW2 and the xref hyperlink doesn't work with it either. IMHO, this isn't a big deal since most Kindle users are not likely to tap the image anyway.

BTW, for some odd reason, my PW2 displays the chapter body text in a a sans-serif font. However, this is most likely a device-specific bug, because the same page displays fine with the Kindle for Android app.

I'd recommend implementing the following minor cosmetic changes to make your ePubs Kindle-friendly:

1. Mark the cover image in Sigil using Add Semantics > Cover Image.
2. Mark the TOC in Sigil using Add Semantics > Table of Contents.
3. Mark the beginning of the book in Sigil using Add Semantics > Text.

(This will add guide entries for KindleGen to the .opf file; ADE ignores this information.)
Attached Thumbnails
Click image for larger version

Name:	Kindle_Android.png
Views:	221
Size:	58.4 KB
ID:	139642   Click image for larger version

Name:	eInkKindle_PW2.png
Views:	228
Size:	40.9 KB
ID:	139643  
Doitsu is offline   Reply With Quote