-
Bug
-
Resolution: Duplicate
-
P4
-
None
-
1.4.0
-
None
-
generic
-
generic
The problem looks very similar to bug 4357971 which happens on Win32,
but on Solaris this problem only happens on Merlin beta builds after b16.
It is likely that even if 4357971 is fixed,
this bug still might keep characters on Win32 to be not printed right.
When CJK unicode characters were printed with composite font (EX: dialog)
on Japanese Solaris, the printout was missing
many characters (instead shows up as a "missing glyph" dot).
The missing characters all seem to be ones defined in JIS X 0212 standard.
To reproduce:
1) Run Font2DTest on Japanese Solaris with Merlin beta b16 and later
2) Set the unicode base to 4e00 (Beginning of CJK Unified Ideograph range)
3) Do "Print" from the file menu
4) Look at characters printed for unicode 4e02, 4e04, 4e05, 4e0c, 4e12
and many others. They do appear on screen, but is missing on the output.
shinsuke.fukuda@Eng 2000-08-03
but on Solaris this problem only happens on Merlin beta builds after b16.
It is likely that even if 4357971 is fixed,
this bug still might keep characters on Win32 to be not printed right.
When CJK unicode characters were printed with composite font (EX: dialog)
on Japanese Solaris, the printout was missing
many characters (instead shows up as a "missing glyph" dot).
The missing characters all seem to be ones defined in JIS X 0212 standard.
To reproduce:
1) Run Font2DTest on Japanese Solaris with Merlin beta b16 and later
2) Set the unicode base to 4e00 (Beginning of CJK Unified Ideograph range)
3) Do "Print" from the file menu
4) Look at characters printed for unicode 4e02, 4e04, 4e05, 4e0c, 4e12
and many others. They do appear on screen, but is missing on the output.
shinsuke.fukuda@Eng 2000-08-03
- duplicates
-
JDK-4303306 Drawing many rotated texts with Japanese fonts eats up 200MB MEM before freeing
-
- Closed
-