Support for Bidirectional text / RTL languages

Open
#3,589 33 comments 75 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust, shell

Research direction

Start by running ls in a directory containing Arabic or Hebrew filenames on macOS 13.4.1 and compare Warp with Terminal, using the screenshots as the expected rendering reference. Done means bidirectional text and RTL filenames display correctly in Warp without affecting the existing terminal output.

Written by the indexing model from the issue text.

Description

enhancement triaged
Discord username (optional)

No response

Describe the bug

Support text written in an RTL language (such as Arabic, Hebrew, Parsian and more)

Using tools like ls for example , I have a lot of file with names n Arabic. Warp displays them incorrectly. while Terminal displays them correctly.

Warp:
image

Terminal:
image

To reproduce

just ls in a directory with Arabic language names.

Expected behavior

See the Terminal screenshot.

Screenshots

No response

Operating system

MacOS

Operating system and version

13.4.1

Shell Version

No response

Current Warp version

v0.2023.08.22.08.03.stable_00

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.