- OpenStack-I18n - lists.openstack.org

Puzzled with Japanese ha-guide
by Andreas Jaeger 06 Jan '17

06 Jan '17

https://review.openstack.org/#/c/417318/ imports the Japanese ha-guide and trying to build it, sphinx fails with: Exception occurred: File "/home/aj/Software/vcs/OpenStack/openstack/openstack-manuals/.tox/venv/lib/python2.7/site-packages/docutils/nodes.py", line 1367, in set_duplicate_name_id old_node = self.ids[old_id] KeyError: 'install-rabbitmq' I'm not sure what's going on here ;( we have in shared-messaging-rst: - :ref:`Install RabbitMQ<rabbitmq-install>` And later the headline "Install RabbitMQ" with the label above. If I remove this entry from the po file, it still fails building: msgid ":ref:`Install RabbitMQ<rabbitmq-install>`" msgstr ":ref:`RabbitMQ のインストール<rabbitmq-install>`" Could somebody investigate and fix this, please? Note for building, I did: diff --git a/doc-tools-check-languages.conf b/doc-tools-check-languages.conf index d562f83..ddb0047 100644 --- a/doc-tools-check-languages.conf +++ b/doc-tools-check-languages.conf @@ -8,7 +8,8 @@ declare -A BOOKS=( ["de"]="install-guide" ["fr"]="install-guide" ["id"]="install-guide user-guide" - ["ja"]="image-guide install-guide networking-guide ops-guide user-guide" +# ["ja"]="ha-guide image-guide install-guide networking-guide ops-guide user-guide" + ["ja"]="ha-guide" ["ko_KR"]="install-guide" ["zh_CN"]="install-guide user-guide" ) @@ -19,7 +20,7 @@ declare -A DRAFTS=( ["de"]="install-guide" ["fr"]="install-guide" ["id"]="install-guide" - ["ja"]="install-guide networking-guide ops-guide" + ["ja"]="ha-guide install-guide networking-guide ops-guide" ["ko_KR"]="install-guide" ["zh_CN"]="install-guide" And then run locally "tox -e buildlang -- ja". Note that it gives a success message despites failing (the next openstack-doc-tools update will fail this), Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: 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

[Bug 1651917] [NEW] Storage 노드 설치와 구성 in Installation Guide
by junghyunchoi 05 Jan '17

05 Jan '17

Public bug reported: There is a typo. The following sentences should be changed 스토리지 노드를 설치dhk -> 스토리지 노드를 설치와 ----------------------------------- Release: 0.1 on 2016-12-21 10:47 SHA: 8868f91f9b758e1f98a2fac0c50b703e6ae1b6d3 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/ko_KR/install-guide-ubuntu/swift-storage-i… ** Affects: openstack-i18n Importance: Undecided Assignee: junghyunchoi (choipro14) Status: In Progress ** Tags: install-guide ** Changed in: openstack-i18n Assignee: (unassigned) => junghyunchoi (choipro14) ** Changed in: openstack-i18n Status: New => In Progress -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1651917 Title: Storage 노드 설치와 구성 in Installation Guide Status in openstack i18n: In Progress Bug description: There is a typo. The following sentences should be changed 스토리지 노드를 설치dhk -> 스토리지 노드를 설치와 ----------------------------------- Release: 0.1 on 2016-12-21 10:47 SHA: 8868f91f9b758e1f98a2fac0c50b703e6ae1b6d3 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/ko_KR/install-guide-ubuntu/swift-storage-i… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1651917/+subscriptions

2 1

Re: [OpenStack-I18n] [openstack-dev] Fwd: [Openstack] The Forum: in more detail
by Ian Y. Choi 04 Jan '17

04 Jan '17

Hello, What a good article for the background of Forum and PTG with details! By the way, I have one question regarding to discount of translators for the Forum. Due to the nature (large number of members, geographically-dispersed, coming from all over our community, ops, devs, users) of I18n team [1], me and previous I18n PTLs (Daisy and Kato-san) have encouraged translators to participate in Forum to meet each other offline and discuss many translation and integration issues rather than attending to PTG. For translators, it seems that few translators will physically attend to PTG because of such nature, which implies that many translators who previously received discount codes for the Summit with the recognition of ATCs will not receive discount codes for the Forum. Then, is there less possibility for them to receive discount codes? I have been so expecting that more translators and I18n members will participate in the Forum and discuss how more translation activities will be vitalized with user community activities. Please give me some direction for successful participation and making fruits from I18n team on the Forum. (Of course, PTG is also an important event for I18n team although few I18n members will go there. I would like to bring some topics to discuss horizontally with many teams in near future, not too late or long.) [1] http://www.openstack.org/ptg#tab_faq [2] http://lists.openstack.org/pipermail/openstack-docs/2016-November/009294.ht… With many thanks, /Ian Tom Fifield wrote on 1/5/2017 1:19 PM: > Hi *dev, > > Post over on the general ML you might be interested in - please send > replies there to avoid cross-posting pain ;) > > > Regards, > > > Tom > > > -------- Forwarded Message -------- > Subject: [Openstack] The Forum: in more detail > Date: Thu, 5 Jan 2017 11:42:53 +0800 > From: Tom Fifield <tom(a)openstack.org> > To: openstack(a)lists.openstack.org > > Hi all, > > working with colleagues, I've just put up a post cobbling together > some more detail on the Forum. Sorry it took so long! > > http://superuser.openstack.org/articles/openstack-forum/ > > > There's now also a wiki page to be the reference for us to follow when > preparing or participating: > > https://wiki.openstack.org/wiki/Forum > > > Please check them out and reply with any thoughts, ideas or angry rants! > > > Regards, > > > Tom > > _______________________________________________ > 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 > > __________________________________________________________________________ > > 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

