W3C home > Mailing lists > Public > www-svg@w3.org > November 2004

Re: SVG 1.2 Comment: image/svg+xml;charset=""

From: Chris Lilley <chris@w3.org>
Date: Wed, 24 Nov 2004 23:28:13 +0100
Message-ID: <02037276.20041124232813@w3.org>
To: Anne van Kesteren <fora@annevankesteren.nl>
Cc: Robin Berjon <robin.berjon@expway.fr>, Bjoern Hoehrmann <derhoermi@gmx.net>, <www-svg@w3.org>

On Wednesday, November 24, 2004, 10:55:31 PM, Anne wrote:

AvK> Chris Lilley wrote:
>> Thanks for responding. I agree that UTF-8 is correct for those two
>> examples. Now please read
>> 8.9 Application/xml with Omitted Charset and UTF-16 XML MIME Entity
>> and tell me why you believe this gets a UTF-8 charset when RFC 3023
>> clearly dsays that it gets UTF-16?

AvK> Because it has a BOM before the start of the document

You mean, it has one and is thus UTF-16 (what the spec says) or , it has
one and is still UTF-8 (what you said)?

AvK> where your example does not? Quite obvious IMHO.

Of course mine does, as I said, the following content, encoded in UTF 16
thus it has one.

My point, in case you had not understood it, is that you made an
incorrect statement. You said that in the absence of a charset parameter,
the default is *always UTF-8*

This is incorrect (I had hoped that by asking you to back up your
assertions with text from the relevant specifications, you would have
discovered this for yourself).

In the absence of a charset parameter, the encoding is whatever the xml
encoding declaration says it is. To quote RFC 3023, section 3.6, second
bulleted list, second point:

  If the charset parameter is omitted, conforming XML processors MUST
  follow the requirements in section 4.3.3 of [XML].

For 4.3.3, see

 Chris Lilley                    mailto:chris@w3.org
 Chair, W3C SVG Working Group
 Member, W3C Technical Architecture Group
Received on Wednesday, 24 November 2004 22:28:14 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:01 UTC