View Single Post
Old 05-31-2013, 07:37 PM   #17
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,083
Karma: 148029447
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by mattcurtis View Post
Here's what confuses me about that: how does that account for paragraph margin, font-size, etc? I mean, if the font size is large enough, how will the pages number ever map correctly to what the user is seeing? Or do page numbers account for swathes of text? I can't seem to find information that explains it thoroughly, or at least has code that implements it.
I've already told you that the Count Pages Calibre plug-in has the code to do the ADE page count. You groaned that it's in Python. Did you forget that fast? You can look there and see how it's calculated.

ADE's method of pages uses a count of the text in the XML files. It does not matter what the CSS tells the XML how to display or what the user has set the font size to. The XML is a set file. Nothing the CSS does changes that. How it displays does not change the size of the file.
JSWolf is offline   Reply With Quote