[Bug 1651329] [NEW] Storage 노드 설치와 구성 in Installation Guide
by Jaeki Hong 22 Dec '16

22 Dec '16

Public bug reported: there are typos The following sentences should be changed [pipeline:mail] 섹션 -> [pipeline:main] 섹션 ----------------------------------- Release: 0.1 on 2016-12-12 10:29 SHA: 703d0574be515e76315ab505d6b2ea25a8450dc7 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/ko_KR/install-guide-ubuntu/swift-storage-i… ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1651329 Title: Storage 노드 설치와 구성 in Installation Guide Status in openstack i18n: New Bug description: there are typos The following sentences should be changed [pipeline:mail] 섹션 -> [pipeline:main] 섹션 ----------------------------------- Release: 0.1 on 2016-12-12 10:29 SHA: 703d0574be515e76315ab505d6b2ea25a8450dc7 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/ko_KR/install-guide-ubuntu/swift-storage-i… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1651329/+subscriptions

2 1

Merry Christmas and Happy New Year
by Alex Eng 21 Dec '16

21 Dec '16

Hi all, Zanata core team will be on holiday from 23 Dec to 2 Jan. We will be back on 3rd Jan 2017. I'm reachable via mobile and my personal email: loones1595(a)gmail.com Wishing you all Merry Christmas and Happy New Year! Regards, --------------------------------------------- Alex Eng Senior Software Engineer 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

1 0

[I18n] Today (Dec 15th) IRC meeting is canceled
by Ian Y. Choi 14 Dec '16

14 Dec '16

Hello, Unfortunately, I am unable to participate in today I18n IRC meeting due to my personal schedule. I am sorry for that. Note that the next IRC meeting will be on December 22nd 13:00 UTC in #openstack-meeting IRC channel. It will be the last meeting in this year (December 29th is during Christmas holiday). I hope to see many I18n members on the next meeting to wrap up what happened this year and also celebrate Christmas :) With many thanks, /Ian

1 0

formatted source text
by Robert Simai 08 Dec '16

08 Dec '16

Hi, I guess everyone translating has seen this, sometimes there's source text formatted by line breaks and even spaces at the beginning of lines which finally forces the translator to keep this format, else Zanata wouldn't allow to save it. For an example, see above :-) I think this formatting is rather bad and shouldn't happen. Text should be either continuous or it needs to be split to go into multiple strings. Are there any reasons where as such formatted text is justified, translator should leave it as it is? Or shall we rather rather flag this through a bug, or even create patches to change it? Opinions? -- Thanks, Robert

3 6

[I18n] IRC Meeting remainder: November 10th at 13:00 UTC
by Ian Y. Choi 07 Dec '16

07 Dec '16

Hello all, I18n team is having our next meeting on November 10th (Thursday) at 13:00 UTC in #openstack-meeting IRC channel. You can find meeting agenda here: https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting#Agenda_for_next_me… Anyone is welcome to add topics on Wiki If you missed previous IRC meeting or want to refresh, please see last IRC meeting minutes and full logs: Minutes: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Log: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Note that I will be moving from one place to another during meeting time. I will bring my laptop with smartphone tethering, but it would be much better if someone (IRC meeting chair or any volunteer) starts meeting. See you tomorrow! With many thanks, /Ian

2 4

[Bug 1647116] [NEW] [i18n-guide] link errors
by Ian Y. Choi 04 Dec '16

04 Dec '16

Public bug reported: In http://docs.openstack.org/developer/i18n/infra.html , http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/j… from include-build-releasenotes.sh and http://docs.zanata.org/projects/zanata-client/en/latest/ from zanata-cli are not working. ** Affects: openstack-i18n Importance: Undecided Assignee: Ian Y. Choi (ianychoi) Status: In Progress ** Changed in: openstack-i18n Assignee: (unassigned) => Ian Y. Choi (ianychoi) -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1647116 Title: [i18n-guide] link errors Status in openstack i18n: In Progress Bug description: In http://docs.openstack.org/developer/i18n/infra.html , http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/j… from include-build-releasenotes.sh and http://docs.zanata.org/projects/zanata-client/en/latest/ from zanata-cli are not working. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1647116/+subscriptions

