Vertical whitespace in FBReader?
Ron Hale-Evans
New to the group. I love FBReader. I use it on my Zaurus and plan to
use it on my OLPC XO when I get that shortly.
I have just one problem: FBReader seems to strip out almost all
vertical whitespace. While reading an anthology, I expect to see at
least a line's worth of vertical spacing between stories, or between
chapters in a novel. Often an author inserts vertical whitespace to
indicate a change of scene. In all these cases, FBReader gives me at
most interline or interparagraph spacing, which is inadequate for the
purpose and confusing.
Sorry to blather. I really like FBReader. Surely this is a known bug,
or can be fixed with the right configuration, but googling and poking
around the FBReader preferences has turned up nothing for me. Can
anyone help?
Kudos to the FBReader team in every other respect! :-)
Cheers,
Ron H-E
--
Ron Hale-Evans ... rw...@ludism.org ... http://ron.ludism.org/
Mind Performance Hacks book: http://www.oreilly.com/catalog/mindperfhks/
Center for Ludic Synergy: http://www.ludism.org/
(revilous life proving aye the death of ronaldses when winpower wine has
bucked the kick on poor won man)
Marius Gedminas
> I have just one problem: FBReader seems to strip out almost all
> vertical whitespace. While reading an anthology, I expect to see at
> least a line's worth of vertical spacing between stories, or between
> chapters in a novel. Often an author inserts vertical whitespace to
> indicate a change of scene. In all these cases, FBReader gives me at
> most interline or interparagraph spacing, which is inadequate for the
> purpose and confusing.
I second this. FBReader keeps the empty paragraphs (the interparagraph
spacing is doubled wherever the book has one), but doesn't render any
vertical space there. Previously I used to edit my books and put a
single nonbreaking space in there to get some vertical spacing, but I
think I noticed newer versions of FBReader stripping those too.
Marius Gedminas
--
I have yet to see any problem, however complicated, which, when
you looked at it in the right way, did not become still more complicated.
-- Poul Anderson
AlanW
http://www.webscription.net/p-352-ring-of-fire.aspx is a collection of
short stories. Both the PRC and the LIT (OEB) versions have a table
of contents, but each story does not start on a new page. However, if
074347175X__p_.htm from the exploded LIT is used (instead of
Ring_of_Fire.opf) the TOC has some extra entries but each story now
starts on a new page. MobiPocket Reader (on the PRC version) starts
each story on a new page.
Nicolas BRICHE
> I second this. FBReader keeps the empty paragraphs (the interparagraph
> spacing is doubled wherever the book has one), but doesn't render any
> vertical space there. Previously I used to edit my books and put a
> single nonbreaking space in there to get some vertical spacing, but I
> think I noticed newer versions of FBReader stripping those too.
And I third this. I've opened bug #56 for this, but I may have
misclassed it as a feature request.
I usually replace empty paragraphs with "***", but that's not an elegant
solution even if it works. It's also breaking formatting on special
cases (double-empties, etc.).
Properly rendering empty paragraphs and the HR element would be a Good
Thing. Maybe also allowing to set up spacing before/after those, too.
N.
Marius Gedminas
That's unrelated. When you have a heading in your text (e.g.
<h1>text</h1> in a .LIT file), you get the page break. When you simply
have some bold text (e.g. <p><b>text</b></p>), you don't get a page
break.
We're talking about empty paragraphs in the middle of a single chapter,
e.g.
<h1>Story about chickens</h1>
<p>Chicken chicken chicken.</p>
<p></p>
<p>Chicken chicken.</p>
Marius Gedminas
--
C++ is a loaded machine gun helpfully pointed at your feet with the safety off.
-- ChaosDiscord on Slashdot
AlanW
> That's unrelated. When you have a heading in your text (e.g.
> <h1>text</h1> in a .LIT file), you get the page break. When you simply
> have some bold text (e.g. <p><b>text</b></p>), you don't get a page
> break.
exploded LIT is opened from the HTML file or the OPF file (which
points to the HTML file). So it can't be <h1>text</h1> vs
<p><b>text</b></p> that causes the different behavior in the two
cases. I think the PRC version will contain essentially the same HTML
content too, although I have not confirmed this.
Ron Hale-Evans
simple newlines instead of HTML tags.
Thanks for everyone's help so far. Thanks for opening the bug, Nicholas.
--