Quote:
Originally Posted by arspr
(Of course this happens because Kobo wants... Kobo uses a database in order to store a lot of settings of the books. So they could have perfectly coded a background process in order to render the whole book once, and then annotate that number of page turns in the database... But they hadn't... They've gone the easy way...)
Nevertheless, take in mind that some people actually prefer an absolute page numbering system and others a relative one...
|
Actually, they would have to re-render the entire book if you made any changes in line spacing, font size or margins. Hmmm, with 24 font sizes, 15 line spacings and 9 margin settings, your background process would have to render the book 3240 times. For added joy, we will watch the database size grow exponentially. "That way lies madness; let me shun that". WS
Personally, I prefer the Adobe synthetic page numbers since I can read to page 134 on my H20, continue from there on my iPad or Nexus 7, switch back to the H2O at page 214 and the page numbers match up. Using a page per screen line numbering system, I would have to do a search in the book for a phrase near the page I was last reading and I find remembering a number as just being easier for me.