starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Add support for Russian characters for PowerShell within #6953

New Issue
Closed
opened 2026-01-31 00:51:24 +00:00 by claunia · 10 comments
claunia commented 2026-01-31 00:51:24 +00:00
Owner
Copy Link

Originally created by @SiarheiKuchukBelitsoft on GitHub (Mar 18, 2020).

This is how it looks now if to type on Russian
image

Originally created by @SiarheiKuchukBelitsoft on GitHub (Mar 18, 2020). This is how it looks now if to type on Russian ![image](https://user-images.githubusercontent.com/60220228/76946420-0fe33680-6915-11ea-81be-a4b836da6207.png)
claunia added the Needs-TriageResolution-ExternalNeeds-Tag-FixProduct-Powershell labels 2026-01-31 00:51:24 +00:00
claunia commented 2026-01-31 00:51:25 +00:00
Author
Owner
Copy Link

@ertyz commented on GitHub (Mar 18, 2020):

it's a system-wide problem. Not a WT. You can see the same issue in your regular PowerShell console.
The reason is: Your current code page in powershell likely is set to "437 (OEM - US)".
To see normal Cyrillic characters it should be set for example to "866 (OEM - Rus)".

You can activate it for whole system in Classic Control Panel -> Region -> Administrative
and set "Current language for non-Unicode programs" to "Russian" (or other Cyr language)

@ertyz commented on GitHub (Mar 18, 2020): it's a system-wide problem. Not a WT. You can see the same issue in your regular PowerShell console. The reason is: Your current code page in powershell likely is set to "437 (OEM - US)". To see normal Cyrillic characters it should be set for example to "866 (OEM - Rus)". You can activate it for whole system in Classic Control Panel -> Region -> Administrative and set "Current language for non-Unicode programs" to "Russian" (or other Cyr language)
claunia commented 2026-01-31 00:51:25 +00:00
Author
Owner
Copy Link

@SiarheiKuchukBelitsoft commented on GitHub (Mar 18, 2020):

@ertyz Thanks. I thought that you were using Unicode and stuff behind the scenes and those setting will go away

@SiarheiKuchukBelitsoft commented on GitHub (Mar 18, 2020): @ertyz Thanks. I thought that you were using Unicode and stuff behind the scenes and those setting will go away
claunia commented 2026-01-31 00:51:25 +00:00
Author
Owner
Copy Link

@SiarheiKuchukBelitsoft commented on GitHub (Mar 18, 2020):

@ertyz Can I ask you to just consider switching to Unicode by-default for PowerShell since it sounds like we have modern technologies with ASCII epoch

@SiarheiKuchukBelitsoft commented on GitHub (Mar 18, 2020): @ertyz Can I ask you to just consider switching to Unicode by-default for PowerShell since it sounds like we have modern technologies with ASCII epoch
claunia commented 2026-01-31 00:51:25 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 18, 2020):

@SiarheiKuchukBelitsoft That might be a request that's better suited for the Powershell repo, powershell/powershell. I'd think that the newer versions of powershell might just handle this better already. The one that's pre-installed on Windows is Powershell 5, and Powershell 7 was just released

@zadjii-msft commented on GitHub (Mar 18, 2020): @SiarheiKuchukBelitsoft That might be a request that's better suited for the Powershell repo, [powershell/powershell](https://github.com/powershell/powershell). I'd think that the newer versions of powershell might just handle this better already. The one that's pre-installed on Windows is Powershell 5, and Powershell **7** was just released
claunia commented 2026-01-31 00:51:26 +00:00
Author
Owner
Copy Link

@SiarheiKuchukBelitsoft commented on GitHub (Mar 18, 2020):

@zadjii-msft Thanks for your input!
@ertyz, Thanks for so fast response!

@SiarheiKuchukBelitsoft commented on GitHub (Mar 18, 2020): @zadjii-msft Thanks for your input! @ertyz, Thanks for so fast response!
claunia commented 2026-01-31 00:51:26 +00:00
Author
Owner
Copy Link

@SiarheiKuchukBelitsoft commented on GitHub (Mar 18, 2020):

I've just checked, Powershell 7 indeed works with Unicode out of the box!

@SiarheiKuchukBelitsoft commented on GitHub (Mar 18, 2020): I've just checked, Powershell 7 indeed works with Unicode out of the box!
claunia commented 2026-01-31 00:51:26 +00:00
Author
Owner
Copy Link

@Aliaksandr3by commented on GitHub (Jan 8, 2021):

[Console]::OutputEncoding = [System.Text.Encoding]::GetEncoding("utf-8")

image

@Aliaksandr3by commented on GitHub (Jan 8, 2021): [Console]::OutputEncoding = [System.Text.Encoding]::GetEncoding("utf-8") ![image](https://user-images.githubusercontent.com/11432724/103971453-aa01bd00-517b-11eb-91bc-0500a6322f50.png)
claunia commented 2026-01-31 00:51:26 +00:00
Author
Owner
Copy Link

@Don-Vito commented on GitHub (Jan 8, 2021):

[Console]::OutputEncoding = [System.Text.Encoding]::GetEncoding("utf-8")

@Aliaksandr3by - Cool! Seems to work in terminal as well:
image

@Don-Vito commented on GitHub (Jan 8, 2021): > [Console]::OutputEncoding = [System.Text.Encoding]::GetEncoding("utf-8") @Aliaksandr3by - Cool! Seems to work in terminal as well: ![image](https://user-images.githubusercontent.com/4639110/103987226-d4ac3f80-5194-11eb-9501-e7d8a67b82f5.png)
claunia commented 2026-01-31 00:51:26 +00:00
Author
Owner
Copy Link

@drweb86 commented on GitHub (Jan 11, 2021):

@Aliaksandr3by It would be better if that it will enabled by default

@drweb86 commented on GitHub (Jan 11, 2021): @Aliaksandr3by It would be better if that it will enabled by default
claunia commented 2026-01-31 00:51:26 +00:00
Author
Owner
Copy Link

@Aliaksandr3by commented on GitHub (Jan 11, 2021):

@Aliaksandr3by It would be better if that it will enabled by default

I use pwsh7
https://github.com/PowerShell/PowerShell

You might use

%windir%\system32\WindowsPowerShell\v1.0
and to create either file:
notepad $pshome\profile.ps1
or
notepad $pshome\Microsoft.PowerShell_profile.ps1
image

@Aliaksandr3by commented on GitHub (Jan 11, 2021): > > > @Aliaksandr3by It would be better if that it will enabled by default I use pwsh7 https://github.com/PowerShell/PowerShell You might use %windir%\system32\WindowsPowerShell\v1.0 and to create either file: notepad $pshome\profile.ps1 or notepad $pshome\Microsoft.PowerShell_profile.ps1 ![image](https://user-images.githubusercontent.com/11432724/104163020-bf3e4c00-5406-11eb-8988-7bc2bb86cab1.png)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Tag-Fix Needs-Triage Product-Powershell Resolution-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6953
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?