Normalization - Do we care about UCA versions #255
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
Epic
good first issue
hacktoberfest
hard fork
help wanted
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
soft fork
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
work in progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbrycrd#255
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I just wanted to get this conversation out of slack and have documented for historical purposes.
The unicode standards are always updated
LBRYcrd is use the ICU library for unicode support v57.1. This uses UCA 8.0
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.
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?
Upstream merge now includes ICU 62.
doing some cleaning. reopen if this is still active.
To clarify one thing: I'm planning to ship the next release with ICU 63.2 (which is still Unicode 11).