Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide how to encode multilingual names #10

Open
pnorman opened this issue Mar 12, 2023 · 1 comment
Open

Decide how to encode multilingual names #10

pnorman opened this issue Mar 12, 2023 · 1 comment

Comments

@pnorman
Copy link
Owner

pnorman commented Mar 12, 2023

For multilingual names, it is necessary to fall back through multiple languages to select the appropriate value.

As an example, an object might have name=東京都 name:en=Tokyo name:ja=東京都. For French user, it would fall back from the non-existent name:fr to display name:en. This figuring out of which tags to use could be done server-side or client-side.

A few properties are needed

  1. Avoid ballooning the number of vector tile attributes for all objects. e.g. a street with just a name tag should not have dozens of name attributes for all possible languages.
  2. Avoid requiring complicated client-side logic.

My inclination is to produce vector tile attributes that produce the right name for a language when you coalesce the language specific attribute with the general attribute. So, for the example above, you would produce attributes for the name in English, French, the general attribute, but not Japanese because that is covered by the general attribute.

@pnorman
Copy link
Owner Author

pnorman commented Mar 12, 2023

Note: Depends on pnorman/tilekiln#3

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

No branches or pull requests

1 participant