View Single Post
Old 01-20-2022, 04:43 AM   #7
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by fabianmoreno01 View Post
Thanks folks!

This seems to be a problem with the kepub format, as in epub it displays the page breaks correctly after my initial code injection.

Is there any way to make sure this formatting stays active when converting to kepub?
If the kepub renderer doesn't support it, then it doesn't support it. kepubify will not be removing it. But, if you want to check, simply put the epub on the device and change the extension to ".kepub.epub". Most of what kepubify or the extended driver does is to add spans. They don't remove any CSS.

But, Kobo actually state they don't support them on the devices. See https://github.com/kobolabs/epub-spec and search for page break. They recommend starting a new HTML file if you need a page break.
davidfor is offline   Reply With Quote