Quote:
Originally Posted by MrSilverstrike
For 5.x, I'm working on something exciting (or, well, I'm having some agents work on some stuff that I'm reviewing) that hopefully makes it so I won't even need a NickelTypeFix for the new system software.
Hope to share more soon, but here's a hint: the built-in reader with the reliability and text rendering capabilities of KOReader  |
I look forward to seeing it.
I have a few questions...
- Are your plans purely related to text rendering? I ask because quite a lot of current kobopatches are cosmetic changes to customise the look of the GUI. The latter are probably not as important but they are still nice to have.
- I've been using eink readers and Android reading apps for many years now and the subject of "user override CSS" for font-family, text-align, line-height has been a constant problem which never seems to improve unless some kind community developer/hacker can create options to hand back control to the user. Is it possible to give complete control to the user by letting them maintain their own small override CSS file on the device which the reading app will use (if it exists) rather than using its own (usually bizarre) default decisions about how heavy-handed the overrides should be?
- A very specific question. Do you think your new renderer will be able to deal with CSS pseudo selectors e.g. ::first-letter and ::first-line? Nickel kepubs handle them with no trouble but KOReader doesn't (unless something has changed recently).