Update CLDR to version 39.0#12314
Conversation
|
CC: @LeonarddeR CC: @michaelDCurran |
|
Hi @OzancanKaratas, please fill in the full PR template in the future. The more background information you can provide the easier it is for us to review. I have updated this for you. This change does not build, I'm going to convert this to a draft. The error can be found via the appveyor console log, I'll paste it here: |
feerrenrut
left a comment
There was a problem hiding this comment.
Please ensure this change builds before converting back from draft.
|
Does this PR fix #11963?
|
I am not sure. Please test this pull request. However, this problem is not caused by CLDR, but by missing translations of the languages. |
I am not convinced that the issue comes from missing translations. Please see #11963 (comment) and comment there since it is a better place to continue this discussion in any case. |
commit 86fe20f Author: Julien Cochuyt <JulienCochuyt@users.noreply.github.com> Date: Tue May 4 03:00:30 2021 +0200 Elements List: Don't remove the label of a filled spin button input field (#12317) (#12318) In browse mode documents, when a spin button input field is filled with a value, its label goes missing from the Elements List dialog. Description of how this pull request fixes the issue: Remove the role ROLE_SPINBUTTON from the set of exceptions for which the content replaces the label.
|
@LeonarddeR Would you mind reviewing this? I'm not very sure what to look for with a CLDR change, could you comment on what you would test / check for so myself and @seanbudd can be better equipped to handle these PRs in the future? Perhaps we should add a readme for this at |
LeonarddeR
left a comment
There was a problem hiding this comment.
Looks good to me. Thanks @OzancanKaratas
|
Do you plan to merge this in time for 2021.1? |
seanbudd
left a comment
There was a problem hiding this comment.
I think we can merge this and create an issue for "create a readme at include/cldr.md" which requires information on updating CLDR and anything else relevant? @feerrenrut
|
Should we have more information in the changelog? It seems like more languages are supported now. |
|
I don't feel confident to make a call on this PR. It isn't clear if this specifically fixes issues, and whether it introduces new ones. |
|
@feerrenrut, I think this pull request should be merged. For users who are experiencing problems due to missing translations in the NVDA and CLDR repository, we should not ignore those who have no problems. |
|
I will merge this now, as it upgrades to cldr 39.0 and enables several new languages previously unavailable. However, to be very clear, this pr does not fix #11963 - This can only be done by switching to the cldr-staging repository and using the generated production data. I'll submit a pr for this once this one is merged. |
Enables several new languages.
Summary of the issue:
CLDR version 39.0 has been released.
http://cldr.unicode.org/index/downloads/cldr-39
Description of how this pull request fixes the issue:
Updates to the latest version of CLDR
Testing strategy:
Testing via Alpha users
Known issues with pull request:
None
Change log entries:
Changes
Code Review Checklist: