Fix/xml escape

partial fixes for #24 

- escape some XML when writing mzXML and mzML
- try to fix the worst offenders
- test for some attributes in mzML
we could check the CV file during loading for invalid terms (ie do it 
once) -- and throw an error or handle it otherwise.

Am 8/21/2014 10:42 AM, schrieb Hannes Roest:
>> @@ -3573,11 +3567,11 @@ namespace OpenMS
>>         }
>>         else if (so_term.id != "")
>>         {
>> -        os << "\t\t\t<cvParam cvRef=\"MS\" accession=\"" << so_term.id << "\" name=\"" << so_term.name << "\" />\n";
>> +        os << "\t\t\t<cvParam cvRef=\"MS\" accession=\"" << so_term.id << "\" name=\"" << writeXMLEscape(so_term.name) << "\" />\n";
>
> good point, however my reasoning was first and foremost to write valid XML. So with this goal, it seemed best to escape user-supplied (or potentially user-supplied) in a very general basis strings. I think that CV term names fall under this category since they are read from a file during runtime, so potentially a user could supply them,
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/OpenMS/OpenMS/pull/949/files#r16526649
>