- OpenStack-I18n - lists.openstack.org

Turkish translation
by Hüseyin Çotuk 15 Jun '15

15 Jun '15

Dear All, My name is Huseyin Cotuk, and i have been using OpenStack for more than 3 years in production. I am working for the Turkish government and we operate an OpenStack cloud for governmental institutions, universities, other research institutes and internal projects. Currently we have more than 4000 cpu cores, 500 TBytes of storage and so on. I am head of cloud department at TUBITAK ULAKBIM in Turkey, and while OpenStack Days Istanbul yesterday, we met with Jonathan and Lauren. We talked about our projects and i promised for the Turkish translation of OpenStack dashboard for the Turkish community. My organization TUBITAK ULAKBIM is also coordinating national operating system (Pardus), and we already have a translation team for this OS. We will work together with this translation team, and my team will review the translations after OS team finishes. My transifex id is huseyincotuk and the project name is openstack_turkish. I am looking forward to hearing from you. Best regards, Huseyin

3 3

Thought on String Freeze
by Akihiro Motoki 15 Jun '15

15 Jun '15

Hi I18N folks, # Congratulation for the official I18N project!! I first thought to send this mail to the dev list, but it seems better to share my thought in the I18N folks first. Problems ========== I am feeling that String Freeze does not work well in the past several releases.There are several I think we should not apply String Freeze for projects for which not so many translators work on. As far as I understand, Horizon and documentations are targets for most translations in the past several releases. On the other hands, core reviewers of projects other than Horizon and docs (including keystone) were taking care of String Freeze exception WELL. My Proposal ============= Considering the current status, I think we should limit "String Freeze" only to projects which translators are interested in. My idea is to declare projects we would like to enable "String Freeze" just after Liberty-3 is cut. By doing so, other projects no longer need to take care of String Freeze exception. (Note that the freeze date of the documentation projects are different and we can apply some different policy on documentations). Thought? I cannot join the team meeting tomorrow due to LinuxCon/CloudOpen Japan, but I hope you will share your thought on this topic. Thanks, Akihiro

2 2

Fwd: [openstack-dev] [horizon][i18n] Ordering of PO files
by Tom Fifield 09 Jun '15

09 Jun '15

-------- Forwarded Message -------- Subject: [openstack-dev] [horizon][i18n] Ordering of PO files Date: Mon, 8 Jun 2015 17:28:39 -0600 From: Thai Q Tran <tqtran(a)us.ibm.com> Reply-To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> Hi folks, In the midst of shifting to angular, we are making use of babel for extracting messages. This would then allow us to write a custom extractor for angular templates. Here's the patch that compare PO files: https://review.openstack.org/#/c/189502/ It looks worse than reality, if you compare the django vs babel makemessages, they are nearly identical, only the ordering is different. Which leads me to my next point. If the ordering of the translatable strings are not the same, how does that affect translation (if at all)?

1 0

I18n team working sessions in Vancouver
by Ying Chun Guo 05 Jun '15

05 Jun '15

Hello, all We had a great day yesterday. There were two I18n team working sessions. People from Japanese, Frech, Russian, Polish, Chinese and Chinese Taiwan team attended. Key persons from Doc team, infra team, and Horizon dev team joined the discussions too. We made good progress with glossaries, document translations, string freeze, tool migration, and etc. More details could be found in the etherpad pages [1] [2]. Yet our translators still want more face to face communications. So I organize an ad hoc meeting on Wednesday afternoon, only for translators. If you are translators and in Vancouver summit now, come to join the ad hoc meeting. The place is at a round table outside the Room 1, East Building at the Vancouver Convention Centre. The time is from 2:05pm to 5:05pm on Wednesday, May 21st. I will sit there and wait for you to join. I created an Etherpad page for us to track the discussion. Feel free to add the topics you want to cover. https://etherpad.openstack.org/p/vancouver-translation-team-workshop Thank you. Best regards Ying Chun Guo (Daisy) [1] https://etherpad.openstack.org/p/Vancouver-I18n-WG-session [2] https://etherpad.openstack.org/p/Vancouver-I18n-Translation-platform-session

3 5

I18n team, OpenStack Project Team!
by Ying Chun Guo 04 Jun '15

04 Jun '15

Hello, all I'm pleased to announce that I18n team is approved by TC to become a OpenStack Project Team. We are now under the authority of the OpenStack Technical Committee. In return, we could get some space and time to discuss our future development at the Design Summits. Our contributors could vote in the Technical Committee election. This is a great milestone after I18n team was created. Next, we need to figure out the criteria of our core members and active members, which might be different from dev team. We will initialize the core team, then grow the team and increase the contributions. Let's work together to make it a successful team. Best regards Ying Chun Guo (Daisy)

11 12

IRC meeting tomorrow
by Ying Chun Guo 03 Jun '15

03 Jun '15

