From: Geoff M. <ub...@ge...> - 2012-05-06 13:49:49
|
On Sun, 2012-05-06 at 10:39 +0200, ThorstenB wrote: > Am 05.05.2012 21:10, schrieb ThorstenB: > > What do we do? Ask maintainers to fix each XML file? Run a script to fix > > these issues on fgdata? Suggestions? > > After discussing with Helijah, the issue is now fixed for all files in > fgdata. A few files belonging to other maintainers were also involved > and corrected - since there isn't really a valid reason leave any files > in an unreadable state. > > cheers, > Thorsten Hi Thorsten, Thanks for summarily fixing the xml encoding declaration to ISO-8859-1 on a number of xml files ;=)) Now no XML parsing errors so far... Just for curiosity, delved a little further, prior to your changes, well git of 2012/03/30, and found some 21,000 files ending '.xml' in fgdata, some 8 million lines, 237 MB! The largest is AAL.xml 20 MB, 600 K lines, 2 blank files, 1 with a UTF-8 BOM, 36 with ISO-8859-1 encoding declaration, 7733 with UTF-8, 1 with Windows-1250, 12328 with no encoding, and 900 with NO <?xml declaration at all! After your commit of what, some 300+, xml file changes, and of others since 30/03, now 21,229 xml files, 234 MB, there is no BOM, 336 with ISO-8859-1, 7635 with UTF-8, 1 Windows-1250, 12353 with NO encoding, and 902 with NO <?xml declaration... Now back to FLYING ;=)) Regards, Geoff. |