- OpenStack-I18n - lists.openstack.org

Ironic's .po files contain only blank msgstr's
by Devananda van der Veen 01 Apr '14

01 Apr '14

Hi all, I recently noticed that none of the ironic/locale/*/LC_MESSAGES/ironic.po files contain any translated strings, even though Jenkins is routinely proposing updates. I looked a bit further into this, with a few pointers from Clark, and it seems that the jenkins translation job is erroring out. It claims there's a duplicate message, but I haven't been able to figure out why. I've filed a bug here: https://bugs.launchpad.net/ironic/+bug/1298645 For quick reference, here's a link to the errors that we think are the cause of this issue: http://logs.openstack.org/periodic/ironic-propose-translation-update/6aed39… Then, today, I noticed that the same error also shows up in Nova and Ceilometer's recent jobs. Here's an example from Nova. http://logs.openstack.org/8d/8df565d39cd3216bde8488e656957a49dd6949fa/post/… I could use some help figuring this out. Since folks have been translating strings for Ironic, I'd really like to be able to include that work in our Icehouse release :) Thanks much, Devananda

4 6

Clarifying String Freeze
by Julie Pichon 01 Apr '14

01 Apr '14

Hi all, During the weekly Horizon meeting [0], a few questions from the Horizon team came up about String Freeze. I think the wiki page on String Freeze [1] at the moment does not match the wishes of the translation team, based on previous conversations [2]. It would be really helpful if the wiki page could be updated to match what the i18n team would prefer. At the moment, in Horizon it seems what we're doing, and planning on doing, is this (somewhat similar to what happened in Havana): - During String Freeze and until RC1, small string changes are ok (Horizon core can just approve) - During String Freeze, string changes in the "grey zone" should use the exception approval process on the wiki (email to i18n list) - After RC1 is released, every string change should follow the exception approval process on the wiki (email to i18n list) ??? - this isn't clearly defined yet, maybe it needs to be earlier? Point #3 is about when the "soft freeze" needs to become a "hard freeze". What is the grey zone? I'm not entirely sure either. An example was: adding several new strings for what could be considered a "mini-feature", during the RC period. Perhaps we can start with this kind of examples + "when in doubt, ask on the i18n list" to define what is the grey zone. In general, I think updating the wiki page would really help reviewers assess patches with a clearer understanding of what is helpful to the i18n/translation team during string freeze, and what might require exception approval or more discussion. Thank you, Julie [0] http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-03-25-16.… [1] https://wiki.openstack.org/wiki/StringFreeze [2] http://lists.openstack.org/pipermail/openstack-dev/2014-March/029868.html

3 2

Translate Horizon for Icehouse version
by Ying Chun Guo 01 Apr '14

01 Apr '14

Hello, It's very near the release of Icehouse now. We need help on the translation of Horizon, especially to the following languages: Portuguese, French, Dutch, Russian, Spanish, Traditional Chinese Polish. The translation of these languages are very near to the goal, only hundreds of strings left. Other languages are welcome too. If you want to help, go to https://www.transifex.com/projects/p/horizon/resource/openstack-dashboard-t… https://www.transifex.com/projects/p/horizon/resource/horizon-translations/ https://www.transifex.com/projects/p/horizon/resource/horizon-js-translatio… If the translation can be 100% done before April 10th, it will be shipped with OpenStack Icehouse. If you have questions, go to IRC channel #openstack-translation, or attend our IRC meeting at March 20th 0000 UTC in the channel of #openstack-meeting. Best regards Ying Chun Guo (Daisy)

8 8

Polish translation ready
by Łukasz Jernaś 29 Mar '14

29 Mar '14

Hi, The Polish translation is ready for Icehouse release. There's one string I'm not happy with (Disk over commit), but at least it's readable for admins. Sorry it took so long :( Best regards, -- Łukasz [DeeJay1] Jernaś

1 0

German horizon translation complete
by Sascha Peilicke 28 Mar '14

28 Mar '14

According to https://www.transifex.com/projects/p/horizon/translate/#de, the German horizon translation is at 100%. It certainly isn't perfect yet, there are some orthographic issues to hunt down and we have to agree on some common style (i.e. work on a dictionary). However, we're confident that it could go into Icehouse in it's current state already. Thanks to everybody that participated in this amazingly fast translation sprint! -- Viele Grüße, Sascha Peilicke

3 2

Traditional Chinese translation has been completed
by 張效維 28 Mar '14

28 Mar '14

Hi all: We has finished the Traditional Chinese translation to 100% since last POT upgrade. https://www.transifex.com/projects/p/horizon/language/zh_TW/ Last POT upgrade has deleted some unperfect translated words. So that our work are good enough. From Xiaowei -- NTHU Xiaowei +886-928337382 zero00072(a)gmail.com

1 0

Horizon upstream_translation_update Jenkins job
by Akihiro Motoki 27 Mar '14

27 Mar '14

Hi Daisy, Perhaps RC1 may be shipped this week and the master branch will be opened to Juno development. Even after the master branch is opened to Juno, Transifex resources are still targeted to Icehouse translations. We need to disable upstream_translation_update for Horizon temporarily. Otherwise Transifex resources will be synced with Juno code. Could you coordinate it with the infra team? At now Horizon is the only project whose translation work is being done synced with the release cycle and we tend to encounter the first thing :-( Thanks, Akihiro

2 2

Horizon translations - and update of strings
by Andreas Jaeger 24 Mar '14

24 Mar '14

Looking at my patch to import back the Horizon translations (https://review.openstack.org/#/c/82176) and the comments by Akihiro Motoki, I notice that horizon has no command to update the message catalogs. For all other projects, we basically do the following as part of the propose job: * Download all translation PO files from transifex * Update POT file * Update PO files based on pot file ("python setup.py update_catalogs") * Upload POT and PO files to transifex Horizon does not implement update_catalogs at all. Is this step really needed or is something that transifex does for us and thus we could remove the step? Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 6

Re: [Openstack-i18n] .tx in git repository
by Sascha Peilicke 24 Mar '14

24 Mar '14

Sorry for replying a bit late, I just recently joined the list. Meanwhile, .tx was removed from openstack-manuals. However, I think the points raised by Akihiro Motoki haven't been answered. Previously unaware of this discussion, I submitted https://review.openstack.org/#/c/81839/. In short, .tx/config should really be versioned since it contains repo-specific file-paths. While of course this can be autogenerated in the infra job, it doesn't help people that want to use local tools (such as vi / $FAVORITE_PO_EDITOR) instead of the Transifex web-interface. This also raises the side-question if it is acceptable to submit reviews that add translations or if those should somehow be imported into Transifex web instead and fetched via the infra job? -- Viele Grüße, Sascha Peilicke

3 5

German translation team changes
by Sascha Peilicke 21 Mar '14

21 Mar '14

Hi guys, I recently took over coordination of the German translation team on Transifex after the previous coordinator didn't show any activity anymore. I'm an engineer from SUSE and contributed to the German translation before. I also took the liberty to add two of my colleagues as reviewers. Both have added to the German translations before and we didn't have any reviewers before. -- Viele Grüße, Sascha Peilicke

2 1