- OpenStack-I18n - lists.openstack.org

Re: [Openstack-i18n] I18n wiki page is translatable
by Ian Y. Choi 11 Nov '15

11 Nov '15

Thank you so much, Daisy and Akihiro! I also hope that everything runs so well. With many thanks, /Ian Ying Chun Guo wrote on 11/11/2015 4:09 PM: > > I think we need to disable the translation at first. > Then we could be able to move them. > I'm not able to move, same as you. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2015/11/11 14:40:43: > > > From: Akihiro Motoki <amotoki(a)gmail.com> > > To: Ying Chun Guo/China/IBM@IBMCN > > Cc: "Ian Y. Choi" <ianyrchoi(a)gmail.com>, Openstack-i18n <openstack- > > i18n(a)lists.openstack.org> > > Date: 2015/11/11 15:05 > > Subject: Re: [Openstack-i18n] I18n wiki page is translatable > > > > Daisy, > > > > It sounds good to me, but normal users like me cannot move pages. > > I got Permission Error. Could you handle all moving of pages? > > > > > > 2015-11-11 15:05 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > > > Thank you for the explain Ian. > > > I think we could move the wiki pages for language teams to > > > /I18nTeam/team/<language-code>, > > > and then keep /I18nTeam/<language-code> for the translation page of > > > I18nTeam. > > > > > > How do you think about it, Akihiro? > > > > > > Best regards > > > Ying Chun Guo (Daisy) > > > > > > > > > "Ian Y. Choi" <ianyrchoi(a)gmail.com> wrote on 2015/11/11 00:55:07: > > > > > >> From: "Ian Y. Choi" <ianyrchoi(a)gmail.com> > > >> To: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun Guo/China/IBM@IBMCN > > >> Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> > > >> Date: 2015/11/11 00:55 > > >> Subject: Re: [Openstack-i18n] I18n wiki page is translatable > > > > > > > > >> > > >> Hello Akihiro, > > >> > > >> Actually I suggested a translatable I18nTeam wiki page [1] for Korean > > >> during last Tokyo Design Summit. > > >> After saying it, I found that there might be a problem in > Japanese local > > >> team > > >> because Japanese language team already used /ja page, as you > mentioned and > > >> which would make conflict with translation functionality in OpenStack > > >> wiki. > > >> > > >> Let me first say why Korean translation page for I18nTeam is > needed and > > >> how Korean translation team wants to use two wiki pages separately: > > >> > > >> 1) https://wiki.openstack.org/wiki/I18nTeam/ko > > >> : To provide Korean guys with official I18nTeam introduction > wiki page > > >> : I think "Local Translation Teams" section is needed because this > > >> information is > > >> beneficial with the knowledge of the various language team > activities. > > >> > > >> 2) https://wiki.openstack.org/wiki/I18nTeam/team/ko_KR > > >> (I found that Daisy moved from .../ko_KR to .../team/ko_KR. > Thank you!) > > >> : To introduce Korean translation team with details and our > specific > > >> translation rules > > >> : Providing links for OpenStack I18n official introduction wiki > page & > > >> its translation > > >> > > >> I would like to respect I18nTeam official wiki page, and this > > >> information is written in English. > > >> In my opinion, translating this page would more clearly advertise > > >> OpenStack I18n overall activities to more Korean. > > >> > > >> This requirement and need might be different from various local > > >> translation teams, I think, > > >> and I also would like to respect the ways Japanese team used more > than 1 > > >> year. > > >> > > >> So I would like to suggest not to include "<languages />" tag on > [1] . > > >> As you know, OpenStack Release Note wiki pages such as [2] > > >> contain "<languages />" tag and displays different language > translated > > >> pages on the top part. > > >> > > >> I think this suggestion would satisfy different needs from various > > >> language translation teams. > > >> However, if https://wiki.openstack.org/wiki/I18nTeam page includes > > >> "<languages />" tag, > > >> then it would not fit to not only Japanese translation team, but also > > >> other teams such as French, Polish and so on. > > >> For Korean translation team, our official page contains the > translated > > >> I18nTeam link so it would be okay. > > >> > > >> I am not sure, but Daisy might already think so Daisy only moved from > > >> .../ko_KR to .../team/ko_KR, and > > >> did not include "<languages />" tag on [1] :) > > >> > > >> This is just my suggestion not to conflict with your team and to > > >> accomplish our team requirement, > > >> and I would like to listen Daisy's opinion and other language > teams' > > >> opinions. > > >> > > >> [1] https://wiki.openstack.org/wiki/I18nTeam > > >> [2] https://wiki.openstack.org/wiki/ReleaseNotes/Liberty > > >> > > >> > > >> With many thanks, > > >> > > >> /Ian > > >> > > >> Akihiro Motoki wrote on 11/10/2015 8:48 PM: > > >> > In addition, Japanese team maintains the original contents which > > >> > are differ from the English version of I18nTeam page. > > >> > Before enabling translation for I18nTeam, I would like to see a > solution > > >> > for language specific content. > > >> > > > >> > > > >> > 2015-11-10 20:45 GMT+09:00 Akihiro Motoki <amotoki(a)gmail.com>: > > >> >> I noticed the existing language team page cannot be edited. > > >> >> For example, https://wiki.openstack.org/wiki/I18nTeam/ja > exists from > > >> >> more than one year ago. > > >> >> After this change, we can no longer edit the original page. > > >> >> What should we do? > > >> >> > > >> >> In addition, I18nTeam wiki page contains contents which is not > > >> >> appropriate for translation, > > >> >> for example, "Local Translation Teams" section. > > >> >> As a local team coordinator, I don't like to display this > section in a > > >> >> translated version. > > >> >> > > >> >> Thanks, > > >> >> Akihiro > > >> >> > > >> >> 2015-11-10 18:11 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > > >> >>> Hi, > > >> >>> > > >> >>> As requested by Korean team, the wiki page of I18nTeam is > > >> translatable now. > > >> >>> If you want to translate this page into your own language, > > >> please go ahead. > > >> >>> Thank you. > > >> >>> > > >> >>> Best regards > > >> >>> Ying Chun Guo (Daisy) > > >> >>> > > >> >>> > > >> >>> _______________________________________________ > > >> >>> 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 > > >> > > >> -- > > >> /Ian > > >> > > > > > >

