Please try to browse sample URL. Some characters are displayed as '?'. I'll attach the snapshots. It seems that only "gb13000.1993-1" fonts are usable for GBK. Is that correct? In Solaris platform, "gbk-0" are used for GBK. I'm not sure this is reasonable fix or not, but after I changed nsFontMetricsGTK.cpp to include "gbk-0", the characters can be displayed. I'll attach the patch. Please evaluate.

Katakai san, I assign this to you since you have a patch, cc to erik, bstell.

Hi Katakai-san, The fix is correct, but please make it align properly with the lines above and below, and please do not use tabs in Mozilla source (only spaces). Thanks. r=erik

I thought your fix would be correct, since it uses the same charset as the other GBK. I.e. they both point to GBK, which says "x-gbk". However, I just had a look at that charset, and it appears to include the ASCII characters (0x00-0x7F), and so this is incorrect, since X Windows double-byte fonts do not contain ASCII glyphs. This means that both of the entries that point to GBK are incorrect. You can see this by setting your Simplified Chinese font to a GBK font in Edit | Prefs | Fonts. ASCII chars will not display correctly. The correct fix would be to do something like nsUnicodeToBIG5NoAscii. Sorry, I hereby remove (undo) my earlier r=erik.

I'd like to reassign to Frank.

I'm reassigning to my self, bstell. I am currently responsible for Unix font issues.

Added intl, nsbeta1 keywords This bug is a showstopper for Sun's Chinese versions (see snapshot)

what is the date that this fix is needed for?

So... according to erik, we need to do the following to fix this bug 1. add a new Unicode Encoder which contains no ASCII and use a new font encoding name for it. 2. change the nsFontMetricsGTK.cpp

Katakai-san, Could you verify these patches / files? Would you try this with both a GB2312 font and an GBK font? (note: bug http://bugzilla.mozilla.org/show_bug.cgi?id=66744 re: using a GB2312 font for GBK) Thanks

Verified Brian's patch on Solaris. When I use gtk-0 fonts, glyphs can be displayed properly. I'll attach the snapshot. When GB2312 is used, yes, as bug 66744 is filed, some glyphs are missing.

Katakai-san, Are the blank spots at 817f, 827f, 837f okay?

Yes, I think so because I got the same result on terminal.

I had nhotta try these on mac. At checkin he will update the mac build info. Erik, would you review this please?

sr=erik

r=ftang please change the FillInfo to public from protected

Checked GBK display on a Simplified Chinese Windows 2000 system. Most characters can be displayed except those between 0xfe50-0xfe9f. Those characters are displayed as question marks. IE and 4.x don't have this problem.

Changed QA contact to ji@netscape.com. Xianglan, I changed QA contact to you since you have already tested this.

the fix has been checked in

Brian, I checked 02/29 mtrunk build. The problem showing on Windows is not fixed. (Please see my comments on 2001-02-09 14:26 and the screenshot following that). Do you need me to file a seperate bug for that?

see: http://oss.software.ibm.com/icu/charset/CharMaps-HTML/windows-936-2000.html

Frank, can you review this? Erik, can you super-review this? thanks

r=ftang

sr=brendan@mozilla.org, rubberstamp is appropriate here! /be

checked in

I don't see in the "View Bug Activity" who reopened this bug. http://bugzilla.mozilla.org/show_activity.cgi?id=60826 I don't see any statements why it was re-opened so I am closing it If there are remaining issues please re-open with a description.

With 03/08 build, there are too many glyphs missing, like 0x8151, 0x8154, 0x8263... Please see attached screenshot. Katakai-san, do you see the problem on Solaris?

Hi, Have you set up font properties for zh-CN correctly? You need to use gtk-0 fonts for zh-CN. Otherwise, you will see the other bug 66744. On my environment of Solaris, after setting gtk-0 fonts, I've verified the characters are displayed properly.

Yes, after I use gbk fonts for zh_CN, all the glyphs can be displayed. Marked it as verified.

And the problem on windows for the characters in 0xFE50 - 0xFE9F range is fixed as well.