Update CLDR to version 43#5
Merged
Merged
Conversation
Contributor
Author
|
You do not seem to be active these days. Hope you're doing well. |
seanbudd
approved these changes
May 10, 2023
Member
|
Thanks @CyrilleB79 |
github-actions Bot
pushed a commit
that referenced
this pull request
May 10, 2023
Commit message: Update CLDR to version 43 (#5)
6 tasks
seanbudd
pushed a commit
to nvaccess/nvda
that referenced
this pull request
May 31, 2023
Follow-up of nvaccess/nvda-cldr#5 Summary of the issue: NVDA's CLDR data need to be updated regularly to follow CLDR releases. CLDR 43 was released on April 12th, 2023. Description of user facing changes CLDR character names updated, especially in translations. Description of development approach In nvda-cldr repo, checked out the commit e3af0878691391cc019d2e1e7965aa5756ac653a which is the one pointed by the branch main-out. This commit was created following the merge of nvaccess/nvda-cldr#5
josephsl
pushed a commit
to josephsl/nvda
that referenced
this pull request
May 31, 2023
Follow-up of nvaccess/nvda-cldr#5 Summary of the issue: NVDA's CLDR data need to be updated regularly to follow CLDR releases. CLDR 43 was released on April 12th, 2023. Description of user facing changes CLDR character names updated, especially in translations. Description of development approach In nvda-cldr repo, checked out the commit e3af0878691391cc019d2e1e7965aa5756ac653a which is the one pointed by the branch main-out. This commit was created following the merge of nvaccess/nvda-cldr#5
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note: the release label did not seem to be automatically available from my local repo, so I did:
git fetch origin refs/tags/release-43:refs/tags/release-43Then, I have built the data and checked that some data have changed with respect to last commit in branch main-out.