You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cito accepts source files with and without the UTF-8 BOM.
The doc currently recommends using them, because that makes the UTF-8 encoding explicit, which helps many tools, especially on Windows.
There are pros and cons of the BOM which can be discussed here.
The text was updated successfully, but these errors were encountered:
Okay, I've been mistaken. I now checked Visual Studio 2019, Git, TortoiseGit, Windows 10 Notepad, MSYS2 tools such as grep/less/cat and they all read UTF-8 w/o BOM. I use SciTE which supports a ton of programming languages and it can be easily configured to default to UTF-8. Windows more and findstr don't support UTF-8 regardless of the BOM.
I've just removed the recommendation. Thanks a lot!
cito
accepts source files with and without the UTF-8 BOM.The doc currently recommends using them, because that makes the UTF-8 encoding explicit, which helps many tools, especially on Windows.
There are pros and cons of the BOM which can be discussed here.
The text was updated successfully, but these errors were encountered: