6 ms·
Putting a BOM in UTF-8 is just silly. Unlike -16, there's no option for which order you put the bytes in. The only time you'll see a BOM in UTF-8 is in poorly
by mcpherrinm 10y ago
Putting a BOM in UTF-8 is just silly. Unlike -16, there's no option for which order you put the bytes in. The only time you'll see a BOM in UTF-8 is in poorly converted UTF-16.
- slavik81 10y agoApparently, Powershell requires a BOM to recognize UTF-8 scripts. https://github.com/chocolatey/choco/wiki/CreatePackages#character-encoding https://github.com/chocolatey/choco/wiki/CreatePackages#char...
- codeulike 10y agoYep, but a lot of MS software will only read UTF-8 correctly if a BOM is present.