If you insert the Java representation of the non-breaking space into the element content (through some \u escape probably) then the serializer should convert it to the &#xxxx; representation automatically.
Really? You mean the serializer should look at the encoding of the document, determine that the character cannot be represented in the encoding and automatically convert it to &#nnnn; form?
I don't know that you're wrong; I'm just surprised. It seems quite ambitious to try to know what characters can be represented in all the encodings in the world. (Some encodings even have user-defined spaces, that can be assigned glyphs by local convention.) Does Xerces do that?
Even if a serializer tried to do that, it would have no justification for converting a character to &#nnnn; form if the character was representable in the encoding, and _all_ Unicode characters can be represented in, e.g., UTF-8.
Bob Foster http://xmlbuddy.com/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
