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

i18n #17

Closed
jfirebaugh opened this issue Aug 27, 2013 · 7 comments
Closed

i18n #17

jfirebaugh opened this issue Aug 27, 2013 · 7 comments

Comments

@jfirebaugh
Copy link
Contributor

We should use Transifex for translating imagery names and descriptions. Follow what iD does for presets:

  • Assign each source an id
  • make builds an imagery.yml source for Transifex
  • make translations pulls down translations into locale directory, split into separate files
  • Downstream consumers merge translations into their own
@tyrasd
Copy link
Member

tyrasd commented Jul 3, 2016

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. "description:fr", etc.?

@bhousel
Copy link
Member

bhousel commented Jul 3, 2016

I almost closed this as stale, but I think that:

  • Each source should have a unique id
  • It would be useful to localize the globally relevant source names and attribution text
  • It's totally ok to not translate something in Transifex that is not relevant

@tyrasd
Copy link
Member

tyrasd commented Jul 3, 2016

It's totally ok to not translate something in Transifex that is not relevant

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).

@manfredbrandl
Copy link

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.

@manfredbrandl
Copy link

There are untranslatable parts in the iD-Editor which are not layer-names:
image

@Klumbumbus
Copy link
Contributor

There are untranslatable parts in the iD-Editor which are not layer-names:

What you highlighted in red are also layer names, which are basically not different from the other layers above.

@bhousel
Copy link
Member

bhousel commented May 15, 2018

This has been done for a while

@bhousel bhousel closed this as completed May 15, 2018
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

5 participants