- OpenStack-I18n - lists.openstack.org

Let's translate horizon for Icehouse!
by Akihiro Motoki 10 Mar '14

10 Mar '14

Hi I18N team, Icehouse-3 milestone has been shipped and it is time to start Horizon translation for Icehouse. Horizon resources on Transifex are now synced with Horizon Git repository automatically. Once a patch is approved and merged, new strings are pushed to Transifex if necessary. Thanks Daisy for the automated script. Let's visit https://www.transifex.com/projects/p/horizon/resources/ and translate! Resources *without* "Havana" are translation targets for Iceshouse. [Translation Import Date] It is not actually decided yet because Horizon RC1 date is not determined yet. According to Icehouse release schedule, RC period begins a week of Mar 27th. Only I can say is the first target date is the beginning of the week of Mar 27th (around Mar 24). Even if your translation is not completed by the date, we have another chance to import translations for Icehouse release (such RC2 or ...). I will update the date if I have an update. [Translation check site] As I did in Havana cycle, I will run translation check site. There is no change in the host and account information from Havana site. (It means my translation check site is switched to Icehouse version) http://157.7.133.23:13580/ Username: demo / admin, Password: opstjpHavana * Translations are imported from Transifex every hour. * Sometimes I will update devstack and latest codes from the official repos. * If something looks wrong, please let me know. Enjoy Icehouse version of OpenStack Dashboard!! Note that it is hosted on a virtual server donated to Japan OpenStack Users Group by GMO internet. Thanks. Cheers, Akihiro

6 5

Gating on string changes
by Łukasz Jernaś 06 Mar '14

06 Mar '14

