My calculation is per resources. It is not a completion rate as a whole.
My script checks completion rates for individual resource and
if all three resources (openstack dashboard, horizon, horizon js) meet the threshold
that language will be imported.

Anyway 95% and 98% show no difference in Juno translation.

Akihiro

2014年10月7日火曜日、Ying Chun Guo<guoyingc@cn.ibm.com>さんは書きました:

The 98% completion rate is caused by the incomplete of Kilo translations.
( I think, translation memory might has small issues in Transifex.
I don't know why some strings in Kilo,which are exact same, don't be filled from translation memory )

Only Spanish and English (United Kingdom) have untranslated strings remained in Juno.

So 95% is a fine rate for me.

Best regards
Ying Chun Guo (Daisy)


Akihiro Motoki <amotoki@gmail.com> wrote on 2014/10/06 21:09:58:

> Akihiro Motoki <amotoki@gmail.com>

> 2014/10/06 21:09
>
> To

>
> "openstack-i18n@lists.openstack.org" <Openstack-i18n@lists.openstack.org>,

>
> cc

>
> Subject

>
> [Openstack-i18n] Juno Horizon translation import

>
> Hi translators,
>
> As Daisy announced last week, I will propose a patch to import Horizon
> translations at Oct 9.
> My planned time is around 1300UTC Oct 9. If you have any problems let me know.
>
> The criteria of translation progress in my mind is 95%.
> Languages with >= 95% translated will be imported.
> Although we voted and the criteria is 100% or with language
> coordinator request,
> Juno Horizon has a lot of translation strings, so I think it is reasonable.
> At the moment, 11 languages with over 95% and 8 languages with 99%.
> Thought?
>
> I would like not to enforce strict criteria, so if there is any request,
> please let  me know.
>
> Thanks,
> Akihiro
>
> _______________________________________________
> Openstack-i18n mailing list
> Openstack-i18n@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>



--
Akihiro Motoki <amotoki@gmail.com>