01-28-2020, 05:56 PM | #91 |
BLAM!
Posts: 13,477
Karma: 26012492
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@rtiangha: Don't rely on old documentation.
Freetype's behavior re: hinting has changed recently (-ish), and how it was built can affect the results anyway. (And even on desktop Linux, where you mostly control the full rendering chain, getting stuff to do what you want can be a bit maddening). Because the autohinter can be configured in a couple different ways, and the defaults and how some settings interact with that have changed recently (again, -ish). Amazon, at least, is using a heavily patched FreeType build, so, who knows what's happening there. The font hack used to be able to override it with a custom build with more control over the hinting settings being used, but that's no longer possible. As for Kobo, they may be using Monotype's iType in some instances, and/or Adobe's own rendering engine, so, also murky. ---- On recent, default Freetype builds, the priority is indeed BCI > autohint > no hinting. And you do explicitly need to request no hinting. ttfautohint will just bake FT's own autohinting into the font as truetype instructions, which is dubiously useful if the final renderer is also FT (it's basically only useful for old fonts with bytecode that FT doesn't deal with properly, when targeting low dpi rendering). On high-dpi devices such as ours, you'll generally vastly prefer unhinted rendering to autohinted rendering. Random related plug: KOReader will allow you to try all three rendering types (with the autohinter set to the new defaults, slight hinting, with a grayscale target screen). For instance, I am happily using Bookerly rendered unhinted on my Forma, and it doesn't look like crap . ---- TL;DR: Yeah, Amazon fucked up on that one. They should have enforced unhinted rendering, too. (Fun fact: this is what's done on Android. And iOS. [Roughly]). Last edited by NiLuJe; 01-28-2020 at 06:10 PM. |
01-28-2020, 06:04 PM | #92 |
Evangelist
Posts: 496
Karma: 356531
Join Date: Jul 2016
Location: 'burta, Canada
Device: Kobo Glo HD
|
Well, I quoted QT 4.6 because that's where the system fonts are stored on Kobo. But I also see directories for QT 4.8 and QT 5 and the documentation for that section essentially say the same thing about behaviour on all the versions. But yeah, I have no idea if things are patched to behave differently or what version of Freetype is being used (on Kobo, I assume it's ancient like the kernel and most other things). I just think that it might be funny if the entire font hints vs no hints on eink thing becomes moot in practice after all because of default renderer settings.
Last edited by rtiangha; 01-28-2020 at 06:14 PM. |
Advert | |
|
01-28-2020, 06:16 PM | #93 |
BLAM!
Posts: 13,477
Karma: 26012492
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@rtiangha: Used to be Qt 4.x, is now 5.2. They kept the filenames as-is to make updates less painful (since it's basically a tarball with no scripting capabilities, so migrating folders & filenames was not easily doable post-install).
FWIW, wonky stem heights is typical of FT autohinting going awry, so, it all tracks . You'd get "fuzzier" rendering if truly unhinted, but with "perfect" (as in, honoring the font's design) shapes. The higher the DPI, the sharper the rendering. Plus, eInk has a tendency to make that fuzziness much less noticeable than on LCD to begin with. Last edited by NiLuJe; 01-28-2020 at 06:19 PM. |
01-28-2020, 06:28 PM | #94 | |
Evangelist
Posts: 496
Karma: 356531
Join Date: Jul 2016
Location: 'burta, Canada
Device: Kobo Glo HD
|
Quote:
Edit: Ah, never mind; found it. Bottom menu. I was looking through the top menu bar options, lol. Last edited by rtiangha; 01-28-2020 at 06:31 PM. |
|
01-29-2020, 02:05 PM | #95 | |
Resident Curmudgeon
Posts: 73,896
Karma: 128597114
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
https://www.freetype.org/ttfautohint/index.html And here is the link to the source on Github so it can be built for Linux. https://github.com/source-foundry/ttfautohint-build |
|
Advert | |
|
01-30-2020, 09:28 AM | #96 | |
Guru
Posts: 916
Karma: 13928438
Join Date: Jan 2013
Location: Ely, Cambridgeshire, UK
Device: Kindle Oasis 3, Kindle Oasis 1
|
Quote:
|
|
01-30-2020, 10:25 AM | #97 |
Resident Curmudgeon
Posts: 73,896
Karma: 128597114
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
I've seen hinting using ttfautohint look better at small sizes under Windows. So why would it not work?
|
01-30-2020, 11:36 AM | #98 |
BLAM!
Posts: 13,477
Karma: 26012492
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
|
01-31-2020, 02:19 AM | #99 |
Evangelist
Posts: 496
Karma: 356531
Join Date: Jul 2016
Location: 'burta, Canada
Device: Kobo Glo HD
|
I'm curious: The renderer in the Kobo Desktop app is essentially nickel and I don't know how Kindle Previewer works, but would they use Freetype like their eink counterparts or would they use whatever Windows uses? It would be nice to test fonts on the desktop without having to set up an emulator (I know one exists for koreader, but I'm not aware of similar for Kobo and Kindle proper; correct me if such things exist), especially to find out if they ever get around to fixing the current weirdness with Bookerly (and yeah, I understand the final output is an LCD so it'd still be comparing apples to oranges, but oh well).
|
02-07-2020, 05:52 PM | #100 | |
Member
Posts: 19
Karma: 32720
Join Date: Apr 2015
Device: Kindle Oasis, Pocketbook 840-2
|
Quote:
https://i.imgur.com/NhiNjNn.png On the top it's the new Bookerly, and on the bottom is the old. It's not a problem to upload the old Bookerly font and continue to read with it, but again, if you only need Latin characters. With any UTF-8 like Cyrillic, Greek, etc. there's a nasty error with custom fonts which makes it almost impossible to use them (sometimes device even crashes and you have to reboot your Kindle). I reported this error many times to Amazon, but it's still not fixed. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Firmware Update Instructions and the latest Firmware Versions | mitchwah | Ectaco jetBook | 113 | 10-24-2023 09:02 PM |
Firmware Update Kindle firmware 5.12.1 | eilon | Amazon Kindle | 102 | 09-26-2019 08:38 PM |
Firmware glitch - typing text slow on some firmware+device combinations | mdp | Onyx Boox | 11 | 11-11-2017 12:48 AM |
Firmware 2.0.3 Pocketbook IQ - another firmware is release for IQ | tvpupsik | PocketBook | 26 | 12-13-2010 03:03 PM |
SMARTQ7: firmware 5 VS .92 firmware 5.1? | wwang | Alternative Devices | 2 | 12-17-2009 12:41 PM |