Nickelmenu on 5.x firmware

[rantanplan]

I’ll definitely try to manually set the line height to 1.5, like the gods intended.

[JSWolf]

Originally Posted by rantanplan

I’ll definitely try to manually set the line height to 1.5, like the gods intended.

Set the line height manually in the config to something lower like 0.9 so we can see that it works. 1.5 doesn't work (even if it works).

[Falkor]

Originally Posted by Falkor

Notable omissions:

• initial-letter

Now I know why they don't support this: This features was added to QT Web Engine in version 6.6. Kobo is still running 6.5.

[JSWolf]

Initial-letter is something I wish would go away. It's just annoying.

[Falkor]

Why? People are gonna use drop cops with or without support for initial-letter.
The workarounds for dropcaps without initial-letter never work properly, so it would be better if it were widely supported.

[JSWolf]

Originally Posted by Falkor

Why? People are gonna use drop cops with or without support for initial-letter.
The workarounds for dropcaps without initial-letter never work properly, so it would be better if it were widely supported.

But it's not widely supported and it's not ePub2 compatible. So you have to do it in CSS and as you said, it doesn't work

[Falkor]

Originally Posted by JSWolf

But it's not widely supported and it's not ePub2 compatible. So you have to do it in CSS and as you said, it doesn't work

There is no compatibility problem here. If the renderer doesn't support it, it will not cause any issues.

The feature is widely supported, just not on reading devices. Thorium, Apple Books, Calibre and Adobe Digital Editions handle it just fine. All major browsers support it. But apparently Kobo/Tolino can't keep its firmware up to date.

[JSWolf]

Originally Posted by Falkor

There is no compatibility problem here. If the renderer doesn't support it, it will not cause any issues.

The feature is widely supported, just not on reading devices. Thorium, Apple Books, Calibre and Adobe Digital Editions handle it just fine. All major browsers support it. But apparently Kobo/Tolino can't keep its firmware up to date.

When you say ADE, you have to say what versions as there are versions that don't use it such as the version of RMSDK that Kobo uses.

[DNSB]

Originally Posted by JSWolf

When you say ADE, you have to say what versions as there are versions that don't use it such as the version of RMSDK that Kobo uses.

Jon, since we are discussing Kobo's v5 firmware, the only books RMSDK is used for are Adobe ADEPT DRMmed ebooks.

[Falkor]

I use the latest version of ADE on my computer: 4.5.12 –*why would I use an old one?
same for Thorium and Calibre.

I installed Koreader on the device last night and it does support initial-letter –*loads of other issues, though. RMSDK and the default renderer handle my stylesheets much better.
What Koreader does really well is rendering fonts. Fonts that I would never use with the stock renderers are quite pleasant to read with Koreader. And the contrast/weight settings help with fonts that are still difficult to read. The kerning is much better, too. And it's FAST.

[JSWolf]

The reason to use an older version of RMSK/ADE is to test eBooks with it since it doesn't do ePub3. So it's really good for testing backwards compatibility.

[Falkor]

Ah, right. Current versions still use the legacy RMSDK for epub2, but I haven't found a way yet to open an epub3 with RMSDK.

[JSWolf]

Originally Posted by Falkor

Ah, right. Current versions still use the legacy RMSDK for epub2, but I haven't found a way yet to open an epub3 with RMSDK.

Send the ePub3 to your Kobo as an ePub and not as a KePub and then you should be able to use RMSDK to open the ePub.

[Falkor]

I’m on 5.18. I can simply choose RMSDK in the developer menu. No file conversion or renaming necessary.

But it would be nice to be able to check on legacy RMSDK on my computer as well. so far I can only do it before upgrading the book internals to epub3.