2 1

What's Up, Doc? Holiday Edition!
by Lana Brindley 01 Dec '16

01 Dec '16

Hi everyone, The end of the year is nearly upon us already, and this will be my last newsletter for 2016, before I disappear for the holidays on the 16th. I've had yet another wonderful year with all you lovely OpenStack people, and I wish all of you and your families a happy and safe holiday, wherever and however you celebrate it. Here in Australia, the temperature is starting to soar, so I'm off on another cruise, followed by a few lazy days by the pool with family and friends. I'll be back in the office early in the new year, and ready to kick Ocata out of the door! As many of you already know, I'm not planning on running for Pike PTL. If you're interested in running for PTL (for Pike or any future release), and would like a crash course in PTLing, please let me know and I can share whatever meagre wisdom I've gleaned before self nominations open in mid-January. == Progress towards Ocata == 82 days to go! Closed 106 bugs so far. Release tasks are being tracked here: https://wiki.openstack.org/wiki/Documentation/OcataDeliverables == The Road to PTG in Atlanta == Event info is available here: http://www.openstack.org/ptg Purchase tickets here: https://pikeptg.eventbrite.com/ Docs is a horizontal project, so our sessions will run across the Monday and Tuesday of the event. The incoming PTL will be responsible for planning and running sessions at the Atlanta PTG. == Speciality Team Reports == * API: Anne Gentle The App Dev Support WG is working on a survey to determine which content areas to invest in for content on http://www.openstack.org/appdev (http://lists.openstack.org/pipermail/user-committee/2016-November/001469.ht…) * Configuration Reference and CLI Reference: Tomoyuki Kato We try to recreating the single page view for the "openstack" command. I'd like to generate the reference from source code automatically. However, python-openstackclient has many plug-ins. It is difficulty, but worth to tackle it. We need your help! * High Availability Guide: Andrew Beekhof No formal report, but Alex Settle has been doing a lot of work on this guide recently, cleaning up, and raising bugs for some of the TODO items. We need to consider if the HA guide is an ongoing concern. Ben Silverman is wondering if we can fold the content into the Ops/Arch Guides. This will be raised on the mailing list for more conversation. * Hypervisor Tuning Guide: Joe Topjian No report this week * Installation guides: Lana Brindley We've heard back from Foundation on design resources, I'm going to reply to that email today and hopefully start drafting the new design next week. I've also got Piet from the UX team on board to help. Anyone who wants to be involved with that, please contact me. * Networking Guide: John Davidge No update this week. * Operations and Architecture Design guides: Darren Chan For the Arch guide, patches for networking and compute content were merged, thanks to Ben and Shaun. For the Ops Guide, there is patch up to update the upgrades chapter and include links to the project upgrade notes: https://review.openstack.org/#/c/404528/ * Security Guide: Nathaniel Dillon No update this week. * Training Guides: Matjaz Pancur BCN Upstream training article in the Superuser magazine: http://superuser.openstack.org/articles/openstack-upstream-training-revamp/ - actively looking for contributors to join the Upstream training, please see http://lists.openstack.org/pipermail/openstack-docs/2016-November/009382.ht… - cleaned test entries in the Launchpad bug queue and the Sandbox repository (left from the Barcelona Upstream training) - updated Training guides README.rst * Training labs: Pranav Salunke, Roger Luethi No update this week. * User guides: Joseph Robinson The legacy command conversion continues at a good pace. I have some more updates to patch today. The only obstacle I have run into is generating new output to match the OpenStack command client. Otherwise, contributors have been adding to the table, and there's been steady patching completed. Just a reminder to update the table if making a change: https://wiki.openstack.org/wiki/Documentation/ReorganizeUserGuides == Doc team meeting == Our next meeting will be on Thursday 16 December at 2100 UTC in #openstack-meeting-alt For more meeting details, including minutes and the agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#1_December_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Re: [OpenStack-I18n] Adding Romanian Language Team
by Ian Y. Choi 01 Dec '16

01 Dec '16

