This repository was archived by the owner on Dec 8, 2021. It is now read-only.
Add UTF-8 BOM for PowerShell files #101
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On English Windows version. What about localized Windows version? |
Yes, it may differ. That's one more reason to add a UTF-8 BOM to files interpreted by Windows PowerShell. 😄 |
rjmholt
approved these changes
Sep 1, 2020
iSazonov
approved these changes
Jul 4, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed in #100, Windows PowerShell defaults to the Windows-1252 file encoding, so the UTF-8 BOM may be needed to avoid encoding issues in PowerShell files.
https://docs.microsoft.com/powershell/scripting/dev-cross-plat/vscode/understanding-file-encoding