Closed superbonaci closed 11 months ago
If a handful of popular editors automatically mess with the BOM without user input, is there really any point for us to normalize all the BOMs?
It's a matter of consistency, it should compile just fine unless some later VS update forces to.
MSBuild removing BOM handling would be a pretty devastating breaking change, so I don't anticipate that ever happening.
Can .cs files be normalized to BOM in .gitattributes
?
No, the BOM cannot be normalize in .gitattributes
. You can set the text encoding for the local working tree, but UTF-8 with BOM does not seem to be an applicable option and all the documentation and examples I found only mention UTF-16.
Checklist
Edition
Both
Describe your issue here
Some files are coded with BOM:
Other don't:
Looks like files with edited with different file editors or operating systems, and the are mixed up: Comparing changes shows changes to lines that weren't actually changed
Add any related files or extra information here
No response