Closed
Bug 172402
Opened 22 years ago
Closed 20 years ago
charset autodetector not working
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
Firefox0.9
People
(Reporter: bobj, Assigned: bugzilla)
References
()
Details
(Whiteboard: px)
Attachments
(1 file)
9.88 KB,
image/png
|
Details |
Go to any iso-8859-a (aka latin1), unlabeled web page. With default settings, this will look like garbage Latin1 characters. Open the View|Character Coding menu and you will still see the checked encoding is "Western (ISO-8859-1)" Try the menu, View|Character Coding|Autodetect|Universal Actual: Nothing happens, open the View|Character Coding menu and you will still see the Open the View|Character Coding menu and you will still see the checked encoding is "Western (ISO-8859-1)" Expected: the page should render in the correct charset, and the View|Character Coding menu will have checked the correct charset. On an unlabeled Simplified Chinese page (see URL above), try Try the menu, View|Character Coding|Autodetect|Chinese Actual: Nothing happens, open the View|Character Coding menu and you will still see the Open the View|Character Coding menu and you will still see the checked encoding is "Western (ISO-8859-1)" Expected: the page should render in the correct charset, and the View|Character Coding menu will have checked the correct charset. As a check, you an then go select View|Character Coding|More|East Asian|Simplified Chinese (GB2312). This forces the page to be treated as GB2312, and then the page will be rendered correctly. However, the checkmark will still claim "Western (ISO-8859-1)". So there looks to be another bug in the feedback. in View|Character Coding will correctly check
Ignore last line in description: "in View|Character Coding will correctly check" Copy&paste error.
For this separate bug: > However, the checkmark will still claim "Western (ISO-8859-1)". So > there looks to be another bug in the feedback. is filed as bug 172658
Comment 3•22 years ago
|
||
*** Bug 172974 has been marked as a duplicate of this bug. ***
Assignee | ||
Updated•22 years ago
|
Whiteboard: px
Assignee | ||
Comment 4•22 years ago
|
||
I think this is fixed now?
Working in 0.4: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021029 Phoenix/0.4
Comment 6•22 years ago
|
||
On 20021108 WinXP, I can't check "View - Character Coding - Auto Detect" to anything othar than "(off)". It is always "(off)", but charset itself is apparently detected without failure.
Assignee | ||
Updated•22 years ago
|
Target Milestone: --- → Phoenix0.5
Comment 7•22 years ago
|
||
This bug as reported is fixed.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 10•22 years ago
|
||
It's partly fixed. I can view JIS and BIG5 pages with the universal but for some reason it will not re-autodetect sometimes, it will keep a previous detection or detect wrongly as UTF8. I'm not exactly sure how this is reproducible but it DOES pop up quite often. Attached is borked-charset hotmail.com login page.
Comment 11•22 years ago
|
||
sorry for the spam.... bleh
Comment 12•22 years ago
|
||
Worse yet, the charset autodetector will NEVER recognize shiftjis. test url: http://village.infoweb.ne.jp/~kino/so-har/ confirm that 0.4 release is plagued by this as well as latest CVS. (refer: Magpie on #phoenix, and me too)
Comment 13•22 years ago
|
||
I spoke a little too soon. Not only will it not detect Shift-JIS, it won't autodetect anything! Yet this functionality works perfectly fine in mozilla latest trunk. what's the deal? Menu choices for charset autodetection never take and it is always stuck on (off).
Assignee | ||
Comment 14•22 years ago
|
||
should work now.
Status: NEW → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → FIXED
Comment 15•21 years ago
|
||
REOPENED Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030721 Mozilla Firebird/0.6 I do not see indicators of the autodetected or non-autodetected character set.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•21 years ago
|
QA Contact: asa
Comment 16•21 years ago
|
||
Nominating for 0.8 as it was originally targetted at 0.5
Flags: blocking0.8?
Comment 17•21 years ago
|
||
is this really broken? it doesn't seem to be in current 0.8 branch builds, but I'm not confident enough about the issue to say for sure. djst, thoughts?
QA Contact: mconnor
Updated•21 years ago
|
Target Milestone: Phoenix0.5 → Firefox0.9
Comment 19•20 years ago
|
||
you could go to View -> Character Coding -> Auto-Detect and add the language you wish to view. you could customize the language too.
Comment 20•20 years ago
|
||
no response indicating this is still broken after three months inactivity minusing blocking request and resolving WORKSFORME.
Status: REOPENED → RESOLVED
Closed: 22 years ago → 20 years ago
Flags: blocking0.9? → blocking0.9-
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•