1 0

I18n wiki page is translatable
by Ying Chun Guo 11 Nov '15

11 Nov '15

Hi, As requested by Korean team, the wiki page of I18nTeam is translatable now. If you want to translate this page into your own language, please go ahead. Thank you. Best regards Ying Chun Guo (Daisy)

3 6

Granting access for a new translator for the finnish (finland) translation project
by Jori Kuusinen 10 Nov '15

10 Nov '15

Hi all i18n mailing list members, I registered myself for the finnish (finland) translation project page and would like to have myself granted as a contributor. As a global project owner, I think "Daisy" is in charge for granting access if I'm not mistaken. Looking forward to begin contributing for the project. With kind regards, J o r i

1 0

FYI: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka
by KATO Tomoyuki 09 Nov '15

09 Nov '15

FYI. KATO Tomoyuki ---- As we discussed at the summit, the release management team is modifying our change management tracking tools and processes this cycle. This email is the official announcement of those changes, with more detail than we provided at the summit. In past cycles, we have used a combination of Launchpad milestone pages and our wiki to track changes in releases. We used to pull together release notes for stable point releases at the time of release. Most of that work fell to the stable maintenance and release teams. Similarly, the release managers worked with PTLs and release liaisons at each milestone checkpoint to update Launchpad to accurately reflect the work completed at each stage of development. It's a lot of work to fix up Launchpad and assemble the notes and make sure they are accurate, which has caused us to be a bottleneck for clear and complete communication at the time of the release. We have been looking for ways to reduce that effort for these tasks and eliminate the bottleneck for some time. This cycle, to address these problems for our ever-growing set of projects, the release management team is introducing a new tool for handling release notes as files in-tree, to allow us to simply and continuously build the release notes for stable branch point releases and milestones on the master branch. The idea is to use small YAML files, usually one per note or patch, to avoid merge conflicts on backports and then to compile those files in a deterministic way into a more readable document for readers. Files containing release notes can be including in patches directly, or you can create a separate patch with release notes if you want to document a feature than spans several patches. The tool is called Reno, and it currently supports ReStructuredText and Sphinx for converting note input files to HTML for publication. Reno is git branch-aware, so we can have separate release notes documents for each release series published together from the master build. The documentation for Reno, including design principles and basic usage instructions, is available at [1]. For now we are focusing on Sphinx integration so that release notes are published online. We will add setuptools integration in a future version of Reno so that the release notes can be built with the source distribution. As part of this rollout, I will also be updating the settings for the gerrit hook script so that when a patch with "Closes-Bug" in the commit message is merged the bug will be marked as "Fix Released" instead of "Fix Committeed" (since "Fix Committed" is not a closed state). When that work is done, I'll send another email to let PTLs know they can go through their existing bugs and change their status. We are ready to start rolling out Reno for use with Liberty stable branch releases and in master for the Mitaka release. We need the release liaisons to create and merge a few patches for each project between now and the Mitaka-1 milestone. 1. We need one patch to the master branch of the project to add the instructions for publishing the notes as part of the project sphinx documentation build. An example patch for Glance is in [2]. 2. We need another patch to the stable/liberty branch of the project to set up Reno and introduce the first release note for that series. An example patch for Glance is in [3]. 3. Each project needs to turn on the relevant jobs in project-config. An example patch using Glance is in [4]. New patches will need to be based on the change that adds the necessary template [5], until that lands. 4. Reno was not ready before the summit, so we started by using the wiki for release notes for the initial Liberty releases. We also need liaisons to convert those notes to reno YAML files in the stable/liberty branch of each project. Please use the topic "add-reno" for all patches so we can track adoption. Once those merge, project teams can stop using Launchpad for tracking completed work. We will still use Launchpad for bug reports, for now. If a team wants to continue using it for tracking blueprints, that's fine. If a team wants to use Launchpad for scheduling work to be done in the future, but not for release tracking, that is also fine. The release management team will no longer be reviewing or updating Launchpad as part of the release process. Thanks, Doug [1] http://docs.openstack.org/developer/reno/ [2] https://review.openstack.org/241323 [3] https://review.openstack.org/241322 [4] https://review.openstack.org/241344 [5] https://review.openstack.org/241343 __________________________________________________________________________ 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

