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

[cliptext] consider modifying wcwidth() #2685

Open
midichef opened this issue Jan 21, 2025 · 0 comments
Open

[cliptext] consider modifying wcwidth() #2685

midichef opened this issue Jan 21, 2025 · 0 comments

Comments

@midichef
Copy link
Contributor

midichef commented Jan 21, 2025

I noted that Visidata's wcwidth() gives different answers than jquasts's more comprehensive implementation of wcwidth():

An example of a character that might get a wcwidth() of 0 is u"\u0ccd" # Joiner, Category 'Lo', East Asian Width property 'N' -- KANNADA SIGN VIRAMA, taken from a test in jquast/wcwidth. Visidata's wcwidth() returns 1 for this character. But wcwidth() from jquast/wcwidth returns 0

@saulpw replied:
We may want/have to vendorize jquast/wcwidth and extend it for our purposes.
Originally posted by @saulpw in #2667 (comment)

I've opened this issue to hold future discussions of how Visidata may need to change its wcwidth() implementation.

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

1 participant