Problems: This meta bug keeps track of all i18n/l10n/localizability issues reported on Solaris. PROBLEMS -------- 1. Input We can not input Chinese/Korean Characters in navigator URL field and some other input areas. the input method can be invoked, and the preedit area is correct, the lookup choices (Candidates) are correct too, but no Chinese/Korean characters can be committed into those fields. However we can input Chinese/Korean in Composer/Mail. The bug has been already reported in http://bugzilla.mozilla.org/show_bug.cgi?id=47568 and http://bugzilla.mozilla.org/show_bug.cgi?id=52416. There is a workaround on Linux platform. However, now we don't have good solution for Solaris (dtwm). We can make a patch for Solaris htt server not to grab input focus. (See 4390729 in BugTraq) 2. Fonts/Display The Chinese characters in the GUI of Netscape, includingMail, Composer..., are displayed irregularly, some of them are very large while others are very small. Masaki saw this problem in japanese locale on some Linux distributons. How about when you change the chinese fonts to Solaris fonts? 3. Printing We cannot print Chinese/Korean webpages from the current version, we need to know what we should provide for Chinese/Korean locales in order to be able to print Chinese/Korean webpages. known problem. http://bugzilla.mozilla.org/show_bug.cgi?id=55021. Hanaki-san of JLC has collected information from ALC. We should ask base team to change defaults/pref/unix.js to include font preferences for Korean and Chinese. 4.GBK support not all of the GBK Characters can be displayed in UTF-8/GBK locales althoug all of the GBK Characters are included in Unicode2.1/3.0. For zh and zh.GBK locale problem, Masaki found the problem that Mozilla try to create default_prefs.js under application directory. When it fails, Mozilla won't start. In Solaris environment, Mozilla's application directory does not have write-permission for normal user, so this problem happens. I'm not sure whey this happens only when zh and zh.GBK locale. The bug is already filed in BugZilla and I've added my comments, http://bugzilla.mozilla.org/show_bug.cgi?id=18989 nsconv does not work at UNICODE -> ASCII in chinese locale. UnicodeToGBK and UnicodeToGB2312 converter don't work on SPARC Solaris: http://bugzilla.mozilla.org/show_bug.cgi?id=60823. -- has patch from Masaki-san. GBK characters can not be dispalyed properly http://bugzilla.mozilla.org/show_bug.cgi?id=60826 -- patch available from Masaki-san. HOW TO REPRODUCE ---------------- To reproduce the problems, you need to do the following steps: 1. download the Netscape6 PR3 build for SPARC and install onto a Solaris machine. SUN have just released Preview Release 3 for Solaris. You can download it from http://www.sun.com/solaris/netscape . 2. install the attached Asian L10N package(including Simplified Chinese, Traditional Chinese and Korean Language). Install steps as follow: a. gunzip the attatched file: "Asian_L10N_package.tar.gz" b. untar the result file: "Asian_L10N_package.tar". c. pkgadd -d Asian_L10N_package/sparc. Then, switch Region/Language to these Asian lauguages, and you will see the problems. The attached files include some images to specify some problems, such as irregularly display of Chinese characters in the menu, and wrong display of some GBK Chinese characters(some display right, but some display as "?"). and I also attached the GBK files which content all the GBK characters.
I am having problem attaching "Asian_L10N_package.tar.gz" to this bug. I put it in the URL field instead.
Status: NEW → ASSIGNED
I've added some critical bugs in dependency field.
Add myself to cc list.
To request to add Sun Localization team alias.
handing over to ftang
Assignee: tao → ftang
Status: ASSIGNED → NEW
Changed QA contact to email@example.com.
QA Contact: teruko → ylong
Adding myself to CC: Q: Should Xprint module bugs be included in the "depends on" list - or is the Xprint module a "dead option" ?
This is Sun issue. I changed QA contact to katakai-san.
QA Contact: ylong → katakai
meta bug. mark this as ---
Target Milestone: mozilla1.0 → ---
Stupid question: Shouldn't Xprint be tracked by this bug, too ?
meta bug, not really a bug. move to future to get off the radar.
Target Milestone: --- → Future
Component: Internationalization → Tracking
Target Milestone: Future → mozilla1.0
move all my "tracking" bug to "M1"
Target Milestone: mozilla1.1 → M1
this tracking bug lost it's meaning now. mark it as wontfix
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.