1 0

What's Up, Doc? 6 November 2015
by Lana Brindley 06 Nov '15

06 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, Wow! What a great Summit! And isn't Tokyo a truly beautiful and amazing city? Thank you so much to the Japanese Stackers who hosted us, and to everyone who came along to the docs sessions and helped us hammer out a great plan for Mitaka. I'm very excited about this release! This week, I've been catching up with everything that happened during Summit, and also working on outreach tasks. Today, I recorded an interview with Foundation about the project, and I've also published a blog post on the same topic, which will be published soon. You might also like to check out the Superuser interview Anne and I did about the docs while we were in Tokyo: http://superuser.openstack.org/articles/openstack-documentation-why-it-s-im… == Progress towards Mitaka == 152 days to go! 77 bugs closed so far for this release. API Docs * The API docs are will be switched to swagger: http://specs.openstack.org/openstack/docs-specs/specs/liberty/api-site.html DocImpact * I've removed the WIP from this blueprint, and will be working on this from next week: https://blueprints.launchpad.net/openstack-manuals/+spec/review-docimpact RST Conversions * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * Ops Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/ops-guide-rst ** Lana will reach out to O'Reilly to discuss the printed book before this work begins * Config Ref ** Thanks for all the offers of help on this one! Please contact the Config Ref Speciality team: https://wiki.openstack.org/wiki/Documentation/ConfigRef Reorganisations * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides Training * Labs ** https://blueprints.launchpad.net/openstack-manuals/+spec/training-labs * Guides ** Upstream University & 'core' component updates, EOL Upstream Wiki page. Document openstack-doc-tools * Need volunteers for this! Reorganise index page * The API docs have already moved off the front page * We need volunteers to look at the organisation of this page and to write one-sentence summaries of each book == Doc team meeting == Meetings will kick off again next week with the APAC meeting: APAC: Wednesday 11 November, 00:30:00 UTC US: Wednesday 18 November, 14: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… - -- Keep on doc'ing! 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/ iQEcBAEBCAAGBQJWPC4TAAoJELppzVb4+KUynpUH/30Y6pv7Zrse+YM1ki2pqLqi dp0f9RysJQkvXOA7OWy48kWLWXgMF0/hq1DIhrZ9AlsUCGOGC04/YVGNyaCAxMkx TTpyi6gJWl9Fiwbrc6k63MPx7OMFDcGu8KQow7tCBewH0jYngiJeP/mxIP6AnhBy SHVsZZ4OG99w/xZyUe8rVGkpXLFUfow8u0r4hCLlFGSUxLD3jz8ABp2HX7mf3ICi 0u1rgxD08lWSHPHRmhzUZ+kx7uW1ZY0UWiX1rsyTU690dsYbYeJSUcY+Saf2md52 eIGk7yevZaYczXvn9vo/rfwZCc4G5jyRFp55yR/BfD/2NVsjmt2vvguWTnDywEE= =Y0ik -----END PGP SIGNATURE-----

