View Single Post
Old 04-10-2017, 07:27 PM   #19
odamizu
just an egg
odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.
 
odamizu's Avatar
 
Posts: 1,841
Karma: 8006346
Join Date: Mar 2015
Device: Kindle, iOS
Quote:
Originally Posted by JSWolf View Post
I've done conversions from ePub to KF8 and I've never heard of this issue until this week.
See below from KovidGoyal:

Quote:
Originally Posted by kovidgoyal View Post
This is a long standing issue with kindle firmware. Basically, under some circumstances parts of the text fail to render and you have to go back a page and forward again to work around it.

IIRC this usually happens when an anchor (the destination for a link) is close to/spans an internal text boundary in the MOBI/AZW3 file. MOBI files have the text/markup split up internally into fixed size chunks and the Kindle renderer basically renders one chunk at a time. THere can be issues if yo follow a link/TOC entry that goes to alocation close to the boundary of one of those chunks.

I dont think it is anything in the HTML markup itself that causes this -- however there is no way to be sure of that since we cant see the source code of the kindle renderer
See also this discussion dating back to last November:
https://www.mobileread.com/forums/sh...60#post3434960

Quote:
Originally Posted by JSWolf View Post
Can you post the relevant HTML code along with the relevant CSS?
This has been happening with every book I've read since last November and to other people as well.

The first few times it happened, I scrutinized the HTML/CSS and there's nothing unusual about it. It's just plain, straight text in <p> elements; no graphics or tables or anything else unusual.

Last edited by odamizu; 04-11-2017 at 11:15 PM.
odamizu is offline   Reply With Quote