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=13447>. 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=13447 DOMWriter doesn't work correctly [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2002-11-27 18:40 ------- For Jan's issues: 1. FormatPrettyPrint - bugzilla bug 13840 addresses this issue. So please refer to there for further discussion. 2. LocalFileFormatTarget is slow - this is now fixed. 3. Cannot write as UTF-8 - this one works for me. Currently the DOMWriter works like this: 1. If the encoding attribute of DOMWriter has been set, that value will be used. 2. else, if the item to be written or the owner document of the item, has the attribute "actualEncoding" specified, that value will be used. 3. If neither of the above, a default encoding of "UTF-8" will be used. I've tested this and it seems to work as expected. And for Robin's question: - The DOM spec says: Issue LS-Issue-79: [..snipped ..] Resolution: writeToString() always writes into a DOMString, which means it's always UTF16. The encoding information available is always ignored in writeToString(). Description updated to reflect this. So writeToString always returns UTF-16 working as designed. And your approach to get encoding string sounds ok. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
