JDK-8198752 : Figure out how to handle the fallback if fonts are not present in jdk-home/lib/fonts directory
  • Type: Bug
  • Component: javafx
  • Sub-Component: graphics
  • Affected Version: openjfx11
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • OS: generic
  • CPU: generic
  • Submitted: 2018-02-27
  • Updated: 2018-09-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8195806 - Eliminate dependency on sun.font.lookup in javafx.graphics
Description
The fallback mentioned in Summary is already handled in JavaFX. It needs a closer look to see if things can be improved especially in case when using with OpenJDK.

This has two parts-
1) To support running OpenJFX against OpenJDK which does not have Lucida Sans Fonts then we need to look at the caller of getJDKFontDir() and see whether it makes sense to remove the call as we know upfront these fonts are not supported by OpenJDK.

2) Consider using "System" as a preferred way of finding fonts. 
Note : We need to make sure we don't have a circularity in the case that we are using this in initializing System.


Also, as noted in a review comment on JDK-8195806, in method getJDKFontDir() of class PrismFontFactory, please check whether the returned string needs a File.separator at the end.