1 0

IRC meeting tomorrow
by Ying Chun Guo 04 Nov '15

04 Nov '15

1 0

mark as read-only policy
by KATO Tomoyuki 01 Nov '15

01 Nov '15

Hi Daisy, Today, I found some projects are translable at both master and stable-liberty branch. In my understand, only one branch should be translable. Just a example,I do not check all projects. * ironic * ceilometer Regards, KATO Tomoyuki

3 6

magnum-ui translation setup
by Andreas Jaeger 01 Nov '15

01 Nov '15

Steve and myself have been working on fixing the broken translation for magnum-ui. I didn't notice that it uses *two* pot files like horizon (one for python files, one for javascript) and uses as well a django and djangojs file and thus wrote these: https://review.openstack.org/#/c/240650/ https://review.openstack.org/#/c/240651/ Will these duplicated names - django in both horizon and magnum-ui - cause any problems in the running system? I doubt it since already horizon has *two* different django files but wanted to double check - and ask for review of the above. I think we need to use this setup for other dashboard related projects, so also for designate-dashboard. Reviews and comments are welcome, 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

I18n team meet up in Tokyo
by Ying Chun Guo 31 Oct '15

31 Oct '15

3 2

What's Up, Doc? 三鷹 Summit Edition
by Lana Brindley 30 Oct '15

30 Oct '15

