-
Bug
-
Resolution: Fixed
-
P3
-
jfx11, jfx13, 8
-
x86_64
-
os_x_10.15
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8238627 | 8u261 | Kevin Rushforth | P3 | Resolved | Fixed | b01 |
| JDK-8244011 | jfx11.0.8 | Jose Pereda | P3 | Resolved | Fixed |
Running on MacOS Catalina, when doing static builds of libjavafx_font.a and linking against this in a JavaFX app compiled with GraalVM native-image, if default fonts are used, the rendered text is garbled, and a warning message is printed:
CoreText note: Client requested name ".SFUI-Regular", it will get TimesNewRomanPSMT rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[UIFont systemFontOfSize:].
CoreText note: Set a breakpoint on CTFontLogSystemFontNameRequest to debug.
According to Apple's WWDC sessions (see for instance : https://asciiwwdc.com/2013/sessions/223?q=periods) or the comment at https://github.com/Cocoanetics/DTCoreText/issues/1168#issuecomment-526411915, font names that start with a period are not to be directly used.
CoreText note: Client requested name ".SFUI-Regular", it will get TimesNewRomanPSMT rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[UIFont systemFontOfSize:].
CoreText note: Set a breakpoint on CTFontLogSystemFontNameRequest to debug.
According to Apple's WWDC sessions (see for instance : https://asciiwwdc.com/2013/sessions/223?q=periods) or the comment at https://github.com/Cocoanetics/DTCoreText/issues/1168#issuecomment-526411915, font names that start with a period are not to be directly used.
- backported by
-
JDK-8238627 [macos 10.15] Garbled text running with native-image
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Closed
-
-
-
- Resolved
-