We iterate theoretically many sources (albeit there's only really ever one) for this data, so accumulate instead of only keeping the last (and initialize it as the list it always ended up being, not a dictionary, so that this can work). The form of each token is a locale name, so it may be lang_Script just as readily as lang_LAND; so parse (and validate) the tags more faithfully to catch both cases. Abstract that parsing into a function and use it in both places that need it. Change-Id: Ibdbc4eafefab6a5ef70646d9fea150f2cb408d05 Reviewed-by: Jędrzej Nowacki <jedrzej.nowacki@qt.io> |
||
|---|---|---|
| .. | ||
| testlocales | ||
| README | ||
| cldr2qlocalexml.py | ||
| cldr2qtimezone.py | ||
| dateconverter.py | ||
| enumdata.py | ||
| formattags.txt | ||
| localexml.py | ||
| qlocalexml2cpp.py | ||
| xpathlite.py | ||
README
local_database is used to generate qlocale data from the Common Locale Data Repository (The database for localized names (like date formats, country names etc)).