@Katsunami,
If I may I'd like to respond to this statement you reported in the 'Kobo Aura One owners thread'. It's probably more technically detailed than the general readers of that thread want to hear about with their new toys.
Quote:
|
edit: an orphans/widows addition completely destroys the rendering of the EPUBs I've tested.
|
Would I be correct in thinking that you are using the 'Modify CSS' option in the KoboTouch/KoboTouchExtended drivers to add the following to the kobo_extra.css file?
Code:
body { widows: 0 !important; orphans: 0 !important; }
If so, your main problem probably isn't that you've used 0 rather than 1 (although 1 is more correct, I think), it's that you've included those
!important. I haven't figured out why the combo of !important and enabling 'Modify CSS' is so destructive, but it is. I first noticed it
a few years ago. Since then I haven't allowed !important to remain in any of my epub css files and I don't use it in kobo_extra.css either. I haven't had a problem with standard epubs since.
For your extra info, you may not be aware that widows, orphans and @page statements are treated as special cases by the calibre drivers if you include new statements for them in kobo_extra.css. All existing widows/orphans/@page CSS code in your epubs will be completely removed before appending your new values. So !important wouldn't achieve anything anyway.
ETA: In case I haven't been clear, all the above refers to dealing with standard epubs not kepubs.