Thread: Kobo Firmware 3.5.0
View Single Post
Old 07-17-2014, 05:08 PM   #187
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,432
Karma: 171313058
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by JSWolf View Post
But, that's not for ePub 2. That's for ePub 3 and what I'm editing is an ePub 2 eBook, not an ePub 3 eBook.

Marvin and iBooks do work with Widows and orphans with a value of 0.
CSS Level 3 is not necessarily for ePub 3 only. An ePub 2 ebook used with a CSS 3 aware renderer can make use of some CSS 3 constructs. You might note that iBooks supports such CSS 3 items as animations but then iBooks has never been noted for following standards correctly -- take a look at such items as it's handling of width tags in a img element.

CSS Level 2 uses the same positive integer requirement for widows/orphans. What it does not spell out is what is to be done when an invalid value is detected.

So best practice, in my not so humble opinion, would be to use a value of 1 which will continue working in the future and not 0 which is non-standard and might not work the way you expect in the future.

Regards,
David
DNSB is offline   Reply With Quote