CRLF/LF mix-up and UTF-8 with BOM about range-v3 HOT 6 CLOSED

Here is a list of files with CRLF line endings.

and

from range-v3.

I also noticed that some files use UTF-8 with BOM.
Is it OK if I change encoding to UTF-8 (without BOM) for files other than libs/range/v3/scratch/*?

Here is a list of files encoded in UTF-8 with BOM.

• TODO.md
• doc/index.md
• doc/std/D4128.md
• doc/std/header.html

and

• libs/range/v3/scratch/range.sln
• libs/range/v3/scratch/range.vcxproj
• libs/range/v3/scratch/range.vcxproj.filters

from range-v3.

Is it OK if I change encoding to UTF-8 (without BOM)

Can I ask why?

from range-v3.

Is it OK if I change encoding to UTF-8 (without BOM)

Can I ask why?

Because some editors do not work well with UTF-8 with BOM. When I fixed typo, my editor silently removes BOM...

I admit that this is a negligible problem. If you prefer not to change the encoding, that's fine.

from range-v3.

Thanks for fixing the issue!

from range-v3.

Looks like my editor of choice (Visual Studio), really wants there to be a BOM on UTF-8 files. I can remove it, but the next time I open the file, it asks me about the encoding, and then puts the BOM back.

I'm going to close this, but I'll be aware of the BOM issue and if it starts causing problems I'll figure something out.

from range-v3.