265430 - chardet.universal_charset_detector

Status: RESOLVED EXPIRED

(Core :: Internationalization, defect)

Description

[Martin Mokrejs]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; X11; Linux i686) Opera 7.54  [en]
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a5) Gecko/20041021

Whenever I start mozilla (current cvs), it spits out messages:

GFX: dpi=87 t2p=0.0588235 p2t=17 depth=16
++WEBSHELL == 1
++DOMWINDOW == 1
++WEBSHELL == 2
++DOMWINDOW == 2
Note: styleverifytree is disabled
Note: frameverifytree is disabled
Note: verifyreflow is disabled
WARNING: GetDefaultCharsetForLocale: need to add multi locale support, file 
nsUNIXCharset.cpp, line 189
WARNING: GetDefaultCharsetForLocale: need to add multi locale support, file 
nsUNIXCharset.cpp, line 189
++WEBSHELL == 3
++DOMWINDOW == 3

I unrolled the View menu option and while moving the mouse over Character 
encoding I get:

intl.charset.detector = universal_charset_detector

When I pick up in the menu come encong, it works:
Charset Overlay menu item pressed: ISO-8859-2
Document about:blank loaded successfully


I have the feeling on startup, mozilla doesn't know which encoding is set
as default. Could it be that "chardet.universal_charset_detector" contains a 
typo in chardet? Those warnings:
GetDefaultCharsetForLocale: need to add multi locale support, file 
nsUNIXCharset.cpp, line 189
make a bit worry. ;)

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[timeless]

reporter: please try to file bugs in relevant components.

Comment 2

[Simon Montagu :smontagu]

What is your locale? If you read the comment at
http://lxr.mozilla.org/seamonkey/source/intl/uconv/src/nsUNIXCharset.cpp#182 you
will see that the warning is not necessarily a sign of anything wrong.

Comment 3

[Martin Mokrejs]

The only variable I have set is LC_CTYPE=cs_CZ to get the keyboard able type
Czech. The rest I prefer in english. ;)

I mozilla I have "by default" ISO-8859-2 under View/Charset encoding.

BTW: There sued to be some years ago a button "Set default encoding". I don't
have it, but seems mozilla starts with the setting used for the last time. If
this is true, I'd prefer having this button back tot he menu. It's clear for
everyone.

Comment 4

[Martin Mokrejs]

Have just unsert LC_CTYPE and started mozilla from scratch. Wow! I have some
different font-type, nothing is marked with the dot in View/Character encoding
menu. I went to mailer to pickup the url of this bugreport, and while writing
this text in browser window, mozilla has itself set the Character encoding to
ISO-8859-2. It's probably because this happened:

Update current mail charset:  
intl.charset.detector = universal_charset_detector
Update current mail charset:  
intl.charset.detector = universal_charset_detector
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file
nsScriptSecurityManager.cpp, line 838
CSS Error (chrome://messenger/skin/messageBody.css :54.6): Unknown namespace
prefix 'html'.  Selector expected.  Ruleset ignored due to bad selector.
mailCharsetLoadListener: ISO-8859-1 
mailCharsetLoadListener: ISO-8859-2 
Document https://bugzilla.mozilla.org/show_bug.cgi?id=265430 loaded successfully
intl.charset.detector = universal_charset_detector
intl.charset.detector = universal_charset_detector
intl.charset.detector = universal_charset_detector
intl.charset.detector = universal_charset_detector
Update current mail charset: ISO-8859-2 
intl.charset.detector = universal_charset_detector
Update current mail charset: ISO-8859-2 
intl.charset.detector = universal_charset_detector

Comment 5

[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 6

[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.