Quote:
Originally Posted by DrChiper
Prior this thread, I never heard about this option before. You have inside information?
|
No inside information, but in those days we did have @davidfor (R.I.P.) which was almost as good.
See
this post from 2020.
Quote:
Originally Posted by DrChiper
It is also very kobo specific, so you still have to include orphans/widows in the CSS when you use other ereader devices.
|
Yes indeed. Every reading app (eink, Android etc) may have its own widows/orphans "solution". One-size-fits-all is pretty rare for anything CSS-related in my experience.
Personally I don't keep any widows/orphans CSS at all in my calibre master epubs. I auto-apply whatever is needed (if anything) during my send-to-device process.
Quote:
Originally Posted by DrChiper
Seems a correct deduction. However, how did you determined the orphans/widows setting to become "2"? Is this somewhere mentioned?
|
Tedious observation by paging through an epub, after having removed the config settings. A 3-line paragraph was never split across pages. A 4-line paragraph (if split at all) was only ever split 2 and 2.
Quote:
Originally Posted by DrChiper
So summarizing, Kobo CSS evaluation is (according to you):
- kobo hardcoded defaults,
- epub CSS settings,
- kobo config file settings.
in which each level is overriding the previous one.
And: the kobo config file settings only overrides the <body> orphans/widows settings. |
Yes, except for item 1 (kobo hardcoded defaults), because I don't know what you mean by it.