July 2016 - OpenStack-I18n - lists.openstack.org

[Bug 1586041] [NEW] Incorrect PO-Revision-Date in some translation files for aodh project
by Alfredo Moralejo 03 Aug '17

03 Aug '17

Public bug reported: Following .po files have empty revision date, "PO-Revision-Date: \n": aodh/locale/it/LC_MESSAGES/aodh.po aodh/locale/pt_BR/LC_MESSAGES/aodh.po aodh/locale/zh_CN/LC_MESSAGES/aodh-log-info.po aodh/locale/zh_CN/LC_MESSAGES/aodh.po aodh/locale/zh_TW/LC_MESSAGES/aodh.po This makes compile_catalog to fail: $ python setup.py compile_catalog running compile_catalog compiling catalog aodh/locale/ja/LC_MESSAGES/aodh.po to aodh/locale/ja/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/ru/LC_MESSAGES/aodh.po to aodh/locale/ru/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/pt/LC_MESSAGES/aodh.po to aodh/locale/pt/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/en_GB/LC_MESSAGES/aodh.po to aodh/locale/en_GB/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/ko_KR/LC_MESSAGES/aodh.po to aodh/locale/ko_KR/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/de/LC_MESSAGES/aodh.po to aodh/locale/de/LC_MESSAGES/aodh.mo Traceback (most recent call last): File "setup.py", line 29, in <module> pbr=True) File "/usr/lib64/python2.7/distutils/core.py", line 151, in setup dist.run_commands() File "/usr/lib64/python2.7/distutils/dist.py", line 953, in run_commands self.run_command(cmd) File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command cmd_obj.run() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/frontend.py", line 178, in run self._run_domain(domain) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/frontend.py", line 218, in _run_domain catalog = read_po(infile, locale) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/pofile.py", line 217, in read_po _add_message() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/pofile.py", line 165, in _add_message catalog[msgid] = message File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 601, in __setitem__ self.mime_headers = _parse_header(message.string).items() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 420, in _set_mime_headers self.revision_date = _parse_datetime_header(value) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 46, in _parse_datetime_header tt = time.strptime(match.group('datetime'), '%Y-%m-%d %H:%M') File "/usr/lib64/python2.7/_strptime.py", line 467, in _strptime_time return _strptime(data_string, format)[0] File "/usr/lib64/python2.7/_strptime.py", line 325, in _strptime (data_string, format)) ValueError: time data u'' does not match format '%Y-%m-%d %H:%M' I've checked in https://translate.openstack.org that files are wrong there too, not only in github. ** 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/1586041 Title: Incorrect PO-Revision-Date in some translation files for aodh project Status in openstack i18n: New Bug description: Following .po files have empty revision date, "PO-Revision-Date: \n": aodh/locale/it/LC_MESSAGES/aodh.po aodh/locale/pt_BR/LC_MESSAGES/aodh.po aodh/locale/zh_CN/LC_MESSAGES/aodh-log-info.po aodh/locale/zh_CN/LC_MESSAGES/aodh.po aodh/locale/zh_TW/LC_MESSAGES/aodh.po This makes compile_catalog to fail: $ python setup.py compile_catalog running compile_catalog compiling catalog aodh/locale/ja/LC_MESSAGES/aodh.po to aodh/locale/ja/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/ru/LC_MESSAGES/aodh.po to aodh/locale/ru/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/pt/LC_MESSAGES/aodh.po to aodh/locale/pt/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/en_GB/LC_MESSAGES/aodh.po to aodh/locale/en_GB/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/ko_KR/LC_MESSAGES/aodh.po to aodh/locale/ko_KR/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/de/LC_MESSAGES/aodh.po to aodh/locale/de/LC_MESSAGES/aodh.mo Traceback (most recent call last): File "setup.py", line 29, in <module> pbr=True) File "/usr/lib64/python2.7/distutils/core.py", line 151, in setup dist.run_commands() File "/usr/lib64/python2.7/distutils/dist.py", line 953, in run_commands self.run_command(cmd) File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command cmd_obj.run() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/frontend.py", line 178, in run self._run_domain(domain) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/frontend.py", line 218, in _run_domain catalog = read_po(infile, locale) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/pofile.py", line 217, in read_po _add_message() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/pofile.py", line 165, in _add_message catalog[msgid] = message File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 601, in __setitem__ self.mime_headers = _parse_header(message.string).items() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 420, in _set_mime_headers self.revision_date = _parse_datetime_header(value) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 46, in _parse_datetime_header tt = time.strptime(match.group('datetime'), '%Y-%m-%d %H:%M') File "/usr/lib64/python2.7/_strptime.py", line 467, in _strptime_time return _strptime(data_string, format)[0] File "/usr/lib64/python2.7/_strptime.py", line 325, in _strptime (data_string, format)) ValueError: time data u'' does not match format '%Y-%m-%d %H:%M' I've checked in https://translate.openstack.org that files are wrong there too, not only in github. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1586041/+subscriptions

2 1

To language team coordinators: get ready for Mitaka translation
by Ying Chun Guo 28 Sep '16

28 Sep '16

Dear coordinators, Mitaka translation will be started at the beginning of March, and probably ended in the week of March 28. We need to get ourselves ready for Mitaka translation from now on. Because of the join of IBM professional translators, we will be able to cover more projects in our translation plan of this release. Generally, the jobs of existing community translators will not be affected, focus on Horizon, same as before. IBM translators will focus on "other" projects. Before Mitaka translation starts, there are several things you can do: 1. Update glossary. If you don't have glossary translations in i18n repo[1], or you want to update glossary translations, you can send a patch with your translations or your updates to i18n repo directly. 2. Document your local team communication method in the team wiki page[2]. While Mitaka translation starts, it's good to open your local communication channel to all of your language translators. Good communication is quite important for people from different places to work well together. 3. Join IRC channel[3] #openstack-i18n with your zanata ID As a coordinator, you have the responsibility to coordinate your language translations. A good practise is to show up in IRC and have your people to get you easily when they have troubles. If you have any questions, talk to me. My IRC ID is "Daisy" in the channel of #openstack-i18n. Thank you. Best regards Ying Chun Guo (Daisy) [1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale [2] https://wiki.openstack.org/wiki/I18nTeam/team [3] https://wiki.openstack.org/wiki/IRC

9 27

[Bug 1587221] [NEW] openstack-manuals stable-mitaka releasenotes on Zanata looks unnecessary
by Akihiro Motoki 20 Sep '16

20 Sep '16

Public bug reported: As we discussed at Austin, only the master version is required for release notes translation on Zanata. Zanata currently has openstack- manuals stable-mitaka releasenotes resource. It looks unnecessary. ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: infra -- 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/1587221 Title: openstack-manuals stable-mitaka releasenotes on Zanata looks unnecessary Status in openstack i18n: New Bug description: As we discussed at Austin, only the master version is required for release notes translation on Zanata. Zanata currently has openstack- manuals stable-mitaka releasenotes resource. It looks unnecessary. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1587221/+subscriptions

2 1

I18n team mascot
by Kato, Tomoyuki 04 Aug '16

04 Aug '16

Hi team, We have a chance to get our team mascot with an illustrator[1][2]. Any ideas are welcome. Please write your candidacy. https://etherpad.openstack.org/p/i18n-mascot Due date: July 25 [1] http://lists.openstack.org/pipermail/openstack-dev/2016-July/099046.html [2] http://www.openstack.org/project-mascots Thanks, KATO Tomomoyuki

13 22

Current status of important topics??
by Akihiro Motoki 01 Aug '16

01 Aug '16

Hi all, Newton-2 is approaching. I would like to know the current status of important topics in Newton cycle. IIRC, we have several critical and important topics Kato-san listed. ## Translation check site We spent two cycles already, but it is not yet ready. We need to wait it one more cycle? ## Glossary management I would like to update Japanese glossary with our latest glossary but it is not easy to add several number of new entries to PO file manually. Is there any progress? If we don't plan any change soon, I will import Japanese glossary on Wiki into PO glossary by script (no manual edit). ## Release notes translation Are translated versions published somewhere? Unfortunately I cannot spend time for these efforts as I mentioned before. I hope you have good progress. Akihiro

3 3

why is "Fix Committed' status used
by Akihiro Motoki 01 Aug '16

01 Aug '16

I see bugs with Fix Committed status in openstack-i18n launchpad. Who changes their status to Fix Released? Why don't we set Fix Released when a bug is fixed? Most OpenStack projects set a bug status to Fix Released when a fix is merged into a repo. What is the bug lifecycle in openstack-i18n?

2 1

[Bug 1573514] Re: Typos in Italian Mitaka translation
by Ian Y. Choi 01 Aug '16

01 Aug '16

No extra character currently on https://git.openstack.org/cgit/openstack/neutron/tree/neutron/locale/it/LC_… ** Changed in: openstack-i18n Status: Fix Committed => 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/1573514 Title: Typos in Italian Mitaka translation Status in openstack i18n: Fix Released Bug description: Zanata proposed another update for mitaka neutron Italian translation: https://review.openstack.org/#/c/309280/ There are several concerns I have here. First, it seems that the change has some typos (e.g. using a ¥ character while the language does not use it at all). Second, the change removes authorship for multiple contributors. I suspect it's not expected. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1573514/+subscriptions

1 0

[Bug 1606115] [NEW] mistranslation in install guide japanese
by Yusuke HIgashino 01 Aug '16

01 Aug '16

Public bug reported: openstack-manuals master Documents (ja) doc/install- guide/source/locale/install-guide Edit the ``/etc/chrony/chrony.conf`` file and add, change, or remove the following keys as necessary for your environment: ↓ ファイル ``/etc/ntp.conf`` を編集して、お使いの環境の必要に応じて、以下の項目の追加、変更、削除を行います。 ``/etc/chrony/chrony.conf``→ ``/etc/ntp.conf``に翻訳されている。 ** 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/1606115 Title: mistranslation in install guide japanese Status in openstack i18n: New Bug description: openstack-manuals master Documents (ja) doc/install- guide/source/locale/install-guide Edit the ``/etc/chrony/chrony.conf`` file and add, change, or remove the following keys as necessary for your environment: ↓ ファイル ``/etc/ntp.conf`` を編集して、お使いの環境の必要に応じて、以下の項目の追加、変更、削除を行います。 ``/etc/chrony/chrony.conf``→ ``/etc/ntp.conf``に翻訳されている。 To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1606115/+subscriptions

2 1

[Bug 1592687] [NEW] wrong cs translation in magnum-ui and designate-dashboard
by Andreas Jaeger 01 Aug '16

01 Aug '16

Public bug reported: >From http://logs.openstack.org/periodic/magnum-ui-propose-translation- update/d8f24a9/console.html 2016-06-15 07:32:26.968627 + msgfmt --check-format -o /dev/null magnum_ui/locale/cs/LC_MESSAGES/djangojs.po 2016-06-15 07:32:26.971559 magnum_ui/locale/cs/LC_MESSAGES/djangojs.po:150: number of format specifications in 'msgid_plural' and 'msgstr[1]' does not match 2016-06-15 07:32:26.971678 magnum_ui/locale/cs/LC_MESSAGES/djangojs.po:411: number of format specifications in 'msgid_plural' and 'msgstr[2]' does not match 2016-06-15 07:32:26.971752 msgfmt: found 3 fatal errors 2016-06-15 07:32:26.972356 + ret=1 2016-06-15 07:32:26.972416 + set -e 2016-06-15 07:32:26.972478 + '[' 1 -ne 0 ']' 2016-06-15 07:32:26.972534 + changed=0 2016-06-15 07:32:26.972612 + echo 'ERROR: File magnum_ui/locale/cs/LC_MESSAGES/djangojs.po is an invalid po file.' 2016-06-15 07:32:26.972679 ERROR: File magnum_ui/locale/cs/LC_MESSAGES/djangojs.po is an invalid po file. 2016-06-15 07:32:26.972748 + echo 'ERROR: The file has not been imported and needs fixing!' 2016-06-15 07:32:26.972795 ERROR: The file has not been imported and needs fixing! ** Affects: openstack-i18n Importance: Undecided Status: New ** Summary changed: - wrong cs translation in magnum-ui + wrong cs translation in magnum-ui and designate-dashboard -- 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/1592687 Title: wrong cs translation in magnum-ui and designate-dashboard Status in openstack i18n: New Bug description: From http://logs.openstack.org/periodic/magnum-ui-propose-translation- update/d8f24a9/console.html 2016-06-15 07:32:26.968627 + msgfmt --check-format -o /dev/null magnum_ui/locale/cs/LC_MESSAGES/djangojs.po 2016-06-15 07:32:26.971559 magnum_ui/locale/cs/LC_MESSAGES/djangojs.po:150: number of format specifications in 'msgid_plural' and 'msgstr[1]' does not match 2016-06-15 07:32:26.971678 magnum_ui/locale/cs/LC_MESSAGES/djangojs.po:411: number of format specifications in 'msgid_plural' and 'msgstr[2]' does not match 2016-06-15 07:32:26.971752 msgfmt: found 3 fatal errors 2016-06-15 07:32:26.972356 + ret=1 2016-06-15 07:32:26.972416 + set -e 2016-06-15 07:32:26.972478 + '[' 1 -ne 0 ']' 2016-06-15 07:32:26.972534 + changed=0 2016-06-15 07:32:26.972612 + echo 'ERROR: File magnum_ui/locale/cs/LC_MESSAGES/djangojs.po is an invalid po file.' 2016-06-15 07:32:26.972679 ERROR: File magnum_ui/locale/cs/LC_MESSAGES/djangojs.po is an invalid po file. 2016-06-15 07:32:26.972748 + echo 'ERROR: The file has not been imported and needs fixing!' 2016-06-15 07:32:26.972795 ERROR: The file has not been imported and needs fixing! To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1592687/+subscriptions

2 1

Disabling translation sync for mitaka?
by Andreas Jaeger 30 Jul '16

30 Jul '16

Hi, we're preparing the move to Xenial now in OpenStack CI and for those I wonder how to handle translations. We have these options: 1) We can continue to run mitaka on Trusty but that means work to split up jobs so that newton runs on Xenial but mitaka on Trusty. 2) We can disable mitaka on Trusty and only do Xenial jobs. 3) We can use translation setup for both newton and mitaka using Xenial. In addition, I'd like to disable the liberty documentation translation that we currently still have for OpenStack manuals. I can work on option 2 - but options 1 and 3 are more involved, if that is the overall preference, I will need help from others - especially in reviewing that everything works and fixing if needed. Can we go with 2 now? If not, which projects still get mitaka translation? 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

5 10