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