Hello Cristian, Sorry for my late reply. I am copying with openstack-i18n(a)lists.openstack.org to keep track of your request. (Note: I always try to read all of my e-mails but since I receive too much e-mails in my account these days, I usually check http://lists.openstack.org/pipermail/openstack-i18n/ for faster responses from openstack-i18n(a)lists.openstack.org.) Cristian Cira wrote on 11/17/2016 11:34 PM: > Hello Ian, > > Nice to meet you too! > > * I have registered to the mailing list > * It is not clear to me what is the difference between the two > encoding. I searched the net for some documentation but failed to > find one that points out the difference -maybe you could point me > to a better source. If my understanding is correct (namely that > the second one includes "somehow" a geographical component in the > characters encoding ) then I would opt for "ro" to keep it as > general as possible since there are few differences in the > Romanian dialects from various regions > Personally, I have been to Romania about 10 years ago shortly (about less than 4 weeks in Bucharest), but I do not have enough knowledge to judge between ro vs. ro-RO. Now I want to follow your decision: "ro". Thanks. > > * I will accept to be a coordinator with some hesitation. This > coordinator position must come with some extra responsibility > which is totally fine with. My concern regards the time I have to > dedicate to this activity. So, as long as I do not have to > officially commit a certain amount of hours to it, I am more then > happy to help translate. Also, I feel confident that I can find > some extra contributors, maybe even better suited for this > position then me. > That's fine. At least, I am not a full-time translator for OpenStack :) > * Also, could you please point me to a place where I can as question > related to how should I approach this task. Surely there are some > more important parts of the documentation that would need to be > tackled first. > Would you read first http://docs.openstack.org/developer/i18n/ ? Then please let me know which points you would like to know or ask. I will follow Romanian language support in Zanata after I18n IRC meeting on this Thursday 13:00 UTC ( http://eavesdrop.openstack.org/#I18N_Team_Meeting ). If you attend to this meeting, I think it will be very nice to talk each other. With many thanks, /Ian > > * > > > Thank you for your time. Have a lovely day, > ~cira > > On Thu, Nov 17, 2016 at 4:53 AM Ian Y. Choi <ianyrchoi(a)gmail.com > <mailto:ianyrchoi@gmail.com>> wrote: > > Hello Cristian, > > I am Ian. Nice to meet you! > > I think adding the support for Romanian language is possible in > Zanata :) > > Before going further, I want to ask you: > > - Please subscribe openstack-i18n(a)lists.openstack.org > <mailto:openstack-i18n@lists.openstack.org> mailing list through > : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > - For Romanian language, I want to ask you which ISO language code > is preferred > : "ro" vs. "ro-RO". > > - Are you willing to be a Romanian language coordinator in i18n team? > Since there is no Romanian translator currently, I want to > assign you as Romanian language coordinator. > As a language coordinator, it would be much better if you will > encourage more Romanian translations > to others, tell PTL (currently, me) for any updates, and share > or ask anything regarding i18n related things > through I18n IRC meeting > http://eavesdrop.openstack.org/#I18N_Team_Meeting or this mailing > list. > > > With many thanks, > > /Ian > > > Cristian Cira (KTH-PDC) wrote on 11/16/2016 4:26 AM: >> Dear all, >> >> I have recently decided to contribute to the translation of the >> OpenStack documentation to Romanian in my limited free time. >> >> I am a native Romanian currently working in Sweden at a HPC >> center. My English is proficient having studied and worked in USA >> for 5 years prior to moving here. Here is my LinkedIn >> <https://se.linkedin.com/in/cristian-cira-246b0933> account for >> some more details. >> >> My username on Zanata is *cira* >> * >> *Please let me know what are the next steps I have to take. >> >> Thank you, >> C >> >> *Cristian Cira,*PhD >> Application Expert in Code Optimization >> *PDC Center for High Performance Computing* >> KTH Royal Institute of Technology >> SE-100 44 Stockholm, Sweden >> *http://www.pdc.kth.se >> * >> Tel : +46 8 790 6309 <tel:08-790%2063%2009> >> Mob : +46 737 65 22 98 >> >> >> _______________________________________________ >> OpenStack-I18n mailing list >> OpenStack-I18n(a)lists.openstack.org >> <mailto:OpenStack-I18n@lists.openstack.org> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > -- > *Cristian Cira,* PhD > Application Expert in Code Optimization > *PDC Center for High Performance Computing* > KTH Royal Institute of Technology > SE-100 44 Stockholm, Sweden > *http://www.pdc.kth.se > * > Tel : +46 8 790 6309 > Mob : +46 737 65 22 98

2 2

[I18n] IRC Meeting remainder: November 3rd at 07:00 UTC
by Ian Y. Choi 30 Nov '16

30 Nov '16

Hello all, I18n team is having our next meeting on November 3rd (Thursday) at 07:00 UTC in #openstack-meeting IRC channel. You can find meeting agenda here: https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting#Agenda_for_next_me… Anyone is welcome to add topics on Wiki If you missed previous IRC meeting or want to refresh, please see i18n Barcelona contributor meetup summary on Etherpad (URL: https://etherpad.openstack.org/p/barcelona-i18n-meetup ), last IRC meeting minutes and full logs: Minutes: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Log: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… With many thanks, /Ian

2 4

searchlight-ui: Broken cs translation / neutron-lbaas-dashboard: broken ja translation
by Andreas Jaeger 24 Nov '16

24 Nov '16

Could somebody check and fix these, please? http://logs.openstack.org/periodic/searchlight-ui-propose-translation-updat… searchlight_ui/locale/cs/LC_MESSAGES/djangojs.po:789: number of format specifications in 'msgid_plural' and 'msgstr[2]' does not match http://logs.openstack.org/periodic/neutron-lbaas-dashboard-propose-translat… neutron_lbaas_dashboard/locale/ja/LC_MESSAGES/djangojs.po:1092: '\''msgid'\'' and '\''msgstr'\'' entries do not both end with '\''\n'\'' Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: 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

[Bug 1641785] [NEW] 环境 in Installation Guide 镜像服务写成了径向服务
by jeck 20 Nov '16

20 Nov '16

Public bug reported: 拼写错误 ----------------------------------- Release: 0.1 on 2016-11-13 23:16 SHA: 5a9c47b83b0209892f887697bb9e8bb871eee8a3 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-ubuntu/environment.html ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1641785 Title: 环境 in Installation Guide 镜像服务写成了径向服务 Status in openstack i18n: New Bug description: 拼写错误 ----------------------------------- Release: 0.1 on 2016-11-13 23:16 SHA: 5a9c47b83b0209892f887697bb9e8bb871eee8a3 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-ubuntu/environment.html To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1641785/+subscriptions

1 1

[Bug 1489311] Re: Chinese words in translations are incorrect
by Ian Y. Choi 20 Nov '16

20 Nov '16

I have found that Zanata now has a fixed string for this bug report: http://git.openstack.org/cgit/openstack/openstack- manuals/tree/doc/common/source/locale/zh_CN/LC_MESSAGES/common.po#n1145 ** Changed in: openstack-i18n Status: Confirmed => Fix Released -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1489311 Title: Chinese words in translations are incorrect Status in openstack i18n: Fix Released Bug description: I found there are mistakes of Chinese words in translations. Details: In source file: https://github.com/openstack/openstack-manuals/blob/master/doc/common/local… there are two places as follow: 1: L413 "<emphasis>用户不可以想传统的硬盘那样使用OpenStack对象存储。</emphasis>对象存" "用户不可以想传统的硬盘" should be "用户不可以像传统的硬盘". 2: L736 msgid "Access associated with a VM" L737 msgstr "访问和VM想关联" "访问和VM想关联" should be "访问和VM相关联". To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1489311/+subscriptions

1 0

[Bug 1612201] [NEW] Some strings which needn't translation appear in Zanata
by zzxwill 20 Nov '16

20 Nov '16

Public bug reported: In Zanata, document 'doc/admin-guide/source/locale/admin-guide' of openstack-manuals, some strings like 'vm2', 'doc/admin- guide/source/locale/admin-guide', 'd693db9e-a7cf-45ef-a7c9-b3ecb5f22645' are waiting for translation, while, which don't need to be translated. I think there should be a way to stop them from being shown in Zanata. Thanks. ** Affects: openstack-i18n Importance: Undecided Status: New -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1612201 Title: Some strings which needn't translation appear in Zanata Status in openstack i18n: New Bug description: In Zanata, document 'doc/admin-guide/source/locale/admin-guide' of openstack-manuals, some strings like 'vm2', 'doc/admin- guide/source/locale/admin-guide', 'd693db9e-a7cf-45ef- a7c9-b3ecb5f22645' are waiting for translation, while, which don't need to be translated. I think there should be a way to stop them from being shown in Zanata. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1612201/+subscriptions

2 1

[Bug 1612878] Re: 安装和配置 in Installation Guide
by Ian Y. Choi 20 Nov '16

20 Nov '16

"controller" vs. "10.0.0.11" is not the target of I18n team. ** Changed in: openstack-i18n Status: New => Invalid ** Tags added: simplified-chinese -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1612878 Title: 安装和配置 in Installation Guide Status in openstack i18n: Invalid Bug description: ----------------------------------- Release: 0.1 on 2016-08-12 08:52 SHA: 739d8d9e6cb81a10aca0068e5ba1b76541b0398d Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-ubuntu/horizon-install… 在memcached里，/etc/memcached.conf 如果-l是controller -l controller 那么在/etc/openstack-dashboard/local_settings.py这个里面也应该是controller CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', 'LOCATION': 'controller:11211', } } 否则在登录dashboard的时候，能出现登录的页面，登录不成功。如果都写IP地址，也是可以成功。在memcached里，/etc/memcached.conf 如果-l是10.0.0.11 -l 10.0.0.11 那么在/etc/openstack-dashboard/local_settings.py这个里面也应该是10.0.0.11 CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', 'LOCATION': '10.0.0.11:11211', } } 这样才能成功。 To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1612878/+subscriptions

