Wim de Vries wrote: > If I try set p.CreateEntityReferenceNodes(true), I get an error stating
Don't call this method -- use the setFeature method instead. This is the standard way of setting parser features and properties (which we borrowed from SAX2).
Check the Features documentation page for more information.
Tried that already, but the basic problem is that the original char entity references (general internal) are resolved at output. Because all my char references are not (yet) supported by UNICODE, I want to keep them in the output.
If I output UTF8 (which I prefer), instead of UTF16, the char references even end up as something unreadable.
I can't figure out where in the process they are resolved: parser, DOM operations (traversal, copying, inserting) or (output) serializer?
-- Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
With kind regards,
W(im) S. de Vries LL M Information Structure Technologist Electronic Production Department Elsevier Science NL tel. (+31) 20 4852733 fax (+31) 20 4852812
Sara Burgerhartstraat 25 1055 KV Amsterdam The Netherlands
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
