[Openstack-i18n] Allow translators to translate BatchActions
amotoki at gmail.com
Tue Sep 9 07:36:13 UTC 2014
It is time to decide whether we should have this in Juno or defer it to Kilo.
I created POT file based on this change and uploaded it to Transifex
as Daisy requested
For the detail change and differences from the original, please check
the original review https://review.openstack.org/#/c/91338/.
As I18N team member, I am happy with this change though there are a
couple of things to be improved.
On the other hand, we need to take into account the pain for
developers, and we need to discuss this
in the horizon team meeting this week (today).
On Fri, Sep 5, 2014 at 5:51 PM, Ying Chun Guo <guoyingc at cn.ibm.com> wrote:
> Thank you for working on it.
> I do wonder if you or somebody could create a pot file with all the
> influenced strings.
> I can create a new project in Transifex and upload this pot file.
> Then translators could see these strings and the context information from
> the translation UI.
> We can evaluate whether these context information could help the
> Best regards
> Ying Chun Guo (Daisy)
> Yves-Gwenaël Bourhis <yves-gwenael.bourhis at cloudwatt.com> wrote on
> 2014/09/04 17:39:41:
>> Yves-Gwenaël Bourhis <yves-gwenael.bourhis at cloudwatt.com>
>> 2014/09/04 17:39
>> openstack-i18n at lists.openstack.org,
>> [Openstack-i18n] Allow translators to translate BatchActions
>> Hi all,
>> I reported a bug concerning the way strings where conjugated on
>> action buttons here:
>> The issue is that automatic conjugation works in English, but may
>> lead the impossibility to have a properly translated string in some
>> languages which have different and more complex conjugation rules.
>> I made a patch to fix this here:
>> However, not all strings are fixed in this patch, only a few ones,
>> and I kept the legacy conjugation method not to brake all existing
>> strings on the action buttons at once.
>> This patch will allow developers to progressively change strings on
>> action buttons per translators request, to strings which can have
>> proper translations.
>> I also added contextual markers on instance actions or status. i.e.:
>> "Shut Down" could be an action to perform, or an instance status,
>> which is the same string in English but different in many languages,
>> this patch allows differentiating them.
>> Could it help to have a test catalog on Transifex based on this
>> patch to have translators feedback on the change brought to the strings?
>> The translators could give feedback to know if translations are improved.
>> Also translators could ask for more strings which they could not
>> translate properly before, to be migrated to this new translating
>> method on action buttons as new (dependent) patches.
>> Also, how fast do translators want all the existing "action buttons"
>> and "status" strings to be migrated to this method? If all are
>> migrated at once we would lose a lot of the currently existing
>> translations on action buttons and status (even though they are not
>> properly translatable) and they would have to be translated again.
>> So adding patches progressively could bring smooth changes. This is
>> where translators feedback would be interesting to know if:
>> - The changes allow translating properly?
>> - They want smooth changes on action buttons to translate
>> progressively, or want a complete fix right now because to many
>> buttons can not be translated properly?
>> - They want changes in other places too where they can not currently
>> translate properly?
>> Yves-Gwenaël Bourhis
>> Openstack-i18n mailing list
>> Openstack-i18n at lists.openstack.org
> Openstack-i18n mailing list
> Openstack-i18n at lists.openstack.org
More information about the Openstack-i18n