- OpenStack-I18n - lists.openstack.org

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

What's Up, Doc? 25 September 2015
by Lana Brindley 25 Sep '15

25 Sep '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, First of all, thank you to everyone who has suggested sessions for docs at Tokyo. I'll keep the etherpad open for another week or so, just to give everyone a chance, and will start working on a draft schedule next week. I have spent most of this week on bug triage, which is repetitive work, but it's gratifying to see the numbers drop a little! == Progress towards Liberty == 19 days to go 534 bugs closed so far for this release. The main areas of focus we had during Liberty were the RST migration, paying down some of our technical debt, and improving our general communication issues. The RST conversion is well and truly complete, with just a couple of books waiting in the wings to be published. We have made some progress on improving our communication generally, with liaisons now more visible and involved, and some improved processes. Regarding old bugs, during Liberty we spotlighted a total of 24 bugs, exactly half of which have now been closed. == Mitaka Summit Prep == The schedule app for your phone is now available. This is a great tool once you're on the ground at Summit: https://itunes.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=98721 6292&mt=8 (Apple) and https://play.google.com/store/apps/details?id=org.sched.openstacksummitm ay2015vancouver (Android) Docs have been allocated two fishbowls, four workrooms, and a half day meetup, so now is the time to start gathering ideas for what you would like to see us cover. Add your ideas to the etherpad here: https://etherpad.openstack.org/p/Tokyo-DocsSessions I'll create a draft session based on this feedback next week. == 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! == Spotlight Bugs == During Liberty we spotlighted a total of 24 bugs, exactly half of which have now been closed. This is a great effort to clear out some old dusty bugs and pay down some technical debt. Thanks go out to Tom Fifield, Olga Gusarenko, Yusuke Ide, Brian Moss, Deena Cooper, and Alexandra Settle for taking them on! With Liberty and the Summit bearing down on us, though, let's focus back on what needs to be done for release. At Summit, we'll discuss how to expand and improve on this effort in future releases. == Doc team meeting == The US meeting was held this week. The minutes are here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-09-23 The next meetings will be the final meetings before the Liberty release: APAC: Wednesday 30 September, 00:30:00 UTC US: Wednesday 7 October, 14:00: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 iQEcBAEBAgAGBQJWBNTTAAoJELppzVb4+KUyW6EH/2kYOYHa2DHfHJxN2XC1QcpD L3wwDWxu9B2G6M/hNzRJ/KELSVikfuK9+ChOA+kD2kXLs6dV1oLXXCbV2KIdHKWP +EYPG0G/CsMkoq8KIfzYwW6c2k+RzSXZAnI1ZhcRJiwhlIC5JlSZ118Y64GeLxmB jISEqsi7WdK76caMmEy+3+QrpBY/WNOVE5Dyu0TiwGTPtU1EuZEAXHkdFjczKEKM azlyyFIF4V28+BjrZpUybarEL2hZerHt2XiNd5dCRoQgE7b8ubJ0cidErPazI9AV mZNZO3VtLTfSC2ytNBwIBaN3ezJzC5mvba6ofDdej3jIvZf3o6IQihbMaYWyLDI= =uZBu -----END PGP SIGNATURE-----

1 0

translating python clients
by Andreas Jaeger 25 Sep '15

25 Sep '15

We now have setup python-keystoneclient for translation and there're requests for python-heatclient and python-novaclient (https://review.openstack.org/224832 heat and https://review.openstack.org/224222 nova) Does it really make sense to translate these? Especially with the openstack client getting translated already? My proposal would be to concentrate on the openstack client and tell the teams to not mark the clients for translation. What do you think? Please see also http://lists.openstack.org/pipermail/openstack-dev/2015-September/073698.ht… 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 11

stable-liberty is created for nova project
by Ying Chun Guo 24 Sep '15

24 Sep '15

Hi, translation team Nova has its RC1 cut yesterday. Hard string freeze is happened. I 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 is set "Read Only" and will be open to accept translations after Liberty is done. Any problems, please let me know. Best regards Ying Chun Guo (Daisy)

1 0

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

23 Sep '15

1 0

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

23 Sep '15

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 >

1 0

Re: [Openstack-i18n] IBM translations to contribute: update
by Ying Chun Guo 23 Sep '15

23 Sep '15

