> 1. Does xerces-c_1_1 support encoding="UTF-16" ?
>    Because I tried this encoding and results were
> negative.

Try adding the endian -- "UTF-16LE" (for little endian) or "UTF-16BE" 
(for big endian).

If I remember correctly, some UTF-16 related bugs were fixed recently. 
Xerces 1.4 is probably a better all-around choice in any case, since 
there have been a _lot_ of bug fixes and enhancements since 1.1.

--Bill

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to