-
Notifications
You must be signed in to change notification settings - Fork 77
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
Reusing translations from other projects? #306
Comments
The concepts for reusing translations on Transifex I found are Sharing Translation Memory and Glossary. These are presented as suggestions, so still invole translators. Translation Memory also allows to automatically translate matching texts, but I'm a bit sceptical about that. I haven't found anything that would allow to reference or link to specific translation keys from other projects. i18next has the concept of Namespaces to load from separate files. So my idea would be extract the required keys directly from the translation files of another project into separate files and not go through Transifex. Some candidates are:
¹ None of the candidates is ideal, other ideas? edit: iD presets moved to id-tagging-schema repo |
Don't parse the wiki, use the corresponding Data Items? |
Thanks for the hint, Data Items would be better than parsing, but probably depends on coverage. The general problem with the wiki is, that there often are no explicit, single-word translations of the values, only descriptions. E.g. the Template:DE:Map Features:surface page has value translations only as bold highlight within the description. And the data items only sometimes seem to have a tag translation, e.g. surface=sett. |
You're right: it depends on coverage but if we start to use it more, the coverage will get improved. If somebody is missing a translation he/she can improve the Wiki. Way easier than to translate in many tools in many formats. |
PR #304 introduces dynamic translations of highway, surface and smoothness tag values. Some with underscore were added manually to the
en.json
and got removed byi18next
:brouter-web/locales/en.json
Lines 196 to 207 in f37489c
They would need to be added to keys.js, but I left them off for now, as I think we should not translate them ourselves, but ideally reuse existing translations, some OSM editor must already have those.
On Transifex we are in the OpenStreetMap organisation, and e.g. the Vespucci editor is also part of that.
Can translations be shared between projects on Transifex (haven't done any research yet)?
The text was updated successfully, but these errors were encountered: