Skip to content

Conversation

@pnorman
Copy link
Contributor

@pnorman pnorman commented Nov 16, 2025

Fixes #68


## Names

Wherever a feature has a `name` attribute it also may have `name_xx` tags, where `xx` is an IETF language code and the contents of the tag come from `name:xx`. For example a feature could have `name_en` and `name_de` attributes that come from the `name:en` and `name:de` tags.
Copy link

@1ec5 1ec5 Dec 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The specification would benefit from a more complex example involving subtags. Otherwise, it could be unclear to implementers whether name:zh-Hant-TW=* should become name_zh-Hant-TW, name_zh_Hant_TW, or name_zh_hant_tw. As the developer of a client-side localization plugin, I’d prefer name_zh-Hant-TW for compatibility with other schemas like Mapbox Streets and OpenHistoricalMap, if not name:zh-Hant-TW for compatibility with OpenMapTiles and Tilezen. However, I understand that there’s some concern in #72 about having anything other than \w characters in field names.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Multilinguality

3 participants