-
Bug
-
Resolution: Unresolved
-
P4
-
None
-
6
-
None
-
generic
-
windows_xp
The windows fontconfig.properties file references LucidaSansRegular.ttf
via its base file name. This means JDK tries to locate it as an installed
windows font. Its actually a JRE font and so should be specified using the
syntax $JRE_LIB_FONTS. The implementation then needs to be tested to ensure
he file is located with this new syntax.
Also the fontconfig file format spec suggests this is a unix only syntax so
that will need updating too.
Also the Lucida font is apparently listed for the Thai locale but why does it
need to be explicitly mentioned as its implicitly included before other
fallback fonts? So an alternative (may) be to just remove it.
ALso the mapping tests need updating as a result of this and in fact appear
to be already failing because they expect the font to be in the windows system
font diectory and its not. I don't know how this part of the test could ever pass,
on 1.5 or 1.6. But I suppose it must have passed ..
###@###.### 2005-06-06 21:12:17 GMT
via its base file name. This means JDK tries to locate it as an installed
windows font. Its actually a JRE font and so should be specified using the
syntax $JRE_LIB_FONTS. The implementation then needs to be tested to ensure
he file is located with this new syntax.
Also the fontconfig file format spec suggests this is a unix only syntax so
that will need updating too.
Also the Lucida font is apparently listed for the Thai locale but why does it
need to be explicitly mentioned as its implicitly included before other
fallback fonts? So an alternative (may) be to just remove it.
ALso the mapping tests need updating as a result of this and in fact appear
to be already failing because they expect the font to be in the windows system
font diectory and its not. I don't know how this part of the test could ever pass,
on 1.5 or 1.6. But I suppose it must have passed ..
###@###.### 2005-06-06 21:12:17 GMT