- OpenStack-I18n - lists.openstack.org

[horizon] contextual-markers for better translations
by Yves-Gwenaël Bourhis 14 Apr '14

14 Apr '14

Hi all, I noticed that translating to certain languages requires some compromises in both grammar and syntax to often have a deceiving result... This is due to the fact that we do not use contextual-markers: https://docs.djangoproject.com/en/dev/topics/i18n/translation/#contextual-m… except in one unique place: https://bugs.launchpad.net/horizon/+bug/1307476 The context is required because a word which is spelled the same in English may be 2 different words in an other language. Even less trivial, a same word with the same meaning can be spelled differently depending on the way it is used in a sentence, and there the context is really important. Some work was already done with https://bugs.launchpad.net/horizon/+bug/1253678 But contextual-markers need to be added to many translatable strings. The issue about changing translatable strings to contextual translatable strings implies redoing all those translations. Do not PANIC :-) , the current translations will remain as is for Icehouse, the impact of using contextual-markers will be for Juno. My concern is that many other languages than my 2 native ones have a richer syntax, so I may not be aware of all possible contexts required for other languages to be properly translatable. Concerning the example I gave in https://bugs.launchpad.net/horizon/+bug/1307476 any comment on the "context" you would need to help you make a better translation will be welcomed, and I'll need your feedback on what context "you" need and in which place in the dashboard, in order to help you make the best translations. So feel free to drop a reply to this mail with all the places where your struggle to provide a translation due to lack of context and where a context and reformulation would really help you do your translations. Thank you all. -- Yves-Gwenaël Bourhis

1 0

Horizon translation status update
by Akihiro Motoki 11 Apr '14

11 Apr '14

Hi all, Thanks for your efforts of Icehouse translations. I would like to share my plan for Horizon translations both for Havana and Icehouse and know your opinions. [Havana] After Iceehouse is release, the last update of Havana (2013.2.4) is planned [1]. As far as I checked Transifex translations, a couple of languages have updates since Havana 2013.2.2 (released Feb 13). IMO it is better to import translations for the last coming Havana update. Thought? [Icehouse] As we did for Havana stable updates, we have a plan to import translations for each stable Icehouse update. The first two stable updates are good chances to update our translations. [Juno] Juno translations of Horizon are now marked as "translation is not accepted" to avoid confusions. I will remove this restriction once Icehouse is released. As you may know, it does not fit for translations as many changes will happen in the next half year. INSTEAD I would suggest to report issues to Horizon if you feel difficulties during translating for Icehouse or have improvement requests. (Of course this list can be used to discuss these topics too.) The exact dates both for Havana and Icehouse will be determined after the next OpenStack Summit is over. [1] https://wiki.openstack.org/wiki/StableBranchRelease#Planned_stable.2Fhavana… Thanks, Akihiro

1 0

Regarding Adding Hindi Language to the icehouse Dashboard Translation release list
by chandan kumar 09 Apr '14

09 Apr '14

Hello All, I am translating OpenStack Dashboard for Hindi Language. Right now 662 strings are left in icehouse-horizon-dashboard. It will be get completed by 12:00 P.M. (IST). https://www.transifex.com/projects/p/horizon/language/hi/ it would be great if Hindi is released in Icehouse for Dashboard. Thanks, Chandan Kumar

5 7

Important notice about Horizon translation
by Ying Chun Guo 07 Apr '14

07 Apr '14

Hello all Now Horizon RC1 is shipped. The source codes of Horizon in git repository will be switched from master branch to icehouse branch. Our translation resources will switch as the same time. If you look at the resources of Horizon, you will notice there are 3 resources with a prefix of "Icehouse", and 3 resources with a prefix of "Juno". Now we are working on the translations for Icehouse release. So the resources we are working on are: - Icehouse - Horizon JavaScript Translations: https://www.transifex.com/projects/p/horizon/resource/horizon-js-translatio… - Icehouse - Horizon Translations: https://www.transifex.com/projects/p/horizon/resource/horizon-translations-… - Icehouse - Openstack Dashboard Translations : https://www.transifex.com/projects/p/horizon/resource/openstack-dashboard-t… The resources for Juno release are marked as "not accept translation". Please pay attention to it. @ French, Korean, Chinese (Taiwan ) and Portuguese translation teams: The translation of "Icehouse - Openstack Dashboard Translations" are not 100% completed. It is caused by the update of source po file. Please take a look at it. Thanks and regards Daisy

8 12

Review I18n meeting time
by Ying Chun Guo 03 Apr '14

03 Apr '14

Hello, team We have used these two meeting times for several months: 0700UTC on the first Thursday and 0000UTC on the third Thursday. I'd like to review if the meeting times work for you, or whether we need to change to another time. Please help to answer these questions: 1. Would you like to attend I18n meeting? (If YES, go to question 2 & 3; if NO, go to question 4 ) --YES to question 1-- 2. Which time and frequency do you prefer? 3. Any suggestions to make the meeting useful and effective. --NO to question 1-- 4. Which communication way do you prefer? You can reply to me only if you don't want to share your thoughts. And I welcome any suggestions to improve our meetings and communication methods. Best regards Ying Chun Guo (Daisy)

3 2

[Ironic] [i18n] Testing translations
by Devananda van der Veen 01 Apr '14

01 Apr '14

For those interested in translations, I'd like to jot down a few notes from the last few days' work to get i18n'd strings into Ironic before our RC. Hopefully some of this will be helpful to someone out there -- it's been a learning experience for me :) Quick background: - the project was set up with transifex a while back - folks have been translating our strings on transifex - jenkins has been regularly proposing updates to ironic, which we've accepted However, late last week I noticed that none of the ironic/locale/*/LC_MESSAGES/ironic.po files had any actual translated strings in them. Some digging revealed that there were two problems: * most of the .po files had somehow gotten malformatted (duplicate blank messages). We now have a tox check to prevent this. * the file timestamps were newer than the translations on transifex. Easy work around is "pull --force". Manual fixes for both of these have landed in Ironic, and longer-term fixes have gone up for infra and some other projects. To determine whether or not this was successful in enabling translated strings in Ironic, I had to learn a few things about babel and gettextutils, but there's still a lot more catching up on the whole i18n discussion that I need to do. This morning, I confirmed, in fact, our LOG messages are getting translated based on the system language, if the correct locale's .mo file is found in the appropriate system path, or that path is overridden with the IRONIC_LOCALEDIR env var. At the moment, Ironic's API strings will also be translated based on the system language, not on the Accept-Language header. https://bugs.launchpad.net/ironic/+bug/1300939 I've jotted down some notes on how to recreate an environment which reproduces this without needing to package and install ironic. https://etherpad.openstack.org/p/TestingTranslations It also seems that we're not programatically testing whether translation works or not. Maybe there's a good reason this hasn't been done yet... but after spending a couple days getting it to work in Ironic, I would like to add a test to our gate so that I know it stays working. I'm not sure the best way to go about that, but I hope someone who knows more about tx/msgfmt/babel/etc can look at my notes above and suggest or get something going from that. Cheers, Devananda

1 0

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 31 Mar '14

31 Mar '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