This separates the large slabs of data (and their documentation) from the code that mixes them with CLDR-derived data and generates the data we actually use. In the process, put the shorter table before the longer one, to make it less likely that folk shall fail to notice it's even there at all. Change-Id: I8457741911657dac0dad53c2e65b977821bb4e71 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io> |
||
|---|---|---|
| .. | ||
| testlocales | ||
| README | ||
| cldr.py | ||
| cldr2qlocalexml.py | ||
| cldr2qtimezone.py | ||
| dateconverter.py | ||
| enumdata.py | ||
| formattags.txt | ||
| iso639_3.py | ||
| ldml.py | ||
| localetools.py | ||
| qlocalexml.py | ||
| qlocalexml.rnc | ||
| qlocalexml2cpp.py | ||
| zonedata.py | ||
README
locale_database is used to generate qlocale data from CLDR. CLDR is the Common Locale Data Repository, a database for localized data (like date formats, country names etc). It is provided by the Unicode consortium. See cldr2qlocalexml.py for how to run it and qlocalexml2cpp.py to update the locale data tables (principally text/qlocale_data_p.h and time/q*calendar_data_p.h under src/corelib/). See enumdata.py for when and how to update the data it provides. You shall definitely need to pass --no-verify or -n to git commit for these changes. See cldr2qtimezone.py on how to update tables of Windows-specific names for zones and UTC-offset zone names.