On Thu, 28 Apr 2022 23:11:20 GMT, Naoto Sato <na...@openjdk.org> wrote:
> The following diff seems to choose the right font: > > ``` > --- a/src/java.desktop/windows/data/fontconfig/fontconfig.properties > +++ b/src/java.desktop/windows/data/fontconfig/fontconfig.properties > @@ -230,7 +230,7 @@ > sequence.dialog.x-MS950-HKSCS-XP=alphabetic,chinese-ms950,ch > inese-hkscs,dingbats > > sequence.dialoginput.x-MS950-HKSCS-XP=alphabetic,chinese-ms950,chinese-hkscs,di > ngbats,symbol,chinese-ms950-extb > > sequence.allfonts.UTF-8.hi=alphabetic/1252,devanagari,dingbats,symbol > -sequence.allfonts.UTF-8.ja=alphabetic,japanese,dingbats,symbol > +sequence.allfonts.UTF-8.ja=japanese,alphabetic,dingbats,symbol > > sequence.allfonts.windows-1255=hebrew,alphabetic/1252,dingbats,symbol > ``` > > This diff intends to choose the `japanese` set before the `alphabetic` set, > in case for `ja` locale in `UTF-8` file encoding. I am not saying this is the > right fix, but could be a starting point. I've been looking at that exact line since I think it is what we'd use in the new default locale and also thinking about the "allfonts" issue we've seen with Korean. And which font is "japanese" in this case ? Maybe we want to fill out the UTF8.<lang> based locales in this file now that is the default I suspect it is a lot safer to do what Toshio is doing but I just want to understand the mechanism. I didn't have all the JA fonts installed on my system and I've been trying but they don't seem to have appeared yet, so specifically I don't have MS Mincho, so there's not much I can test yet. It migh ------------- PR: https://git.openjdk.java.net/jdk/pull/8329
