Right now we have CLDR support for languages (en, es, ...) but not locales (en_US, en_GB, ...).
Step 1: Find a good source of the locales that are presenting in the CLDR system. The cldr charts are here: https://www.unicode.org/cldr/charts/latest/ . Alternatively you can use the list of XMLs from https://github.com/unicode-org/cldr/tree/main/common/main and augment the data from the CLDR coverage file we already imported https://github.com/Translation-Commons/lang-nav/blob/master/public/data/unicode/cldrCoverage.tsv
Step 2: Decide on the CLDR data to show for each locale. Some ideas are "localePresentInCLDRDatabase", "numberOfXMLFieldsFilledOut" "localeIsDefaultForLanguage" -- the final data items though may change depend on...
Step 3: Decide how you want to visualize CLDR data support. We can do something similar to languages, where LanguageDetails and LanguageTable include information about CLDR support -- but in this case you will update the LocaleDetails and LocaleTable components.
Step 4: Implement it above. Feel free to separate this into multiples PRs doing specific tasks.
You can see how we list general language support for CLDR in the LanguageTable component today. https://translation-commons.github.io/lang-nav/?view=Table
Right now we have CLDR support for languages (en, es, ...) but not locales (en_US, en_GB, ...).
Step 1: Find a good source of the locales that are presenting in the CLDR system. The cldr charts are here: https://www.unicode.org/cldr/charts/latest/ . Alternatively you can use the list of XMLs from https://github.com/unicode-org/cldr/tree/main/common/main and augment the data from the CLDR coverage file we already imported https://github.com/Translation-Commons/lang-nav/blob/master/public/data/unicode/cldrCoverage.tsv
Step 2: Decide on the CLDR data to show for each locale. Some ideas are "localePresentInCLDRDatabase", "numberOfXMLFieldsFilledOut" "localeIsDefaultForLanguage" -- the final data items though may change depend on...
Step 3: Decide how you want to visualize CLDR data support. We can do something similar to languages, where
LanguageDetailsandLanguageTableinclude information about CLDR support -- but in this case you will update theLocaleDetailsandLocaleTablecomponents.Step 4: Implement it above. Feel free to separate this into multiples PRs doing specific tasks.
You can see how we list general language support for CLDR in the
LanguageTablecomponent today. https://translation-commons.github.io/lang-nav/?view=Table