1 0

[Bug 1637920] [NEW] 网络选项2：私有网络配置Linuxbridge代理中[linux_bridge]部分应为 physical_interface_mappings = provider:PUBLIC_INTERFACE_NAME
by gavin 20 Nov '16

20 Nov '16

Public bug reported: section of PUBLIC_INTERFACE_NAME ----------------------------------- Release: 0.1 on 2016-10-30 16:22 SHA: 0aec93ae3cabb0ba77ca4a0a2498b5dcaf454984 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/neutron-controller… ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1637920 Title: 网络选项2：私有网络配置Linuxbridge代理中[linux_bridge]部分应为 physical_interface_mappings = provider:PUBLIC_INTERFACE_NAME Status in openstack i18n: New Bug description: section of PUBLIC_INTERFACE_NAME ----------------------------------- Release: 0.1 on 2016-10-30 16:22 SHA: 0aec93ae3cabb0ba77ca4a0a2498b5dcaf454984 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/neutron-controller… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1637920/+subscriptions

2 1

Re: [OpenStack-I18n] [OpenStack-docs] stable/newton created, publishing frozen for now
by Ian Y. Choi 20 Nov '16

20 Nov '16

Hello, Andreas Jaeger wrote on 11/13/2016 3:52 AM: > On 11/12/2016 07:18 PM, Andreas Jaeger wrote: >> Clark just created a stable/newton branch. >> >> I'll create the changes now for both master and stable so that >> publishing is correct. >> >> Please do not approve any changes until those are in. >> >> I'll sent in a few minutes an email with links to those changes for >> review, > > The changes that need to merge are: > > https://review.openstack.org/396874 > https://review.openstack.org/396875 > > In addition: > * stable-newton needs to be created on zanata (i18n team) Zanata now has a stable-newton version for openstack-manuals, and this version can be seen in https://translate.openstack.org/project/view/openstack-manuals and https://translate.openstack.org/iteration/view/openstack-manuals/stable-new… . i18n team will translate backported guides (common, install-guide, networking-guide) in stable-newton instead of master for translation plan and priority during Ocata cycle. Thank you all kind help and communication, especially Andreas and Olena! With many thanks, /Ian > * import of newton translations: https://review.openstack.org/396876 > * Documentation for the above: https://review.openstack.org/396877 > > Please review everything and help updating these if I missed anything, > I really like to have this properly documented so that the release > managers can do it next time, > > Andreas

