View Single Post
Old 06-16-2020, 05:39 PM   #29
MGlitch
Wizard
MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.
 
Posts: 2,857
Karma: 22003124
Join Date: Aug 2014
Device: Kobo Forma, Kobo Sage, Kobo Libra 2
Quote:
Originally Posted by JSWolf View Post
If you had page numbers for the ToC with KePub, it would take a lot more time to update if you changed line height, font size, and/or the font as every time you made a change, the ToC page numbers would have to be updated.

But with RMSDK page numbers in the ToC, that can be done once when the eBook is imported to the database. And from there on, no need to update the page numbers.

Jon, Access already updates the chapter start and stop pages when you make any of those changes, it adjusts instantly. That's why it can display xx of yy for a chapter. Do you really think the maths involved to figure out the new page number for the start of the chapter are so complex that it'd throw the device for a loop?

Becuase, I promise you, they aren't.
MGlitch is offline   Reply With Quote