Hi, continuing from todays meeting as I got caught up in work stuff (sorry Julie) So the idea was that changes on stable/* and milestone/proposed would run an additional gate job which would check for changes in strings and if they detect one would add a -1 review on the patchset in gerrit a new category. An i18n team member could accept the freeze exception by adding a +1 and only changes with 0 in that gerrit review category would pass or maybe a +1 if we settle on two members. This is modelled loosely on the rules used by the GNOME project (which I'm accustomed to, so forgive me the bias) described here: https://wiki.gnome.org/ReleasePlanning/Freezes https://wiki.gnome.org/TranslationProject/HandlingStringFreezes It just a thought of course, but seeing that the OpenStack project community is more diverse adding gerrit/jenkins checks would be a nice idea as enforcing an "send email" policy could be a lot harder. Best regards, -- Łukasz [DeeJay1] Jernaś

2 1

I18n meeting tomorrow
by Ying Chun Guo 05 Mar '14

05 Mar '14

Hello We will have our I18n meeting tomorrow at 0070 UTC in the channel "openstack-meeting". March starts. We should begin Horizon messages translation and I18n test for Icehouse release now. At the same time, we should conclude the installation guide translation and publish our results to the doc website. Let's discuss about these two topics in this meeting. Thanks and regards Ying Chun Guo (Daisy)

1 0

Korean install guide
by Łukasz Jernaś 25 Feb '14

25 Feb '14

Hi, I see, that I've been called out on the last meeting about the Korean install guide ;) So the problem with that guide has been noted earlier and reported on Launchpad as https://bugs.launchpad.net/openstack-i18n/+bug/1276434. Basically there's a wrong tag in the translated string which makes the maven plugin cry. As I don't have sufficient access to Transifex I can't fix it myself so only project admins or the Korean team can fix the issue. I hope the description in the mentioned bug helps to fix it! Best regards, -- Łukasz [DeeJay1] Jernaś P.S. ujuc if I somehow managed to miss the email from you, I'm sorry...

4 10

Travel Support Program for Summit in Atlanta
by Ying Chun Guo 24 Feb '14

24 Feb '14

Hello, The Atlanta summit will be held from May 12 to May 16 in Atlanta. If you want to attend but you cannot find travel support, you can try this program: https://wiki.openstack.org/wiki/Travel_Support_Program The program is to support the travel of "key contributors" to attend the summit. Key contributors are contributors whose presence is specifically relevant for the topics to be discussed at the Summit they're applying to. Contribution to translation and translation platform is definitely a kind of important contribution. A good idea to enhance our translation platform and translation process could be a candidate of design summit session. The Final deadline to submit applications is March 2nd. After you submit your application, please inform me. I will try my best to help. Thank you and best regards Ying Chun Guo (Daisy)

2 1

IRC meeting tomorrow
by Ying Chun Guo 19 Feb '14

19 Feb '14

Hello all, As the schedule, we will have I18n team meeting at 0000 UTC tomorrow in #openstack-meeting. I don't have many topics, except: * Issues collection and progress check for "Installation guide" translation * Synchronization processes for Horizon messages translation If you have other topics to discussion, please bring up. Let's meet at IRC tomorrow. Best regards Ying Chun Guo (Daisy)

1 0

Here to help about french translation
by Sonny TADJER 14 Feb '14

14 Feb '14

Hello everybody, I do not really know how to introduce myself. it’s been the third time we helped me about openstack so I just put my services to you about french translation. I do not know who to contact exactly (saw this : https://wiki.openstack.org/wiki/I18nTeam) and apparently no translators for french. How sad. So I will try to be on openstack-meeting at 2am tonight :) id : Sonny78

4 5

About "installation guide" translation
by Ying Chun Guo 14 Feb '14

14 Feb '14

@ teams who are translating "installation guide": "Installation guide" has references to a few xml files under the folder "common" in openstack-manuals. While you are translating "installation guide", don't forget these xml files. They are: keystone-concepts.xml kvm.xml qemu.xml introcution-to-xen.xml compute-options.xml ch_installdashboard.xml colocating-services.xml You can locate the strings of these xml files by the following steps: 1. Go to "common" in Transifex, and select your language. https://www.transifex.com/projects/p/openstack-manuals-i18n/resource/common/ 2. In the "search" box (at the top left corner), select "File" and input the xml file name . All the strings in this file will be listed. With the help of Łukasz Jernaś, there is an easy way to review your translation result. Go to website http://docs.przytulnoc.pl/ and select your language, you will see the translated document. There are 2 weeks left in Feb, let's try to complete the translation by this month! Thanks and regards Ying Chun Guo (Daisy)

2 1

[RFC] another message id generation proposal
by Peng Wu 14 Feb '14

14 Feb '14

Hi, Recently I read about the idea of REST API message and log message i18n proposals. I think maybe we could generate the message id by file name, method name and line no, like "test2.py#Main#15". I think this new message id is shorter and more readable than md5sum. And with this kind of information, the developer can locate the message as follows: 1. find all files with the same file name; 2. jump to the line no; 3. verify the function name and the gettext call; Then the developer can find the corresponding message. In the attachment, it is a small python program to print the information. Feel free to comment this new proposal. Thanks, Peng Wu Refer URL: https://blueprints.launchpad.net/oslo/+spec/log-messages-id https://blueprints.launchpad.net/oslo/+spec/log-messages-translation-domain PS: I just noticed that some developers are considering to log both English and translated log messages, dunno whether they plan to return both English and translated REST API messages.

2 2

Some hacks on gettext for separate pot file generation
by Peng Wu 11 Feb '14

11 Feb '14

Hi, Recently my colleagues pointed out that gtk+ project already support multiple pot files, it supports both _("msg") and P_("msg") notation. In gtk+ project, it has two directories, po for _("msg"), po-properties for P_("msg"). The po directory is the same as other projects, the po-properties directory has modified the po-properties/Makefile.in.in file, to recognize P_("msg"). It uses "XGETTEXT_KEYWORDS = --keyword --keyword=P_" to extract the P_("msg") messages. Actually this approach requires one directory for each pot file, maybe good to not introduce many gettext directories for openstack projects. Thanks, Peng Wu

1 0