Thread: Firmware 4.32.19501
View Single Post
Old 04-16-2022, 09:59 PM   #127
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by NiLuJe View Post
I seem to remember reading either in the official release notes or @davidfor's recap that that this worked best (as in, that's what it was designed for) for actual mixed language content, *not* a single stray codepoint in a sea of otherwise covered codepoints .

So, my TL;DR: would be, yeah, I suppose it's the expected behavior.

EDIT: That was indeed spelled out in @davdfor's recap .
Yes, that is correct. When I saw that individual characters were not being fixed, I asked and was given an explanation by one of the Kobo developers about what is happening. It is related to how Webkit, Qt and several other things do it, whether the fonts actually having the glyphs they claim to have, and, of course, some optimisation for speed.
davidfor is offline   Reply With Quote