- From: Justin Couch <justin@vlc.com.au>
- Date: Mon, 23 Jul 2001 23:18:02 +1000
- To: xml-dev@lists.xml.org
- CC: www-xml-blueberry-comments@w3.org
Elliotte Rusty Harold wrote: > >example, the DOM would require two-passes to serialize > >(one to see if Bluberry is used, to set the header, and > >one to do the output) for some implementations. > > > > That would be a naive approach. DOM could easily be implemented so > this was not an issue. For example, give every element, attribute, > and processing instruction a boolean usesBlueberry flag. Then have > the document keep a reference count of the number of Blueberry items > in the document that could be incremented and decremented as nodes > were added to the document. I don't believe so, at least from the Java perspective. DOM passes everything thing in as a String. All the underlying DOM implemenation needs to do is check what encoding is used for that string. If it finds something that is not US-ASCII then it sets the useBlueberry flag internally and off it goes. As for other languages, can't comment, but I suspect at least similar string handling capabilities exist for dealing with internationalisation issues (even just look at the CodePage of the underlying system for a tip) -- Justin Couch http://www.vlc.com.au/~justin/ Freelance Java Consultant http://www.yumetech.com/ Author, Java 3D FAQ Maintainer http://www.j3d.org/ ------------------------------------------------------------------- "Humanism is dead. Animals think, feel; so do machines now. Neither man nor woman is the measure of all things. Every organism processes data according to its domain, its environment; you, with all your brains, would be useless in a mouse's universe..." - Greg Bear, Slant -------------------------------------------------------------------
Received on Monday, 23 July 2001 09:15:39 UTC