Normalization - Do we care about UCA versions #255

Closed
opened 2019-02-13 18:16:34 +01:00 by tiger5226 · 4 comments
tiger5226 commented 2019-02-13 18:16:34 +01:00 (Migrated from github.com)

I just wanted to get this conversation out of slack and have documented for historical purposes.

The unicode standards are always updated

screen shot 2019-02-13 at 12 10 28 pm

LBRYcrd is use the ICU library for unicode support v57.1. This uses UCA 8.0

screen shot 2019-02-13 at 12 43 27 am

Among our different services, there are 3 that standout in requiring unicode support also.

LBRYNet - The base lbry uses UCA 11.0
Chainquery(MySQL) - MySQL 8.0 users UCA 9.0
Lighthouse(ElasticSearch) - as of yet unknown

@lyoshenka Has already made the call that for Chainquery we will wait and see if there will be any issues between UCA 8.0 and UCA 9.0.

The list of migration issues are below

https://www.unicode.org/versions/Unicode9.0.0/#Migration
https://www.unicode.org/versions/Unicode10.0.0/#Migration
https://www.unicode.org/versions/Unicode11.0.0/#Migration

So the question is do we care? If not lets close this issue.

I just wanted to get this conversation out of slack and have documented for historical purposes. The unicode standards are always updated <img width="649" alt="screen shot 2019-02-13 at 12 10 28 pm" src="https://user-images.githubusercontent.com/3402064/52730003-6058c980-2f88-11e9-97a3-8a7a1f6e256a.png"> LBRYcrd is use the ICU library for unicode support v57.1. This uses [UCA 8.0](http://www.unicode.org/Public/UCA/8.0.0/?C=M;O=A) <img width="483" alt="screen shot 2019-02-13 at 12 43 27 am" src="https://user-images.githubusercontent.com/3402064/52729920-28518680-2f88-11e9-8a9d-dbe599e7bcb6.png"> Among our different services, there are 3 that standout in requiring unicode support also. LBRYNet - The base lbry uses [UCA 11.0](http://www.unicode.org/Public/UCA/11.0.0/?C=M;O=A) Chainquery(MySQL) - MySQL 8.0 users [UCA 9.0](http://www.unicode.org/Public/UCA/9.0.0/?C=M;O=A) Lighthouse(ElasticSearch) - as of yet unknown @lyoshenka Has already made the call that for Chainquery we will wait and see if there will be any issues between UCA 8.0 and UCA 9.0. The list of migration issues are below https://www.unicode.org/versions/Unicode9.0.0/#Migration https://www.unicode.org/versions/Unicode10.0.0/#Migration https://www.unicode.org/versions/Unicode11.0.0/#Migration So the question is do we care? If not lets close this issue.
BrannonKing commented 2019-02-21 04:41:39 +01:00 (Migrated from github.com)

After upstream merge, update Boost and ICU versions to match Unicode 11. In fact, can we ditch the lbrycrd_dependencies repo and use the "depends" folder instead?

After upstream merge, update Boost and ICU versions to match Unicode 11. In fact, can we ditch the lbrycrd_dependencies repo and use the "depends" folder instead?
BrannonKing commented 2019-03-08 23:39:11 +01:00 (Migrated from github.com)

Upstream merge now includes ICU 62.

Upstream merge now includes ICU 62.
lyoshenka commented 2019-05-07 21:43:40 +02:00 (Migrated from github.com)

doing some cleaning. reopen if this is still active.

doing some cleaning. reopen if this is still active.
BrannonKing commented 2019-05-07 22:43:55 +02:00 (Migrated from github.com)

To clarify one thing: I'm planning to ship the next release with ICU 63.2 (which is still Unicode 11).

To clarify one thing: I'm planning to ship the next release with ICU 63.2 (which is still Unicode 11).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbrycrd#255
No description provided.