View Single Post
Old 04-05-2017, 12:16 AM   #10
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,378
Karma: 27230406
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
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
kovidgoyal is online now   Reply With Quote