279162 - in javascript document.write firefox look at utf-8 characters as ascii

Status: RESOLVED INVALID

(Core :: Internationalization, defect)

Description

[Reza Alavi]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

in this site which is in farsi and using utf-8 for encoding, the top most part
of page is generated with document.write("something") where "something" is in
utf-8 but cause the firefox can not recognize it as utf-8 the text will not
render in proper code page.

Reproducible: Always

Steps to Reproduce:
1.for this page you most first install farsi encoding on your system
2.login to the page the upper part of page is in ascii while it most be in utf-8
3.please check it with a test file which you will create in a language that you
can understand, use non-ascii characters in utf-8 encoding as parametrs of
document.wite in a simple javascript script and see the result.

Actual Results:  
the text will be shown as ascii characters which will result in a sequence of
characters which have no meaning

Expected Results:  
the software most recognize this text as utf-8 to.

Comment 1

[Simon Montagu :smontagu]

External javascript files are interpreted in the encoding of the source page,
unless there is a "charset" attribute in the <src> element or the server sends a
Content-Type header including charset information. But if the charset in the
Content-type header is invalid, we will use a default value of ISO-8859-1. This
is true even if there is a "charset" attribute in the <src> element.

In this case the server sends http://iranadwords.com/showvver2.php?id=6 with a
header "Content-Type: text/html; charset=no". If the charset parameter is
corrected to "charset=utf-8", the text should display correctly.

Comment 2

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

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

Comment 4

[timeless]

per comment 1