1 1

What's Up, Doc? 18 November
by Lana Brindley 17 Nov '16

17 Nov '16

Hi everyone, Welcome to Ocata! It was great to catch up with many of you in Barcelona, and always refreshing to see the energy around our little project and catch that enthusiasm all over again :) Of course, Ocata is a *very* short cycle, so we've deliberately cut down our deliverables list to ensure we can squeeze it all in. We have two main priorities this release: tidying up the new Install Guides index page, and a little bit of navel gazing in terms of social structures and procedures. More on that in this newsletter! == Progress towards Ocata == 96 days to go! Closed 77 bugs so far. Release tasks are being tracked here: https://wiki.openstack.org/wiki/Documentation/OcataDeliverables == The Road to PTG in Atlanta == Event info is available here: http://www.openstack.org/ptg Purchase tickets here: https://pikeptg.eventbrite.com/ Docs is a horizontal project, so our sessions will run across the Monday and Tuesday of the event. == Specs on review == * Ops/Arch Guides: https://review.openstack.org/#/c/392372/ [arch-design] Revise the Architecture Design Guide https://review.openstack.org/#/c/394261/ [ops-guide] Add project upgrade notes https://review.openstack.org/#/c/391786/ Proposed use case form * Training Labs: https://review.openstack.org/#/c/391548/ training-labs: Rewrite training-labs in python == Speciality Team Reports == We've made some structural changes to how Speciality Teams and our regular docs meeting work. Speciality teams will now meet no more than once monthly (most on an 'as needed' basis), and participants are instead encouraged to attend the main docs meeting to discuss work and report on progress. This is aiming to keep all the information about the work we're doing a little more centralised, and give newcomers a way to find out where they can best help. It also gives us a chance to find out where we can help each other, without going to a dozen meetings! * API: Anne Gentle Karen Bradshaw has been working on updates to the openstackdocstheme that would fix this bug: https://launchpad.net/bugs/1583623. The review is up at https://review.openstack.org/#/c/393890/ and getting input from the affected teams who have recognized the need because of errors building when you have multiple API versions with very similar calls, so you end up with identical headings. Launchpad bug 1583623 in openstack-doc-tools "os-api-ref: duplicate labels for selectors" [Low,In progress] - Assigned to Karen Bradshaw (kbhawkey) I've had a couple of inquiries on IRC about "where did the draft/swagger files go?" but to meet their stated end goals, those particular files wouldn't have worked any way due to inaccuracies in the content and incomplete content. See the 100 api-ref doc patches up for review at: https://review.openstack.org/#/q/status:open+file:api-ref. * Configuration Reference and CLI Reference: Tomoyuki Kato No report this week * High Availability Guide: Andrew Beekhof No report this week * Hypervisor Tuning Guide: Joe Topjian No report this week * Installation guides: Lana Brindley No major updates to the guides themselves, but we are planning updates to the landing page. We're also working on getting our first deployment guide landed there, with OpenStack Ansible. I've requested design resources from foundation, but haven't heard back yet, so if you have ideas/suggestions (or design skillz!) then please let me know. * Networking Guide: John Davidge A couple of new articles are close to merging: https://review.openstack.org/#/c/361776/ - VLAN Trunking and https://review.openstack.org/#/c/356013/ - Routed Provider Networks. Need to decide how best to track the work that's going on for https://blueprints.launchpad.net/openstack-manuals/+spec/use-openstack-comm…. Probably a google spreadsheet or etherpad with a list of all the network guide pages to be converted, and the person working on it would be best. That way we can hopefully avoid duplicating efforts. * Operations and Architecture Design guides: Darren Chan We're slowly making progress with the arch guide, and have cloudnull onboard to help. So the focus is completing the design chapter and migrating stuff from the ops guide. * Security Guide: Nathaniel Dillon No update this week. * Training Guides: Matjaz Pancur We changed our IRC meeting to every two weeks (on even weeks) on Tuesday at 1300 UTC in #openstack-meeting-3. There will be an article published about BCN Upstream training in OpenStack's Superuser magazine. BCN Upstream training retrospective https://etherpad.openstack.org/p/upstream-training-barcelona-retrospective * Training labs: Pranav Salunke, Roger Luethi We have the python port already under review, the spec is not done yet, but we hope to get them merged soonish and in the right order :) User guides: Joseph Robinson * This the current work on converting the legacy commands to OS commands: https://wiki.openstack.org/wiki/Documentation/ReorganizeUserGuides#Ocata_Ta…. Thanks to csatari and visnyei and allen, there's progress happening. I need to finish adding the files affected to the checklist, and then also start making changes. Apart from that, keeping track of any admin or user guide bugs is also a task. == Doc team meeting == We have re-started the docs team meetings, with a new cadence. Our first meeting was held today, with much success. Thank you to everyone who participated, either directly in IRC, or by making sure you sent me your updates ahead of schedule. Our next meeting will be on Thursday 1 December at 2100 UTC in #openstack-meeting-alt For more meeting details, including minutes and the agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#18_November_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Adding Romanian Language Team
by Cristian Cira (KTH-PDC) 16 Nov '16

