Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support new BiDi standard #8

Closed
XVilka opened this issue Jul 4, 2019 · 12 comments
Closed

Support new BiDi standard #8

XVilka opened this issue Jul 4, 2019 · 12 comments

Comments

@XVilka
Copy link

XVilka commented Jul 4, 2019

There is a BiDi/RTL standardization effort. And it is already supported by VTE library (not yet released though), see https://terminal-wg.pages.freedesktop.org/bidi/implementations.html#vte

See also https://gist.github.com/XVilka/a0e49e1c65370ba11c17 for tracking other terminals and programs.

@faridcher
Copy link

faridcher commented Sep 30, 2019

After updating my Gnome Terminal with the new BiDi libvte (thanks to @XVilka 's efforts ), neatvi does not render BiDi text correctly anymore. Vim seems to work well if we :set biditerm.

@aligrudi
Copy link
Owner

aligrudi commented Oct 1, 2019 via email

@faridcher
Copy link

faridcher commented Oct 1, 2019

Thanks for the clarification. I really expect BiDi support in the Terminal by default because I personally prefer to use Persian characters for certain filenames or to print an object with Persian chars in R to stdout without having to pipe it to neatvi . I think the best practice is to provide an option at the application level to disable the Terminal BiDi feature.

@aligrudi
Copy link
Owner

aligrudi commented Dec 2, 2021 via email

@faridcher
Copy link

@aligrudi
Thank you very much for the enhancement. I will test it as soon as possible.

@lobre
Copy link
Contributor

lobre commented Nov 24, 2023

If the proposal is disapproved, should this issue be closed?

@aligrudi
Copy link
Owner

aligrudi commented Nov 24, 2023 via email

@lobre
Copy link
Contributor

lobre commented Dec 12, 2023

I cannot close it myself, so I let @XVilka or yourself @aligrudi close it.

@aligrudi
Copy link
Owner

aligrudi commented Dec 12, 2023 via email

@lobre
Copy link
Contributor

lobre commented Dec 12, 2023

Hmm. I am not sure issues can be closed by mail.

@lobre
Copy link
Contributor

lobre commented Jan 11, 2024

@XVilka, would you be able to close it yourself? Thanks a lot.

@XVilka
Copy link
Author

XVilka commented Jan 13, 2024

@XVilka, would you be able to close it yourself? Thanks a lot.

Done.

@XVilka XVilka closed this as completed Jan 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants