Quote:
Originally Posted by JSWolf
The idea is not to try to emulate a Kindle, but to show the Kobo in the best light.
|
When a review compares two devices side by side, the idea is to compare. It's a comparison. If the fact of a wide footer/statusbar on the Kobo as compared to the Kindle caught the reviewer's attention and he deems it noteworthy, then there's no reason to blame him for mentioning the fact. The more facts the better.
In my view, it's a fair plan: Set the fonts visually to the same size and see how much more text the bigger screen can fit - dang! it cannot! This
is noteworthy. And in this case the reviewer makes no big deal of it, he passes over it quickly, says there are patches to fix this and moves on. There's no bias there.
Quote:
Originally Posted by JSWolf
You don't need to disable the CSS.
|
Of course, I completely agree. Until you need to.
If you like things styled for you, good for you. My strong preference happens to be the opposite. I am old enough to already have eyesight issues, so by now I forcefully apply my own styles everywhere in ebooks and all over the web (a text-mode webbrowser in a terminal emulator is best for that), until I run into indigestible markup that displays the way the designer meant it only in Chrome or the like. Or until I encounter an ebook whose inbuilt styles are truly gorgeous - this happens also, and I am actually looking forward to it, so I habitually test ebooks both ways before starting reading.
But as far as possible, all fonts and colors and styles everywhere must be possible to be set my way. It's a basic user-friendliness issue that happens to be in good line with accessibility. There is no argument against this.