Tested bundle:
javaws-1_0_1-fcs-bin-b15-solsparc-int-16_apr_2001.zip
javaws-1_0_1-fcs-bin-b15-win-int-16_apr_2001.exe
javaws-1_0_1-fcs-bin-b15-win-int-rt-16_apr_2001.exe

Tested environment:
Windows 95 (T.Chinese)/IE 4.0 (T.Chinese)/JRE 1.3.0_02
Solaris 8 (zh_TW.UTF-8)/Netscape 4.7 (T.Chinese)/JRE 1.3.0

Problem found:
Launch SwingSet2 Demo from Application Manager in Traditional Chinese environment. The demo itself seems to be localized, but the messages are actually Simplified Chinese characters. Some characters are displayed as square boxes because those S.Chinese characters cannot be mapped into T.Chinese.

I think the reason might be that Swing Demo probably was localized into S.Chinese (by Swing team or demo team). The resource files are named xxx_zh.java or xxx_zh.properties.

When the user tries to run the demo in T.Chinese environment, they couldn't find the T.Chinese resource files. S.Chinese files were there, so it felt back to S.Chinese resources according to Java's locale fallback algorithm.

The S.Chinese resource files in the demo should either be removed or renamed to xxx_zh_CN.java or xxx_zh_CN.properties. "zh_CN" specifies that the resources are only to be used on S.Chinese environment. It will not be used in T.Chinese environment (which is zh_TW).