View Single Post
Old 08-31-2013, 11:00 AM   #56
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Man Eating Duck View Post
What amazes me is that an (admittedly very clever) guy with a hex-editor can fix long-standing bugs and add basic functionality that should've been in the FW from the start. That indicates that Kobo really don't care about listening to feedback from their customers. Neither do Sony, of course, but their FW is very solid as-is. I understand that Kobo are no longer present (at least not visibly) on these forums either.
Sorry, that isn't what he is doing. What he is doing is hacking at the settings that Kobo has hard-coded into the reader application. Effectively, what he is doing is changing from one set of hard-coded values, to another. If Kobo were to make the same changes, then there would be an equal number of complaint about loss of page heading, footings or whatever. 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.

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.
davidfor is offline   Reply With Quote