Created attachment 320750 [details]
Netbeans example GUI form cannot display Chinese
Description of problem:
Netbeans and Gui application create by Netbeans cannot display Chinese character.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Install Chinese fonts(install fonts command: yum install cjkunifonts-uming), ensure system can display Chinese character.
2.Open Netbeans, open any source file in Netbeans, input or paste some Chinese character.
Chinese character display as a box or display blank.
Adding to F10Target... it is a "new feature"
It must be java open jdk problem, if I use Sun's jdk with --jdk-home switch, Chinese display correctly.
And I think file /etc/java/font.properties maybe missing Chinese fonts config.
Qiao, I agree with you - It is not an issue of the NetBeans.
Because, both the NetBeans itself and the GUI Form examples use Swing components that are completely responsible for displaying glyphs. If some glyphs can't be displayed then it means either
the Java platform hasn't correct info about an installed system font
the font itself has a bug.
I've tried to reproduce the described bug, but I needed have an input method and I've followed the instructions described here:
After installation of the Chinese Language Support via the command
$ su -c 'yum groupinstall chinese-support'
I can input and see hieroglyphs in the editable Swing components in both editor window of the NetBeans and the GUI Form examples application.
I think, such test is enough to be sure that the issue in the underlying components (i.e OpenJDK, the cjkunifonts-uming font, or Fedora configuration), but not in the NetBeans or its examples.
Also, please note, the examples are only simplest Java Swing applications not more and their functionality doesn't have any impact on I18N features provided by underlaid Java and Fedora platforms.
John, I suggest to reassign this bug sequentially to responsible persons for the underlying components (and begin this with OpenJDK) to find both a source of the bug and a way to fix it.
this problem have resolved, please see https://bugzilla.redhat.com/show_bug.cgi?id=468193
*** This bug has been marked as a duplicate of bug 468193 ***