-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Intl.Segmenter: isWordLike does not match Node.js and browsers #4370
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Stop sweeping your bugs under the carpet. Blindly closing tickets helps no one. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Not stale |
PR's welcome |
Which package?
@formatjs/intl-segmenter
Describe the bug
As described in #4184, the value of
isWordLike
in the output ofSegmenter::segment()
is almost alwaystrue
(the exception being newlines). This does not match the behaviour present in Node.js and Chrome (ICU4C), and Firefox Nightly (ICU4X).To Reproduce
Codesandbox URL
https://codesandbox.io/p/sandbox/dank-smoke-cv9hl7
Reproducible Steps/Repo
Steps to reproduce the behavior:
Intl.Segmenter
in Chrome or Node.js or Firefox NightlyExpected behavior
FormatJS' polyfill matches Intl.Segmenter, in that it marks punctuation as non-word-like
The text was updated successfully, but these errors were encountered: