212128 - Request: override the MIME charset by my default charset.

Status: RESOLVED EXPIRED

(Core :: Internationalization, enhancement)

Description

[Clotho]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030612
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030612

Most authors of Big5 web pages incorrectly set the charset to "big5" instead of
"big5-HKSCS", results in incorrect coding of some special Hong Kong characters.
However, as Internet Explorer can display the special characters with BIG5
encoding after downloading the fonts, most authors ignore the error.

I hope that I can choose to override the MIME charset by my defualt charset, so
that I can view all web page by Big5-HKSCS, ignoring the original charset. I
need to change the charset page by page now, which is unconvenient.



Reproducible: Always

Steps to Reproduce:
1. Install the extended BIG5 fonts at the site
http://input.foruto.com/jptxt/fonteudc/Jptxt_Sakura.zip
2. Set the Preferences->Navigator->Languages->Default Character Coding to
"Chinese Traditional (Big5-HKSCS)"
3. Go to the page http://ayakanon.tripod.co.jp/mp3.htm
Actual Results:  
The page is encoded in "Chinese Traditional (Big5)", with incorrect coding of
some characters, as the author of the page has set:
<meta http-equiv="Content-Type" content="text/html; charset=big5">
I need to change the charset to Big5-HKSCS manually.


Expected Results:  
The page should be encoded in my default charset, Big5-HKSCS, automatically.

Comment 1

[Jo Hermans]

You can force it with the "View -> Character Coding" menu. Have you tried
"auto-detect" ? That will try to guess the charset from the content, and works
too when the real charset is different from the declared one.

Comment 2

[Clotho]

Yes, I can force it. But I need to do it page by page everytime, which is
inconvenient.
For auto-detect, it always detects "BIG5" instead of "BIG5-HKSCS"

Comment 3

[Simon Montagu :smontagu]

Is Big5 a subset of Big5-HKSCS? Could we solve this by aliasing?

Comment 4

[Anthony Fok]

Hello Simon,

Well, Big5 is more-or-less subset of Big5-HKSCS (if you only count the
"assigned" range of Big5), but there are subtle differences and other reasons
(future different updates by TW and HK) that we'd better keep the two apart
instead of making Big5 an alias of Big5-HKSCS.

My suggestion is simple.  Just apply the patches listed in Bug 9686 and the
problem will be gone.  (The current Mozilla Big5 table neglects EUDC.)  It would
be great to see the patches finally included in Mozilla 1.4.1.

Thanks,

Anthony

Comment 5

[Simon Montagu :smontagu]

Is this still a problem now that bug 9686 is fixed?

Comment 6

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 7

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.