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

Handle grapheme contains more than one code points #52

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

fisker
Copy link
Contributor

@fisker fisker commented Oct 29, 2023

I'm not sure if there are cases calculated wrong, but the grapheme width should not decided by the first code point.

@@ -40,6 +40,12 @@ export default function stringWidth(string, options = {}) {
continue;
}

// For grapheme contains more than one code points
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is correct. Graphemes can have two code points and still take up a 1 width.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yea, I can see that from test, but not sure what's correct.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[...grapheme].some(codePoint => eastAsianWidth(codePoint ) > 2)?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm honestly not sure. The East Asian Width spec doesn't provide any guidance for that. From what I have seen from other implementations, all others use the first code point too.

@sindresorhus
Copy link
Owner

sindresorhus commented Oct 29, 2023

We could maybe use .normalize() on the string. Just so that it uses single code points whenever possible.

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

Successfully merging this pull request may close these issues.

None yet

2 participants