-
Bug
-
Resolution: Fixed
-
P2
-
1.2.0
-
1.2beta4
-
x86
-
generic
-
Not verified
[this is information that was improperly added to 4100565 after that bug was improperly marked verified]
On the Far East version of Win32, kanji font files are almost always in TTC (TrueTypeCollection) format. The current implementation, which only searches ttf format for truetype font on win32 platform will probably fail to find o an appropriate font file for Japanese/Chinese strings from System font directory.
xueming.shen@Japan 1998-02-23
While investigating this bug I found another "swap" bug in MapString.c, and I
think this bug is also as serious as the 4113795, so please put it into the
the beta3 if possible, otherwise even if you implement the TTC format, Japanese
will still be unavailable on Win32 platform. (even I have not done any test yet,
but I believe this one will also effect some char points in Japanese/Chinese
TTF font foramt). I attach the suggested fix here.
On the Far East version of Win32, kanji font files are almost always in TTC (TrueTypeCollection) format. The current implementation, which only searches ttf format for truetype font on win32 platform will probably fail to find o an appropriate font file for Japanese/Chinese strings from System font directory.
xueming.shen@Japan 1998-02-23
While investigating this bug I found another "swap" bug in MapString.c, and I
think this bug is also as serious as the 4113795, so please put it into the
the beta3 if possible, otherwise even if you implement the TTC format, Japanese
will still be unavailable on Win32 platform. (even I have not done any test yet,
but I believe this one will also effect some char points in Japanese/Chinese
TTF font foramt). I attach the suggested fix here.
- relates to
-
JDK-4100565 JDK1.2 's java.awt.Font does not support Not-8859-1 character set
-
- Closed
-