Feature Request: RTL (Arabic/Hebrew) input support in line editing
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- csharp
- Domain
- cli, internationalization
Research direction
Start by reproducing Arabic and Hebrew input at the pwsh prompt in Windows Console Host, then examine PSReadLine's line-buffer rendering and cursor, cut, copy, and paste behavior. Done means RTL text displays in the correct reading order while editing, cursor movement respects RTL runs, and clipboard operations preserve the text.
Written by the indexing model from the issue text.
Description
Feature Request: RTL Text Input Support (Arabic / Hebrew)
Problem
PSReadLine handles all interactive line editing in PowerShell. When an Arabic-speaking user types Arabic text at the pwsh prompt, the characters appear in reversed order because PSReadLine processes input strictly left-to-right. This makes it impossible to type Arabic naturally at the PowerShell prompt.
Expected Behavior
- Arabic (and other RTL) characters should appear in correct right-to-left reading order as the user types
- Cursor movement (
←/→) should respect text direction within RTL runs - Cut/copy/paste operations should preserve RTL text correctly
Current Behavior
Arabic letters are displayed in reversed order (LTR rendering of RTL text), making the input unreadable until submitted.
Environment
- Shell: PowerShell 7.x (
pwsh) — standalone, not inside Windows Terminal - Console host: Windows Console Host (
conhost.exe) - PSReadLine: 2.x
- OS: Windows 11
Suggested Approach
- Implement basic Unicode Bidirectional Algorithm (UAX #9) support in the line buffer rendering
- Detect RTL Unicode ranges (U+0600–U+06FF Arabic, U+0590–U+05FF Hebrew, etc.) and apply correct display order
- This is the highest-impact fix for RTL users since PSReadLine controls all prompt input
Impact
Arabic, Hebrew, Persian, and Urdu speakers cannot type their native language at the PowerShell prompt. This affects a significant global developer community.
Also filed in PowerShell/PowerShell and microsoft/terminal repos for full coverage:
- Dominant language
- C#
- Stars
- 4.4k
- Forks
- 341
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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 PowerShell/PSReadLine
-
Needs-Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSReadLine#5205 ·
-
Needs-Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PowerShell/PSReadLine#5195 ·
-
Needs-Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PowerShell/PSReadLine#5121 ·
-
Needs-Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
PowerShell/PSReadLine#5045 ·
-
Area-CommandHelp Issue-Enhancement
Difficulty 1/5 Under an hour Newbie friendliness 68/100
PowerShell/PSReadLine#3470 · 3 reactions ·
All issues in PowerShell/PSReadLine
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 75/100
sillsdev/languageforge-lexbox#2665 ·
-
bug documentation frontend
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
azurenoops/spin_agent#975 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·