W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2002

RE: DOMString Character Encoding

From: Allen, Michael B (RSCH) <Michael_B_Allen@ml.com>
Date: Tue, 19 Feb 2002 19:06:13 -0500
Message-ID: <2D31030A810FD611973700306E0208F61997C6@ehope07.hew.us.ml.com>
To: "'Philippe Le Hegaret'" <plh@w3.org>
cc: "WWW DOM" <www-dom@w3.org>

> -----Original Message-----
> From:	Philippe Le Hegaret [SMTP:plh@w3.org]
> Sent:	Tuesday, February 19, 2002 6:53 PM
> To:	Allen, Michael B (RSCH)
> Subject:	RE: DOMString Character Encoding
> On Tue, 2002-02-19 at 18:40, Allen, Michael B (RSCH) wrote:
> > > big endian or little endian is platform dependent. I don't think that
> > > the BOM doesn't have anything to do in a DOMString.
> > > 
> > 	Internally I doubt Java Strings have BOMs but if you serialize one they sure do.
> sure but then this is an issue for the serializer, not the DOMString
> itself. I don't think we need to specific and define what happen
> regarding the BOM. I expect the XML specification to be clear on that if
> needed.
	I'm sorry, I didn't mean to make BOMs the issue. I was just trying to make
	the point that character encoding is totally irrellivant to DOMString just as it
	is to Java's String type which is refereneced in the section in question.

Received on Tuesday, 19 February 2002 19:07:27 UTC

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