[Openstack-i18n] [horizon] contextual-markers for better translations
francois.bureau at cloudwatt.com
Thu Apr 24 14:32:39 UTC 2014
Today, we have talked with Yves-Gwenaël about this e-mail. He didn’t' received any answers and I think we need to discuss about it.
I would like to know one thing, if we change a marker for a string are we going to lose the related current translation ?
For example :
currently I have somewhere month = gettext("May")
So in transifex I have a string May I have translated in "Mai" (in French)
If tomorrow you change into the code month = pgettext("month name", "May")
Do we lost the translation already done in Transifex ? Or is it just going to add the context in the string already translated ?
If we lost the translation already, for me adding the context into already translated string is a bad idea. We are going to lose too much work.
And in this case the context markup has to be used only for new strings. I prefer to keep the legacy for old strings.
Thanks a lot for your answers :)
Responsable Centre de Contact
E-mail : francois.bureau at cloudwatt.com
Mobile : 06 40 76 18 01
----- Mail transféré -----
De: "Yves-Gwenaël Bourhis" <yves-gwenael.bourhis at cloudwatt.com>
À: openstack-i18n at lists.openstack.org
Envoyé: Lundi 14 Avril 2014 17:13:27
Objet: [Openstack-i18n] [horizon] contextual-markers for better translations
I noticed that translating to certain languages requires some compromises in both grammar and syntax to often have a deceiving result...
This is due to the fact that we do not use contextual-markers:
except in one unique place:
The context is required because a word which is spelled the same in English may be 2 different words in an other language.
Even less trivial, a same word with the same meaning can be spelled differently depending on the way it is used in a sentence, and there the context is really important.
Some work was already done with https://bugs.launchpad.net/horizon/+bug/1253678
But contextual-markers need to be added to many translatable strings.
The issue about changing translatable strings to contextual translatable strings implies redoing all those translations.
Do not PANIC :-) , the current translations will remain as is for Icehouse, the impact of using contextual-markers will be for Juno.
My concern is that many other languages than my 2 native ones have a richer syntax, so I may not be aware of all possible contexts required for other languages to be properly translatable.
Concerning the example I gave in https://bugs.launchpad.net/horizon/+bug/1307476 any comment on the "context" you would need to help you make a better translation will be welcomed, and I'll need your feedback on what context "you" need and in which place in the dashboard, in order to help you make the best translations.
So feel free to drop a reply to this mail with all the places where your struggle to provide a translation due to lack of context and where a context and reformulation would really help you do your translations.
Thank you all.
Openstack-i18n mailing list
Openstack-i18n at lists.openstack.org
More information about the Openstack-i18n