Problems with encoding UTF-8 in Powershell
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- powershell
- Domain
- tooling
Research direction
Start with PowershellSyntax.sublime-settings and reproduce the UTF-8 and UTF-8 with BOM behavior on Windows with the UTF-8 beta feature disabled. Check the related build-panel behavior and the effect of running chcp.exe; done means an agreed encoding behavior is validated for the affected PowerShell and build workflows, including the compatibility concern for Linux and PowerShell Core users.
Written by the indexing model from the issue text.
Description
Per default Windows 10 and Windows 11 do not use UTF-8 unless you manually enable as a Beta feature under Region Settings in intl.cpl
Without that setting enabled both Sublime and Powershell are having problems reading and displaying special characters such as "åäö".
Here is an example below on a machine without UTF-8 enabled running files from the Powershell console.
File encoding: UTF-8
File encoding: UTF-8 with BOM
As you can see Powershell is unable read the string when the file encoding is "UTF-8" and everything works fine when the encoding is set to "UTF-8 with BOM".
Here is another example with the Build Panel is Sublime Text
File encoding: UTF-8
File encoding: UTF-8 with BOM
As you can see the output is still wrong in the Build Panel even when the encoding is set to "UTF-8 with BOM". But it can be fixed by running chcp.exe in cmd
And then changing the encoding settings in the build job.
As stated before this is only an issue when the UTF-8 Beta feature in Windows is disabled. If you enable UTF-8 support the Sublime Text build panel and powershell console works without any issues.
I am not sure how to handle the build panel problem but at least changing the default encoding format for Powershell files to "UTF-8 with BOM" would prevent scripts processing special characters from causing unwanted bugs. This could probably be done by updating PowershellSyntax.sublime-settings with "default_encoding": "UTF-8 with BOM". But I am not sure how that would affect Linux or Powershell Core users.
- Dominant language
- PowerShell
- Stars
- 335
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SublimeText/PowerShell
-
tooling
Difficulty 4/5 3-5 days Newbie friendliness 42/100
SublimeText/PowerShell#226 ·
-
syntax
Difficulty 3/5 1-2 days Newbie friendliness 55/100
SublimeText/PowerShell#218 · 1 comment ·
-
syntax
Difficulty 3/5 1-2 days Newbie friendliness 48/100
SublimeText/PowerShell#211 ·
-
build system
Difficulty 4/5 3-5 days Newbie friendliness 25/100
SublimeText/PowerShell#167 · 2 comments ·
-
autocomplete
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
SublimeText/PowerShell#82 · 6 comments ·
All issues in SublimeText/PowerShell
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
idean3885/claude-ops-agent#521 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
0xMiden/bridge-portal#132 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
newrelic-experimental/preflight#793 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
babalae/bettergi-scripts-list#3674 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
caddyserver/caddy#8046 ·