Upgrade to Unicode 12.0

[eyeplum]

Description

Update external data and all modules to Unicode 12.0. For changes in Unicode 12.0, see: https://www.unicode.org/versions/Unicode12.0.0/

According to Section M of the change note, migrating from Unicode 11.0 to 12.0 should be straight forward. For us, presumably it's basically updating all data files to Unicode 12.0 and regenerate all tables.

Blocked by #259 .

Unicode 12.1

It might be trivial to upgrade to Unicode 12.1 at the same time (assuming this issue will be implemented after 2019 May 7), as it only adds one character U+32FF SQUARE ERA NAME REIWA.

For details, see: https://unicode.org/versions/Unicode12.1.0/

[data-man]

Time for Unicode 13.0 :)

[crlf0710]

Time for Unicode 15.0 :(

I'm... trying to help implementing rust-lang/rust#101840 . Currently rustc is relying on unic_emoji_char::is_emoji for diagnostics. But it seems the Unicode data here is quite outdated...

[eyeplum]

Time for Unicode 15.0 :(

I'm... trying to help implementing rust-lang/rust#101840 . Currently rustc is relying on unic_emoji_char::is_emoji for diagnostics. But it seems the Unicode data here is quite outdated...

Hi there!

I have been using my own fork in recent years, the fork is currently updated to Unicode 14.0 (and will be updated to Unicode 15.0 soon).

I've been meaning to eventually merge those changes into here, perhaps now is a good time to give it a go :)

Cc: @behnam

[eyeplum]

My fork current has these changes:

• A new module for Unihan (data updated to Unicode 14.0)
• Unicode 11.0 data changes and segmentation algorithm changes
• Unicode 12.0 and 12.1 data changes
• Unicode 13.0 data changes
• Unicode 14.0 data changes

If we want them to be merged here, I think we will need to decide a way to release the changes. Perhaps each Unicode version as a point releases? E.g.:

• unic 0.10.0 for Unicode 11.0
• unic 0.11.0 for Unicode 12.0
• unic 0.11.1 for Unicode 12.1
• unic 0.12.0 for Unicode 13.0
• unic 0.13.0 for Unicode 14.0

Though I'm not sure what's the best way to handle the new Unihan module... Perhaps we can just chuck it in one of those releases...