https://bugzilla.redhat.com/show_bug.cgi?id=1833858
--- Comment #18 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> ---
Akira, after removing the locale in the font specific setup I did intend to
look at the generic orth part. I did not want to imply the korean orth was
broken before checking it myself. You did it, thank you very much, that
confirms other Droid-like fonts may be matched fontconfig-side for Hangul even
though are too incomplete for the shaper to make use of them.
Anyway, given what harfbuzz upstream wrote, fontconfig should probably either
only match a Korean locale for fonts that include precomposed Korean glyphs, or
for fonts that include decomposed glyphs and otlayout:hang. I’m quite sure apps
don’t want to get into the business of comparing langs to otlayouts, for every
lang that relies on an otlayout, that would require separate matching lists in
every single app for every locale that does this, which would be insane. This
kind of filtering belongs in fontconfig.
However, even if we fix font filtering for hangul in a generic way in
fontconfig, there still remains the need to explicitly blacklist Droid if
selected by the user. We don’t have a good mechanism for that, that’s the key
difference between
https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/197
and just hiding the lang for Droid.
Anyway I will keep this bug open for the local partial fix (hiding korean lang
for droid in the droid package). But you probably need to open some generic
issues fontconfig side.
--
You are receiving this mail because:
You are on the CC list for the bug.