Can the ncName be mapped for a given encoding
See default SF for logic on this, however faulty :-)
Override this to order the attributes.
LSSerializer in 6_24 is garbage, but the xalan one isn't much better.
LSSerializer in 6_24 is garbage, but the xalan one isn't much better. jre uses hex, xalan numberic character refs. And jre is totally useless for cdata, writing no end part, both ignore the split-cdata-sections option when escaping, choosing to split, I assume this is only being done for character refs but follows the DOMConfiguration (instead of the load and save spec) for end sequence splitting.
As such there only seems to be one safe way to handle this: # Use the encoder to check if a CData or Comment can be written without splitting, throw if it can't. # Write the start and end CData directly
Performs the actual write for Comments/CData/PI, due to LSSerializer issues this function is seperated for easy overriding, should anyone really trust their DOM/JAXP versions.
Performs the actual write for Comments/CData/PI, due to LSSerializer issues this function is seperated for easy overriding, should anyone really trust their DOM/JAXP versions.
For this method to be called the encoding has already been verified.
Default serializer, correctness first. Uses the LSSerializer present in each DOM L3 impl. XmlItems are always serialized with the LS, elements and attributes are however for speed reasons, verified for encoding once per QName; the attribute values themselves are written via Text nodes and LS.