still fussing with bad formatting

[lumpynose]

I think my current and hopefully remaining problem is caused by a bug in how the kindle displays an azw3. The epub has blank lines between lines of text in a paragraph, i.e., two line feeds/newlines between lines between the opening and closing p tags. When I look at the azw3 on the kindle that calibre produced it starts a new line where the blank lines are (and doesn't display a blank line). Calibre left the blank lines when it converted to azw3.

If I change calibre's conversion settings to use justify instead of left align then the kindle displays it properly. But I'm fussy and can't abide justified text.

I can fix the epub with sigil's mend and prettify, so I have a solution to the problem.

Is this a bug in the kindle? Seems like it is to me but I'm no expert on this stuff.

[theducks]

Originally Posted by lumpynose

I think my current and hopefully remaining problem is caused by a bug in how the kindle displays an azw3. The epub has blank lines between lines of text in a paragraph, i.e., two line feeds/newlines between lines between the opening and closing p tags. When I look at the azw3 on the kindle that calibre produced it starts a new line where the blank lines are (and doesn't display a blank line). Calibre left the blank lines when it converted to azw3.

If I change calibre's conversion settings to use justify instead of left align then the kindle displays it properly. But I'm fussy and can't abide justified text.

I can fix the epub with sigil's mend and prettify, so I have a solution to the problem.

Is this a bug in the kindle? Seems like it is to me but I'm no expert on this stuff.

CODE VIEW BLANK LINES BETWEEN TAG PAIRS, HAS NO EFFECT ON RENDERING. 5 blanks is the same as none when between </p> and the next <p
I have reformatted hundreds of AZW3 books for my K4nt and the only issue I have found affects dropcaps position vs other kindle versions.
Your CSS code is bad (for what you want)

[retiredbiker]

As theducks said, "Your CSS code is bad (for what you want)"

Since you are in code view anyway, have a look at the paragraph coding and the stylesheet.

Look at the <p class="something"> of the paragraphs that don't space the way you want them to. Open the CSS file and find the ".something" entry--does it have any top or bottom margin?

Since you seem to want some whitespace between paragraphs, try adding a line like "margin-bottom: 1em;" to the CSS entry, and see what happens.

BTW, If you have the Live CSS pane open (it's in the View menu), you can click on text in the code pane and it will show you any and all codes that go into the final display. Then you can click on one of the entries and go right to editing the CSS file in that exact spot. Bit of a bear to get used to, but super helpful once you do.

[lumpynose]

Originally Posted by retiredbiker

As theducks said, "Your CSS code is bad (for what you want)"

Since you seem to want some whitespace between paragraphs, try adding a line like "margin-bottom: 1em;" to the CSS entry, and see what happens.

Nah, I don't want any whitespace between paragraphs. I had that idea beaten out of me way back when I was using something called TeX and now I'm just as zealous about it.

In my conversion settings I've checked "Remove spacing between paragraphs". And the one for inserting blank lines is unchecked. Under Look & Feel, Styling, "you want completely removed" I have the following checked: Margins, Padding, Floats, and Colors.

I absolutely agree with theducks that those blank lines between the p tags shouldn't have changed the way it was rendered on the kindle but for whatever reason it seems that they did. The only change I made between the working and non-working version was in Look and Feel, Text, setting the justification to Justify Text, from my usual Left Align. After running Sigil's mend and prettify on it (which removed the blank lines) I changed it back to Left Align and it was ok again.

All day today I've been going through my books and running Sigil's mend and prettify on the epub files and of course I've forgotten which one was misbehaving. I would like to have eyeballed its css.