Hi everyone, Welcome to the Summit edition of the docs newsletter! Docs have had a wonderfully productive week here in Tokyo, and we've now established a plan for Mitaka. This newsletter covers the more important announcements, and the main points we want to hit in the next release. Karin has kindly written up the summary of the Design Summit sessions here: https://etherpad.openstack.org/p/Mitaka-Docs-Meetup == Mitaka Goals == This is the list at the moment. There are more notes in the docs etherpads, and not everything has blueprints yet. * Switch API docs over to swagger http://specs.openstack.org/openstack/docs-specs/specs/liberty/api-site.html (???) * Implement new docimpact plan: https://blueprints.launchpad.net/openstack-manuals/+spec/review-docimpact * RST Conversions: ** Arch Guide: https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Ops Guide: https://blueprints.launchpad.net/openstack-manuals/+spec/ops-guide-rst (pending O'Reilly conversation) ** Config Ref * Reorganisations: ** Arch Guide: https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Ops Guide: https://blueprints.launchpad.net/openstack-manuals/+spec/improve-ops-guide ** User Guides: https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… * Training ** Labs: https://blueprints.launchpad.net/openstack-manuals/+spec/training-labs ** Guides: Upstream University & 'core' component updates, EOL Upstream Wiki page. * First App Guide: testing & improvements * Reorganise the index page * Document the openstack-doc-tools == Speciality Team Changes == More detail on the Speciality Team wiki page: https://wiki.openstack.org/wiki/Documentation/SpecialityTeams * Install Guide is now with Christian Berendt * HA Guide is now with Bogdan Dobrelya * Networking Guide is now with Edgar Magana * New Hypervisor Tuning Guide team with Joe Topjian あなたの東京ありがとう! Lana Lana Brindley Technical Writer Rackspace Cloud Builders Australia

1 0

dashboard translation check site
by KATO Tomoyuki 29 Oct '15

29 Oct '15

Hi, Elizabeth, Akihiro, Daisy Just a memorandum from the Summit session. We need share the operation process of Akihiro's personal dashboard translation check site before we prepare the our official check site. The check site is built with DevStack. Basic scripts for import and export tranlations are: https://github.com/amotoki/horizon-i18n-tools * need update from Transifex client to Zanata client Akihiro-san, please follow up and correct the details. Thanks, KATO Tomoyuki

2 1

Request to join local Translation in thai language.
by sawangpong muadphet 29 Oct '15

29 Oct '15

Dear Team My name is Sawangpong Muadphet from Thailand. I would like to join the Local Translation Teams for Thailand. I am contribute on Openstack promotion in Thailand for 2 yrs. I do training openstack also. But thai language is not in the openstack yet. I do hope that Thai people will have more opportunity in openstack my transfix account: sawangpongm Sincerely yours Sawangpong Muadphet CEO www.itbakery.net <http://www.itbakery.net/> Thailand

4 3

Call for Presentation Proposals for FUEL GILT Conference 2015!
by Rajesh Ranjan 24 Oct '15

24 Oct '15

FUEL GILT Conference is one of the largest events of FOSS language technology - Its challenges, solutions, best practices and its conventions. Due to some unavoidable reasons, we are a bit late in announcing CFP. We apologize for the same. We are late, but this time we have grand plan to celebrate the presence of our languages on new technology platform. Yes, we have a grand plan! Total three days for the event : 20,21 and 22 Nov 2015. So, save these dates on your calender! The host for the event and venue is - Tamil Virtual Academy (Erstwhile Tamil Virtual University), Anna University Campus, Gandhi Mandapam Road, Kottur, Chennai, Tamil Nadu. Thank you TVA. We are happy that, this time Mozilla Localisation Hackathon is being organised as a part of FUEL Gilt Conference 2015. We have FUEL Gilt Conference on 20th Nov and Mozilla l10n Hackthon on 21-22 Nov.However, the localization hackathon is open to the invited members only. If you are one of the localizers contributing to Mozilla, you may contact your locale leader to know more about it. This year Mozilla Corporation, Centre for Development of Advance Computing (C-DAC), Pune and Red Hat are the main organizers of the Conference. The event is being hosted at Tamil Virtual Academy and supported by Free Software Foundation Tamil Nadu. Thank you all for helping hand. Call for Presentation Proposal is open till Oct 31, 2015. Please send your proposal in required format mentioned on the page: http://fuelproject.org/gilt2015/index FUEL is growing only because of the support of volunteer communities world-wide and several well known organizations! The power of the event is the power of collaboration, the power of sharing, the power of volunteerism! Currently, More than 60 language communities are working with the FUEL Project. Since 2008, FUEL Project is consistently working with the different language communities to provide standard linguistic resources eg. Terminologies, style guides, assessment methods etc. to the world.Like last year, please collaborate and cooperate to make the event a huge success! For more details, please visit: http://fuelproject.org/gilt2015/index -- Rajesh Ranjan www.rajeshranjan.in @kajha <https://twitter.com/kajha> Developing a linguistic standard for language localization <http://www.livemint.com/Industry/zWJ1943VQmwABkZGmMTT2H/Developing-a-lingui…>

