Problems with encoding UTF-8 in Powershell
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 45/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Stack tecnologico
- powershell
- Ambito
- tooling
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- PowerShell
- Stelle
- 335
- Fork
- 80
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di SublimeText/PowerShell
-
tooling
Difficoltà 4/5 3-5 giorni Idoneità per principianti 42/100
SublimeText/PowerShell#226 ·
-
syntax
Difficoltà 3/5 1-2 giorni Idoneità per principianti 55/100
SublimeText/PowerShell#218 · 1 commento ·
-
syntax
Difficoltà 3/5 1-2 giorni Idoneità per principianti 48/100
SublimeText/PowerShell#211 ·
-
build system
Difficoltà 4/5 3-5 giorni Idoneità per principianti 25/100
SublimeText/PowerShell#167 · 2 commenti ·
-
autocomplete
Difficoltà 2/5 1-3 ore Idoneità per principianti 35/100
SublimeText/PowerShell#82 · 6 commenti ·
Tutte le issue di SublimeText/PowerShell
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
nightscout/nocturne#1424 ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Apertaarea: repo bug perceived difficulty: 2
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
impl detach for native Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
paritytech/zombienet-sdk#591 ·
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
mruangutai/harness#1897 ·