JDK-7074386 : Fall back to fontconfig file based on only OS major version number on Linux
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt:i18n
  • Affected Version: 6u25,6-pool
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: linux,linux_redhat_6.1
  • CPU: generic,x86
  • Submitted: 2011-08-03
  • Updated: 2011-11-04
  • Resolved: 2011-10-11
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 Availabitlity Release.

To download the current JDK release, click here.
Other JDK 6 JDK 7 JDK 8
5.0u33Fixed 6u30 b08Fixed 7u2Fixed 8Fixed
Related Reports
Duplicate :  
Description
with RHEL 5, Red Hat switched their version scheme from a single number (i.e. RHEL 4) to a <major>.<minor> (i.e. RHEL 5.6). This causes problems because FontConfiguration will expect a different fontconfig file for each update of RHEL.

The solution is to first search for a fontconfig file based on the <major>.<minor> version number and if we don't find that, fall back to a file based on just the major file number. That way we can have a ���default��� fontconfig for the major release, and add an update specific file if there is a need to override the behavior.

For example, on a Solaris 10 machine (Sun OS 5.10) , it currently would look for the following files in order :

fontconfig.5.10.properties
fontconfig.5.10.bfc
fontconfig.properties
fontconfig.bfc

We want it to also look for a fontconfig file with a name based off of the major version alone:

fontconfig.5.10.properties
fontconfig.5.10.bfc
fontconfig.5.properties
fontconfig.5.bfc
fontconfig.properties
fontconfig.bfc

Comments
EVALUATION code added to fallback to fontconfig file based off of single number version number
2011-09-09