W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2003

RE: i18n reviews of DOM 3 Core and Load&Save

From: Francois Yergeau <FYergeau@alis.com>
Date: Fri, 3 Oct 2003 15:11:23 -0400
Message-ID: <F7D4BDA0E5A1D14B99D32C022AEB73660EB3B2@alis-2k.alis.domain>
To: "'Johnny Stenback'" <jst@w3c.jstenback.com>
Cc: "'www-dom@w3.org'" <www-dom@w3.org>

Johnny Stenback wrote:
> Francois Yergeau wrote:
> > LS5) In DOMSerializer, the contents of the encoding 
> pseudo-attribute of the
> > XML (or text) declaration is underspecified.  It should be 
> specified that
> > this MUST be the actual encoding that is used for output, 
> whatever the
> > source that determined that was.
> Agreed. The spec was clarified to state that when an XML decl 
> is output, the encoding is always included in the XML decl.

Looking at the latest internal spec
rializer), I see this within the description of the true value of the
xml-declaration parameter of the config attribute of LSSerializer (phew!
that's deep!):

« The version [...] and the output encoding (see LSSerializer.write for
details on how to find the output encoding) is specified in the serialized
XML declaration. »

This is fairly satisfactory, apart from a little grammatical problem
(s/is/are/) and the following issue:  Charmod section 3.6.2
ngIdent) says that "[S]  If the unique encoding approach is not taken,
specifications SHOULD mandate the use of the IANA charset registry names,
and in particular the names identified in the registry as 'MIME preferred
names', to designate character encodings in protocols, data formats and
APIs."  XML 1.0 (and the upcoming 1.1) also mandate IANA names, or x- for
private encodings.

We would appreciate if you could add a little bit of text (or a ref to
Charmod 3.6.2) to properly mandate IANA encoding names.


François Yergeau
Received on Friday, 3 October 2003 15:14:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:11 UTC