185590 - problem with this sign (�) in every page with charset=iso-8859-9

Status: RESOLVED INVALID

(Core :: Internationalization, defect)

Description

[Fuat Taneri]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021214
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021214

http://www.fenerbahce.com/haber/haber_oku.php?frm_id=2580


Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[R.K.Aa.]

i see several "?" at http://www.stargazete.com/ when testing on Linux
The other URL doesn't allow connections. Changing component.

Comment 2

[Simon Montagu :smontagu]

Background information: 

As in the case for many other languages, the Windows Turkish codepage
(windows-1254) is a superset of ISO-8859-9, and many codepoints in the range
0x80-0x9F which are undefined in ISO-8859-9 are defined in windows-1254. In this
and parallel cases (e.g. windows-1252 and ISO-8859-1, windows-1255 and
ISO-8859-8, etc.) Internet Explorer will display the characters from the
relevant Windows codepage even when the browser is set to the ISO codepage
(either manually or by a charset declaration in a document). Mozilla does the
same at least for cp1252/ISO-8859-1, but not in all cases, and specifically not
for Turkish.

Of the two URLs listed here,
http://www.fenerbahce.com/haber/haber_oku.php?frm_id=2580 contains

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-9">

and http://www.stargazete.com/ hedges its bets with 

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-9">
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1254">

I believe there is another open bug on how to handle dual charset declarations,
but I haven't succeeded in finding it. Leaving that issue on one side, this bug
is strictly speaking either INVALID or Evangelism, because the characters
displayed as question marks are not defined in ISO-8859-9. On the other hand, we
might want to become more consistent and treat ISO codepages as equivalent to
the Windows supersets whenever possible.

Comment 3

[Simon Montagu :smontagu]

For the time being you can work around the problem by manually selecting Turkish
(Windows-1254) from View | Character Coding | SE & SW Asian.

Comment 4

[Christopher Hoess (gone)]

I'd vote for Evang on the grounds that we really don't want to encourage 
the proliferation of Windows-specific character sets disguised as ISO, but 
you have a better idea of the charset picture than I do.

Comment 5

[Frank Tang]

Estimate work- 0.5 develping days. 

Comment 6

[Frank Tang]

assign

Comment 7

[Frank Tang]

what a hack. I have not touch mozilla code for 2 years. I didn't read these bugs
for 2 years. And they are still there. Just close them as won't fix to clean up.

Comment 8

[Travis Chase]

Mass Re-open of Frank Tangs Won't fix debacle. Spam is his responsibility not my own

Comment 9

[Travis Chase]

Mass Re-assinging Frank Tangs old bugs that he closed won't fix and had to be
re-open. Spam is his fault not my own

Comment 10

[Jean-Marc Desperrier]

INVALID.

Use of windows-1252 inside iso-8859-1 labeled pages is a thing nobody can
succesfully oppose against, but we should not encourage a similar confusion for
other character sets. That's what comment #2 et #4 concluded, before FT decided
to assign to himself.