Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
XMLSerializer and Character Encoding

XMLSerializer and Character Encoding

2003-11-12       - By Adrian Sutton

Hi all,
I'm probably dreaming here and what I'm doing is just outside of the realms
of possibility but let me try anyway. :)

I'm in a situation where I need to take XML documents from different
encodings (anything supported by the particular Java instance), make a few
changes to them, and output them all using the same encoding.  Now were
these random text files that would nessecarily involve screwing up a bunch
of characters because they're not supported in the target charset, however
with XML, any character can be represented in entity form so the process I'd
like is:

1. Create a DOM object by parsing with the input encoding for the document
(taken from the <?xml ...?> declaration.

2. Manipulate the DOM

3. Use XMLSerializer to serialize the DOM in the target encoding -
converting any characters not supported by the target encoding to their
entity form.

Unfortunately, XMLSerializer doesn't convert the unrepresentable characters
to their entity form and they wind up getting corrupted.

The particular piece of code I'm using for serializing the DOM is:

   XMLSerializer ser = new XMLSerializer(new OutputFormat(doc,
_outputCharset, false));
       ser.setNamespaces(true);
       ByteArrayOutputStream out = new ByteArrayOutputStream();
       ser.setOutputByteStream(out);
       ser.serialize(doc);
       String result = new String(out.toByteArray(), _outputCharset);
       return result;

Couple of notes:
a. I realize it's pointless to convert to a byte array and back to a String,
mostly I want XMLSerializer to convert the unsupported characters to
entities and also the output will likely be redirected to a "real" output
stream at some point.

b. I'm already very much tied into Xerces so have no qualms about using XNI
or any other unsupported trickery to get what I need to do done.  I don't
see us changing the version of Xerces we're using any time soon.

So is there a way to escape characters that aren't supported in a particular
encoding or should I extend XMLSerializer and do it myself?  Am I completely
insane for attempting this?

Regards,

Adrian Sutton, Software Engineer
Ephox Corporation
www.ephox.com

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)