Feature Request: RTL (Arabic/Hebrew) input support in line editing
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 35/100
- Issue 類型
- 功能
- 描述清晰度
- 需要釐清
- 活躍度
- 冷清
- 技術堆疊
- csharp
研究方向
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.
由索引模型根據 Issue 內容生成。
描述
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:
- 主要語言
- C#
- 星號
- 4.4k
- 分支
- 341
- PR 合併指標
- 30 天內沒有已合併 PR
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
PowerShell/PSReadLine 的其他 Issue
-
Needs-Triage :mag:
難度 2/5 1-3 小時 新手友好度 78/100
PowerShell/PSReadLine#5205 ·
-
Needs-Triage :mag:
難度 2/5 1-3 小時 新手友好度 68/100
PowerShell/PSReadLine#5195 ·
-
Needs-Triage :mag:
難度 2/5 1-3 小時 新手友好度 72/100
PowerShell/PSReadLine#5121 ·
-
Needs-Triage :mag:
難度 2/5 1-3 小時 新手友好度 64/100
PowerShell/PSReadLine#5045 ·
-
Area-CommandHelp Issue-Enhancement
難度 1/5 1 小時以內 新手友好度 68/100
PowerShell/PSReadLine#3470 · 3 個 reaction ·
查看 PowerShell/PSReadLine 的全部 Issue
相似的 Issue
-
bug documentation frontend
難度 2/5 1-3 小時 新手友好度 72/100
azurenoops/spin_agent#975 ·
-
難度 2/5 1-3 小時 新手友好度 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
難度 2/5 1-3 小時 新手友好度 92/100
dotnet/AspNetCore.Docs#37699 ·
-
難度 2/5 1-3 小時 新手友好度 72/100
SubtitleEdit/subtitleedit#15108 · 1 則留言 ·
-
area/docs-content Bug pulumi/docs
難度 1/5 1-3 小時 新手友好度 94/100