View Single Post
Old 12-18-2018, 06:59 PM   #565
jhowell
Grand Sorcerer
jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.
 
jhowell's Avatar
 
Posts: 7,108
Karma: 92190133
Join Date: Nov 2011
Location: Charlottesville, VA
Device: Kindles
Quote:
Originally Posted by Jane Eyre View Post
I love the plugin, but I've got an odd occurance.

This rule in a css of mine:

Code:
p.poem
    {
    text-align: left;
    text-indent: 0em;
    font-style: italic;
    }
And in the xhtml file:

Code:
<p class="poem">blablabla <br />
blablabla<br />
blablabla<br />
blablabla<br />
blablabla</p>
In kfx conversion it works well, but each broken sentence is unexpectedly separeted by unwanted spaces, this way:


blablabla

blablabla

blablabla

blablabla




In azw3 all that does NOT happen.

Any solutions?
I assume that you meant to post this to the KFX Output plugin thread.

It appears that calibre adds the "display:block" property to <br> elements during conversion causing the Kindle Previewer to treat them incorrectly. I have no idea why calibre does this and am still looking into it.

In the mean time you can fix the problem by changing your conversion settings. In the "Look & feel" section under the "Styling" tab enter the following into "Extra CSS":

br {display:inline;}
jhowell is offline   Reply With Quote