On Tue, Aug 30, 2005 at 06:07:44PM +0100, Hamish Lawson wrote:
> Remember that the question of ISO-8859-1 being the default for HTTP
> doesn't come into this - the HTTP standard says nothing about how a
> sender should decide which encoding to use.
I think that it does (from section 3.7.1):
The "charset" parameter is used with some media types to define
the character set (section 3.4) of the data. When no explicit
charset parameter is provided by the sender, media subtypes of
the "text" type are defined to have a default charset value of
"ISO-8859-1" when received via HTTP. Data in character sets
other than "ISO-8859-1" or its subsets MUST be labeled with an
appropriate charset value. See section 3.4.1 for compatibility
problems.
> For unicode objects Quixote is deciding which encoding it *will*
> choose to use; ISO-8859-1 is a poor choice as it will be unable to
> encode the majority of Unicode character points
This is exhausting. Let's break it down:
* If no charset parameter is specified and the content type
is text/*, then the client must interpret the charset as
ISO-8859-1.
Do you agree with that? The HTTP specification is clear on this
point.
* If the client is interpreting the content as ISO-8859-1, then
Quixote should not encode the dat in some other charset.
Do you agree?
Neil
_______________________________________________
Quixote-users mailing list
[email protected]
http://mail.mems-exchange.org/mailman/listinfo/quixote-users
