April 2016 - OpenStack-I18n - lists.openstack.org

To language team coordinators: get ready for Mitaka translation
by Ying Chun Guo 28 Sep '16

28 Sep '16

Dear coordinators, Mitaka translation will be started at the beginning of March, and probably ended in the week of March 28. We need to get ourselves ready for Mitaka translation from now on. Because of the join of IBM professional translators, we will be able to cover more projects in our translation plan of this release. Generally, the jobs of existing community translators will not be affected, focus on Horizon, same as before. IBM translators will focus on "other" projects. Before Mitaka translation starts, there are several things you can do: 1. Update glossary. If you don't have glossary translations in i18n repo[1], or you want to update glossary translations, you can send a patch with your translations or your updates to i18n repo directly. 2. Document your local team communication method in the team wiki page[2]. While Mitaka translation starts, it's good to open your local communication channel to all of your language translators. Good communication is quite important for people from different places to work well together. 3. Join IRC channel[3] #openstack-i18n with your zanata ID As a coordinator, you have the responsibility to coordinate your language translations. A good practise is to show up in IRC and have your people to get you easily when they have troubles. If you have any questions, talk to me. My IRC ID is "Daisy" in the channel of #openstack-i18n. Thank you. Best regards Ying Chun Guo (Daisy) [1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale [2] https://wiki.openstack.org/wiki/I18nTeam/team [3] https://wiki.openstack.org/wiki/IRC

9 27

Release notes translation
by Ying Chun Guo 05 Jul '16

05 Jul '16

Hello, team Release notes[1] are published. I know our tools don't support release notes at present. I have gotten requests from Chinese team to translate release notes. Any suggestions to do that? Surely we can download and translate offline. One more question is where we should put the translated release notes. I hope to get some inputs from other language teams who want to translate release notes. Thank you. Best regards Ying Chun Guo (Daisy) [1] http://releases.openstack.org/mitaka/index.html

9 9

pot files in git trees?
by Andreas Jaeger 07 May '16

07 May '16

Looking at the daily imports we do for our translations, a lot of that is importing pot files (translation source). Do we really need these for anything in the git trees? We've stopped importing those pot files which are not translated at all but import pot files that have translations and update them daily (only if there are real translations as well). I really wonder whether we need these pot files in our git repositories at all, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

5 14

FW: [Bug 1573514] [NEW] Typos in Italian Mitaka translation
by Kato, Tomoyuki 22 Apr '16

22 Apr '16

Hi Italian team, KATO Tomoyuki > -----Original Message----- > Title: > Typos in Italian Mitaka translation > > Status in openstack i18n: > New > > Bug description: > Zanata proposed another update for mitaka neutron Italian translation: > https://review.openstack.org/#/c/309280/ > > There are several concerns I have here. > > First, it seems that the change has some typos (e.g. using a ¥ character while the language does not use it at all). > Second, the change removes authorship for multiple contributors. I suspect it's not expected.

2 1

Re: [OpenStack-I18n] IRC meeting this week
by Kato, Tomoyuki 21 Apr '16

21 Apr '16

> Thank you, Kato-san. > I'm not able to attend the meeting this time because of a conflict. > I have added some topics to austin-i18n-workshop. quick short response. > In total we have 2 i18n related sessions, 40-minute austin-i18n-workshop 90-minutes, isn't it? https://www.openstack.org/summit/austin-2016/summit-schedule/events/7707 Kato > and a half day austin-i18n-meetup. > I see there are a long list of topics in austin-i18n-workshop. > I suggest we move some topics to austin-i18n-meetup in order to have > thorough discussions for every topic. > Maybe we move glossary and bug management discussions to > austin-i18n-meetup. > And in austin-i18n-workshop, we focus on Zanata, translation check website > and stackalytics. > > Best regards > Ying Chun Guo (Daisy) > > > "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> wrote on 04/19/2016 > 11:12:05 AM: > > > From: "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> > > To: "'openstack-i18n(a)lists.openstack.org'" <openstack- > > i18n(a)lists.openstack.org> > > Date: 04/19/2016 11:14 AM > > Subject: [OpenStack-I18n] IRC meeting this week > > > > Hi team > > > > We will have IRC meeting at UTC 13:00 UTC Thursday in > #openstack-meeting. > > > > The agenda is > > > > * Summit Planning > > - https://etherpad.openstack.org/p/austin-i18n-workshop > > - https://etherpad.openstack.org/p/austin-i18n-meetup > > > > If you have more topics, feel free to email. > > > > Regards, > > KATO Tomoyuki (katomo) > > > > _______________________________________________ > > OpenStack-I18n mailing list > > OpenStack-I18n(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > >

2 1

IRC meeting this week
by Kato, Tomoyuki 19 Apr '16

19 Apr '16

Hi team We will have IRC meeting at UTC 13:00 UTC Thursday in #openstack-meeting. The agenda is * Summit Planning - https://etherpad.openstack.org/p/austin-i18n-workshop - https://etherpad.openstack.org/p/austin-i18n-meetup If you have more topics, feel free to email. Regards, KATO Tomoyuki (katomo)

2 1

translation syncronization disabled due to broken Babel release
by Andreas Jaeger 17 Apr '16

17 Apr '16

A heads up and a request for advise: Babel 2.3.3 release broke extraction of log level messages from strings and extracted instead of e.g. "_LW" the default "_". So, the proposal job removed all content for that. Fortunately, Zanata will keep the strings, so once an upload with a fixed Babel happens, this should be fine again. See https://review.openstack.org/#/c/304985/ for one example - the error manifests with all pot files having exactly the same content. But I wanted to be safe and since babel 2.3.2 broke horizon and now 2.3.3 breaks python projects, I have - as teemporary measure - disabled translation sync completely to buy us time to evaluate what to do. There's a requirements change to update versions (blocking all broken babel releases): https://review.openstack.org/#/c/305000 Upstream bug report https://github.com/python-babel/babel/issues/388 And one way of working around it the bug is not using "python setup.py" but "pybabel" directly for python projects - like we do for django already. This needs testing and review - and some updates (see review comment): https://review.openstack.org/305043 We can also wait for Babel 2.3.4 release - and test first that it works as desired. Advise on which way to go forward as well as testing and review of 305043 are welcome! Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 3

技术因素 in OpenStack 架构设计指南 - 当前最新
by KATO Tomoyuki 16 Apr '16

16 Apr '16

Hi Chinese team, Please take a look at: https://bugs.launchpad.net/openstack-i18n/+bug/1571100 Kato

1 0

Renaming of resources
by Andreas Jaeger 13 Apr '16

13 Apr '16

I propose to change the setting of the locale source dir from "$module/locale" to "." for all projects to have this consistent. This will change the names of all resources since those are relative to the locale source dir. This will enable us to translate release notes using Zanata for the python projects. This is only relevant for python projects - not for documentation ones or for Django based projects since those already use "." as source directory. This implies a scripting change as well as a manual copying translation files around. I'm willing to do both later this week. My proposal would be to only do this for *master* but not for stable/mitaka, I don't want to risk anything on that branch. Everybody ok with this? Or has anybody concerns and suggestions? Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

4 6

Re: [OpenStack-I18n] Renaming of resources
by Andreas Jaeger 12 Apr '16

12 Apr '16

On 2016-04-12 12:03, Ying Chun Guo wrote: > Hi, Andreas > > Just release Horizon project have two pairs of resources with same name: > django and djangojs. And that will not change, they will stay the same. > Will they have both the same name and same location after changing ? Yes, as the new setup is exactly the setup that horizon has. > Is there a way to separate them from the web UI after changing? > See: > https://translate.openstack.org/iteration/view/horizon/master/documents I think that is clear, it gives name and path now, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 0