September 2015 - OpenStack-I18n - lists.openstack.org

I18n sessions plan in Tokyo summit
by Ying Chun Guo 22 Oct '15

22 Oct '15

Hello, team I plan to have two I18n working sessions and a half day I18n contributors meet up in Tokyo summit. Here are the descriptions of the two working sessions. Working session #1. Time: 4:40pm - 5:20pm on Oct. 27, Tuesday Title: Review of the tool support in Liberty translations Abstract: We just moved to the new translation tool in Liberty. In this session, we will review how Liberty translation went with Zanata. We will collect issues/problems we met in Liberty translation, talk about how to improve in the future, and figure out the next steps. The agenda will be tracked here: https://etherpad.openstack.org/p/tokyo-translation-tool-support Working session #2. Time: 5:30pm - 6:10pm on Oct. 27, Tuesday Title: How translation schedule fits the development schedule? Abstract: In Liberty, we redefined the string freeze, split into soft string freeze and hard string freeze. In this session, we will collect the feedback to translation schedule from both translators and developers, refine the definition of string freeze, and figure out a better translation schedule for next release. The agenda will be tracked here: https://etherpad.openstack.org/p/tokyo-translation-schedule The time of i18n meet up is not decided yet. It's a kind of round table, and doesn't have title and abstract. People could join and raise any discussions/questions related with i18n/l10n/translation there. We will use this page to track the agenda: https://etherpad.openstack.org/p/tokyo-i18n-meetup If you have any issues with these sessions, please let me know. Thank you. Best regards Ying Chun Guo (Daisy)

2 2

Re: [Openstack-i18n] [Openstack] OpenStack Kilo Release Note Translation
by Tom Fifield 17 Oct '15

17 Oct '15

Hi, I just clicked "Mark This Page for Translation", which should fix this, I think. """ The page ReleaseNotes/Kilo has been marked up for translation with 166 translation units. The page can now be translated. """ Regards, Tom On 01/05/15 10:40, Ray Sun wrote: > By the way, I found this in mediawiki translation plugin document: > > This page contains changes which are not marked for translation." if you > are not a translation administrator > > Best Regards > -- Ray > > On Fri, May 1, 2015 at 10:38 AM, Ray Sun <xiaoquqi(a)gmail.com > <mailto:xiaoquqi@gmail.com>> wrote: > > Stackers, > I try to translate OpenStack Kilo release note, but I don't think I > have permission to do that even if I added translation tag for it. > Any one who have that permission, please help. Thanks. > > Best Regards > -- Ray > > > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack(a)lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >

4 10

API Quick Start
by Anne Gentle 06 Oct '15

06 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

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

01 Oct '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 30 Sep '15

30 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 26 Sep '15

26 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 26 Sep '15

26 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 25 Sep '15

25 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