Someone has closed bug 4172480 as a duplicate of 4168102. Then I can not
reopen this bug. Bugtraq told me that if I have any question, I can contact
with the Bugtraq Development Group. I have file this bug again.

JDK Version: 1.2fcs-I
OS: Solaris 2.6
Locale: zh & C

In this build (1.2fcs-I) build, all AWT components can not display
ASCII characters in Solaris 2.6 environment.
If we use "xset fp+ /usr/openwin/lib/X11/fonts/TrueType", then the
AWT Components can display ASCII characters correctly.
It is not acceptable to ask all the users to set font path in their system
to make awt work correctly.

I don't think it is a duplicate of 4168102. Because in build
1.2fcs-H, all awt application can display ascii correctly without
setting up extra info in fontpath, but
in 1.2fcs-I build, all awt applications failed. Yes, there exists
the same work around for the two bugs, but you can not say that
they are duplicate just because of this.
By default, in solaris 2.6 system, fontpath does not contain
"/usr/openwin/lib/X11/fonts/TrueType" dir, while in 1.2fcs-I
build, it is required as an necessary condition that if you
want awt to display ascii, you should add that dir to fontpath,
but solaris 2.6's default setup does not meet this requirement,
so, by default, in solaris 2.6, all awt can not display ascii
characters in this build. It is a big problem. It is not acceptable
to ask all solaris 2.6's users to set fontpath as you guys did.


jim.hu@prc 1998-09-11