Don't put BOM and CRLF in text files

[GoogleCodeExporter]

Text files created with Microsoft Windows contain BOM and CR LF line endings. 
These characters cause problems for the ponomar.net web interface and for the 
Java app running on non-Windows platforms.

We should have an automated script that we REQUIRE Windows-based developers to 
run on their machine before committing their changes to SVN which strips BOM 
and converts line endings to the Unix format (LineFeed ONLY).

Original issue reported on code.google.com by aleksandr.andreev@gmail.com on 22 Aug 2014 at 2:50

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

More information:

UTF-8 encoding is not endianness-sensible and using the BOM with this encoding 
is discouraged by the Unicode standard. Unfortunately some Windows utilities, 
notably Microsoft Notepad, keep on adding a BOM in your UTF-8 files thus 
breaking those application that aren't prepared to deal with it.

Another serious problem is that a BOM will break a UNIX shell script 
interfering with the shebang (#!).

Original comment by aleksandr.andreev@gmail.com on 22 Aug 2014 at 2:54

[GoogleCodeExporter]

At a teleconference between Yuri and Aleksandr, it was decided that nothing 
could be done about this problem, except, perhaps, telling Linux users to run 
their files through dos2linux.

Original comment by aleksandr.andreev@gmail.com on 2 Feb 2015 at 5:53

• Added labels: Invalid
• Removed labels: Priority-High, Type-Task

[GoogleCodeExporter]

Original comment by aleksandr.andreev@gmail.com on 2 Feb 2015 at 5:54

• Changed state: Invalid
• Added labels: Security
• Removed labels: Invalid