1 0

Horizon problem in pt
by Andreas Jaeger 22 Oct '15

22 Oct '15

Looking at todays bot run for Horizon on stable/liberty - see https://jenkins.openstack.org/job/horizon-propose-translation-update-libert… - I noticed a failure writing pt file for openstack_dashboard/locale/django: 2015-10-20 06:36:20.057 | [INFO] Writing translation file in locale pt for document openstack_dashboard/locale/django 2015-10-20 06:36:20.536 | [ERROR] Operation failed: javax.xml.bind.UnmarshalException 2015-10-20 06:36:20.536 | - with linked exception: 2015-10-20 06:36:20.536 | [org.xml.sax.SAXParseException; lineNumber: 4; columnNumber: 357; An invalid XML character (Unicode: 0x8) was found in the element content of the document.] 2015-10-20 06:36:20.536 | 2015-10-20 06:36:20.536 | To retry from the last document, please set the following option(s): 2015-10-20 06:36:20.536 | 2015-10-20 06:36:20.536 | --from-doc "openstack_dashboard/locale/django" 2015-10-20 06:36:20.537 | Is there anybody to fix this, 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

3 7

I18n contributors meetup in Tokyo
by Ying Chun Guo 22 Oct '15

22 Oct '15

1 0

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

Stable translations?
by Andreas Jaeger 19 Oct '15

19 Oct '15

We had a few days ago some IRC discussion on how to translate stable branches and wrote up the following: https://wiki.openstack.org/wiki/Translations/Infrastructure#New_proposal Is that clear? Is it something we should try? Daisy, did you talk to the stable team yet? 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 2

How is openstack-manuals/common-rst updated?
by Akihiro Motoki 17 Oct '15

17 Oct '15

Hi team, During translation of common-rst in Zanata, I found a bit odd entries in openstack-manuals/doc/common-rst/source/locale/common-rst.pot. When and how is openstack-manuals/common-rst updated? For example, we see the following in common-rst.pot: --- #: ../common/app_support.rst:3 msgid "Community support" msgstr "" #: ../common/app_support.rst:5 msgid "Community Support" msgstr "" ---- However, we actually have only the first entry in common-rst/*.rst: --- $ grep -r 'Community Support' doc/common-rst/*.rst $ grep -r 'Community support' doc/common-rst/*.rst doc/common-rst/app_support.rst:Community support --- If you look at app_support.rst, we have only the first one. Where does the second one come from? In tools/generatepot-rst.sh, processing on 'common-rst' is skipped. I wonder which script we update common-rst.pot. Thanks, Akihiro

3 7

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

New translation plan is published
by Ying Chun Guo 16 Oct '15

16 Oct '15

Hello, team During the IRC meeting yesterday, the team decided to focus on "installation guide" translation in the next 3 months. The documents of "installation guide" is in the project "openstack-manuals". We will work with the master version, because the liberty version is not branched yet. When documentation team branches the stable-liberty, we will create the same version in Zanata and switch our translations there. The plan is published in the homepage of translate.openstack.org. BTW, I failed to set the hyperlink to doc "install-guide" directly. The hyperlink in the homepage will direct you to the project "openstack-manuals", not the doc. Then you have to select document "install-guide" from the list. Thank you. Best regards Ying Chun Guo (Daisy)

1 0

IRC meeting tomorrow
by Ying Chun Guo 15 Oct '15

15 Oct '15

Hi, team We will have our IRC meeting tomorrow in IRC channel #openstack-meeting at 1300 UTC on 15th October. I'm going to discuss following topics: Discussion: document translation plan Open discussions If you have topics, please propose here. Best regards Ying Chun Guo (Daisy)

