November 2013 - OpenStack-I18n - lists.openstack.org

Horizon(Havana) found typing error at korean translation.
by Sungjin Kang 17 Nov '13

17 Nov '13

Hi, Sorry, Horizon korean translation is typing error. Firewall page -> Policy is “폴린드어(Polish)”…. :( So, I edited Transifex this string. :) This edit patch at next horizon update(2013.2.1). PLZ…. And where is typing error reporting? Launchpad?? or other?? Thanks, Sungjin

3 2

Collecting requirements to translation tools
by Ying Chun Guo 17 Nov '13

17 Nov '13

Hi, I18n team One year ago, when the community was making the decision to use Transifex as the translation management tool, a table was made to compare several different tools: https://docs.google.com/spreadsheet/ccc?key=0Aqevw3Q-ErDUdFgzT3VNVXQxd095bF… Now since Transifex began to close its source code, we will do another round of tool selection to find the translation management tool for Openstack translation. We will start from requirements collection. Here I listed some. (Some are copied from the old table. The last three items are newly added. ) * Cross-project translation teams * Cross-project translation memory * Good in-browser translation interface * Good in-browser review interface * Easy import/export of translation files * Support for all common translation formats * Git/GitHub Integration * Hooks for CI infrastructure * Management workflows that fit OpenStack process * Self-hosted * Proven success with large projects * API to gather statistics about translators * Easily see the translating context, i.g. the paragraph or section that contains the translation string. * Cross-project glossary and dictionary Please feel free to present your requirements to the translation management tool. If you know some good candidate tools, please speak out too. Let's find out the most appropriate tool together, and build a "wonderful" working environment for ourselves. Regards Ying Chun Guo (Daisy)

6 13

Interested in contributing translations for OpenStack
by Shilla Saebi 15 Nov '13

15 Nov '13

Hello, I signed up for an account in Transifex and attempted to add an available language (Persian - Farsi) but I was only able to request the language. Per the following link: https://wiki.openstack.org/wiki/Documentation/Translation I should see an option to create language but I did not see that. Can you please take a look and let me know what's going on? Thanks a lot! Shilla Saebi

3 2

Re: [Openstack-i18n] [Openstack-docs] On translations and ITS
by Tom Fifield 05 Nov '13

05 Nov '13

(CC OpenStack-i18n - consider joining!) A very nice lead in discussion to our two sessions related to this at the summit :) Right now, we have some custom code for 1 that has been customised for the OpenStack docs (for example, it excludes screen elements ;)), giving some of the practical benefits of ITS. It's in tools/generatepot. Looking forward to discussing more next week. Regards, Tom On 02/11/13 05:34, Shaun McCance wrote: > I have some experience (read: bias) in translation tools, so I'm writing > up a synopsis in the hopes in will be useful for the documentation > translation session at the summit next week. > > Document translation generally follows a three-step process: > > 1) Segmentation: A program takes the XML files and breaks it up into > chunks (often paragraphs) that can be individually translated and > tracked. These are usually stored in either PO or XLIFF files, but in > some systems they might be records in a database. > > 2) Translation: Translators translate those segments. They might edit > the PO or XLIFF files directly. They might use a graphical front-end. > They might do it through a web site that hides the files from them, but > still presents the individual segments. > > 3) Merging: A program takes the translated segments, matches them up to > the appropriate nodes in the source document, and writes a localized XML > file. > > Online tools like Transifex, Zanata, and Pootle are really about step 2, > but they often include code for steps 1 and 3 to give you an all-in-one > package. Unfortunately, to my knowledge, none of them use the W3C > Internationalization Tag Set (ITS) to accomplish those steps. Luckily, > they let you provide POT files and can give you PO files, which means > you can plug your own code in for steps 1 and 3. > > ITS is a W3C recommendation that provides a standard way to specify what > parts of a document are translatable, what elements are inline, and > various other things that are really critical for good segmentation. ITS > 2.0 was released this week, and addresses a whole slew of other issues. > > http://www.w3.org/TR/its20/ > > ITS lets you assert things about elements on a global level using XPath > expression. For example, let's say we don't want any of our screen > elements to be translated. We could use a rule like this: > > <its:translateRule translate="no" selector="//db:screen"/> > > Magically, hundreds of messages will disappear from translators' view, > allowing them time to have dinner with their families instead. You can > also mark things locally. So for example, if we don't want to exclude > all screen elements from translation, then on the ones we do want to > exclude, we'd write this: > > <screen its:translate="no"> > > You can also specify which elements are within text (inline), which are > space-preserving, where there are references to external resources like > images that have to be localized, and lots more. > > Biased opinion: If you have an XML translation process that doesn't > involve ITS, you're doing something wrong. (Disclosure: I was on the > working group that created ITS 2.0, and I'm the developer of itstool.) > > There are a number of tools that support ITS. Many of them work with PO > or XLIFF files, so you can plug them into most online translation tools. > I happen to be fond of my program, itstool, which supports PO files and > has a number of extensions that have been useful for other open source > projects like GNOME. > > http://itstool.org/ > > If you want a workflow that uses XLIFF files, you should look into > Okapi, a fantastic open source framework that supports ITS. > > http://okapi.sourceforge.net/ > > I do have a dog in this race, so I'm trying not to be too pushy. But > there are a lot of smart people who spent a lot of time figuring this > stuff out. If you have non-ITS segmentation and merging code, you'll > just end up chasing problems that have already been solved. > > If it's not obvious, I love talking about this stuff. So feel free to > ask me questions. > > Thanks, > Shaun > > > > _______________________________________________ > Openstack-docs mailing list > Openstack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs >

3 3

experiences and tips in ops-guide translation (a case of Japanese community)
by Akihiro Motoki 04 Nov '13

04 Nov '13

Hi I18N community, I summarized our experiences and tips of Japanese community in ops-guide translation. https://docs.google.com/presentation/d/1kQN-9765PzNbTSw5YoSl9kNOsUU_Gj74HQZ… While several months passed after the ops-guide translation finished, I believe it is still useful to clarify requirements for document translations and it may bring us some ideas in the discussion in Hong Kong and the future. I don't think our approach works well for everyone and is ideal, but at least it works for us and makes us much efficient compared to a case where we use Transifex. Thanks, Akihiro

3 3

Relevant sessions for i18n at the summit
by Tom Fifield 03 Nov '13

03 Nov '13

Hi, A couple of people have asked about sessions they can attend about i18n at the summit. Here's my list: Thursday November 7, 2013 11:00am - 11:40am AWE Level 2, Room 202 Translation tools and scripts http://icehousedesignsummit.sched.org/event/36d10d27f8a030c02fc35553cc24187… Tuesday, November 5 • 3:40pm - 4:20pm AWE Level 2, Room 202 Publishing translated documentation http://icehousedesignsummit.sched.org/event/a7731c633cd4c57d4647af8c5482941… Wednesday November 6, 2013 11:15am - 11:55am AWE Level 2, Room 201B I18n policies of messages http://icehousedesignsummit.sched.org/event/b55de8b048803806c9acace66c21f6d… Friday, November 8 • 5:00pm - 5:40pm Developing a Roadmap for Global Adoption: Exploring OpenStack's Globalization Best Practices http://openstacksummitnovember2013.sched.org/event/70cbdbcb75e4b20410d318e1… Friday November 8, 2013 4:10pm - 4:50pm AWE Level 2, Room 204-205 Icehouse release schedule & coordination http://icehousedesignsummit.sched.org/event/839c04a94f50b18f3b963d8e1c58707… Regards, Tom

1 0