On 5 May 2012, at 20:10, ThorstenB wrote: > This is actually showing to be a really bad issue. We have loads of XML > files with invalid encodings. Also, there's many files which even > explicitly state > <?xml version="1.0" encoding="UTF-8"?> > so they are explicitly asking for UTF-8 decoding - but then these files > still contain non-UTF-8 (usually Latin1 byte codes). So, even changing > the parser's default to use Latin1 (which would be hack anyway) wouldn't > help. > > List of files with invalid encodings (will be rejected by the parser > now) is attached. > > What do we do? Ask maintainers to fix each XML file? Run a script to fix > these issues on fgdata? Suggestions?
Ooof :( Run a script gets my vote, but I had no idea I was opening up such an issue when I made this change. James ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
