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

Update Unicode property lists per Unicode v11 #1218

Merged
merged 1 commit into from Sep 12, 2018

Conversation

Projects
None yet
4 participants
@mathiasbynens

This comment has been minimized.

Member

mathiasbynens commented Jun 7, 2018

I believe this is not a needs-consensus PR and as such am hoping this can be merged sooner rather than later. Rationale: the committee already reached consensus to follow the latest Unicode version back in 2016 per #620 and https://tc39.github.io/tc39-notes/2016-07_jul-27.html#10ia-require-unicode-900.

Once this PR goes in, I’ll update Test262 and the surrounding ecosystem w.r.t. the Unicode property escapes changes:

@mathiasbynens mathiasbynens force-pushed the mathiasbynens:unicode-11 branch from fc8ea20 to afe4c33 Jun 7, 2018

mathiasbynens added a commit to mathiasbynens/unicode-property-escapes-tests that referenced this pull request Jun 7, 2018

Update to Unicode v11
Emoji data is now published as part of the Unicode standard itself, and thus follows the same version number.

Ref. tc39/ecma262#1218.
Ref. tc39/ecma262#1219.

mathiasbynens added a commit to mathiasbynens/test262 that referenced this pull request Jun 7, 2018

Update RegExp Unicode property escape tests per Unicode 11
Emoji data is now published as part of the Unicode standard itself, and thus follows the same version number.

Ref. mathiasbynens/unicode-property-escapes-tests@f302c60.
Ref. tc39/ecma262#1218.
Ref. tc39/ecma262#1219.
@ljharb

ljharb approved these changes Jun 7, 2018

I agree this shouldn’t need consensus; however, it is a normative change (per your diff comment in the test262 PR)

@littledan

This comment has been minimized.

Member

littledan commented Jun 24, 2018

@mathiasbynens Many normative changes follow a convention of using commit messages starting with Normative:. Could be useful here. I agree that this upgrade process should not generally be considered "needs-consensus", but I think it'd be good to mention in a quick status update to the committee that this upgrade is happening, and you expect it to happen in the future.

If you like upgrading Unicode things, see this bug in ECMA-402.

@ljharb ljharb assigned ljharb and unassigned bterlson Aug 3, 2018

jridgewell added a commit to jridgewell/babel that referenced this pull request Aug 25, 2018

Remove test262 exceptions
Per tc39/ecma262#1218 (comment),
ECMA262 follows whatever the latest Unicode version specifies for Zs
Space_Separator category. MONGOLIAN VOWEL SEPARATOR was moved to the Cf
Other_Format category in Unicode 8.

jridgewell added a commit to babel/babel that referenced this pull request Aug 25, 2018

Update parser whitespace for clarity (#8539)
* Update parser whitespace for clarity

Has the nice benefit of not requiring a charCode to String conversion.

* Remove test262 exceptions

Per tc39/ecma262#1218 (comment),
ECMA262 follows whatever the latest Unicode version specifies for Zs
Space_Separator category. MONGOLIAN VOWEL SEPARATOR was moved to the Cf
Other_Format category in Unicode 8.

@ljharb ljharb force-pushed the mathiasbynens:unicode-11 branch from afe4c33 to 13bc82b Sep 12, 2018

@ljharb ljharb force-pushed the mathiasbynens:unicode-11 branch from 13bc82b to 691173a Sep 12, 2018

@ljharb ljharb merged commit 691173a into tc39:master Sep 12, 2018

1 check was pending

continuous-integration/travis-ci/push The Travis CI build is in progress
Details

rockie pushed a commit to rockie/oolong-parser that referenced this pull request Oct 21, 2018

Update parser whitespace for clarity (#8539)
* Update parser whitespace for clarity

Has the nice benefit of not requiring a charCode to String conversion.

* Remove test262 exceptions

Per tc39/ecma262#1218 (comment),
ECMA262 follows whatever the latest Unicode version specifies for Zs
Space_Separator category. MONGOLIAN VOWEL SEPARATOR was moved to the Cf
Other_Format category in Unicode 8.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment