View Single Post
Old 12-29-2017, 07:58 PM   #78
tiltowait
Zealot
tiltowait considers 'yay' to be a thoroughly cromulent word.tiltowait considers 'yay' to be a thoroughly cromulent word.tiltowait considers 'yay' to be a thoroughly cromulent word.tiltowait considers 'yay' to be a thoroughly cromulent word.tiltowait considers 'yay' to be a thoroughly cromulent word.tiltowait considers 'yay' to be a thoroughly cromulent word.tiltowait considers 'yay' to be a thoroughly cromulent word.tiltowait considers 'yay' to be a thoroughly cromulent word.tiltowait considers 'yay' to be a thoroughly cromulent word.tiltowait considers 'yay' to be a thoroughly cromulent word.tiltowait considers 'yay' to be a thoroughly cromulent word.
 
Posts: 113
Karma: 89990
Join Date: Jun 2017
Device: Kobo Aura One
Quote:
Originally Posted by ZodWallop View Post
One weird thing: The text in your Nook picture looked gritty and jagged. I'm pretty sure that's just from the picture as I haven't seen the same on my actual GL3.

Wolf should be here in about thirty seconds to tell you the Nooks are garbage at rendering fonts.

Was the Kobo book ePub or kepub?

Assuming the book was kepub (and you have more time than you know what to do with) it might be interesting to upload the same book as an ePub on both devices and compare the fonts. Kobo uses different engines for kepub vs. ePub and fonts are rendered differently. I'm not sure which renders the fonts more accurately though.
Pretty sure that was just an issue of the photograph; I haven't noticed that in actual reading. And ... yeah, I did check how Georgia looks in a regular ePub, and both renderers have it skinnier than the Nook (and skinnier than the font preview in the picker, incidentally).

Quote:
Originally Posted by JSWolf View Post
RMSDK (ADE) displays pages as 1024 compressed bytes. So whatever that uncompresses to is a page. This means that when you change the font, the font size, the line hight, the margins, or hyphenation on or off, the page number does not change. It remains the same. There's nothing wrong or phony about that.

Counting screens is not accurate ad does change when you change any of the above listed settings. Those page numbers are wrong and are phony.

ADE style page numbers can be cited. Number of screens cannot.
I don't know about you, but I find an appropriate font size and stick with it. I don't change it around, and I've never once cited an eBook. If nothing else, an option would be nice.

One problem with RMSDK's algorithm is that it makes effective page sizes inconsistent. A book I finished yesterday has shorter pages than the book I'm currently reading due to some difference in the underlying HTML. This inconsistency between books makes it harder to judge just how long a page is and, thus, how long a chapter is. Pages as screens avoids this issue.

If nothing else, it would be nice to have an option, like Kobo has.
tiltowait is offline   Reply With Quote