Closed Bug 131858 Opened 24 years ago Closed 23 years ago

Mozilla does not display webpage using user specific char setting

Categories

(Core :: Internationalization, defect)

x86
Windows 98
defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: youying, Assigned: tetsuroy)

Details

(Keywords: intl)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.9+) Gecko/20020317 BuildID: 2002031708 Recently I found an issue of character coding in Mozilla 0.9.9+. If I visit a website which does not tell its charset, the Mozilla does not show it using my default character setting. For example, my default char-setting is "Traditional Chinese". And the Auto-Detect of Char-setting is enable. Mozilla just show webpage using "Chinese Simplified(GB18030)". I have to force it to Chinese-Big5 manually. Reproducible: Always Steps to Reproduce: 1.setup your char-setting to "Traditional Chinese" and turn off "Auto-Detect" in "Character Setting" 2.visit any website does not give "setchar=" information 3.And then you will see Mozilla using "Chinese Simplified(GB18030)" to display, not the one, "Traditional Chinese", to display. Expected Results: Mozilla should display according to user's specific setting, while Auto-Detect off.
I think this looks more like a I18N issues, than a bug in the MozillaTranslator program.
Assignee: Lynggaard → yokoyama
Component: MozillaTranslator → Internationalization
QA Contact: Lynggaard → ruixu
reporter: Can you provide few links for our testing? There could be number of things in determining the charset. Thanks
Hello Roy, Of course I can provide them. But please give me some time, I'm busy recently for my business...:-( I'll ask some one to do this also. Thanks :)
Hello Roy, About this issue occurs in 0.9.9+. Now in 1.0 Final or 1.1 Alpha, it does not occur again. If you are still interested in this, you can try this URL as following. http://www.csie.ntu.edu.tw/~b7506051/mozilla/145199.html
Keywords: intl
QA Contact: ruixu → ylong
I can not reproduce it on 06-18 1.0.0 branch build. It sounds like a problem(bug 132006) that exisiting in mozilla 0.9.9 but fixed now. I'm marking this as invalid cause it's not existing any more. Please re-open if disagree.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.