119510 - joins.com - many pages do not set charset to euc-kr

Status: RESOLVED WONTFIX

(Tech Evangelism Graveyard :: Other, defect, P3)

Description

[Steve Chapel]

Many web pages at the joins.com site do not return a charset in the HTTP header
or meta http-equiv tags. The result is that if you do not explictly select a
Korean charset in View | Character Coding, the Korean text on these pages
appears like: ÄÁÅÙÃ÷¸

The pages include:
http://contents.joins.com/
http://club.joins.com/
http://healthcare.joins.com/
http://patzzi.joins.com/

Comment 1

[Katsuhiko Momoi]

Steve, as far as I know, there is no requirement in the current
web standards that web properties must send charset info. I know
that this is desirable if this is an evangelism bug then there are
literally millions of pages like this aorund the world. I'll confirm
that the problem exists but I am inclined to mark it Wontfix afterward.

Comment 2

[Steve Chapel]

I suppose the concern is that Bugzilla will get flooded with charset Tech
Evangelism bugs. However, I can find only six such bugs currently (including
this one), and two of them are already fixed:
http://bugzilla.mozilla.org/buglist.cgi?product=Tech+Evangelism&short_desc=charset&short_desc_type=allwordssubstr

If Bugzilla does get flooded with these bugs, I wouldn't mind if some of the
minor sites get marked WONTFIX. But joins.com is a major international site and
in my opinion should be encouraged to use charset to indicate what character
coding the browser should use.

Comment 3

[Frankie]

1 year later... 

http://contents.joins.com no longer exists.
http://club.joins.com uses euc-kr.
http://patzzi.joins.com/ uses euc-kr.
http://healthcare.joins.com/ has no encoding set, and displays gibberish.

Comment 4

[Katsuhiko Momoi]

A Korean site problem. Moving to Other.

Comment 5

[Katsuhiko Momoi]

Mrking this as Wontfix since there is no requirement 
that the site has to declare the charset. It is recommended,
yes, but not required. In time, they will fix remaining
problems.
Also most Korean users will have set the default encoding to 
Korean or auto-detection for Korean. Other users who frequent Korean
or other language sites should set auto-detection to Universal,
which will solve this problem. 

This is really a problem that will affect a very small number
of people who don't surf Koran sites or other East Asian language
sites often and therefore don't set the encoding or auro-detection
to an optimal setting.

Comment 6

[Katsuhiko Momoi]

Moving to Other.