Quote:
Originally Posted by franklekens
I'm not sure I understand. I don't want to have to edit CSS for every book I read, I don't even know how to do that. I just want the reader to display a book the way it should be. That means that when there's paragraphs spanning several pages, the reader shouldn't suddenly decide to make one paragraph fill only half a screen.
If there's some CSS setting that causes this (and I wonder which fool ever created *that*), at least the GUI of the reader should have some option to ignore it. (Called, for user friendliness' sake, something like "don't split long paragraphs" or "don't bother about orphans widows".)
When I say the option was created by a fool, by the way, I mean I genuinely don't understand it. Orphans/widows are supposed to be a typographer's nightmare: an orphaned single line at the top of a page, oh no, we should prevent that!
Alright, I get that. Although I don't find it very troublesome myself.
But in this case the remedy is to have pages where the text suddenly stops half page, whereas the author has never intended for there to be even a blank line: as though *that* isn't a typographer's nightmare!
I really don't get it. I don't get why the bug is there, I don't get why nothing is being done about it, and I don't exactly get how I can remedy it myself. (Plus I don't really want to manually edit all my books.)
Guess I'm just clueless.
|
I say this half tongue-in-cheek but perhaps you should try a Kindle which renders a book correctly without the orphans/widows problem and uses the entire display for text. However, there is not the same level of customization and no native epub support but conversions are painless and don't require work.
I do agree with you that the end-user should not have jump through hoops to have an ebook display correctly.
EDIT: Well, never mind. I see you have a Kindle Touch in your profile. I should know better than to post via Tapatalk from a phone.
