-
-
Notifications
You must be signed in to change notification settings - Fork 780
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
Add solution for East Asian Width Problem #6289
Labels
enhancement
New feature or request
Comments
ref: #1888 |
hamano
added a commit
to hamano/wezterm
that referenced
this issue
Oct 18, 2024
Is the issue I am having in #6228 related to this do you think? Particularly look at my most recent comment where running |
@NathanCummings #6228 is not EAW issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
We would like to express our gratitude from the Far East for implementing the
treat_east_asian_ambiguous_width_as_wide
option in wezterm.However, this option is a adhoc workaround and is inadequate.
Describe the solution you'd like
Regarding the EAW issue, better solutions:
Since wezterm is a cross-platform application, using
wcswidth()
might not be appropriate.I propose adding a cellwidth configuration option to wezterm.
This is a feature provided by mlterm, Emacs, and Vim, and it offers a practical solution to the ambiguous Unicode standard.
With this option, it is possible to unify character widths across terminal, shell, and text editors.
Based on vim's
setcellwidths()
, I propose the following syntax for the settingsHowever, it seems that keyword omission is not preferred in wezterm
I will handle the actual work and submit a pull request.
Additionally, I understand that there is a difference in perspective regarding the EAW issue between Latin users and CJK users.
If additional explanations are needed regarding the difficulties faced by the CJK users, I am more than willing to provide them.
The text was updated successfully, but these errors were encountered: