forked from nvaccess/nvda
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use pre-processed cldr production data (nvaccess#12422)
Fixes nvaccess#11963 Summary of the issue: Some time around CLDR release 36, CLDR started including "↑↑↑" in annotation values as a placeholder which meant that the value should be inherited from a parent locale. These ↑↑↑ values were being put straight into NVDA's cldr dictionaries without any further processing, causing languages such as Chinese (Hongkong) and others to speak these ↑↑↑ values instead of useful emoji labels. Description of how this pull request fixes the issue: NVDA now includes the cldr-staging repository as a submodule, rather than the cldr repository. The cldr-staging repository contains a production directory, with all its xml files pre-processed to include inherited values rather than the ↑↑↑ placeholders.
- Loading branch information
1 parent
9390d02
commit 7e6561a
Showing
4 changed files
with
5 additions
and
4 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Submodule cldr
updated
from 651afe to 443ca2
This file contains 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