View Single Post
Old 03-27-2016, 06:37 AM   #41
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,680
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by JSWolf View Post
ADE does this now. It does use 1024 compressed characters = 1 page. B&N uses ADE so they already do this. It's iBooks that cannot do proper page numbers and Kindle that does make believe page numbers (when they bother to do page numbers).
1024 un-compressed characters OF HTML MARKUP. Which helps very little, when the same rendered text can be produced with varying volumes of markup. Consider Kobo's penchant for surrounding everything with extra paragraph spans, and you can quickly see how 1024 characters of a Kobo book will never match 1024 characters of a different vendor's epub. Not to mention style parameters being used inline VS style primarily applied via CSS. Characters VS Entities. No, I'm afraid Adobe's 1024-characters-of-uncompressed-html = 1 "page" doesn't come close to providing a "one unit to rule them all" solution. For a character-count-based solution, nothing short of a rendered character count would suffice (which I'm sure is what Hitch was suggesting).

Last edited by DiapDealer; 03-27-2016 at 12:07 PM.
DiapDealer is offline   Reply With Quote