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
Do not save your *.nuspec files with a Byte Order Mark (BOM). A BOM is neither required nor recommended for UTF-8, because it can lead to several issues.
This is largely FUD; while it is possible to have issues with older programs, there are more benefits than not to contain a BOM.
PowerShell scripts need to be saved in UTF-8 with BOM. PowerShell is ignoring the standards and needs a BOM in order to recognize scripts as UTF-8. Otherwise it processes non ASCII characters incorrectly.
I realized many of by PS1 files do not have a BOM.
The text was updated successfully, but these errors were encountered:
The notes at https://github.com/chocolatey/choco/wiki/CreatePackages#character-encoding regarding BOMs is inaccurate. The wiki needs to get updated.
This is largely FUD; while it is possible to have issues with older programs, there are more benefits than not to contain a BOM.
I realized many of by PS1 files do not have a BOM.
The text was updated successfully, but these errors were encountered: