DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24317>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24317 DOMWriter::writeToString ignores encoding ------- Additional Comments From [EMAIL PROTECTED] 2003-11-02 03:49 ------- Hey Alberto, Thanks for the clarification. I understand why the decision was made. However there is a subtle problem. XMLCh* by definition is a UTF-16 encoded string, but for projects like Xerces-P which wrap Xerces-C we may (and do) convert the XMLCh* representation into a Perl (or Python) string representation. So while the UTF-16 assumption is reasonable for Xerces-C, users of other platforms are going to expect something different. I'd like to add a simple note to the documentation that indicates that all encoding information will be discarded and the output encoding will be set to UTF-16. This will help others. So if it's OK with you, I'll commit the doc change to CVS. jas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