Hi, team I have made enough tests on the test server with the help from Doug and his colleagues. In the test server, I created versions for nova, glance, cinder, swift, ceilometer, heat, keystone, and ironic. Doug and his colleagues uploaded their po files for languages de, es, fr, it, ja ko-KR, pr-BR, ru, zh-CN, and zh-TW. I tested merging two versions. Things are running well. The test server is still in good condition. So there is no technical issues block me to do the same in the production server. I even tried "Group" in the test server. The "Group" feature looks wonderful. So if there is no objections, I will go to production server, doing the same as what I did in the test server. Best regards Ying Chun Guo (Daisy) Douglas Fish/Rochester/IBM wrote on 09/18/2015 05:14:22 AM: > From: Douglas Fish/Rochester/IBM@IBMUS > To: guoyingc(a)cn.ibm.com > Cc: openstack-i18n(a)lists.openstack.org > Date: 09/18/2015 05:14 AM > Subject: Re: [Openstack-i18n] IBM translations to contribute: update > > Hi Daisy, > > We have translations to contribute for ceilometer, cinder, glance, > heat, ironic, keystone, nova and swift for languages de, es, fr, it, > ja ko-KR, pr-BR, ru, zh-CN, and zh-TW > > We are working to upload those to the Zanata test server to make > sure there are no technical issues. > > Doug > > ----- Original message ----- > From: Ying Chun Guo <guoyingc(a)cn.ibm.com> > To: Douglas Fish/Rochester/IBM@IBMUS > Cc: "Openstack-i18n Openstack-i18n" <openstack-i18n(a)lists.openstack.org> > Subject: Re: [Openstack-i18n] IBM translations to contribute: update > Date: Thu, Sep 17, 2015 11:04 AM > > Hi Doug, Hi team, > > In today's IRC meeting, we talked about the process to get IBM translations. > I'm going to normalize the process to contribute translations by > uploading po files. > > Here are some key points during the meeting: > > 1. It is strongly discouraged to use the offline editor other than web tool. > Because the offline editor could not take the advantages of > translation memory and glossary, > which might affect the translation quality. > 2. Simply uploading po files are not allowed because it has a risk > that the po files might contain bad translations. > 3. In some special cases, if people who want to contribute > translations by uploading po files, following below steps > 3.1 Send email to I18n mailing list, describing the source > documents and languages he/she is going to upload. > 3.2 Zanata admin will create a branch. Then contributors could > upload po files to the proposed branch. > 3.3 When the uploading is done, language coordinators could > review the translations. > The coordinators could have two kinds of review results: > agree to merge or deny to merge. > If the coordinators deny to merge, coordinators should > give some comments, either to delete this branch, or to suggestions > to improve. > 3.4 If the coordinators agree to merge to the master branch, > Zanata admin will make the merge. > A option could set during the branches merging to make sure not > overwrite translated/approved translations in the source branch. > After merging, the proposed branch will be deleted. > > I have been testing branches in the Zanata test server for several days. > When I make sure it works fine, I will go to the production server. > > @Doug, please let us know which resources and which languages you > are going to propose ? > > Best regards > Ying Chun Guo (Daisy) > > > "Douglas Fish" <drfish(a)us.ibm.com> wrote on 09/16/2015 08:05:52 PM: > > > From: "Douglas Fish" <drfish(a)us.ibm.com> > > To: "Openstack-i18n Openstack-i18n" <openstack-i18n(a)lists.openstack.org> > > Date: 09/16/2015 08:06 PM > > Subject: [Openstack-i18n] IBM translations to contribute: update > > > > Here's the revised approach we are taking to contributing our IBM > > translations to the community, based on feedback on suggestions: > > > > We are planning to make the proposed translations available for a > > pre-review as a separate branch in Zanata, but they are not there > > yet. While testing out this upload on the development server we > > discovered that uploading PO files caused the server to become > > unresponsive for a while. Thanks to pleia2 and the infra team for > > sorting that out and addressing the issue. We'll try the upload on > > dev again tomorrow and if it goes well we will make the translations > > available for pre-review in a separate Zanata branch. > > > > I had originally proposed ending the pre-review on Monday. Obviously > > that's not going to happen! I understand that different language > > teams have differing levels of readiness to accept these > > contributions. I understand some groups are ready at this time, > > while others would like to have more time, possibly even into Mitaka > > to review. We aren't going to upload PO files for any language were > > the team does not want them. > > > > Language coordinators, please let me know how you'd like to proceed > > with these contributions for your language. Do you want > > 1) us to upload them to Zanata's current master translations for > > normal review and editing as soon as we can, > > 2) us to upload them to Zanata as a separate branch for further > pre-review, or > > 3) hold off any submission or preview at this time. > > > > Please note that it important to us that we upload these > > translations. The translations are a valued IBM asset, it's > > important to us that they are recognized as contributed by IBM. > > > > I'll be at the Thursday i18n team meeting, and am available by IRC > > (doug-fish) or email if you have questions or further concerns. > > > > Thanks! > > > > Doug_______________________________________________ > > Openstack-i18n mailing list > > Openstack-i18n(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

6 17

Arabic Script mixed with Gurmukhi Script in Translation Memory
by ਅਨਪੜ੍ਹ ਜਿਮੀਂਦਾਰ 23 Sep '15

23 Sep '15

Hi there, As I don't know how this mix up happened so someone please respond to this issue. After the migration has done and i am doing translation in Zanata I am quite surprised to see Arabic script in my Translation Memory of many projects. I have clarified before, and explaining again, that Punjabi has two entirely different scripts i.e. Gurmukhi (ਪੈਂਤੀ) and Shahmukhi (اردو), while former is widely used in Indian side of Punjab aka Eastern Punjab the latter is used in Pakistani side of Punjab aka Western Punjab. I guess while migration someone has mistaken both the scripts as one and joined them. As this is my assumption so it is you guys, will have to help me out. Thanks Amandeep Singh Saini Co-ordinator Punjabi Team (pa-IN)

3 5

Re: [Openstack-i18n] Russian translations with 4 pluralities?
by Douglas Fish 23 Sep '15

23 Sep '15

3 2