180703 - Kanji characters are not shown proparly on a page in which does not define "charset" meta tag/

Status: RESOLVED DUPLICATE of bug 153150

(Camino Graveyard :: Page Layout, defect)

Description

[wp4hizw]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021117 Chimera/0.6+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021117 Chimera/0.6+

After I installed Navigator, Build ID:2002111504, pages that have Kanji without
definition of "charset" meta tag. This could be due to missing the
charset.detector or due to inconsistent with installation of OS X 10.2.2.  

Reproducible: Always

Steps to Reproduce:
1.Opened the url mentioned in this report
2.reload it and clear page cache then opened the url
3.browsed other Japanes pages and found out all the pages did not define
"charset" meta tag. 

Actual Results:  
Kanji in the page were not readable.

Expected Results:  
Kanji in the page were not readable as well, however after changing the
character coding to Autodetect Japanese, showed Kanji correctly.

Comment 1

[kaldari]

I believe this is a result of charset auto-detection being turned off as of the
11-15 build (due to problems such as bug 168526). I'm not a Netscape developer,
so feel free to correct me if I'm wrong. I recommend marking this bug a
duplicate of bug 153150 (Need to be able to control page encodings).

Comment 2

[kaldari]

I suspect the developers will have some kind of solution to the character
encoding problem soon (hopefully). In the meantime, you can turn universal
auto-detect on manually by deleting the following line in all-chimera.js (which
is inside the Chimera package:

pref("intl.charset.detector", "universal_charset_detector");

*** This bug has been marked as a duplicate of 153150 ***

Comment 3

[kaldari]

*** Bug 181966 has been marked as a duplicate of this bug. ***