Quote:
Originally Posted by davidfor
Sorry Jon, but that is a complete load of BS. It is easy to get the pretty much the same number of characters on the screen at the same apparent font size with kepubs as epubs. There was a difference when the epub reader didn't have the header, but, now both formats can either have it or not, they can both get the same number of characters.
For reference, your justification for more text is based on things like ligatures. If you are using fonts that don't have them, there won't be as much of a difference.
|
If I was to read KePub, I would need a large line height to prevent the first line of the next page being split bug. With ePub, I read with a smaller line height. Even if I didn't have any ligatures, I would still get more text on screen with the same font/font size.
Quote:
|
As to battery life, prove it. You are making the claim, so please prove it. I don't remember anyone claiming this before, so I think you will have to present the testing you are doing.
|
A Reader uses power to change screen pages. With ePub having more text on screen then KePub, you have less page turns with ePub. Less page turns equals less battery usage.
Quote:
|
But, consider this: By not having to handle ligatures and similar, the kepub renderer actually has to do less work. That means less CPU used and hence less battery. Any extra page turns is probably immaterial. If it is saving battery on the rendering, then an extra 1% of page turns is unlikely to be an issue.
|
That depends if ligatures and hyphens are turned on. If I do read KePub, I have ligatures and hyphens on.
I agree that the difference in the amount of page turns between ePub and KePub is not a big deal. I mentioned it in attempts to be more complete.