![]() I originally assumed it was similar to the Adobe algorithm. ![]() Have you ever been able to delve deep enough into the firmware to find out more? I'd really like to know what algorithm Kobo use. Not consistent with other eink brands or 3rd-party Android reading apps, though, where the Adobe page count is the only real contender for epubs. I noted this in one textbook where the 7th reprint was re-typeset, the illustrations were redone and various errata corrected resulting in a book with 11 fewer pages. Even if you stick to hardcover only, the page numbers are not necessarily consistent. If you are worrying about matching page numbers to a print edition, we'd have to ask which print edition as the page numbering will vary from hardcover to trade paperback to paperback. ![]() The Adobe synthetic page algorithm has at least the virtue of being consistent across devices. However worrying about page numbers in a reflowable format where the amount of data on the screen can and does vary widely with font size, line and paragraph spacing, margins, etc. How do I fix it in Calibre?īasically, for epubs you would need to generate Adobe's non-standard and poorly supported page-map or the standard and poorly supported pagelist. Have a tip to share? Experience converting books? Let’s hear about it in the comments.Thanks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |