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

\u200B interpreted as ​ even though encoding set to utf-8 #537

Open
anirbanmu opened this issue Jul 8, 2018 · 0 comments
Open

\u200B interpreted as ​ even though encoding set to utf-8 #537

anirbanmu opened this issue Jul 8, 2018 · 0 comments

Comments

@anirbanmu
Copy link

anirbanmu commented Jul 8, 2018

What I'm seeing is that when someone copy-pastes a zero width space into IRC, the text that is seen in my callback has ​ instead of the actual zero width space (https://en.wikipedia.org/wiki/Zero-width_space). Maybe this is somehow expected, but my IRC client interprets the text correctly & is sent over the network correctly preserving the zero-width space.

Any idea what's happening?

EDIT: I played around in the node shell, and I can assign a string with a zero-space width to a variable - if I do a charCodeAt(i) at the index for the zero-space width I get the correct code 8203. I'd have expected the same thing to be true when I see the same string coming from IRC.

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