16 Nov '16

Dear all, I have recently decided to contribute to the translation of the OpenStack documentation to Romanian in my limited free time. I am a native Romanian currently working in Sweden at a HPC center. My English is proficient having studied and worked in USA for 5 years prior to moving here. Here is my LinkedIn <https://se.linkedin.com/in/cristian-cira-246b0933> account for some more details. My username on Zanata is *cira* Please let me know what are the next steps I have to take. Thank you, C *Cristian Cira,* PhD Application Expert in Code Optimization *PDC Center for High Performance Computing* KTH Royal Institute of Technology SE-100 44 Stockholm, Sweden *http://www.pdc.kth.se <http://www.pdc.kth.se>* Tel : +46 8 790 6309 Mob : +46 737 65 22 98

2 1

Re: [OpenStack-I18n] [openstack-dev] [i18n] [glance] ESL question 'shared' vs 'shareable'
by Ian Y. Choi 16 Nov '16

16 Nov '16

Hello devs, As a Korean translator, I also quite agree with the idea. Some images with "shared" state but actually not shared yet would be awkward, and "shareable" word would cover such context : those images can be shard but may not be shared yet (although the addition of "image members"is needed) or already shared. Hello translators, I am copying openstack-i18n(a)lists.openstack.org on this. Would you pleased think about this and share your thoughts? (Or please attend to the next i18n IRC meeting about in 9-10 hours and tell me.) With many thanks, /Ian Sean McGinnis wrote on 11/17/2016 1:44 AM: > On Wed, Nov 16, 2016 at 04:04:52PM +0000, Brian Rosmaita wrote: >> Hello Translators, >> >> We're having a discussion about a new image "visibility" value for Glance, >> and before we go too far, it would be helpful to know whether what we're >> worried about is going to matter for ESL people. >> >> Here's the situation: Since the Diablo release, Glance end users have had >> the ability to share images with other cloud users by adding "members" to >> the image. We call those "shared images". Previously, we haven't had a >> special "visibility" keyword for these, but we are introducing one now >> [0]. Here's the problem introduced by that change: >> >> (1) Members can only be added to an image if its current visibility value >> allows for it. We're going to make this an explicit visibility state that >> we ware proposing to call 'shared'. >> >> (2) An image with visibility == 'shared', however, isn't actually >> accessible to other users unless they are added as "image members". So >> it's going to be possible for a user to have some images with visibility >> == 'shared', but they aren't *really* shared with anyone yet. >> >> (3) For reasons outlined on [0], we're proposing to make this new >> visibility the default value in Glance. This will enable the current >> sharing workflow to work in a backward-compatible way. But some people >> are worried that users will panic when they see that their new images have >> visibility == 'shared' (even though no other users have access to such >> images until "image members" are added). >> >> (4) To address this, we're thinking that maybe the identifier for this >> kind of image visibility should be 'shareable'. >> >> Finally, here's my question. For an ESL person looking at these two >> identifiers (which, as identifiers, won't be translated): >> * shared >> * shareable >> >> Are the above so similar that the nuances of the discussion above would be >> lost anyway? In other words, are we just bikeshedding here, or is there a >> clear distinction? What I mean is, is the panic described above likely or >> unlikely to happen for an ESL person? >> >> thanks, >> brian > Good question. I think technically it would be shareable, which would > mean that it then able to be shared. > > Realistically though, in my opinion, calling it shared to denote that it > _can be_ shared is probably intuitive enough that there wouldn't be any > confusion about the naming. > > My 2 cents. > >> [0] https://review.openstack.org/#/c/396919/ >> >> >> __________________________________________________________________________ >> 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

1 0

Creating i18n-specs for I18n specifications
by Ian Y. Choi 08 Nov '16

08 Nov '16

Hello, Official OpenStack project teams can have specification repositories, and the specifications are published on: http://specs.openstack.org/ . As we decided on last Barcelona i18n contributor meetup (Please see number 2 part in Etherpad for more details: https://etherpad.openstack.org/p/barcelona-i18n-meetup ), I have just requested to create i18n-specs repository using the following patchsets - https://review.openstack.org/#/c/394680/ - https://review.openstack.org/#/c/394681/ Hope that more i18n activities will be documented with details and shared using this i18n-specs repo. I will notice again after i18n-specs repo will be landed successfully :) With many thanks, /Ian

3 3

Feedback is needed for I18n draft logo!
by Ian Y. Choi 08 Nov '16

08 Nov '16

Hello, On last July, i18n team decided *parrot* as i18n project mascot. OpenStack Foundation has a plan for all the official OpenStack teams to have logos based on mascots. Logos will be ready by the 1st Project Team Gathering on next February. Please see the attached figure for draft logo. The attached is a draft logo for i18n team to target Barcelona Summit for project teams to more discuss on logos. If you are interested in how illustrators worked, please refer a video: https://youtu.be/JmMTCWyY8Y4 . I18n team needs to return a feedback from the draft logo by Nov 11 (Fri) with a feedback form: http://tinyurl.com/OSmascot . Direct feedback to the URL is also fine, but please share feedback through i18n mailing list! (e.g., color, style, design, form, ...) The following is what I was received what we can expect through the logo: * A horizontal version of the logo, including your mascot, project name and the words "An OpenStack Community project" * A square(ish) version of the logo, including all of the above * A mascot-only version of the logo * Stickers for all project teams distributed at the PTG * One piece of swag that incorporates all project mascots, such as a deck of playing cards, distributed at the PTG * All digital files will be available through the website With many thanks, /Ian

5 6

I18n in BCN: I18n contributor meetup wrap up
by Ian Y. Choi 02 Nov '16

02 Nov '16

Hello! There were around total 20 participants for last I18n contributor meetup @Barcelona, including Daisy, Zanata team, Infrastructure team, Docs team, and Stackalytics team members! Thank you very much for such all kind and so active participation! Although there have been sort of time conflicts for some active translators and main contributors on other projects but who are helping i18n team a lot, we have met each other and discussed for better i18n. I think i18n team members have dealt various topics with so long time. If there was no time limit: 6pm, i18n members might have discussed much longer :) I am now transferring to go home and my final flight has been delayed about 3 hours, but thanks to such delay, I have briefly summarized now what have been discussed and what are results from I18n contributor meetup. Please see Etherpad: https://etherpad.openstack.org/p/barcelona-i18n-meetup , and "Discussed Topics and Results" (2nd) section. - Andreas Jaeger shortly visited due to his return flight and we agreed with translation job import and export criteria. I have briefly summarized in number *(1)*. - Ilya Shakhat, who is a Stackalytics core developer and maintainer, kindly participated in the meetup. If anyone is interested in Stackalytics with i18n statistics, please refer to number *(3)* for the details. - Although there is another infrastructure team meeting on the same time, Elizabeth K. Joseph and Clark Boylan came to I18n contributor meetup (thank you so much again!). Zanata upgrade *(4)* is what i18n team is really waiting for. Alex Eng and Patrick Huang from Zanata team gave some beneficial feedback (e.g., current Zanata version number and new version release plan) through IRC in real time. Moreover, I hope that some discussion of translation checksite *(5)* will yield more positive progress, although it seems that more discussion is needed. - Also, Lana from Docs team PTL visited to i18n contributor meetup, although she was leading Docs contributor meetup on the same time. Lana and me both agreed that more communication between two teams will make nice fruit *(6)*. - For i18n activities, we have differentiated and clarified the usage of web pages : Zanata dashboard, Wiki, i18n contributor guide, and so on *(2)*, and also finalizing Ocata translation plans is very important during Ocata Design Summit *(7)*! I will update Zanata dashboard according to the finalization. Because of some time restriction, some topics has not been discussed yet or just briefly mentioned. Let's also consider those topics gradually such as on the next IRC meeting. Some meetup participants took photos. Frank shared photos to Etherpad! I hope that other participants will share photos soon. Hope all to have a return flight safely. Again, thank you very much all! With many thanks, /Ian

4 5