Comment 19 for bug 2002290

Hi Egmond.

Thank you for the info.

About lam-alif: Yes, you are right. It indeed is displayed like a U in my screenshot, although it should have been similar to a "y", but as you said, it is not that terribly bad and can be read without an issue. Perhaps we can improve it in a future work!

About RTL bug:

I have searched and found the following file from you regarding the modes you described: https://github.com/skirino/vte/blob/master/perf/bidi.sh

And I tried the following modes:
- alias ltr='printf "\e[1 k"'
- alias rtl='printf "\e[2 k"'

I attached images for how they look like (Also a 3rd screenshot for autodetect again).

The RTL base one would have been good if the user is expected to write everything 100% in Arabic. However that's not the case; normal commands are written in English but the output of the commands may be Arabic, and some strings may not be translated. You can see how the Shell interrupter is displayed totally missed up if you write one line in English, and the other line in Arabic. In fact, if you try to write in English using RTL base, then you will notice that the shell interrupter is moving to the left side with you as you write! :D

I think it would be good if someone developed a command line based tool in Arabic/RTL languages, then he/she can opt for using this mode by default (because their application is 100% for RTL-based audience), but in the normal average terminal it would be a horrible user experience.

The LTR one was just like the default situation in VTE. The text is not displayed good if it was Arabic and the line gets messed up.

Please tell me if you need more tests or experiments, I would be happy to provide them.

Yes, of course we can also add Urdu and Persian and other RTL-based languages to the list from $locale, it was just a simple example.

Thank you again Egmont for taking time to do all this work and respond here.
Best.