W3C home > Mailing lists > Public > www-xml-xinclude-comments@w3.org > February 2004

RE: accept-charset vs. encoding

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Wed, 25 Feb 2004 15:56:20 -0800
Message-ID: <DF1BAFBC28DF694A823C9A8400E71EA202B9552A@RED-MSG-30.redmond.corp.microsoft.com>
To: "Elliotte Rusty Harold" <elharo@metalab.unc.edu>, <www-xml-xinclude-comments@w3.org>

The removal of the accept-charset attribute makes this issue obsolete.

> -----Original Message-----
> From: www-xml-xinclude-comments-request@w3.org
[mailto:www-xml-xinclude-
> comments-request@w3.org] On Behalf Of Elliotte Rusty Harold
> Sent: Wednesday, November 12, 2003 1:04 PM
> To: www-xml-xinclude-comments@w3.org
> Subject: accept-charset vs. encoding
> 
> 
> Now that we have accept-charset do we still need the encoding
> attribute? Or do we need acceptCharset given that we have encoding?
> 
> I'm know they aren't quite the same thing, but are you ever going to
> want to set the encoding attribute to anything other than the charset
> you use in acceptCharset? You might specify several charsets in
> accept-charset, but if you do that what will the encoding attribute
> mean anyway? You probably won't have it? Could we get by with one
> attribute here instead of two?
> --
> 
>    Elliotte Rusty Harold
>    elharo@metalab.unc.edu
>    Effective XML (Addison-Wesley, 2003)
>    http://www.cafeconleche.org/books/effectivexml
> 
>
http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaula
it
> A
> 
Received on Wednesday, 25 February 2004 18:56:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:09:34 UTC