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

Regional presets cause unnecessary duplication of translations #351

Closed
Mahabarata opened this issue Jan 11, 2022 · 2 comments
Closed

Regional presets cause unnecessary duplication of translations #351

Mahabarata opened this issue Jan 11, 2022 · 2 comments
Labels
question Further information is requested

Comments

@Mahabarata
Copy link

Hi,

Could someone explain to me why we have now 2 'primary link', 2 'trunk link', 2 'motorway link' to translate in transifex ?
Both are the same (highway=primary/trunk or motorway), the only difference is the context :

  • presets.presets.highway/primary_link.name for the older one (9 years old according to transifex).
  • presets.presets.highway/primary_link-US-CA.name for the new one (7 days old).

Do you think you will add in a few weeks new strings to translate with a specific context for Germany, Canada, France, US-CO, US-MI, Bresil-Bahia, Bresil-Goias, all countries, all states in the world ?

Thanks.

@tyrasd tyrasd added the question Further information is requested label Jan 18, 2022
@tyrasd
Copy link
Member

tyrasd commented Jan 18, 2022

These were added to solve #217 (see especially my comment). It's unfortunate that this adds some superfluous and confusing work for translators. Unfortunately, there is currently no option to skip or mark these special localized presets texts on transifex (see ideditor/schema-builder#27). Sorry for the inconvenience.

All preset keys ending with one or more -<region-code> suffixes are specific to the mentioned region codes (here, the US and Canada). As a translator, you are free to skip these strings if a language is unlikely to be used in the indicated regions.

Do you think you will add in a few weeks new strings to translate with a specific context for […] all countries, all states in the world ?

We have only started to experiment with regional presets lately. Given the somewhat negative effects it has for translators, I am currently quite reluctant to used it more widely (e.g. it would have been possible to use it for #287 (comment), but only by putting additional unnecessary work to translators). Here are some examples where regional presets have been suggested: #356, #267, #331 or #318.

@tyrasd tyrasd changed the title Strange new presets Regional presets cause unnecessary duplication of translations Jan 18, 2022
@Mahabarata
Copy link
Author

Ok, thanks for your answer, very clear.

Just a comment : I'm not sure that many people are watching at the context when they translate a string, I think a lot don't remember the old one and probably add a different translation than the first one (when you look at the history for a translation, you will see that sometimes we have a lot of imagination). And if I understand what you are saying, it means that a contributor who wants to add a new object will search the old translation (because he knew it) and will not find the tag because, in this country or area, the tag has another translation.

Best regards.
I close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants