- OpenStack-I18n - lists.openstack.org

[Bug 1536226] Re: Not all .po files compiled
by OpenStack Infra 05 Apr '17

05 Apr '17

Reviewed: https://review.openstack.org/319353 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=cf42abc85e385ea… Submitter: Jenkins Branch: master commit cf42abc85e385eac12123ccac63a7dd3eb4f83ce Author: Sven Anderson <sven(a)redhat.com> Date: Fri May 20 18:35:52 2016 +0200 Let setup.py compile_catalog process all language files Two years ago the translation files have been split into several files, separating the log messages of different log levels from each other, like X.pot, X-log-warning.pot, X-log-info.pot, and so on. However, the setup.py command `compile_catalogs`, that comes from the babel package and compiles the corresponding .po files into .mo files, only supported one file per python package. This means that during packaging `compile_catalogs` never compiled the X-log-*.po files, so the corresponding translations were always missing. Since babel 2.3 the domain can be set to a space separated list of domains. This change adds the the additional log level files to the domain list. Change-Id: I436072d03f401240df6d7b8348616bc7c4731c4a Closes-Bug: #1536226 ** Changed in: neutron Status: In Progress => 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/1536226 Title: Not all .po files compiled Status in Cinder: Fix Released Status in Glance: In Progress Status in heat: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in openstack i18n: New Bug description: python setup.py compile_catalog only compiles one <domain>.po file per language to a <domain>.mo file. By default <domain> is the project name, that is nova.po. This means all other nova-log-*.po files are never compiled. The only way to get setup.py compile the other files is calling it several times with different domains set, like for instance `python setup.py --domain nova-log-info` and so on. Since this is not usual, it can be assumed that the usual packages don't contain all the .mo files. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1536226/+subscriptions

1 0

request for help from ESL readers
by Brian Rosmaita 04 Apr '17

04 Apr '17

Hello i18n team, There's a section of Glance documentation that's written in a colloquial american english style, but some contributors have expressed concern that this attempt to make a concept clear to non-technical american english readers may actually make it more difficult for ESL readers to understand. It would be awesome if a few ESL people would take a look and let us know what you think: http://specs.openstack.org/openstack/glance-specs/specs/api/v2/sharing-imag… thanks, brian

3 3

[openstack-docs] [dev] What's up, doc?
by Alexandra Settle 27 Mar '17

27 Mar '17

Team team team team team, Well the last month has just FLOWN by since the PTG. We've got plenty going on in the doc team... This week I have been helping out the security team with the Security Guide. We've been working on some cursory edits, and removal of content. A few patches have already made it through - thanks to the OSIC security team for tackling some of the outstanding bugs. There'll be more edits coming from me in the next few weeks. To see our planning: https://etherpad.openstack.org/p/sec-guide-pike I am also in the process of drafting a governance tag for our install guides. Would be great for everyone to review and understand what the process will involve: https://review.openstack.org/#/c/445536/ Shoutout and big thanks to Brian Moss and the nova team who worked together tirelessly to document Nova v2 Cells and Placement API - which was a massive blocker for our Installation Guide. Also, thank you to our Ocata release managers, Maria Zlatkova and Brian Moss for cutting the branch! Pike is well and truly underway now. Ianeta Hutchinson has done an awesome job for the last two weeks in keeping our bug list under control. We are down to an amazing 104 bugs in queue, and 59 bugs closed this cycle already! Next week, we have Lana who will be looking after the bug triage liaison role! If you're sitting there thinking "bugs are for me, I really love triaging bugs!" well, you're in luck! We have a few spots open for the rest of the cycle: https://wiki.openstack.org/wiki/Documentation/SpecialityTeams#Bug_Triage_Te… == The Road to the Summit in Boston == * Schedule has been released: https://www.openstack.org/summit/boston-2017/summit-schedule/ * Docs and I18n have a project onboarding room at the summit, keep an eye out on the dev ML for more information. Kendall will inform us when the time comes. Anyone around to help me with that? http://lists.openstack.org/pipermail/openstack-dev/2017-March/114149.html * Docs project update will be delivered by me (asettle) on Mon 8, 3:40pm-4:20pm. https://www.openstack.org/summit/boston-2017/summit-schedule/global-search?… == Specialty Team Reports == * API - Anne Gentle: There's still a lot of discussion on https://review.openstack.org/#/c/421846/ which is about API change guidelines. Take a look and join in on the review. Also on the openstack-dev list, there's a thread about the future of the app catalog, which is relevant to the app developer audience so I include it here: http://lists.openstack.org/pipermail/openstack dev/2017-March/113362.html<http://lists.openstack.org/pipermail/openstack%20dev/2017-March/113362.html> Also related to the app dev audience is the wrapping up of the App Ecosystem working group: http://lists.openstack.org/pipermail/user-committee/2017-March/001825.html * Configuration Reference and CLI Reference - Tomoyuki Kato: N/A * High Availability Guide - Ianeta Hutchinson: At the Atlanta PTG, the documentation team outlined a new table of contents that is now upstream as a draft here: https://github.com/openstack/openstack-manuals/tree/master/doc/ha-guide-dra…. A blocker to progress in the past had been a lack of SME’s for the topic of high availability but that is no longer the case \o/. The OSIC DevOps team has an “adopt-a-guide” project in which they are collaborating with the OpenStack docs community and OSIC Docs team to apply the new ToC and validate all content for the guide. The progress of this collaboration is being tracked here https://docs.google.com/spreadsheets/d/1hw4axU2IbLlsjKpz9_EGlKQt0S6siViik7E… We are calling for more contributors both as SME's and tech writers. Ping iphutch if interested! * Hypervisor Tuning Guide - Blair Bethwaite: N/A * Installation guides - Lana Brindley: Cells bug is closer to being fixed, and we are closer to a complete test install https://wiki.openstack.org/wiki/Documentation/OcataDocTesting look at all that green!). We're planning to branch Ocata by the end of this week. * Networking Guide - John Davidge: N/A * Operations and Architecture Design guides - Darren Chan: Arch Design Guide: Minor IA and general cleanup of the storage, compute, and networking sections in the Design chapter. Currently updating gaps in storage design content. Ops Guide: Removed cloud architecture content (migrated to the Arch Design Guide). * Security Guide - Nathaniel Dillon: Edits from Alex going through, and patches from the OSIC DevOps team. See above for more info. * Training Guides - Matjaz Pancur: For Training guides, related topics: a new brand for activities around OpenStack Upstream University/Training. It is now known as OpenStack Upstream Institute (https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute) * Training labs - Roger Luethi: We are currently testing our automated version of the Ocata install-guide. We had a problem with Ubuntu's new ISO image (16.04.2 LTS) which is now resolved. * User guides - Joseph Robinson: Several other Legacy commands were converted to OS commands this week. Reviewed the Admin Guide spec. * Theme and Tools - Brian Moss: I'd like to do an openstackdocstheme release soon, as we've got some items (PDF styling, search page JS fix, image centering) that would be good to have in production. Any concerns or last minute items to merge please let me know. We've had some issues come up with the auto-generation scripts. Some have been fixed already (thanks Kato and Christian!), and we're investigating others. If you notice anything amiss or would like to help out, please let me know. 46 open bugs, 8 closed in Pike == Doc team meeting == Our next meeting will be on Thursday, 7 April at 2100 UTC in #openstack-meeting-alt. For more meeting details, including minutes and the agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting -- Have a great week :) Alex IRC: asettle Twitter: dewsday

1 0

Generate horizon language list automatically
by Akihiro Motoki 27 Mar '17

27 Mar '17

Hi I18n team, I just push my patch which changes horizon to generate the language list automatically [1] and the this topic is traced by the bug [2]. I would like to share my long-standing idea with the team. Does it sound reasonable? * The basic idea is to generate the language list based on message catalogs (PO files) availability. * Horizon now has four types of message catalogs (django, djangojs) in horizon and openstack_dashboard respectively. If all message catalogs are present, such languages are listed in the language list. There are some corner case logic. * Some languages share a same locale prefix. Good example is Spanish variants: es, es-ar, es-mx and es-ve. When horizon searches message catalogs for es-ar, a locale "es_AR" is first checked and then "es" (prefix) locale is checked. In this case, if "es-ar" has no corresponding translations ("es_AR") and "es" is already registered in the language list, "es-ar" will not be added in the language list. * For the source language (i.e., English), message catalog existence check is skipped. * The current setting LANGUAGES still has effect. Operators can use e used to limit the initial set of languages to exclude languages they want to show to their users. (Note that even when a language is specified in LANGUAGES setting, if not all message catalogs for the language exist the language will be skipped.) Thanks, Akihiro [1] https://review.openstack.org/#/c/450126/ [2] https://bugs.launchpad.net/horizon/+bug/1675298

1 0

Re: [OpenStack-I18n] [OpenStack-docs] stable/ocata created, publishing frozen for now
by Ian Y. Choi 25 Mar '17

25 Mar '17

Oh, great! Congrats for stable/ocata in openstack-manuals! To work translation sync job successfully with https://review.openstack.org/#/c/449385 <https://review.openstack.org/#/c/449385> , I18n team needs to create stable-ocata version for openstack-manuals in Zanata: https://translate.openstack.org. I checked that someone (maybe Kato-san or Andreas I think) already created stable-ocata version for openstack-manuals in Zanata. Thanks a lot! I have merged from openstack-manuals translations in stable-newton version to master and stable-ocata, and updated brief documentation translation plan for Pike cycle (aims to translate stable-ocata install-guide, common, network-guide, and some master documents). For more concrete plan, I18n team will discuss Documentation translation plan & priority on later IRC meeting. With many thanks, /Ian Mariia Zlatkova wrote on 3/25/2017 2:36 AM: > The changes have been merged. Kudos to Andreas for all his reviews and > fixes! > > So core-reviewers can go ahead and merge now. > > On Fri, Mar 24, 2017 at 1:42 PM, Andreas Jaeger <aj(a)suse.com > <mailto:aj@suse.com>> wrote: > > On 2017-03-24 11:24, Mariia Zlatkova wrote: > > Hi all, > > We have the stable/ocata branch created. Brian has prepared the > > following changes to master: > > > > https://review.openstack.org/#/c/449383 > <https://review.openstack.org/#/c/449383> > > <https://review.openstack.org/#/c/449383 > <https://review.openstack.org/#/c/449383>> > > https://review.openstack.org/#/c/449385 > <https://review.openstack.org/#/c/449385> > > <https://review.openstack.org/#/c/449385 > <https://review.openstack.org/#/c/449385>> > > > > I'm going to make the required changes to stable/ocata. So > please do not > > approve any changes until those are in. > > good idea, thanks! > > Note that since we tagged again, the release scripts added comments to > lots of closed bugs - you can ignore them... > > Andreas > -- > Andreas Jaeger aj(a){suse.com <http://suse.com>,opensuse.org > <http://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 > > > > > -- > *Mariia Zlatkova* > Technical Writer | Mirantis, Kharkiv > www.mirantis.com <http://www.mirantis.com> > > > > _______________________________________________ > OpenStack-docs mailing list > OpenStack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

1 0

Pike dashboard translation plan & priority are updated in Zanata Dashboard
by Ian Y. Choi 23 Mar '17

23 Mar '17

Hello all translators and language coordinators, Pike dashboard translation plan and priority are updated in Zanata Dashboard : https://translate.openstack.org . Some notes regarding this update are: - I have merged all dashboard translations for projects from stable-ocata to master in https://translate.openstack.org/version-group/view/ocata-dashboard-translat… . - For such merge purposes, translations in master version is being overwitten by translations in stable-ocata version, since I18n team prioritized primarily on Ocata version. - Pike dashboard translations group is available at : https://translate.openstack.org/version-group/view/pike-dashboard-translati… . Tripleo-ui has been added to Pike dashboard translations group. - I have checked that Docs team will create stable/ocata branch soon. I will follow to create stable-ocata version in Zanata, do merge stuffs later, and announce through I18n mailing list. With many thanks, /Ian

1 0

[Bug 1675298] Re: automatic generation of LANGUAGES list in settings.py
by Akihiro Motoki 23 Mar '17

23 Mar '17

Added openstack-i18n to share the information ** Also 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/1675298 Title: automatic generation of LANGUAGES list in settings.py Status in OpenStack Dashboard (Horizon): New Status in openstack i18n: New Bug description: At now, LANGUAGES list in openstack_dashboard/settings.py is updated manually. It is better to generate the language list automatically based on the existence of PO files. In horizon, there are four types of PO files ([horizon/locale, openstack_dashboard] * [django, djangojs]). It looks better to check whether all four types of PO files exist in the repo and list such languages. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1675298/+subscriptions

1 0

[I18n] IRC Meeting reminder: March 23th at 07:00 UTC
by Ian Y. Choi 22 Mar '17

22 Mar '17

Hello all, I18n team is having our next meeting on March 23th 2017 (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 last IRC meeting minutes and full logs: Minutes: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… Log: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… With many thanks, /Ian

1 0

release notes POT file now contains branch info
by Akihiro Motoki 21 Mar '17

21 Mar '17

Hi team, Small news on release note translations. Previously POT files of release notes did not contain branch information (such as ocata, newton). I made a small change on reno (release note tool) and POT files of release notes now contains branch information (example [1]). Thanks, Akihiro [1] http://tarballs.openstack.org/translation-source/horizon/master/releasenote…

2 1

[Bug 1670640] [NEW] zanata_stat.py does not honor branch (version) and stats of the last processed branch is used
by Akihiro Motoki 19 Mar '17

19 Mar '17

Public bug reported: zanata_stat.py can process multiple versions (branches) at the same time, but the logic does not honor a version processed. As a result, user stats from the last processed version is used as user translation stats. AFAIK the tool is used to retrieve translation stats and determine ATC status. https://github.com/openstack/i18n/blob/master/tools/zanata/zanata_stats.py#… ** Affects: openstack-i18n Importance: Critical Assignee: Akihiro Motoki (amotoki) Status: New ** Changed in: openstack-i18n Assignee: (unassigned) => Akihiro Motoki (amotoki) -- 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/1670640 Title: zanata_stat.py does not honor branch (version) and stats of the last processed branch is used Status in openstack i18n: New Bug description: zanata_stat.py can process multiple versions (branches) at the same time, but the logic does not honor a version processed. As a result, user stats from the last processed version is used as user translation stats. AFAIK the tool is used to retrieve translation stats and determine ATC status. https://github.com/openstack/i18n/blob/master/tools/zanata/zanata_stats.py#… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1670640/+subscriptions

2 1