Hello, team There are several responses to the mail "Review IRC meeting time"[1]. I don't see objections. So let's use them from now on. I hope active team members could have chances to join the discussion at least once a month. If these two time slots are not suitable for you, please let me know. We could still adjust the meeting times in the future. Tomorrow, we will have the IRC meeting at UTC 0600 in the channel #openstack-meeting, on June 4th. Following topics would be covered: * Briefing of I18n meetings in Vancouver summit * Criteria of I18n core members and active members * Open discussions Hope to talk to you then. Best regards Ying Chun Guo (Daisy) [1] http://lists.openstack.org/pipermail/openstack-i18n/2015-June/001107.html

1 0

Review IRC meeting time
by Ying Chun Guo 02 Jun '15

02 Jun '15

Hello, team I would like to review our IRC meeting time. Now we are using UTC 0800 and we meet on every first and third Thursday. I18n team have people from all over the world. Some people would like to use their day time, and some people prefer to use their evening time. I want to change to two time slots for the meetings. We use them alternately. Hope every team member could find a suitable time to join the team meeting. I suggest below two time slots: 1. The first Thursday every month UTC 6am, Thur Paris 08am, Thur Warsaw 08am, Thur Moscow 09am, Thur New Delhi 11:30am, Thur Beijing 14pm, Thur Seoul 15pm, Thur Tokyo 15pm, Thur Vancouver 23pm, Wed 2. The third Thursday every month UTC 13pm, Thur Paris 15pm, Thur Warsaw 15pm, Thur Moscow 16am, Thur New Delhi 18:30am, Thur Beijing 21pm, Thur Seoul 22pm, Thur Tokyo 22pm, Thur Vancouver 06am, Thur Please let me know which time slot works for you. Or if neither works for you, please suggest a time. Thank you. Best regards Ying Chun Guo (Daisy)

4 3

Re: [Openstack-i18n] Specialty teams connecting to translation team
by Ying Chun Guo 21 May '15

21 May '15

Sorry, wrong wiki link in my last email. It is https://wiki.openstack.org/wiki/I18nTeam/docs-translation Best regards Ying Chun Guo (Daisy) Ying Chun Guo/China/IBM wrote on 2015/05/22 01:42:18: > From: Ying Chun Guo/China/IBM > To: Anne Gentle <annegentle(a)justwriteclick.com> > Cc: "openstack-docs(a)lists.openstack.org" <openstack- > docs(a)lists.openstack.org>, "openstack-i18n(a)lists.openstack.org" > <openstack-i18n(a)lists.openstack.org> > Date: 2015/05/22 01:42 > Subject: Re: [Openstack-i18n] Specialty teams connecting to translation team > > Thank you, Anne. > > We use a wiki page to track the status of documentation: > https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categori… > > I hope specialty team leads could keep an eye on this table. > If there is any changes of your documents, like, changing from > stable to unstable, changing from unstable to stable, > let the translation team know by sending an email to openstack-i18n > mailing list. > So that we could make a translation plan for your documents. > > Thanks. > Best regards > Ying Chun Guo (Daisy) > > Anne Gentle <annegentle(a)justwriteclick.com> wrote on 2015/05/22 01:35:14: > > > From: Anne Gentle <annegentle(a)justwriteclick.com> > > To: "openstack-docs(a)lists.openstack.org" <openstack- > > docs(a)lists.openstack.org>, "openstack-i18n(a)lists.openstack.org" > > <openstack-i18n(a)lists.openstack.org> > > Date: 2015/05/22 01:35 > > Subject: [Openstack-i18n] Specialty teams connecting to translation team > > > > Hi all, > > I'm sitting here in Vancouver next to Daisy (Ying Chun Guo) who > > leads the i18N efforts for OpenStack. She would like each specialty > > team lead to connect with the i18N team to communicate the amount of > > change expected so that they can evaluate the timing of translation, > > and how much is done that can be translated. > > > > We also had a session with the i18N team and want to work on more > > communication with each team, and I think the specialty team leads > > are a great way to start that effort. > > > > Thoughts or ideas? Let us know. > > Thanks, > > Anne > > > > -- > > Anne Gentle > > annegentle@justwriteclick.com_______________________________________________ > > Openstack-i18n mailing list > > Openstack-i18n(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

1 0

Magnum, magnumclient translations?
by Andreas Jaeger 14 May '15

14 May '15

The magnum project wants to enable translation, see https://review.openstack.org/#/c/182835/ and https://review.openstack.org/#/c/182848/ Is there any guideline from the translation team which projects get translation enabled? I know that enabling translation does not mean, something gets translated - Davanum, keep that in mind ;) Btw. magnum is an OpenStack project that provides a set of services for management of application containers in a multi-tenant cloud environment. And so far we've enabled all projects in the OpenStack project. Only the last months this was not done with each new project moving under the big tent. I'll review the requests today or tomorrow and will setup transifex for the team unless I hear otherwise from the translation team, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 2

Update on Dogri, Konkani, Manipuri, Sanskrit, Santali
by Tom Fifield 14 May '15

14 May '15

Hi all, I just wanted to let you know that Transifex has added Dogri, Konkani, Manipuri, Sanskrit and Santali to their site's code repository, and will update the code of the live site (so we can use them) before the end of this month. Regards, Tom

2 4