Quote:
Originally Posted by JSWolf
Sorry, but that's not correct. Tolino has RMSDK and the CSS code I posted for a pagebreak does work.
The other thing that works in the other renderer is to split the HTML file where the page break is wanted.
|
I was referring to hyphenation. But I have to admit the hyphenation options are not
entirely useless. Hyphenation does work on the device, but only when soft hyphens are set in the text (I don't think I have any books with soft hyphens, though.) Apparently the Shine 5 doesn't have hyphenation dictionaries.
Many users complain about this, as Tolino is mainly distributed in Germany and German tends to use long compound words. It's important here.
When soft hyphens are set, hyphenation is activated by default. For the default renderer you can deactivate them with "hyphens", while RMSDK uses "adobe-hyphenate".
About pagebreaks: Most users will never use RMSDK. The device opens all Epubs with the default renderer unless RMSDK is activated in the developer menu or config file.
Spltting up html files for every page break sure feels like a giant step backwards.
Do webkit column breaks work for pagebreaks in the Kobo kepub renderer?
While RMSDK is really old and outdated, the overall user experience is currently much better than the default renderer's.
It opens books almost instantly, letter spacing is much better, setting the font weight works, page breaks work, embedded fonts work, the left-align/justify buttons only apply to the style set for the body tag so it doesn't mess with headings...
The default renderer on the other hand has a couple of useful modern features like support for pseudo classes and I can even make mirrored text work instead of having to rely on images. But more importantly it supports LCP DRM, which is what the public libraries here use. This is the only reason why I
need the default renderer to work properly.