Closed Bug 7473 Opened 25 years ago Closed 25 years ago

HTML meta charaset does not work

Categories

(Core :: Internationalization, defect, P2)

All
Linux
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: teruko, Assigned: ftang)

References

()

Details

Tested 6-02-08-M7 Linux build.

Above URL page has HTML meta tag for charset ISO-2022-jp.
When you go to this page at the first time, you see Japanese characters as garbage.
If you change the Default Character set menu to Japanese (ISO-2022-JP), you can see the
Japanese characters correctly.

Another example is
http://babel/tests/browser/bft/jis/bft_frame_body_jis.html
Also, in this page, this happens.

Every HTML meta charset page does not display correctly unless you change the Default encoding to
the proper character set.
Priority: P3 → P2
Summary: Linux-HTML meta charaset does not work → Linux-HTML meta charaset does not work
Target Milestone: M7
Status: NEW → ASSIGNED
Meta charset got broken by rickg's nsString2 check in. He fix that part
yesterday. teruko, can you verify with build after 6/3 ?
Summary: Linux-HTML meta charaset does not work → [PP] Linux-HTML meta charaset does not work
Hardware: Other → All
Summary: [PP] Linux-HTML meta charaset does not work → HTML meta charaset does not work
I realized this happens in all platform.  I changed Platform to All.
I checked this in 6-3-08 Win and Linux build.  This stil happens.
Assignee: ftang → rickg
Blocks: 7228
Status: ASSIGNED → NEW
reassign this to rickg since the nsStr.cpp cause this. Rickg tell me thorugh the
phone that he will check in the fix. But I think we need to verify it.
Assignee: rickg → ftang
Frank -- I think this is fixed now. Please try it, and then close this bug.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
RickG, if you think it is fixed, please mark it fixed instead reassign that back
to me. Otherwise, IQA won't start to verify it. Teruko, please verify. Thanks.
Status: RESOLVED → VERIFIED
I verified this in 6-07-08 Win32, Mac PPC, and Linux build.
You need to log in before you can comment on or make changes to this bug.