Quote:
Originally Posted by davidfor
What is really desired is options built into the reader application to turn these things on and off. Adding those is not as easy as it might seem.
|
Sure, but it is still something that should be done by a customer-oriented hardware maker as long as it is of importance to users. If this is very hard to do, it seems that Kobo should have designed those parts of their UI to be more flexible (the hacks themselves modify css, it appears, so adding options to modify those values shouldn't be impossible), but that should be of no concern for the users.
Quote:
Originally Posted by davidfor
The fix for the long-paragraph bug is something else. It solves that problem, but it apparently breaks the widows/orphans handling. I assume the fix he has implemented is to replace a page feed character with a non-display character that doesn't cause a page feed. While it solves the problem for most people, it isn't a real fix. It definitely isn't something that should be put into the applications code base.
|
Yes, that sounds like a hack-ish workaround all right
Still, same thing goes. This appears to be a serious bug in their display engine, and should be fixed as such. As a (probable) customer I don't really care about the difficulty of fixing the bug, but I find it hard to believe that it can't be done. What also worries me as a potential customer is that they haven't actually fixed it by now.