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

Higher unicode #67

Closed
StoneCypher opened this issue Apr 18, 2021 · 1 comment
Closed

Higher unicode #67

StoneCypher opened this issue Apr 18, 2021 · 1 comment

Comments

@StoneCypher
Copy link
Contributor

There's a long argument to be had here. It's been had several times.

One of the big problems with Javascript is that it actually mandates 16-bit max character storage. (lol what?) It does not mandate representation, but pretty much everybody is utf16le as a result.

This won't last forever. There's no good backcompat reason not to switch; the space outside the BMP is becoming increasingly important; et cetera.

There exists a patch for astral codepoints and a patch for uppercase supers.

There exist arguments against; some people feel that differing from contemporary Javascript is bad. However, this is almost certainly going into future Javascript, and this is an important topic now for many of us (dealing with surrogate pairs in PEG is nigh impossible.)

I believe that one or both (ideally at least the first) should go in.

@hildjj
Copy link
Contributor

hildjj commented Apr 18, 2021

See #15 please, and copy from this whatever needs to be in that discussion. Let's discuss there, then open a bug once we have a plan of attack.

@hildjj hildjj closed this as completed Apr 18, 2021
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

2 participants