Comment 2 for bug 1004084

Toxicity of that test file is due to the description string. A hex dump of the part that prints is:

3f 3f 3f 3f 3f 20 3f 3f 3f 3f 3f 3f 3f 3f e1 6a 3f 23 3f

and this triggers (not sure what this will look like once pasted in):

Entity: line 2: parser error : xmlParseComment: invalid xmlChar value 28
<!-- ????? ???????∟áj♥#♥ -->
                  ^
Entity: line 2: parser error : Start tag expected, '<' not found
<!-- ????? ???????∟áj♥#♥ -->
                  ^

Emergency save activated!
Emergency save completed. Inkscape will close now.

28 is ASCII file separator symbol, not clear if that would print to a Windows command prompt.
Anyway, the problem is seen right after all of the question marks.

Apparently it isn't safe to stuff just any row of binary data into an XML statement. No big surprise there.