Closed Bug 140902 Opened 23 years ago Closed 22 years ago

[gtk2] Some code displayed on page title when launch non-english web site;

Categories

(Core :: XUL, defect)

x86
Linux
defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: alvin.duan, Assigned: blizzard)

References

Details

***************
This is a gtk2 bug
***************

Start Mozilla testing build and launch a non-English web site. Such as
http://www.cctv.com or http://www.sony.co.jp/Entertainment/index_text.html;

Bug - Please note the page title

If you visit "http://www.cctv.com", the page title will be
"\x{592E}\x{89C6}\x{56FD}\x{9645}\x{9996}\x{9875}"; 

If you launch "http://www.sony.co.jp/Entertainment/index", the page title will
be "Sony
Japan\x{FF5C}\x{30A8}\x{30F3}\x{30BF}\x{30C6}\x{30A4}\x{30E1}\x{30F3}\x{30C8}"

Or other non-English web site;

Note: 
I don't think this bug is due to incorrect language setting of browser, or
language pack. In my opinion, if this bug is due to language setting, the page
title should be some garbage code (just like "8f9y9asd7f87asd&*>#@$NKH*").

But now, the page title is some regular numbers; 

I checked this issue on Mozilla 1.0 RC1 and not repro, in Mozilla 1.0 RC1, there
are some garbage code were displayed when I launch non-English site;
Blocks: gtk2
The code should convert the page title to UTF-8 and then gtk probably converts
it to the local encoding.  What is the local encoding and what window manager is it?
Can we find a different owner for these gtk2 bugs (and perhaps a different QA 
since I don't really have time to do this). And can we label the gtk2 bugs with 
[gtk2].
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Some code displayed on page title when launch non-english web site; → [gtk2] Some code displayed on page title when launch non-english web site;
->blizzard@mozilla.org
Assignee: jaggernaut → blizzard
I test mozilla(trunk) on linux 7.2 with Chinese locale. The Chinese title
display correctly.
I also can not reproduce it.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
This bug doesn't happen to current browser (Whatever Mozilla or Netscape), so I
close this bug;
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.