Open Stack

Checking Zanata feature is good,
but how can we move forward the issue which currently happens?
Transifex admin can update the string (i.e., remove corresponding
translations)?

There are two possible cases.
The one is a case where a translation PO file is directly uploaded to
Transifex.
It seems Transifex does not check any formatting check for such case.
The other is Transifex behavior.
>From my experience, I sometimes saw a bit strange behavior of Transifex
when translations are updated by uploading new version of source language.
I am afraid some processing similar to msgmerge has a problem,
but I am not sure when it happens.

Akihiro




The

2015-07-15 8:08 GMT+09:00 Ying Chun Guo <guoyingc at cn.ibm.com>:

> I read [3] and found three errors:
>
> a format specification for argument 'ip_protocol' doesn't exist in 'msgstr'
> a format specification for argument 'ip_protocol' doesn't exist in 'msgstr'
> a format specification for argument 'firewall', as in 'msgstr', doesn't
> exist in 'msgid'
>
> That's strange.
> In my mind, there are simple format checks in Transfiex while translating.
> That kind of errors should be detected and the translation should not be
> able to save.
> How these happened then?
>
> I see "tr_TR/LC_MESSAGES/django.po" is newly added.
> Why is there a "newly added" po file?
>
> @ Carlos, are there similar format checks in Zanata while translating ?
> Like, if the same arguments exist both in source string and translated
> string;
> if brackets must come in pairs; and etc.
>
> Best regards
> Ying Chun Guo (Daisy)
>
>
> Akihiro Motoki <amotoki at gmail.com> wrote on 2015/07/15 01:00:58:
>
> > From: Akihiro Motoki <amotoki at gmail.com>
> > To: "openstack-i18n at lists.openstack.org" <
> Openstack-i18n at lists.openstack.org>
> > Date: 2015/07/15 01:01
> > Subject: [Openstack-i18n] Turkey Horizon translation broken
>
> >
> > Hi Turkey language team and I18N whole team,
> >
> > Horizon daily translation import patch [1] detects an translation error
> > that turkey translation has invalid message format string.
> > It is detected in "check-tempest-dsvm-full" job [2], more precisely [3].
> >
> > It is an expected behavior, but my question is how we should deal with.
> > Is there any defined process? AFAIK we have never had this kind of
> discussion.
> >
> > Ideally, it is great that Turkey team can take an action soon.
> >
> > On the other hand, we need to have a process as the I18N project
> > because this blocks translations of all languages.
> > Transifex administrators can delete such translations,
> > but I would like to see the consensus.
> >
> > [1] https://review.openstack.org/#/c/200793/
> > [2] http://logs.openstack.org/93/200793/4/check/check-tempest-dsvm-
> > full/33e49b1/
> > [3] http://logs.openstack.org/93/200793/4/check/check-tempest-dsvm-
> > full/33e49b1/logs/devstacklog.txt.gz#_2015-07-14_10_03_38_504
> >
> > Thanks,
> > Akihiro
> > _______________________________________________
> > Openstack-i18n mailing list
> > Openstack-i18n at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-i18n/attachments/20150715/904fb7bd/attachment.html>