MantisBT - CMake
View Issue Details
0015637CMakeCTestpublic2015-07-01 10:322015-07-02 08:45
Zach Mullen 
Zach Mullen 
normalminoralways
closedfixed 
 
 
0015637: Consider escaping all utf8 chars in XML test output
Right now, any characters we deem non-printable are escaped in a non-standard way, e.g.:

    "[NON-XML-CHAR-0x1B]"

Instead of the standard NCR escaping: "&#x1B". I propose that we change to using NCR escaping to provide more portable XML and let CDash (or other consumers of the XML) decide how to render those characters. For instance, my personal use case involves terminal control characters -- services like travis render colors and styles in the web UI just as they would appear in a terminal, and it would be nice to enable CDash to do the same thing without having to look for our nonstandard string.
No tags attached.
Issue History
2015-07-01 10:32Zach MullenNew Issue
2015-07-01 10:53Nils GladitzNote Added: 0039004
2015-07-01 11:08Zach MullenNote Added: 0039005
2015-07-01 11:18Zach MullenNote Edited: 0039005bug_revision_view_page.php?bugnote_id=39005#r1814
2015-07-01 11:18Zach MullenStatusnew => closed
2015-07-01 11:18Zach MullenAssigned To => Zach Mullen
2015-07-01 11:18Zach MullenResolutionopen => fixed

Notes
(0039004)
Nils Gladitz   
2015-07-01 10:53   
I don't think XML containing a character reference for 0x1B would be well formed since the codepoint still is required to follow the char production

  http://www.w3.org/TR/REC-xml/#NT-Char [^]

which excludes 0x1B.
(0039005)
Zach Mullen   
2015-07-01 11:08   
(edited on: 2015-07-01 11:18)
Good point Nils. I guess one alternative would be base64-encoding the output, but that incurs more space.

Given that caveat, I think it may be easier to simply have CDash handle the current escaped values. I will close this.