-
Bug
-
Resolution: Duplicate
-
P2
-
None
-
1.4.0
-
sparc
-
solaris_9
*****************************************
JDK version : 1.4.0_00
OS : Solaris 9 Sparc s81_56
LOCALE : ja
*****************************************
JIS X 0212 characters are not displayed the methods below;
GlyphVector.getOutline + draw
TextLayout.getOutline + draw
* This is reproducible on Solaris9 s81_56 also with jdk1.4.0 fcs(b92).
* This is NOT reproducible on Solaris9 s81_53 with both of jdk1.4.0_00 and jdk1.4 fcs(b92).
* This is NOT reproducible on Solaris 2.6, 7 and 8.
To reproduce,
1. cd $JAVAHOME/demo/jfc/Font2DTest
2. Launch Font2DTest : java -jar Font2DTest.jar
3. Select one of the font among Dialog, DialogInput, Serif, SansSerif and Monospaced from Font.
3. Select "CJK Unified Ideographs" from Range.
4. Select GlyphVector.getOutline + draw or TextLayout.getOutline + draw
Then, the problem is seen.
\u4e02, \u4e04, \u4e05, \u4e12, \u4e0c.... are not displayed.
From the reason that this problem occurs on Solaris9 s81_56, but does not occur on Solaris9 s81_53, this seems
a problem on S9 side.
If so, please change the Category/Subcategory to proper one.
This seems to relate to See Also Bug 4637183.
JDK version : 1.4.0_00
OS : Solaris 9 Sparc s81_56
LOCALE : ja
*****************************************
JIS X 0212 characters are not displayed the methods below;
GlyphVector.getOutline + draw
TextLayout.getOutline + draw
* This is reproducible on Solaris9 s81_56 also with jdk1.4.0 fcs(b92).
* This is NOT reproducible on Solaris9 s81_53 with both of jdk1.4.0_00 and jdk1.4 fcs(b92).
* This is NOT reproducible on Solaris 2.6, 7 and 8.
To reproduce,
1. cd $JAVAHOME/demo/jfc/Font2DTest
2. Launch Font2DTest : java -jar Font2DTest.jar
3. Select one of the font among Dialog, DialogInput, Serif, SansSerif and Monospaced from Font.
3. Select "CJK Unified Ideographs" from Range.
4. Select GlyphVector.getOutline + draw or TextLayout.getOutline + draw
Then, the problem is seen.
\u4e02, \u4e04, \u4e05, \u4e12, \u4e0c.... are not displayed.
From the reason that this problem occurs on Solaris9 s81_56, but does not occur on Solaris9 s81_53, this seems
a problem on S9 side.
If so, please change the Category/Subcategory to proper one.
This seems to relate to See Also Bug 4637183.