XML generated for report text of reporting results of For loop contravenes W3 XML spec

[GarryG]

Using the stock reportgen_xml.seq file, the text value of the XML node shouldn't contain the characters < or >:

http://www.w3.org/TR/xml/#syntax

When using LabVIEW VI's to parse this, you (rightly) get errors, so it's incredibly difficult to just search and replace the offending characters with their XML escapes. 

Example node contents from the XML report:

<Prop Name='ReportText' Type='String' Flags='0x400000'>
                            <Value><![CDATA[{0} Locals.i = 0; Locals.i < 2; Locals.i += 1]]></Value>
                        </Prop>

[Darin.K]

Wait!  Those characters are inside of a CDATA section?  That should be valid.  The .NET parser handles it with ease.

I commend the TS folks for getting it right, but I think there needs to be coordination with the LV team so that TS only generates XML that the LV parser can handle.  Of course that means an upgrade of the LV parser, not a degradation of the TS code.

[GarryG]

Yeah, let's decline this one and throw it back to the LabVIEW IE.

[WireWeaver]

I'm declining this idea due to lack of community support.