RFR: 8190907: Windows 10 default Korean Font Malgun Gothic available not used by GUI elements even though available without Korean Language Pack [v3]
Phil Race
prr at openjdk.java.net
Fri Mar 11 03:36:50 UTC 2022
On Fri, 4 Mar 2022 05:07:44 GMT, Prasanta Sadhukhan <psadhukhan at openjdk.org> wrote:
>> Malgun_Gothic(https://en.wikipedia.org/wiki/Malgun_Gothic) had replaced Gulim korean font so it needs to be updated to show korean fonts
>
> Prasanta Sadhukhan has updated the pull request incrementally with one additional commit since the last revision:
>
> Revert dialogInput. Add Bolditalic
I'm reviewing https://docs.oracle.com/javase/8/docs/technotes/guides/intl/fontconfig.html#windows where it says
The keys have the forms:
allfonts.CharacterSubsetName
LogicalFontName.StyleName.CharacterSubsetName
The first form is used if the same font is used for a character subset independent of logical font and style (in this case, the font rendering engines apply algorithmic styles to the font). The second form is used if different physical fonts are used for a character subset for different logical fonts and styles. In this case, properties must be specified for each combination of logical font and style, so 20 properties for one character subset. If a property of the first form is present for a character subset, then properties of the second form for the same character subset are ignored.
So if you remove the allfonts entry, does it pick up serif.plain.korean (etc) ?
And the allfonts entry does (I am fairly sure) then apply to the fallback sequence if there are no "second form" entries, but regardless it seems odd that fallback entries are ignored because the second form is present, but ignored and in turn causing the fallback to be ignored ?
This does not seem to be working intuitively.
Perhaps it hasn't been much of an issue if serif.plain.korean (etc) generally refers to an existent font that is usually installed and no one needs to worry about the fallback entries. But I think nothing should "hide" fallback entries.
So this may need code changes as well. And that doc may need to be updated ..
-------------
PR: https://git.openjdk.java.net/jdk/pull/7643
More information about the client-libs-dev
mailing list