From: Dean Harding (dean.harding@dload.com.au)
Date: Thu Mar 03 2005 - 23:01:25 CST
According to this section of the HTTP/1.1 protocol:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7.1
the default encoding is iso-8859-1, unless otherwise stated. However,
some HTTP/1.1 clients will try to "detect" the encoding, based on
statistical analysis of the text.
Dean.
-----Original Message-----
From: unicode-bounce@unicode.org [mailto:unicode-bounce@unicode.org] On
Behalf Of Doug Ewell
Sent: Friday, 4 March 2005 3:37 pm
To: Unicode Mailing List
Cc: Elliotte Harold
Subject: Re: Bad Content-type headers on Unicode web site?
Elliotte Harold <elharo at metalab dot unc dot edu> wrote:
> The URL
>
> http://www.unicode.org/Public/UNIDATA/NormalizationTest.txt
>
> appears to be served as type text/plain with no charset parameter...
>
> However, that file's contents seem to be UTF-8. Shouldn't this be
> changed to
>
> Content-Type: text/plain; charset=utf-8
>
> or some such?
What is the "default" encoding for text/plain with no charset parameter?
Is there one?
I like to think UTF-8 is "plain text" as much as Latin-1 or anything
else.
-Doug Ewell
Fullerton, California
http://users.adelphia.net/~dewell/
This archive was generated by hypermail 2.1.5 : Thu Mar 03 2005 - 23:02:26 CST