NickelTypeFix: a mod for better typography and typesetting (kepub only)

[Falkor]

Originally Posted by MrSilverstrike

TENG can be optimized, but it's likely a bunch of optimizations spread all across the reader app in a way that I can't easily fix. If TENG is fast, it's because the pages you visited were cached, and they're not always -- it's why page turns can feel very inconsistent.

It was really extraordinarily fast. No loading screen for any book either.

Originally Posted by MrSilverstrike

I suspect most CSS you'd find in an ebook is going to work just fine, yes

sure would be nice to have in TENG. I wonder why it's deactivated

Originally Posted by sherman

Another option might be to try and adapt WPE Webkit if you want to use a fully featured browser engine.

Webkit may be a good choice, I think it even supports hanging punctuation, which would be awesome to have on a reading device.

[jackie_w]

Originally Posted by MrSilverstrike

Happy to answer them! ... <snip>

Thanks for your replies.

[JSWolf]

Originally Posted by MrSilverstrike

I'm using KOReader's engine (CREngine) for the prototype. The idea is simple: KOReader's engine letting you read your purchased books in a familiar (Kobo-like) UI.

There's a possible problem with using KOReader's engine. It make not support ePub3 well enough. Before you do this, are you sure there's enough ePub3 support?

What would be good is a mod to allow using RMSDK for DRM-Free eBooks if the user so chooses.

[MrSilverstrike]

Originally Posted by JSWolf

There's a possible problem with using KOReader's engine. It make not support ePub3 well enough. Before you do this, are you sure there's enough ePub3 support?

What would be good is a mod to allow using RMSDK for DRM-Free eBooks if the user so chooses.

I did some research and I'm happy enough with the CREngine's support of ePub3 features. Building my own engine or bolting on functionality to make it all work as the spec desires would simply be too much work.

As far as RMSDK is concerned: I believe in 5.18 you can already force RMSDK for epubs via a configuration edit in .kobo/Kobo/Kobo eReader.conf. No mod needed:

[DeveloperSettings]
EpubSideloadedRenderer=RMSDK

[JSWolf]

Originally Posted by MrSilverstrike

I did some research and I'm happy enough with the CREngine's support of ePub3 features. Building my own engine or bolting on functionality to make it all work as the spec desires would simply be too much work.

As far as RMSDK is concerned: I believe in 5.18 you can already force RMSDK for epubs via a configuration edit in .kobo/Kobo/Kobo eReader.conf. No mod needed:

[DeveloperSettings]
EpubSideloadedRenderer=RMSDK

But then how do you load side loaded ePub to the Kobo renderer instead of RMSDK?

[Falkor]

Originally Posted by MrSilverstrike

I did some research and I'm happy enough with the CREngine's support of ePub3 features. Building my own engine or bolting on functionality to make it all work as the spec desires would simply be too much work.

I haven't been using Koreader for long, but I already found a couple of CSS features that are not supported. It can do basic stuff very well, though. And its font settings a really good.

Personally I'd find a modern, webkit based renderer much more useful than a Koreader based on. I can already use Koreader on the device, anyway.

Originally Posted by MrSilverstrike

As far as RMSDK is concerned: I believe in 5.18 you can already force RMSDK for epubs via a configuration edit in .kobo/Kobo/Kobo eReader.conf. No mod needed:

It can also be selected from the developer menu.

[Falkor]

Originally Posted by JSWolf

But then how do you load side loaded ePub to the Kobo renderer instead of RMSDK?

You set it back back to default or TENG.

[MrSilverstrike]

Originally Posted by Falkor

I haven't been using Koreader for long, but I already found a couple of CSS features that are not supported.

Any particular ones you want to point out? If you have an epub you can link that leverages these features, that'd be even better. I can integrate it into my test suite if I find it's too much of an omission.

[JSWolf]

Originally Posted by Falkor

You set it back back to default or TENG.

NickelMenu should be good for that. Do you need to reboot after a change?

[Falkor]

Originally Posted by JSWolf

NickelMenu should be good for that. Do you need to reboot after a change?

No, just select the option in the developer menu and the book opens with the selected renderer.

[JSWolf]

Originally Posted by Falkor

No, just select the option in the developer menu and the book opens with the selected renderer.

If you have the developer menu accessible, does it log like it does on 4.x firmware?

[Falkor]

Originally Posted by MrSilverstrike

Any particular ones you want to point out? If you have an epub you can link that leverages these features, that'd be even better. I can integrate it into my test suite if I find it's too much of an omission.

From what I remember

overflow: hidden

,

display: flex

and

position: absolute

aren't supported.

There are also some funny little rendering oddities I've encountered. E.g. it supports

initial-letter

, but for some reason my fallback for readers that don't support it messes with how the drop caps are being displayed –*which might be caused by the way I implemented removal of the fallback solution, though it doesn work fine in quite a number of software readers…

[DNSB]

Originally Posted by JSWolf

But then how do you load side loaded ePub to the Kobo renderer instead of RMSDK?

Have you tried sending them as .kepub.epub?

[Falkor]

Originally Posted by JSWolf

If you have the developer menu accessible, does it log like it does on 4.x firmware?

No idea how 4.x handles it, but it does have settings for logs and I found some logs on the device.

[JSWolf]

Originally Posted by DNSB

Have you tried sending them as .kepub.epub?

I don't have firmware 5.18. I'm still on some version 4.x firmware.