2 1

Fwd: [Bug 1505870] [NEW] 安装配置控制节点服务器 in Red Hat Enterprise Linux 7, CentOS 7, and Fedora 20 的 OpenStack 安装手册 - Kilo
by Lana Brindley 14 Oct '15

14 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi i18n team, I noticed this bug in our queue today. Zhu Rong has been kind enough to help me with the translation. I understand that there's an issue in the Chinese version of the guide, which doesn't appear in the English version. Are you able to help? Thank you, Lana - -------- Forwarded Message -------- Subject: [Bug 1505870] [NEW] 安装配置控制节点服务器 in Red Hat Enterprise Linux 7, CentOS 7, and Fedora 20 的 OpenStack 安装手册 - Kilo Date: Wed, 14 Oct 2015 01:46:28 -0000 From: fangc <swjfc22(a)163.com> Reply-To: Bug 1505870 <1505870(a)bugs.launchpad.net> To: openstack(a)lanabrindley.com Public bug reported: 这个显示是kilo安装手册，但是在同步数据时参数仍然用的juno，这会在后续步骤中报错。 # su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf \ --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade juno" neutron juno应该改为kilo才可以，不然下一步就会出错，网络节点无法连接到控制节点。 - ----------------------------------- Built: 2015-03-30T21:27:48 08:00 git SHA: 3da25b5440ad6ef89618eb6ec20c8dc8f465d3c6 URL: http://docs.ocselected.org/openstack-manuals/kilo/install/rpm/content/neutr… source File: file:/media/develop/develop/openstack/openstack-manuals/generated/zh_CN/install-guide/section_neutron-controller-node.xml xml:id: neutron-controller-node ** Affects: openstack-manuals Importance: Undecided Status: New - -- You received this bug notification because you are subscribed to openstack-manuals. Matching subscriptions: Manuals Bugs, Openstack Manuals https://bugs.launchpad.net/bugs/1505870 Title: 安装配置控制节点服务器 in Red Hat Enterprise Linux 7, CentOS 7, and Fedora 20 的 OpenStack 安装手册 - Kilo Status in openstack-manuals: New Bug description: 这个显示是kilo安装手册，但是在同步数据时参数仍然用的juno，这会在后续步骤中报错。 # su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf \ --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade juno" neutron juno应该改为kilo才可以，不然下一步就会出错，网络节点无法连接到控制节点。 ----------------------------------- Built: 2015-03-30T21:27:48 08:00 git SHA: 3da25b5440ad6ef89618eb6ec20c8dc8f465d3c6 URL: http://docs.ocselected.org/openstack-manuals/kilo/install/rpm/content/neutr… source File: file:/media/develop/develop/openstack/openstack-manuals/generated/zh_CN/install-guide/section_neutron-controller-node.xml xml:id: neutron-controller-node To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1505870/+subscriptions -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWHcyeAAoJELppzVb4+KUyz9sH/2s20AHuYFX7IFoZJscAg1kS T9DTbrDdBay9LN7Z9QYgc/lSSnW6K7IzQSNOwlgHD1BvoAI2pW1AMuYrTuy69Yu4 h1Udn3f2j+e79U19qvqoOTpu/5QUiXwD+ySPHhUbVEkXg6jvrQmrYtwFyO8gSsb/ yWsBvuxVc1yqhsUnLm5/PG92Ijy/Jh5d5NxaR+LeUcDIGg8GL15CQczwEP2PZMAj zHvxYrhw10YMs+jhtHAfTPOTr1cv38KIuzpBeki7sQ9yz+Gb07/2Oy+Lm9/QzjKr oDvUr3XdERona8/Yq/fGPNb/ReKsC393vgtnxvYc+t9znoBMEYpLV8iDpq7Q5D4= =+JvA -----END PGP SIGNATURE-----

3 4

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 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