Quote:
Originally Posted by DNSB
Basically, RMSDK/epub handles typography better than the WebKit based renderer/kepub.
[rant mode]
Accurate page counts in a reflowable ebook? 
To me, that is a joke.Even using page maps, you are looking at page counts for a specific physical edition. The only page counts that I've ever found useful was Adobe's synthetic page map algorithm since that gives the same page numbers for the same epub file on any size of device regardless of playing with line spacing, margins, font size, etc.
Page counts that vary with font size, margins, line spacing, line height, etc. are not transferable and so, to me, of no use.
[/rant mode]
Out of a perhaps morbid curiosity, is there a reason that you are modify the font size on your messages? |
Debatable that RMSDK gives better typography. Personally I preferred the Webkit renderer. Last time I checked Kobo's RMSDK version lacked support for things like RTL and vertical writing and MathML which limits utility. It's also just really annoying and confusing frankly to have this dual system based on file extension. They really need to rethink how it's done as naive sideloading can lead to unusable results.
Page counts are only useful in stuff like courses and book clubs.