- OpenStack-I18n - lists.openstack.org

API Quick Start now RST
by Anne Gentle 13 Oct '15

13 Oct '15

Hi all, The API Quick Start migration change has landed and Andreas has been working on language builds for it: https://review.openstack.org/232937 https://review.openstack.org/232945 https://review.openstack.org/232950 It will build to developer.openstack.org/LANG/api-guide/quick-start. The goal is to also build developer.openstack.org/api-guide/compute -- one directory for each service, sourced from each project team's preferred location. I'm not sure that you need to prioritize the API Quick Start for translation, but wanted to let this list know. Thanks, Anne -- Anne Gentle Rackspace Principal Engineer www.justwriteclick.com

4 8

Approved & rejected translations after versions merging
by Ying Chun Guo 13 Oct '15

13 Oct '15

Hi, A translation could be approved or rejected. This action is called translation review. A version merging is to copy all matching translated/approved translations from the source version to the target version. If there is an existing translated/approved translation, the newer translation will be used. After liberty translations are closed, we will merge translations from stable-liberty version to master version, and then open both stable-liberty version and master version to accept translations. I investigated whether translation review would be copied after version merging. Here are the results: The review result - "approve" will be copied to the target version, while the review result - "reject" will not. Only "rejecting" existing translations will not have the same translations rejected in master version. But "approving" existing translations will have the same translations approved in the master version. That means, if there are "rejected" translations in stable-liberty, it's better to input the correct translations. The investigation result is OK with me. If you have different opinions, please propose here. If you want to understand more about version merging, please let me know. Best regards Ying Chun Guo (Daisy)

2 9

[openstack-i18n], [openstack-infra][project-config] Glance metadef JSON files need i18n support.
by Okuma, Wayne 09 Oct '15

09 Oct '15

Hi All, Not sure if this email got through the last time I sent it, so sending it again. Sorry if I've created a duplicate. I have a blueprint that I need feedback/approval for Mitaka. Please review it at: https://blueprints.launchpad.net/glance/+spec/metadefs-i18n-support https://review.openstack.org/#/c/229211/ Work for it is at: glance: https://review.openstack.org/#/c/229690/ python-glanceclient: https://review.openstack.org/#/c/231810/ project-config: https://review.openstack.org/#/c/232304/ Thanks and Regards, Wayne Okuma

1 0

[openstack-dev][glance]; [openstack-i18n]; [openstack-infra][project-config]; Glance metadefs JSON i18n support
by Okuma, Wayne 09 Oct '15

09 Oct '15

Hi All, I have a blueprint that I need feedback/approval for Mitaka. Please review it at: https://blueprints.launchpad.net/glance/+spec/metadefs-i18n-support https://review.openstack.org/#/c/229211/ Work for it is at: glance: https://review.openstack.org/#/c/229690/ python-glanceclient: https://review.openstack.org/#/c/231810/ project-config: https://review.openstack.org/#/c/232304/ Thanks and Regards, Wayne Okuma

1 0

Survey results of translated materials in Japanese community
by Akihiro Motoki 09 Oct '15

09 Oct '15

