XmlDocument.Load替换“>”

Question

When running the following code:

 static void Main(string[] args)
    {
        var xmlDoc = new XmlDocument();

        var fileReader = new BinaryReader(File.Open(@"C:\Users\username\Desktop\doc.xlf",FileMode.Open,FileAccess.Read,FileShare.Read));
        var sourceStream = new MemoryStream(fileReader.ReadBytes((int)fileReader.BaseStream.Length));
        xmlDoc.Load(sourceStream);
    }

On a file with a node that looks like this:

<source xml:lang="en-us">
        &lt;b>This text is displayed in Bold.&lt;/b>&lt;br>
        &lt;i>This text is displayed in italics.&lt;/i>
</source>

The node gets converted to the following when it is read in:

<source xml:lang="en-us">
        &lt;b&gt;This text is displayed in Bold.&lt;/b&gt;&lt;br&gt;
        &lt;i&gt;This text is displayed in italics.&lt;/i&gt;
</source>

In other words, all > are being replaced with >

Normally that would be OK (and I am even under the impression that it would be technically legal, even if bad practice), but in this case it is absolutely imperative that the node not change when it is read in. Any thoughts on either (1) how to read in the xml to allow > or (2) how to work around this issue? Thanks!

Answer 1

Although the right angle bracket is legal in XML, there is no option on XmlDocument to avoid changing it to the corresponding entity.

You could use a CDATA section instead:

<source xml:lang="en-us">
    <![CDATA[&lt;b>This text is displayed in Bold.&lt;/b>&lt;br>
&lt;i>This text is displayed in italics.&lt;/i>]]>
</source>

Answer 2

There is no difference in XML between > and > in values of text nodes. So XML parser/DOM is free to represent value in either form as it see fit.

Note that there are other normalizations in XML (whitespace and new lines) which almost guarantee that saved XML will not be byte-by-byte identical to source XML.

If you really need to keep > intact try using CDATA, also even that guarantees that text will not be touched - some parsers may let you keep > instead of converting to > on save.

Real solution is to accept the fact that some characters will be encoded (including non-ASCII characters if saved with encoding that does not directly support) on save to produce valid XML.