On Mon, 20 Oct 2025 05:58:25 GMT, Sergey Nazarkin <[email protected]> wrote:
>> There is a reproducible bug in symbol rendering on Windows machines with >> [particular](https://github.com/openjdk/jdk/blob/9d71af108ea2cc3682607527246d60a19fd820ba/src/java.desktop/windows/native/libawt/windows/awt_Win32GraphicsEnv.cpp#L244) >> default locales. This changeset fixes the deferred font initialisation >> request, which now skips the last font in the list. >> >> The test (attached to the jira) was performed on a Windows 11 machine with >> the Japanese locale set as the default. Without the fix, it fails with an >> NPE. With the fix it displays a window showing glyphs drawn by all the fonts >> accessible from the Java application. > > Sergey Nazarkin has updated the pull request incrementally with one > additional commit since the last revision: > > Get rid of eudc.reg PS as referenced in that bug the updated INTL guide https://docs.oracle.com/en/java/javase/25/intl/font-configuration-files.html#GUID-F8ABF748-F3C3-4781-97B2-66C7E1E10EE9 says The JDK places any files that it provides in $JDKHOME/lib. Do not modify that location. Instead, put any updates or custom versions of the configuration files in $JDKHOME/conf/fonts. On platforms that support font configuration files, the runtime will look first in $JDKHOME/conf/fonts. ------------- PR Comment: https://git.openjdk.org/jdk/pull/27551#issuecomment-3427721018