Hi I18N team, In the last moment in Liberty cycle, many translations of server side projects were incorporated. I think many language teams need to decide their priorities among various resources in the next release. I would like to share the survey result on translated materials we made in Japan. We, Japanese community, made a rough survey on the interest in translated materials in OpenStack 5th birthday event in Japan (in July). It was done in a lightning talk and we roughly count the number of raised hands. We have >300 folks in the hall. The question is very simple: Do you want or use translated version of the following or use English version? The results are as follows. The numbers are percentage of interested folks. - Horizon : 70~80% - Documentations : 40~50% (as long as they are kept up-to-date) - CLI : <5% (7~8 of >300) - Log messages : 0 (I could not find raised hands) The following is my impression on priories in Japanese translations. - Horizon and documentations: should be prioritized. horizon first. - CLI: low priorities - log messages: Lowest priorities. - User visible messages from server projects: low priorities (though our survey didn't cover it). Note that it need to be prioritized if Horizon use these strings directly. This is just my impression, and other languages must have different priorities. Thanks, Akihiro

2 2

What's Up, Doc? 9 Oct 2015
by Lana Brindley 08 Oct '15

08 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, We're hurtling head first to Liberty, with only about a week left to go. I've been working on Summit preparations, and making sure we're ready to go when the time hits. This week, I'm working on Release Notes, keeping an eye on the final Install Guide testing, and some other housekeeping tasks. This is my last docs newsletter before the Liberty release, although I'll endeavour to get a special Summit edition out as well. We will pick up regular meetings (and other tasks, like core team reviews) after the Summit. == Progress towards Liberty == 5 days to go! 601 bugs closed so far for this release. The main things that still need to be done before release: - - Testing, testing, testing: https://wiki.openstack.org/wiki/Documentation/LibertyDocTesting - - Reviews: https://review.openstack.org/#/q/status:open+project:openstack/openstack-ma… and https://review.openstack.org/#/q/status:open+project:openstack/api-site,n,z - - Bug triage: https://bugs.launchpad.net/openstack-manuals/+bugs?search=Search&field.stat… == Release Notes == Can all PTLs and Cross-Project Liaisons please check the Release Notes page, and ensure they've included all the new features for their project here: https://wiki.openstack.org/wiki/ReleaseNotes/Liberty The best way to do this (I'm told) is to go through the blueprints created for Liberty. I will be editing these during the next few days, so please ensure you're up to date ASAP. Please contact me directly if you have any questions or problems. == Mitaka Summit Prep == Thank you to everyone who provided suggestions for Design Summit sessions. I've now mangled them into a draft schedule, which is available on Sched: http://mitakadesignsummit.sched.org/type/Documentation == Doc team meeting == The US meeting was held this week. The minutes are here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-10-07 The next meetings will be the final meetings before the Liberty release: APAC: Wednesday 14 October, 00:30:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… - -- 東京でお会いしましょう Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJWF1vMAAoJELppzVb4+KUyjNAH/iWkObcXhsCagd/Ht6N5IjsY SRQ1+B9PDpRU1281VCmy0MfIRIGATCOOaSlpumEfpz8lIOnPmR/yXU/mKm6xJ55k gCRCXSdb0wGomn7b346b3kvfRD6AUanVfq/6LnQsP0c6XCH8graqPwB5LMT9ndVm 68n/bOm2KlHh1NHmlI40l7eKOUCL0J82VOgdyqrWup55kg4R96cc1wUFH7gbz0jf 5b7khgD/P6XTzD1dbJIigKMxy8cj49FMx4tsrxdZZxZds2NauoE5inteI7HOuZMH /iBf1SB1NbzFGSGH6upQVVZsxR0vKpq3WO/VwNTtlFZkjPrNDQXt0/n3wLv6REU= =aUM2 -----END PGP SIGNATURE-----

1 0

Re: [Openstack-i18n] Curious Strings
by Alex Eng 08 Oct '15

08 Oct '15

The first source string (all in single line) is from https://github.com/openstack/openstack-manuals/blob/master/doc/install-guid… . According to record in Zanata the second string (broken into 2 entries) is from /neutron-controller-install.rst:13, https://github.com/openstack/openstack-manuals/blob/master/doc/install-guid…, which is broken into 2 lines. Both pot files in github repo ( https://github.com/openstack/openstack-manuals/blob/master/doc/install-guid…) and the one uploaded to Zanata ( https://translate.openstack.org/iteration/view/openstack-manuals/master/doc…) is totally different. --------------------------------------------- Alex Eng Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com On Thu, Oct 8, 2015 at 3:41 AM, Douglas Fish <drfish(a)us.ibm.com> wrote: > Kato, Alex, > > This still seems like a bug to me. The POT file has this as a single > string that is written on two lines > > https://github.com/openstack/openstack-manuals/blob/master/doc/install-guid… > but Kato has shown that is it available in Zanata as two separate strings > to translate. > > In fact, it seems that it's also available as a proper string in Zanata. > This query shows 2 matches: > > https://translate.openstack.org/webtrans/translate?project=openstack-manual… > > > Use the database access client to connect to the database server as the ``root`` user: > > > - Resource ID: 6cfac5f7b0e6f238895e3dcc7ac03206 > - Message Context: > - Source Comment: > - Last Modified By: OpenStack Infra > - Last Modified Time: 09/09/15 11:55 > > which seems expected and proper, and > > Use the database access client to connect to the database server as the > > > - Resource ID: ca3fdc8a1c36bfac2c20fbad11897afb > - Message Context: > - Source Comment: > - Last Modified By: > - Last Modified Time: > > which is unexpected. I don't see anything in the POT file that corresponds > to the 2nd version. > Perhaps the bug is that items that used to be in the POT file but have > been removed remain in Zanata? > > Doug Fish > > > ----- Original message ----- > From: Alex Eng <aeng(a)redhat.com> > To: KATO Tomoyuki <tomo(a)dream.daynight.jp> > Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> > Subject: Re: [Openstack-i18n] Curious Strings > Date: Tue, Oct 6, 2015 11:19 PM > > Hi Kato, > > According the source, the string is extracted from > https://github.com/openstack/openstack-manuals/blob/master/doc/install-guid…. > > > Its a markup syntax with the single quote. The source string has been in > this format since it first imported into Zanata. > > You can see the history for this file: > https://github.com/openstack/openstack-manuals/commits/master/doc/install-g… > > > https://github.com/openstack/openstack-manuals/commit/f22caf8bc349b6a6b97a7… > > > --------------------------------------------- > > Alex Eng > Globalisation Tools Engineering > DID: +61 3514 8262 <callto:+61+3514+8262> > Mobile: +614 2335 3457 <callto:+614+2335+3457> > > Red Hat, Asia-Pacific Pty Ltd > Level 1, 193 North Quay > Brisbane 4000 > Office: +61 7 3514 8100 <callto:+61+7+3514+8100> > Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> > Website: www.redhat.com > > On Wed, Oct 7, 2015 at 1:53 PM, KATO Tomoyuki <tomo(a)dream.daynight.jp> > wrote: > > Hi all, > > I encounter a curious situation. > The string [1] is separately displayed in Zanata [2]. > > #890 @Zanata > Use the database access client to connect to the database server as the > > #891 @Zanata > ``root`` user: > > This situation itself is very inconvinient for me to translate. > > Any thought? > Zanata bug???? > > [1] source message catalog: > > https://github.com/openstack/openstack-manuals/blob/master/doc/install-guid… > > [2] Zanata > openstack-manuals > install-guide > master > https://translate.openstack.org/iteration/view/openstack-manuals/master > > Thanks, > KATO Tomoyuki > > _______________________________________________ > Openstack-i18n mailing list > Openstack-i18n(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > _______________________________________________ > Openstack-i18n mailing list > Openstack-i18n(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > >

3 3

Re: [Openstack-i18n] Liberty translations are closing
by Ying Chun Guo 08 Oct '15

08 Oct '15

Hello, team We have finished Liberty translations. Look at the achievements we have made within 1 month: * Horizon translations 12 language teams finished Horizon translations 100%. 13 languages will be shipped together with Liberty. They are: Chinese (China), Chinese (Taiwan), Czech, English (Australia), French, German, Japanese, Korean (South Korea), Polish (Poland), Portuguese (Brazil), Russian, Spanish and Turkish (Turkey). * Nova message translations 3 language teams finished the translations of nova.po 100%. They are: Chinese (China), Czech, and German. 12 language translations of Nova messages are more than 75% and will be imported into Liberty branch. * In total, we have translated more than 1 million words in 1 month. (The exact number is 1037k.) It's an amazing number. Congratulations for those language teams, and many thanks to the hard work of translators, reviewers and coordinators. We will conclude liberty translation from today. According to Andreas suggestion, I leave stable-liberty in open status. You could continue the improvement of stable-liberty versions. All your improvements will be imported into liberty branches and shipped with the liberty stable releases. As to the master versions, I have set them writable and merged the translations of stable-liberty versions into master versions. Both stable-liberty and master versions are open to accept translations now. Thank you again for your hard work. Best regards Ying Chun Guo (Daisy) Ying Chun Guo/China/IBM wrote on 10/05/2015 10:53:37 PM: > From: Ying Chun Guo/China/IBM > To: Openstack-i18n <openstack-i18n(a)lists.openstack.org> > Date: 10/05/2015 10:53 PM > Subject: Liberty translations are closing > > Hello, team > > Liberty translations will be closed in 24 hours from now on. > After that, I will set stable-liberty "Read Only" for a few days, > in order to preserve time for development team to package them. > > I see zh-TW, fr, tr-TR have a very few words left in Horizon translations: > https://translate.openstack.org/iteration/view/horizon/stable-liberty. > Translation patches to Horizon and Heat still have unit test errors: > https://review.openstack.org/#/q/status:open+branch:stable/liberty > +topic:zanata/translations,n,z > > Translation teams have only 24 hours to clean up your work. > Please hurry up. > Thank you for the corporation. > > Best regards > Ying Chun Guo (Daisy)

5 16

Curious Strings
by KATO Tomoyuki 07 Oct '15

07 Oct '15

Hi all, I encounter a curious situation. The string [1] is separately displayed in Zanata [2]. #890 @Zanata Use the database access client to connect to the database server as the #891 @Zanata ``root`` user: This situation itself is very inconvinient for me to translate. Any thought? Zanata bug???? [1] source message catalog: https://github.com/openstack/openstack-manuals/blob/master/doc/install-guid… [2] Zanata > openstack-manuals > install-guide > master https://translate.openstack.org/iteration/view/openstack-manuals/master Thanks, KATO Tomoyuki

3 2

Fwd: [OpenStack-docs] Import failure - Japanese Install Guide
by Andreas Jaeger 07 Oct '15

07 Oct '15

Sorry, send to wrong list... Andreas -------- Forwarded Message -------- Subject: [OpenStack-docs] Import failure - Japanese Install Guide Date: Wed, 7 Oct 2015 08:51:24 +0200 From: Andreas Jaeger <aj(a)suse.com> To: openstack-docs(a)lists.openstack.org <openstack-docs(a)lists.openstack.org> Today's translation import of openstack-manuals fails the testing: 2015-10-07 06:49:00.393 | ++ msgfmt --statistics -o /dev/null doc/install-guide/source/locale/ja/LC_MESSAGES/install-guide.po 2015-10-07 06:49:00.431 | + trans='doc/install-guide/source/locale/ja/LC_MESSAGES/install-guide.po:6685: '\''msgid'\'' and '\''msgstr'\'' entries do not both begin with '\''\n'\'' Could somebody from Japanese team check and fix this, please? This is similar to what we discussed with horizon, let's mark this as error in Zanata. 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, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 _______________________________________________ OpenStack-docs mailing list OpenStack-docs(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

2 2

"Warning: none, Errors: 1" from the difference of number of lines
by Ian Y. Choi 06 Oct '15

06 Oct '15

Hello, Sorry if I am asking an already discussed issue. I am now reviewing horizon > stable-liberty > Documents (ko-KR) > openstack_dashboard/locale/django before our freezing deadline, as Daisy mentioned. But I have found that some Korean strings still have an error with the following message like: "Not enough lines in translation (expected 4, found 3)". The main reason I think is that in our previous translation platform Transifex, truncating the last empty line was recommended as far as I remember. (If not, Transifex generated an error.) My question is: should we fix those error translated strings with same number of lines and same spaces? I think it would be ignored because when I see Chinese translation, there were the same type of error message for almost translated strings. (Screenshot: https://www.dropbox.com/s/bvd098wsakpi192/Zanata_horizon_translation_exampl… ) And if this error would be negligible to us, are there some ways not to see this type of errors? I would like to copy an example sentence string in Zanata from Korean for my better explanation. <in English>(Translated from) === First, select which type of job that you want to run. This choice will determine which other steps are required === <in Korean>(Translated to) === 먼저, 실행하고자 하는 job 유형 을 선택합니다. 이 선택을 통해 필요로 하는 다른 과정들을 결정할 것입니다. === With many thanks, /Ian

7 13

Liberty translations are closing
by Ying Chun Guo 06 Oct '15

06 Oct '15

Hello, team Liberty translations will be closed in 24 hours from now on. After that, I will set stable-liberty "Read Only" for a few days, in order to preserve time for development team to package them. I see zh-TW, fr, tr-TR have a very few words left in Horizon translations: https://translate.openstack.org/iteration/view/horizon/stable-liberty. Translation patches to Horizon and Heat still have unit test errors: https://review.openstack.org/#/q/status:open+branch:stable/liberty+topic:za… Translation teams have only 24 hours to clean up your work. Please hurry up. Thank you for the corporation. Best regards Ying Chun Guo (Daisy)

3 2

API Quick Start
by Anne Gentle 05 Oct '15

05 Oct '15

Hi all, I've got a patch in progress to convert the "API Quick Start" from Docbook to RST: https://review.openstack.org/#/c/217467/ Since it has quite a few translations completed, I want to make sure that converting that document is okay with the translators. So, is it okay to convert and build using RST instead of Docbook? Is the tooling available for files in the api-site repository? Thanks, Anne -- Anne Gentle Rackspace Principal Engineer www.justwriteclick.com

3 3

What's Up, Doc? 2 October
by Lana Brindley 01 Oct '15

01 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, Welcome to October, which means: it's nearly release day! I've been brushing up on the release management tasks, and continued my housekeeping duties to make sure we're in shape. The next two weeks will be spent watching the Installation Guide pretty closely, and making sure we get it all tested and ready to ship. If you are looking for something to do this week, please treat Install Guide testing as your main priority from here until 15 October. Also, don't forget to vote in the TC election next week! == Progress towards Liberty == 12 days to go 534 bugs closed so far for this release. The main things that still need to be done as we hurtle towards release: * Testing, testing, testing: https://wiki.openstack.org/wiki/Documentation/LibertyDocTesting * Reviews: https://review.openstack.org/#/q/status:open+project:openstack/openstack - -manuals,n,z and https://review.openstack.org/#/q/status:open+project:openstack/api-site, n,z * Bug triage: https://bugs.launchpad.net/openstack-manuals/+bugs?search=Search&field.s tatus=New == Mitaka Summit Prep == Thank you to everyone who provided suggestions for Design Summit sessions. I've now mangled them into a draft schedule, which looks a little like this: Workrooms (Thursday AM): - - Docs toolchain/infra info session - - IA working session - Ops/Arch Guides & User Guides - - Doc Contributor Guide: new content addition - - API Docs Session Fishbowls (Thursday PM): - - The docs process, plus best practices - - Mitaka planning - deliverables for the next release Meetup (Friday AM): - - Contributors meetup. No agenda. We can assist with setting up devstack/working through the Install Guide during this session Once I have access to Cheddar and Sched, I'll get this allocated more accurately. In the meantime, feedback or questions are welcome. == Bug Triage Process == The core team have been noticing a lot of people trying to close bugs that haven't been triaged recently. It is very important that you have someone else confirm your bug before you go ahead and create a patch. Waiting just a little while for triage can save you (and our core team!) a lot of work, and makes sure we don't let wayward changes past the gate. If you're unsure about whether you need to wait or not, or if you're in a hurry to work on a bug, you can always ping one of the core team on IRC or on our mailing list. The core team members are listed here, and we're always happy to help you out with a bug or a patch: https://launchpad.net/~openstack-doc-core This is even more important than usual as we get closer to the Liberty release, so remember: If it's not triaged, don't fix it! == Doc team meeting == The APAC meeting was held this week. The minutes are here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-09-30 The next meetings will be the final meetings before the Liberty release: US: Wednesday 7 October, 14:00:00 UTC APAC: Wednesday 14 October, 00:30:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_ meeting - -- Remember, if you have content you would like to add to this newsletter, or you would like to be added to the distribution list, please email me directly at openstack(a)lanabrindley.com, or visit: https://wiki.openstack.org/w/index.php?title=Documentation/WhatsUpDoc Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJWDgItAAoJELppzVb4+KUyvy4H/3J5Dg5Z2Rv5yHImXU7ZhY4U chAQQ8ZUTysKcKtShIvqWqiejOWUql0Y2L9cV+28P9A8NFjJ/meWAckjC+LQgl1X WrqDimHjtStkLTft0kbmsVN3HYDpdH9QJhLh0ut3YHieWy5DeFaKZGbnP5MrTwFi 7WPjWCChECyCx0olrsr8AoYtLu9wUjtX0rDFJTC/4T3kZ1wauUnkWeRVT4S2e09c mjpGf7xgkciRqOyFgACzL0dGYXFlQhPxrRAnGMMRjpGERTIkWzlptk5v/oF9rx4v 84B/Ni3eTH2O+uqmVuXzjesvzV27Yzhoq4UvN14SeN7cHJ43mTfVsPi9kUZYPGM= =aCzp -----END PGP SIGNATURE-----

1 0

Re: [Openstack-i18n] Would like Zanata branch to correct 1494819
by Douglas Fish 01 Oct '15

01 Oct '15

1 0

Do your translations have English in them?
by Douglas Fish 01 Oct '15

01 Oct '15

1 0

Re: [Openstack-i18n] Would like Zanata branch to correct 1494819
by Ying Chun Guo 01 Oct '15

01 Oct '15

Hi, The new stable-liberty is created. The old stable-liberty was renamed to stable-libery-backup, and set as ReadOnly. Please verify if the bug is fixed. Thank you. Best regards Ying Chun Guo (Daisy) Douglas Fish/Rochester/IBM wrote on 10/01/2015 09:58:15 AM: > From: Douglas Fish/Rochester/IBM@IBMUS > To: aj(a)suse.com > Cc: guoyingc(a)cn.ibm.com, openstack-i18n(a)lists.openstack.org > Date: 10/01/2015 09:58 AM > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > I have examined the files in the russian-fix branch. They look > right. Also I've tested them and they appear to be working correctly > in Horizon. > > We'll need this in stable-liberty. It renders Horizon pretty broken > for Russian: https://bugs.launchpad.net/openstack-i18n/+bug/1494819 > > Doug Fish > > > > ----- Original message ----- > From: Andreas Jaeger <aj(a)suse.com> > To: Ying Chun Guo <guoyingc(a)cn.ibm.com>, Douglas Fish/Rochester/IBM@IBMUS > Cc: openstack-i18n(a)lists.openstack.org > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > Date: Wed, Sep 30, 2015 7:19 AM > > On 2015-09-30 13:21, Ying Chun Guo wrote: > > Hi, Doug > > > > After testing, I figured out a best way which has the lowest impact. > > 1. Create Russian translation files with only the correct header and the > > pluralitiestranslation items. > > 2. Create a new version named as russian-fix > > 3. Upload the source files and the Russian translation files created in > > #1 to the version russian-fix > > 4. Merge the stable version with version russian-fix > > 5. Rename stable version to stable-old, and rename russian-fix to stable. > > > > You could verify if the issues are fixed in russian-fix ? > > https://translate.openstack.org/iteration/view/horizon/russian-fix > > Do we need this fix for stable-liberty branch as well? > > Let's move forward quickly here for the release, please, > > 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, Graham Norton, > HRB 21284 (AG Nürnberg) > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 >

1 0

Re: [Openstack-i18n] IRC meeting tomorrow
by Ying Chun Guo 01 Oct '15

01 Oct '15

Sorry, guys. Today is my National Day. I had so a good time with my family that I forgot the meeting time. Thank you for take it over, Andreas. I will check how reviews merge when versions merge, and will response later. Many thanks for the attendees, and sorry again for my absence. Best regards Ying Chun Guo (Daisy) Andreas Jaeger <aj(a)suse.com> wrote on 10/01/2015 04:34:18 PM: > From: Andreas Jaeger <aj(a)suse.com> > To: Ying Chun Guo/China/IBM@IBMCN > Date: 10/01/2015 04:34 PM > Subject: Re: [Openstack-i18n] IRC meeting tomorrow > > On 2015-09-30 13:46, Ying Chun Guo wrote: > > Hello,team > > > > We will have the IRC meeting at UTC 0600 in the channel > > #openstack-meeting on October 1st. > > We could talk about the ongoing liberty translations: progress, > > importing, issues, and etc. > > If you have other topics, feel free to propose. > > > > Best regards > > Ying Chun Guo (Daisy) > > > > Hi Daisy, > > we missed you today. Hope everything is fine with! > > I took the liberty to run it today, there were a couple of questions > regarding merging back, could you review those, please? > > http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2015/ > openstack_i18n_meeting.2015-10-01-08.10.log.html > > 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, Graham Norton, > HRB 21284 (AG Nürnberg) > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 >

2 1

Re: [Openstack-i18n] Would like Zanata branch to correct 1494819
by Ying Chun Guo 30 Sep '15

30 Sep '15

Hi, Doug After testing, I figured out a best way which has the lowest impact. 1. Create Russian translation files with only the correct header and the pluralities translation items. 2. Create a new version named as russian-fix 3. Upload the source files and the Russian translation files created in #1 to the version russian-fix 4. Merge the stable version with version russian-fix 5. Rename stable version to stable-old, and rename russian-fix to stable. You could verify if the issues are fixed in russian-fix ? https://translate.openstack.org/iteration/view/horizon/russian-fix Best regards Ying Chun Guo (Daisy) Douglas Fish/Rochester/IBM wrote on 09/24/2015 02:41:16 AM: > From: Douglas Fish/Rochester/IBM@IBMUS > To: Ying Chun Guo/China/IBM@IBMCN > Cc: ilyaalekseyev(a)acm.org, openstack-i18n(a)lists.openstack.org > Date: 09/24/2015 02:41 AM > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > I don't think these kinds of structural edits are available through > the Zanata UI (I'm not expert and welcome any correction) > > I don't have a script to automatically do the updates but I did > outline my plan in the bug description. To repeat here: > cd openstack_dashboard/locale/ru/LC_MESSAGES > cp django.po django.po-tmp > grep -v msgstr.2. django.po-tmp > django.po > sed -i s/msgstr.3./msgstr[2]/ django.po > and edit the plurality function to be > "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n" > "%10<=4 && (n%100<12 || n%100>14) ? 1 : 2);\n" > was my plan to fix the openstack_dashboard ... django.po file. This > is the only one that results in bad behavior in Horizon today. > > However, since this is such a difficult process I think we should > update all 4 Russian PO file while we are doing this: > openstack_dashboard/horizon and django.po/djangojs.po for each part. > > Daisy - I'm happy to help work through this, including testing out > our proposed files in Horizon. Do you want to schedule a time and > coordinate this through openstack-i18n or some meeting IRC channel? > > Doug > > ----- Original message ----- > From: Ying Chun Guo/China/IBM > To: Douglas Fish/Rochester/IBM@IBMUS@IBMAU > Cc: ilyaalekseyev(a)acm.org, openstack-i18n(a)lists.openstack.org > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > Date: Wed, Sep 23, 2015 11:25 AM > > Thank you for looking into it, Illya. > I think we need to fix it, although the manually process might be a > little complex. > > I'm going to: > 1. Create a new version in Zanata > 2. Mark master as read only > 2. Pull the source files and the translation files. > 3. Change the pluralities settings in Russian translation files. > 4. Upload the source files and translation files to the new version. > 5. Check if the all things are right, change master version name to > "master-old", > and then change the new version name to "master" > > How do you want to update these pluralities then? By program ? Or manually ? > Is it possible to make the changes through Zanata UI, other than > uploading po files ? > > Best regards > Ying Chun Guo (Daisy) > > > Douglas Fish/Rochester/IBM wrote on 09/23/2015 04:38:19 AM: > > > From: Douglas Fish/Rochester/IBM@IBMUS > > To: ilyaalekseyev(a)acm.org > > Cc: guoyingc(a)cn.ibm.com, openstack-i18n(a)lists.openstack.org > > Date: 09/23/2015 04:38 AM > > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > > > Hi Ilya, > > > > Thanks for looking at this! Unfortunately having 4 pluralities > > confuses Horizon. I've tested out stripping one of the pluralities > > and restoring the expected Plural-forms definition (just like the > > one you linked) and it works great. > > > > I had hoped to just repair the PO files in this way and upload the > > corrected translations to Zanata. > > > > Unfortunately, I understand from Daisy's research that once a > > language/project has been created in Zanata in this way we cannot > > just upload a PO file with corrected pluralities . More > > investigation will be needed to understand the process to fix this. > > > > Doug > > > > > > ----- Original message ----- > > From: Ilya Alekseyev <ilyaalekseyev(a)acm.org> > > Sent by: ilya(a)phpcoder.ru > > To: Douglas Fish/Rochester/IBM@IBMUS > > Cc: Ying Chun Guo <guoyingc(a)cn.ibm.com>, "openstack- > > i18n(a)lists.openstack.org" <openstack-i18n(a)lists.openstack.org> > > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > Date: Tue, Sep 22, 2015 2:39 PM > > > > Hi Doug and Daisy! > > > > Looks like we have wrong pluralities in current release: > > in https://github.com/openstack/horizon/blob/master/ > > openstack_dashboard/locale/ru/LC_MESSAGES/django.po > > > > we have: > > "Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n" > > "%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n% > 10<=9) || (n" > > "%100>=11 && n%100<=14)? 2 : 3);\n" > > > > but in previuos releses we have: > > "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n% > > 10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" > > > > Last one is right for Russian. > > > > We can make translation in Zanata for 4 pluralities, but it can give > > in some cases bugs with wrong plural forms. > > > > Kind regards, > > Ilya Alekseyev. > > > > 2015-09-22 14:22 GMT+03:00 Douglas Fish <drfish(a)us.ibm.com>: > > Hi Daisy, > > > > I am certain this issue is caused by plural forms. The issue with > > missing menus is seen with the current 4 plural form translations; > > when I correct the PO file to have 3 forms Horizon properly > displaysthe menus. > > > > Doug > > > > > > ----- Original message ----- > > From: Ying Chun Guo/China/IBM > > To: Douglas Fish/Rochester/IBM@IBMUS@IBMAU > > Cc: openstack-i18n(a)lists.openstack.org > > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > Date: Tue, Sep 22, 2015 12:49 AM > > > > Hi, Doug > > > > We need to consider it carefully. > > > > After working with Zanata dev team, I got to understand: > > > > 1. Zanata has its own plural forms. If po file has its own plural > > form, Zanata will use that. > > Otherwise, Zanata will use its own plural form. Pluralforms in Zanata: > > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && > > (n%100<10 || n%100>=20) ? 1 : 2). > > So it looks like that OpenStack po files overrode the pluralforms in Zanata. > > > > 2. Zanata currently don't allow update of plural forms once the > > document has been uploaded to Zanata. > > Even with deletion of that source document and re-upload (in the > > same project-version, same doc name and same path), > > Zanata will still reuse the old pluralform. > > > > 3. If we want to update the pluralforms, we will need to do it in > > new project-version > > (don't use copy-from previous version function). > > > > I think we need to carefully design the steps to change pluralforms > > of Russian. > > At first, I want to confirm with you, are you sure this issue is > > caused by plural forms? > > > > Best regards > > Ying Chun Guo (Daisy) > > > > > > Douglas Fish/Rochester/IBM wrote on 2015/09/18 23:38:22: > > > > > From: Douglas Fish/Rochester/IBM@IBMUS > > > To: guoyingc(a)cn.ibm.com > > > Cc: openstack-i18n(a)lists.openstack.org > > > Date: 2015/09/18 23:38 > > > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > > > > > Hi Daisy, > > > > > > Yes, I understand - I don't think I can even propose my branch > > > unless I am added as a translator by the Russian team. > > > > > > My proposal would include removing one plural form for > > > 4 messages in horizon django.po > > > 1 message in horizon djangojs.po > > > 144 messages in openstack_dashboard django.po > > > 0 messages in openstack_dashboard djangojs.po > > > plus the pluralization specification would be updated in all 4 files. > > > > > > Doug > > > > > > ----- Original message ----- > > > From: Ying Chun Guo <guoyingc(a)cn.ibm.com> > > > To: Douglas Fish/Rochester/IBM@IBMUS > > > Cc: openstack-i18n(a)lists.openstack.org > > > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > > Date: Fri, Sep 18, 2015 3:25 AM > > > > > > Are there a lot of changes in your proposed po files ? > > > I'm still waiting for Russian team's response. > > > > > > Best regards > > > Ying Chun Guo (Daisy) > > > > > > > > > "Douglas Fish" <drfish(a)us.ibm.com> wrote on 09/18/2015 05:37:07 AM: > > > > > > > From: "Douglas Fish" <drfish(a)us.ibm.com> > > > > To: openstack-i18n(a)lists.openstack.org > > > > Date: 09/18/2015 05:38 AM > > > > Subject: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > > > > > > > Hi translation friends, > > > > > > > > I'd like to contribute 4 PO files for the Horizon Russian > > > > translation to correct the issue > > > > https://bugs.launchpad.net/openstack-i18n/+bug/1494819 > > > > > > > > These uploads won't contain any new translations, but instead will > > > > be an adjustment to the PO files so they have 3 pluralities, which > > > is standard > > > > http://localization-guide.readthedocs.org/en/latest/l10n/ > pluralforms.html > > > > > > > > Specifically, I plan to remove the msgstr[2] translation from the > > > > files (because msgstr[2] is blank for many cases), rename the msgstr > > > > [3] translation to msgstr[2] and adjust the plurality specification to > > > > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && > > > > (n%100<10 || n%100>=20) ? 1 : 2); > > > > > > > > As discussed in the team meeting http://eavesdrop.openstack.org/ > > > > meetings/openstack_i18n_meeting/2015/openstack_i18n_meeting. > > > > 2015-09-17-13.00.log.html > > > > please create a Zanata branch so I can propose these corrections > > for review. > > > > > > > > Thanks! > > > > > > > > Doug > > > > _______________________________________________ > > > > Openstack-i18n mailing list > > > > Openstack-i18n(a)lists.openstack.org > > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > > > > _______________________________________________ > > Openstack-i18n mailing list > > Openstack-i18n(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > >

4 3

IRC meeting tomorrow
by Ying Chun Guo 30 Sep '15

30 Sep '15

Hello,team We will have the IRC meeting at UTC 0600 in the channel #openstack-meeting on October 1st. We could talk about the ongoing liberty translations: progress, importing, issues, and etc. If you have other topics, feel free to propose. Best regards Ying Chun Guo (Daisy)

1 0

Handling of translations for Liberty
by Andreas Jaeger 29 Sep '15

29 Sep '15

We had some IRC discussion today about how to handle the "other" projects with importing and here's a proposal based on discussions with Clark, Lyz, Steve, Daisy and Thierry. I'd like to prepare everything for this tomorrow if possible, so please speak up if you have questions or concerns, Andreas Challenge: We have translations for some projects like keystone that are not on the liberty branch. Master is already open for Mitaka. Proposal: Handle all projects that have currently translations of main files (so, not only LOG files) and liberty branches the same - like we do with horizon and nova. Details: This means, the following projects will get liberty branches: List of projects that branch with translations: openstack/ceilometer openstack/cinder openstack/designate openstack/designate-dashboard openstack/django_openstack_auth openstack/glance openstack/horizon openstack/keystone openstack/neutron openstack/nova openstack/swift openstack/zaqar List of projects branching later: openstack/openstack-manuals - to translate Install Guide The following projects will not be translated: List of projects that branch without translations in git : openstack/aodh openstack/ironic-inspector openstack/magnum openstack/magnum-ui openstack/manila openstack/sahara openstack/searchlight List of projects that branch with only LOG translations in git: openstack/barbican openstack/glance_store openstack/heat openstack/ironic openstack/trove List of projects not branching: openstack/api-site openstack/ha-guide openstack/operations-guide openstack/oslo.cache openstack/oslo.concurrency openstack/oslo.db openstack/oslo.i18n openstack/oslo.log openstack/oslo.messaging openstack/oslo.middleware openstack/oslo.policy openstack/oslo.reports openstack/oslo.service openstack/oslo.utils openstack/oslo.versionedobjects openstack/oslo.vmware openstack/python-magnumclient openstack/python-openstackclient openstack/security-doc Process 1. Before RC1 is cut, translators work with master version. 2. When stable branch is cut, branches get created in Zanata as well. Syncing will get enabled for them. 3. Translators focus on translation of stable branch. 4. Once translators are finished with translations, a copy of new translations from stable branch to master is done in Zanata . 5. Open master version to accept translations. Note: Around RC1 time, a patch to cleanup "old" translations gets proposed to both stable and master to remove any translations in git that are less than 50 % translated (we normally only delete less than 20 % to avoid to frequent deletion). What do we want to see in Liberty release: * Updated translations of files that are sufficiently translate (> 75 %) * Updated po source file that reflect state of repository * No empty/mainly untranslated language files (< 50 %) 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, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

4 13

dashboard trans checksite
by KATO Tomoyuki 25 Sep '15

25 Sep '15

Hi team, A.I. from last IRC meeting. I updated translation check site spec. Any comments are welcome. https://review.openstack.org/#/c/184559/ Thanks, KATO Tomoyuki

2 2

horizon, django_openstack_auth and other stable/liberty created
by Andreas Jaeger 25 Sep '15

25 Sep '15

Hi, translation team, horizon, django_openstack_auth, and other projects as mentioned in my email have now stable/liberty branches created [1]. Daisy and myself have created the corresponding version for liberty in Zanata. The version name is stable-liberty. So from now on, all translations/review should be made in the stable-liberty version. The master version of horizon and django_openstack_auth is now set "Read Only" and will be open to accept translations after Liberty is done. Andreas [1] Horizon is currently get prepared for branch, the git repo is not yet updated but our version will be the branch point -- 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, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 2

Re: [Openstack-i18n] [openstack-dev] [nova][i18n] Is there any point in using _() inpython-novaclient?
by Matt Riedemann 25 Sep '15

25 Sep '15

On 9/6/2015 12:18 AM, Steve Martinelli wrote: > Isn't this just a matter of setting up novaclient for translation? IIRC > using _() is harmless if there's no translation bits set up for the project. > > Thanks, > > Steve Martinelli > OpenStack Keystone Core > > Inactive hide details for Matt Riedemann ---2015/09/04 01:50:54 PM---I > noticed this today: https://review.openstack.org/#/c/219Matt Riedemann > ---2015/09/04 01:50:54 PM---I noticed this today: > https://review.openstack.org/#/c/219768/ > > From: Matt Riedemann <mriedem(a)linux.vnet.ibm.com> > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev(a)lists.openstack.org>, openstack-i18n(a)lists.openstack.org > Date: 2015/09/04 01:50 PM > Subject: [openstack-dev] [nova][i18n] Is there any point in using _() in > python-novaclient? > > ------------------------------------------------------------------------ > > > > I noticed this today: > > https://review.openstack.org/#/c/219768/ > > And it got me thinking about something I've wondered before - why do we > even use _() in python-novaclient? It doesn't have any .po files for > babel message translation, it has no babel config, there is nothing in > setup.cfg about extracting messages and compiling them into .mo's, there > is nothing on Transifex for python-novaclient, etc. > > Is there a way to change your locale and get translated output in nova > CLIs? I didn't find anything in docs from a quick google search. > > Comparing to python-openstackclient, that does have a babel config and > some locale po files in tree, at least for de and zh_TW. > > So if this doesn't work in python-novaclient, do we need any of the i18n > code in there? It doesn't really hurt, but it seems pointless to push > changes for it or try to keep user-facing messages in mind in the code. > > -- > > Thanks, > > Matt Riedemann > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > Yeah, doffm is working on enabling i18n for python-novaclient via bug: https://bugs.launchpad.net/python-novaclient/+bug/1492444 -- Thanks, Matt Riedemann

5 6

Re: [Openstack-i18n] translating python clients
by Ying Chun Guo 24 Sep '15

24 Sep '15

Ying Chun Guo/China/IBM wrote on 2015/09/25 10:17:52: > From: Ying Chun Guo/China/IBM > To: Andreas Jaeger <aj(a)suse.com> > Cc: Matt Riedemann <mriedem(a)linux.vnet.ibm.com>, openstack- > i18n(a)lists.openstack.org > Date: 2015/09/25 10:17 > Subject: Re: [Openstack-i18n] translating python clients > > Andreas Jaeger <aj(a)suse.com> wrote on 2015/09/23 15:06:56: > > > From: Andreas Jaeger <aj(a)suse.com> > > To: Matt Riedemann <mriedem(a)linux.vnet.ibm.com>, Ying Chun Guo/ > China/IBM@IBMCN > > Cc: openstack-i18n(a)lists.openstack.org > > Date: 2015/09/23 15:07 > > Subject: Re: [Openstack-i18n] translating python clients > > > > On 2015-09-22 22:53, Matt Riedemann wrote: > > > > > > > > > On 9/21/2015 10:49 AM, Ying Chun Guo wrote: > > >> Andreas Jaeger <aj(a)suse.com> wrote on 09/21/2015 10:27:29 PM: > > >> > > >> > From: Andreas Jaeger <aj(a)suse.com> > > >> > To: Matt Riedemann <mriedem(a)linux.vnet.ibm.com>, openstack- > > >> > i18n(a)lists.openstack.org > > >> > Date: 09/21/2015 10:28 PM > > >> > Subject: Re: [Openstack-i18n] translating python clients > > >> > > > >> > On 2015-09-21 16:09, Matt Riedemann wrote: > > >> > > > > >> > > > > >> > > On 9/18/2015 10:54 AM, Akihiro Motoki wrote: > > >> > >> I have no comment on Liberty translation priority atm. > > >> > >> > > >> > >> I think a couple of different topics are discussed at the same > > >> here. > > >> > >> > > >> > >> * CLI translation priority > > >> > >> * Server side project translation priority > > >> > >> * (potential) usage of server side project translations in Horizon > > >> > >> > > >> > >> We need to have more contact with project teams in the next cycle > > >> > >> more deeply to decide translation priorties before starting > > >> translations. > > >> > >> In the past releases, i18n team tended to start discussions after > > >> > >> starting > > >> > >> translations and it is too late for the game in most cases. > > >> > >> > > >> > >> Regarding client projects, I know openstackclient is our future and > > >> > >> the keystone team encourage to use openstackclient for Keystone v3 > > >> API. > > >> > >> However, regarding other projects like nova or neutron, > > >> > >> the progress of openstackclient integration is not well enojgh > > >> > >> and a new feature is implemented in each client. > > >> > >> Thus we need to consider the priority in the next cycle. > > >> > > > > >> > > I agree with this. We are nowhere near, as far as I can tell > > >> anyway, of > > >> > > deprecating python-novaclient. The reason we pushed the changes to > > >> > > translate the project is because people are pushing changes into > > >> > > python-novaclient to mark strings for translation, but there was > > >> never > > >> > > any infrastructure in place to do those translations (the project > > >> wasn't > > >> > > even configured with babel until a couple of weeks ago). > > >> > > > > >> > > So the feeling was, why not translate it? It's easy to setup. I > > >> agree > > >> > > that python-openstackclient is higher priority for the CLI, but > > >> > > python-novaclient is not going away anytime soon, especially now > > >> that we > > >> > > have microversion support in it for the compute API, which I don't > > >> think > > >> > > python-openstackclient has. > > >> > > > >> > But just the setup will not give you translations for free. Even if we > > >> > set it up, I fear no one will translate it. Therefore I wonder whether > > >> > it makes sense at all to enable the infrastructure if no translator > > >> > looks at it. > > >> > > > >> > Or in other words: Does the translation team want to have every > > >> possible > > >> > project in Zanata? Or only those they want to translate? And then the > > >> > question is which ones to translate? > > >> > > >> In my mind, translation platform should not block any people who want to > > >> translate > > >> any resources if the resources are available in Openstack community. > > >> So if dev team want to put their resources, put them there. > > > > > > This is my thinking as well. If the infrastructure is not in place, > > > people are definitely not going to translate it. I understand that > > > people might not translate it anyway, but I don't see the harm in having > > > it available for translation if someone wants that. And as pointed out > > > somewhere else on this topic, python-openstackclient and Horizon both > > > use python-novaclient, so unless those are completely handling all > > > errors that come out of novaclient, we should probably have novaclient > > > available for translations - at least of errors. > > > > > >> Andreas is right, putting projects in Zanata will not bring free > > >> translations. > > >> Based on my observation, translators prefer to translate UI projects > > >> more than other projects. > > >> For example, even I include Nova in the Liberty translation plan, the > > >> nova translation progress > > >> is not that good. > > >> In translation community, translation team, coordinators and even > > >> individual translators > > >> have the autonomy. > > > > So, policy sounds like: > > > > A project that wants translations - and is part of the big tent - can > > set it up. The i18n PTL suggests a priority and ask for translation of > > specific projects but translators are not limited on what to translate. > > > > Correct? > > > > Yes. > > > So, do you want to enable python-keystoneclient, python-novaclient, and > > python-neutronclient? Or only the later two since keystoneclient is > > deprecated and even throws warnings when used: > > > > Pending deprecation: Command-line interface to the OpenStack Identity API. > > This CLI is pending deprecation in favor of python-openstackclient. For a > > Python library, continue using python-keystoneclient. > > > > keystoneclient is only used for Python binding and the CLI in is deprecated. > So if there is no objections from keystone dev team, we could remove > keystoneclient. > Please enable openstack-novaclient because we get the request that > it needs translation. > I don't see neutronclient is deprecating. So please enable it too. > Thank you. > Just got inputs from keystone dev team. They said "openstackclient still receives strings from keystoneclient, (it uses keystoneclient to perform the requests) also, keystoneclient can be used by customer applications so they might want translated strings." So let's include python-keystoneclient in the translation projects. > > 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, Graham Norton, > > HRB 21284 (AG Nürnberg) > > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 > >

2 1