-
Notifications
You must be signed in to change notification settings - Fork 258
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
i18n #17
Comments
Is this approach really practical for this use case? There's quite a large (and ever growing) amount of layers by now and most of them only have local or regional importance. While it certainly makes sense to translate the description of the aerial imagery layer a city like Brussels into the locally used languages (here: at least French and Dutch), it may not be necessary to translate it into every other language as well. What if we'd just let the contributors of imagery add multiple descriptions in the locally relevant languages? Idk, but why not just use OSM's multilingual tags pattern here as well, e.g. |
I almost closed this as stale, but I think that:
|
yeah, but that's a bit hard to convey in transifex's UI (with all its 0-100% progress bars and rankings that suggest one should translate each and every string). |
I would like to translate the interface strings and not the layer names. Is it possible to separate these into extra transifex resources? Then the interface part could be added as an extra resource to the iD-editor-team. |
What you highlighted in red are also layer names, which are basically not different from the other layers above. |
This has been done for a while |
We should use Transifex for translating imagery names and descriptions. Follow what iD does for presets:
make
builds an imagery.yml source for Transifexmake translations
pulls down translations into locale directory, split into separate filesThe text was updated successfully, but these errors were encountered: