Quote:
Originally Posted by cybmole
i disagree - with my old sony readers - they would override book css & give a uniform reading experience.. I never needed to know about line-heights CSS or how to tweak it.
Kobo have chosen to let book settings over-ride device seeings - that is a deliberate choice - & personally I call it a bug.
A device that is advertised as " you can adjust..." should do what it says - all the time.
|
Sony and other ereader brands have features to override css code and when enabled, the reader parses some additional code (on the fly) into the html/xml file before it is displayed on the screen. This is what they also do for other device specific features.
This is a good example of a device feature that is taken care off/dealt with on the user-agent itself, and making it software independent (epub).
This is exactly the opposite what Kobo has implemented with its kepub format. Where, to enable device features, code is parsed into the epub itself (software side) while this should have been done on the hardware side.
This is also why books (kepubs) that are displayed incorrectly (empty lines, wrong text alignment, etc.) can not be fixed by a simple firmware update by tweaking the additional parsed code and fix all incorrect books at once.
Kobos implementation requires that all incorrect books must be regenerated individually to fix these kind of errors. Unfortunately, Kobo doesn't do this. Maybe it does for books published in English but for other languages it doesn't and a incorrect book stays incorrect forever.