epub -> azw3 conversion resulting in blank spaces where text belongs

[JSWolf]

Can you post the relevant HTML code along with the relevant CSS?

[BetterRed]

Originally Posted by JSWolf

Can you post the relevant HTML code along with the relevant CSS?

Or post a version that's had its text obfuscated by the ScrambleEbook optional plugin

Then you won't have to read JSWolf's mind as what he regards as relevant or otherwise

BR

[JSWolf]

Originally Posted by BetterRed

Or post a version that's had its text obfuscated by the ScrambleEbook optional plugin

Then you won't have to read JSWolf's mind as what he regards as relevant or otherwise.

BR

I've done conversions from ePub to KF8 and I've never heard of this issue until this week.

[odamizu]

Originally Posted by JSWolf

I've done conversions from ePub to KF8 and I've never heard of this issue until this week.

See below from KovidGoyal:

Originally Posted by kovidgoyal

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

Originally Posted by JSWolf

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.

[genoasalami]

I've converted a book from ePub to mobi (instead of AZW) in Calibre and -- so far -- the blank space issue hasn't happened. On the other hand, for some reason, the book isn't searchable. At this point.... **sigh**

[JSWolf]

Originally Posted by odamizu

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.

But what about the CSS for <p> and body and any other CES that has an effect of that paragraphs and page?

[odamizu]

Originally Posted by JSWolf

But what about the CSS for <p> and body and any other CES that has an effect of that paragraphs and page?

body { text-align: left; font-size: 150%; }

p { text-align: left; }

p.Body-Text { margin-bottom: 0; margin-top: 0; text-indent: 1em; }

P.S. The above is just my latest book. The "missing text" bug has happened with every book I've read since last fall. Obviously, the CSS varies from book to book.

[theducks]

I have had paragraph text that gets misinterpreted to be a HTML comment during conversion

<!--

Is there code, and it is just not visible in the viewer?

[odamizu]

Originally Posted by theducks

I have had paragraph text that gets misinterpreted to be a HTML comment during conversion

<!--

Is there code, and it is just not visible in the viewer?

Interesting! But no, there is nothing commented out.

At this point I do think it's a software bug in the Kindle software and not related to HTML/CSS.

(Though if anyone has any other ideas I'm willing to check.)