- OpenStack-I18n - lists.openstack.org

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 10 Oct '15

10 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 10 Oct '15

10 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 09 Oct '15

09 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 09 Oct '15

09 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