[Openstack-i18n] Horizon translation status update for Havana
francois.bureau at cloudwatt.com
Wed Oct 9 08:11:08 UTC 2013
Go for importing the french translation as-is :)
Responsable Centre de Contact
E-mail : francois.bureau at cloudwatt.com
Mobile : 06 40 76 18 01
De : Akihiro Motoki [mailto:amotoki at gmail.com]
Envoyé : mercredi 9 octobre 2013 08:00
À : openstack-i18n at lists.openstack.org
Objet : Re: [Openstack-i18n] Horizon translation status update for Havana
Horizon RC2 is now being prepared.
I am preparing a patch to import the latest translations from Transifex.
* French translation has 14 untranslated phrases. Is it okay to import them as-is?
If you are translating, please let me know. I can wait for several hours before uploading the patch.
* Russian team has completed the translations. Congrats! I will import it.
We have complete translations for 11 languages in Havana release.
Thanks for your great work!
On Thu, Oct 3, 2013 at 4:49 AM, Łukasz Jernaś <deejay1 at srem.org> wrote:
> On Wed, Oct 2, 2013 at 7:31 PM, Akihiro Motoki <amotoki at gmail.com> wrote:
>> Hi all,
> Hi Akihiro!
> Thanks for the work you and Daisy were doing to make this happen!
>> == Extra translation request ==
>> Horizon made several number of fixes in RC1 phase and there are
>> several changes in translation strings.
>> I just synced POT files with the latest Horizon master repository and
>> pushed them to Transifex.
>> == Schedule for Havana Horizon RC2 (not determined yet) == I will
>> request another Release Candidate (RC2) to import translations.
>> The exact plan will be discussed with Gabriel, Horizon PTL from now.
>> My current plan is to import translation updates at the middle next week.
>> I will let you all know if there is an update.
> Let's hope not many new strings will come between RC1 and the next
> release. There are some patches on gerrit which do implement new
> strings, but they should be pretty easy to handle.
> I wonder has there been any discussion on enforcing a stricter string
> freeze policy in OpenStack? Theoretically according to the release
> schedule string freeze was on the 7th of September :) Maybe we can do
> some enforcement either in gerrit via a "i18n accepted" flag enabled
> after the last milestone or some gate tests for new strings? Just a
> thought though...
> Have a nice day,
> Łukasz [DeeJay1] Jernaś
> P.S. Yes, I know I'm new to the community and may sometimes come out
> as a "know it all" type of guy - please know that it certainly isn't
> my intention!
> Openstack-i18n mailing list
> Openstack-i18n at lists.openstack.org
Akihiro MOTOKI <amotoki at gmail.com>
Openstack-i18n mailing list
Openstack-i18n at lists.openstack.org
More information about the Openstack-i18n