W3C home > Mailing lists > Public > www-international@w3.org > July to September 2003

Fwd: Re: Mojibake on my Web pages

From: Asmus Freytag <asmusf@ix.netcom.com>
Date: Wed, 24 Sep 2003 10:18:55 -0700
Message-Id: <4.2.0.58.20030924101629.01da0da0@popd.ix.netcom.com>
To: www-international@w3.org

This issue has been raised on the unicode@unicode.org list.

A./


>From: "Doug Ewell" <dewell@adelphia.net>
>To: "Unicode Mailing List" <unicode@unicode.org>
>Subject: Re: Mojibake on my Web pages
>Date: Wed, 24 Sep 2003 08:32:42 -0700
>
>Stefan Persson <alsjebegrijptwatikbedoel at yahoo dot se> wrote:
>
> > Is there no way to force the browsers to use the encoding as specified
> > in the documents instead of that specified by the server?  I'm having
> > this problem myself with a different server, and would like to find a
> > solution to it.
>
>I can always visit View | Encoding and change the setting to UTF-8 on a
>one-time basis.  But as soon as the page is refreshed, it reverts to
>whatever the server specifies.
>
>I don't know if there's a way to teach IE that a given URL should
>*always* be overridden to UTF-8, but even if there was, that would only
>help me and those who know the secret.  It should work for everybody.
>
> > It is very irritating that the HTTP header overrules the <meta> tag,
> > since it seems that the error is more often in the HTTP header than in
> > the <meta> tag.
>
>Indeed.  You'd think if the author (or software) included a <meta> tag
>AND an explicit declaration in the XML header, he (or it) knew what he
>(or it) was doing and the tag(s) should be honored.
>
>Apologies to the list if this is getting OT.
>
>-Doug Ewell
>  Fullerton, California
>  http://users.adelphia.net/~dewell/
---------------------------------------------
>To: "Unicode Mailing List" <unicode@unicode.org>
>Subject: Mojibake on my Web pages
>
>Apologies in advance to anyone who visits my Web site and sees garbage
>characters, a.k.a. "mojibake."  It isn't my fault.
>
>Adelphia is currently having a character-set problem with their HTTP
>servers.  Apparently they are serving all pages as ISO 8859-1 even if
>they are marked as being encoded in another character set, such as
>UTF-8.  So, instead of seeing U+2022 BULLET on my page, for example,
>you'll see:
>
>     •
>
>If you manually change the encoding in your browser to UTF-8, or
>download the page and display it as a local file, everything looks fine
>because Adelphia's server is no longer calling the shot.  Their tech
>support people acknowledge that the problem is at their end and said
>they would look into it.
>
>I understand that having the "Unicode Encoded" logo on my page next to
>these garbage characters may not reflect well on Unicode, especially to
>newbies.  I'm considering putting a disclaimer at the top of my pages,
>but I'm waiting to see how quickly they solve the problem.
>
>-Doug Ewell
>  Fullerton, California
>  http://users.adelphia.net/~dewell/
Received on Wednesday, 24 September 2003 13:16:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:17:02 GMT