Tilezen remaps localized names into 2-char languages codes from OpenStreetMap, Natural Earth, and OpenStreetMap – which each has their own way of representing name localizations.
In the case of Chinese (and possibly other languages), this "spoken" language has multiple "written" character sets (Traditional and Simplified) and is spoken and written in multiple countries using different configs.
But in Tilezen we only export a generic and ambiguous name:zh value. In UX design generally it's best practice to target each language as a combination of language + country code to allow for local colloquialisms. But for mapping sometimes less is better / mostly we're dealing in proper nouns - so another alternative is to say zh-hans (Chinese simplified irresepctive of country) and zh-hant (Chinese traditiional irrespective of country). Let's pick one and stick with it, and make it work with the point-of-view / worldview being introduced in v5.
Tilezen remaps localized names into 2-char languages codes from OpenStreetMap, Natural Earth, and OpenStreetMap – which each has their own way of representing name localizations.
In the case of Chinese (and possibly other languages), this "spoken" language has multiple "written" character sets (Traditional and Simplified) and is spoken and written in multiple countries using different configs.
But in Tilezen we only export a generic and ambiguous
name:zh
value. In UX design generally it's best practice to target each language as a combination of language + country code to allow for local colloquialisms. But for mapping sometimes less is better / mostly we're dealing in proper nouns - so another alternative is to sayzh-hans
(Chinese simplified irresepctive of country) andzh-hant
(Chinese traditiional irrespective of country). Let's pick one and stick with it, and make it work with the point-of-view / worldview being introduced in v5.For example:
https://github.com/tilezen/vector-datasource/blob/024909ed8245a4ad4a25c908413ba3602de6c335/vectordatasource/transform.py#L523-L558