----------------------------------------
Bug switched category several times:
 JMQ/doc
 javahelp/other
 JMQ/doc
 java/classes_swing
----------------------------------------

Bring up the online help from Admin GUI.
Under MQ Object Store Management, two pages contain a "square box" instead of a character, Add Object Store, and Object Store Properties.
Please look for "java.naming.factory.initial" and "java.naming.provider.url"
Between these two strings, one square box is displayed.


###@###.### 2003-11-03
-----------------------------
Changing category to javahelp.

I can't figure out why this problem is seen. I've written a small self contained
example and attached it to this bug (javahelp_l10n.tar).

To reproduce problem:

Switch to zh_CN locale

Save/uncompress javahelp_l10n.tar in bug to disk

Extract it with tar
% tar xvf javahelp_l10n.tar
x javahelp_l10n, 0 bytes, 0 tape blocks
x javahelp_l10n/jhall.jar, 404079 bytes, 790 tape blocks
x javahelp_l10n/build.xml, 3572 bytes, 7 tape blocks
x javahelp_l10n/helpfiles, 0 bytes, 0 tape blocks
x javahelp_l10n/helpfiles/Master.jhm, 269 bytes, 1 tape blocks
x javahelp_l10n/helpfiles/MasterTOC.xml, 267 bytes, 1 tape blocks
x javahelp_l10n/helpfiles/Master_zh_CN.hs, 473 bytes, 1 tape blocks
x javahelp_l10n/helpfiles/ide.css, 907 bytes, 2 tape blocks
x javahelp_l10n/helpfiles/add_object_store.htm, 495 bytes, 1 tape blocks
x javahelp_l10n/runit, 100 bytes, 1 tape blocks
x javahelp_l10n/TestApp.java, 2006 bytes, 4 tape blocks
x javahelp_l10n/build, 0 bytes, 0 tape blocks
x javahelp_l10n/build/TestApp$1.class, 502 bytes, 1 tape blocks
x javahelp_l10n/build/TestApp.class, 3052 bytes, 6 tape blocks

cd javahelp_l10n

Run it via:
 ./runit (on Solaris)

or
 java -cp CP TestApp
 where CP is a classpath containing "build", "jhall.jar", and "helpfiles"

When the frame comes up, select the "Show Help" button. The help viewer that
comes up shows a square box in between the text java.naming.factory.initial
and java.naming.provider.url. If you look at the help source file
helpfiles/add_object_store.htm you'll see that a Chinese character is supposed to be
displayed. Not sure if the help HTML source is at fault, encoding used (GB2312),
application code, javahelp, or JDK. The jhall.jar I am using here is from the 1.1.3
distribution. If any of the source is in error, please let me know and I will
gladly close this or reassign back to JMQ.


###@###.### 2003-11-04
-----------------------------
ThanX for the quick clarification, Roger ! (See evaluation)

Not quite sure if this should be sent to java/classes_swing, java/localization.

JDK version:
% java -fullversion
java full version "1.4.2-b28"

I wrote a small test app that uses JEditorPane. I include this complete
self contained example, including test HTML file as an attachment (jeditorpane.tar.Z)
for this bug.

To reproduce problem:

Switch to zh_CN locale. From CDE login screen, I chose the Simplified Chinese
locale that had "(GB2312)" in it.

Save/uncompress jeditorpane.tar.Z in bug to disk

Extract it with tar:
% tar xvf jeditorpane.tar
x jeditorpane, 0 bytes, 0 tape blocks
x jeditorpane/build.xml, 3581 bytes, 7 tape blocks
x jeditorpane/build, 0 bytes, 0 tape blocks
x jeditorpane/build/JEditorPaneTest.class, 1424 bytes, 3 tape blocks
x jeditorpane/runit, 81 bytes, 1 tape blocks
x jeditorpane/pkginfo.out, 96057 bytes, 188 tape blocks
x jeditorpane/test.htm, 397 bytes, 1 tape blocks
x jeditorpane/JEditorPaneTest.java, 865 bytes, 2 tape blocks

cd jeditorpane

Run it via:
 ./runit <URL to test.htm>
 e.g. ./runit file:///tmp/jeditorpane/test.html

or

 java -cp build JEditorPaneTest <URL to test.htm>

The JEdtitorPane that comes up shows a square box (instead of Chinese text) between the
text java.naming.factory.initial and java.naming.provider.url.

Not sure if something is wrong with JEditorPane or fonts.

I have a clean install of Solaris 9 update 3 (Solaris 9 4/03 s9s_u3wos_08 SPARC)
and I had the Solaris installer install all the Asian localizations (one check box
for this). I ran 'pkginfo' and saved it to jeditorpane/pkginfo.out in case that
is useful. Roger suspected that some fonts were missing. Not sure how to determine
what fonts or solaris packages are missing. Since I installed *all* the Asian pkgs
I expect things to work out of the box.

FYI, my list of installed Chinese font pkgs looks like:

% grep -i chinese pkginfo.out | grep -i font
ALE SUNW5ttf Traditional Chinese BIG5 True Type Fonts Package
ALE SUNW5ttfe Traditional Chinese BIG5 True Type Fonts Package Extension
ALE SUNW5xfnt Traditional Chinese BIG5 X Windows Platform required Fonts Package
ALE SUNW5xmft Traditional Chinese (BIG5) X Windows Platform minimum required Fonts Package
system SUNWcdft Simplified Chinese L10N for CDE Fonts
system SUNWcfdl Simplified Chinese Font Downloader
ALE SUNWcttf Simplified Chinese (EUC) True Type Fonts
ALE SUNWcttfe Simplified Chinese (EUC) True Type Fonts Extension
ALE SUNWcufnt Simplified Chinese (UTF-8) X Windows Platform required Fonts Package
ALE SUNWcxfnt Simplified Chinese (EUC) X Windows Platform Required Fonts
ALE SUNWcxmft Simplified Chinese (EUC) X Windows Platform minimum Required Fonts
ALE SUNWgttf Simplified Chinese (GBK) True Type Fonts
ALE SUNWgttfe Simplified Chinese (GBK) True Type Fonts Extension
ALE SUNWgxfnt Simplified Chinese (GBK) X Windows Platform required Fonts Package
system SUNWhdft Traditional Chinese L10N for CDE Fonts
system SUNWhfdl Traditional Chinese Font Downloader
ALE SUNWhkfnt Traditional Chinese (Hong Kong) X Windows Platform required Fonts Package
ALE SUNWhkttf Traditional Chinese Hong Kong Supplementary Character Set True Type Fonts Package
ALE SUNWhttf Traditional Chinese True Type Fonts Package
ALE SUNWhttfe Traditional Chinese True Type Fonts Package Extension
ALE SUNWhufnt Traditional Chinese (UTF-8) X Windows Platform required Fonts Package
ALE SUNWhxfnt Traditional Chinese X Windows Platform required Fonts Package

I even tried switching the charset from GB2312 to GBK with no success. Also tried removing the
 <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=GB2312">
line completely - no improvement.

Could it be possible that the offending character here:
\u00ba\u00cd
is not supported for this locale ? (Above is output from native2ascii of test.htm)

Let me know if you need more info.