>Yes, Librera will support old devices as long as possible
That’s real good news!
>Yes, just set use Document style (please see screenshot)
I knew it was somewhere—thanks for the heads-up!
>You can compare mupdf 1.11 vs mupdf 1.19 in the latest build (beta.librera.mobi)
Thanks for investigating this matter. It seems mupdf 1.19 gets the bold right, but fails not only on the OTF font rules but also on ligatures (like "tz" in "Hatz") now. 1.11 got the ligatures right (albeit not the Fraktur typesetting rules) but failed on the bold.
I’d love to see better OpenType support in Librera, since it is still my favourite reader, and I recommend it to others. So it seems, currently only MoonReader does things correctly, CoolReader and Librera don’t (yet).
The reason I opted for an OpenType rule set (and a standard Antiqua base text) for setting Fraktur and Kurrent fonts was:
- Easy switching to Antiqua fonts while keeping text readable for readers that can’t read Kurrent/Fraktur. I believe in "the Reader’s Choice".
- Easy searching within the document, using Antiqua letters.
- Only way to have current Text-to-Speech engines speak the text correctly.
I used "LOV" type fonts
LOV.HammerUnziale.otf,
LOV.NeueDeutscheKurrent.otf and
LOV.UnicodeFraktur.otf from
ligafaktur.de for this test.
If you want to experiment with these fonts (they also work in programs like LibreOffice), here is a
link to the downloadable fonts and a
guide (in German).
Here are some screenshots of MoonReader, CoolReader, Librera (1.11 mupdf) and the mupdf 1.18 Android Viewer.
As you can see, the "pure" mupdf 1.18 Android Viewer (installed from here) does everything correctly, so maybe we’ll have a chance for Librera to do as well?