- OpenStack-I18n - lists.openstack.org

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

Collecting requirements to translation tools
by Dwayne Bailey 31 Oct '13

31 Oct '13

Hi There, I was pointed to this discussion while on #pootle. Let me give some feedback on the items listed on your Google Doc adding info as needed and correcting any errors that I see. - *Cross-project translation teams* - Not 100% sure of the exact needs here. Pootle has a user centric permissions model, users can have permissions for languages, projects and translation project (i.e. a project in a given language). - *Cross-project translation memory* - Yes served from Amagama our global TM server. Amagama is a publicly hosted server loaded with translations for FOSS projects, optimised for high speed Levenshtein distance measurement. - We're landing local TM in Pootle in the next few weeks. - *Strong Crowdsource community* - Does this mean the development team or the translators on a shared hosted platform, seems to indicate the later based on the current analysis. - Simple management interface for project resources - Would someone mind elaborating on what the main benefits or use case for resources are for openstack? - Good in-browser management of resource priorities - Would someone mind elaborating on what the main benefits or use case for resources are for openstack? - While we don't have resource priorities Pootle does allow you to place files into goals. These goals can be prioritised to ensure that translators focus on the most important aspects of translation first. - *Proven success with large projects* - LibreOffice, Apache OpenOffice, Mozilla - Firefox, Thunderbird, Firefox OS and website localisations, Evernote. - *API to gather statistics about translators* - Data is there, the API framework is in place but no active users so no finalised, published or stable API - *Easily see the translating context, i.g. the paragraph or section that contains the translation string.* - Yes. Have a look at http://mozilla.locamotion.org/bn_IN/firefox/translate/#filter=incomplete&un… - Surrounding translations even when moving through the editors in a filtered way. You can expand and contract this context as needed and it is hidden when stepping through all translations to remove clutter. - You will see location information e.g. file location as well as line number if that is the only context you have - msgctxt and notes are shown if present. We don't show anything that doesn't exists, which might explain the current comment on the spreadsheet. Pootle UI approach is that we only show what is available i.e. no comment then we won't show you a missing comment. - *Cross-project glossary and dictionary* - Yes. Cross-project, you can load any terminology resource into any language's Terminology project - A project specific terminology file can also be used. - We don't have any specific dictionary integration but use Weblookups for e.g. Wikipedia to make it easy to research source texts without leaving Pootle UI. - *Code maturity (age of the code)* - Pootle was officially released in Dec 2004, about the same time as Launchpad, http://translate.sourceforge.net/pootle-release-2004-12-16.html - So almost 9 years of history in Pootle. The Translate Toolkit is somewhat older. Virtaal, our desktop translation tool, is younger. - Query by filename (eg to assign particular xml files for translation within a resource, as in Japanese ops guide translation) - Does that mean you have a repo but only want to see certain files? - Pootle can ignore files, so the opposite of that - Merging of uploaded PO files, so that only translations that changed in the PO file are changed in the project. Avoids overwriting when multiple translators work offline. - Yes, when uploading you have 3 choices, overwrite (if you have permission), turn conflicts into suggestion or make everything a suggestion - We err on making things a suggestion if we can't resolve the change. So does mean you might need to review the suggestions for your translations. - Performance of translation memory matching for non-latin languages - We use Levenshtein matching. So we're not doing anything special for non-Latin languages. - Training available? (devs, users, none) - Not sure what the needs or wants are here exactly - We've trained localisers across Africa, in India and other places - Written localisation guides for FOSS - Run Translateathons - etc - Roadmap - We haven't published a public roadmap but will be doing that once we get 2.5.1 out the door. Scheduled to go into beta this week. - Technical Support - Translate provides commercial support and development, primarily development - There is an active community that assist on the mailing list and IRC channels. -- Dwayne *Translate* +27 12 460 1095 (work)

1 0

Release Notes pt_BR
by Gabriel Wainer 30 Oct '13

30 Oct '13

Hi all, Finally, the pt_BR release notes are done. I've also added the link in the original page. https://wiki.openstack.org/wiki/ReleaseNotes/Havana/pt_BR Thanks! Gabriel.

2 1

Translated documents publish processing discussion in HongKong summit
by Ying Chun Guo 29 Oct '13

29 Oct '13

Hi, In HongKong summit, there is a slot in doc track to discuss about publish process of translated documents. If you will attend the design summit, I hope you can join the discussion and share your points with us. Hope to see you there. Regards Ying Chun Guo (Daisy) ----- Forwarded by Ying Chun Guo/China/IBM on 2013/10/24 09:09 ----- Anne Gentle <anne(a)openstack.org> wrote on 2013/10/23 11:09:01: > Anne Gentle <anne(a)openstack.org> > 2013/10/23 11:09 > > To > > "openstack-docs(a)lists.openstack.org" <openstack-docs(a)lists.openstack.org>, > > cc > > Subject > > [Openstack-docs] Summit Doc track proposals due > > Hi all, > We have four proposals for four slots for the Summit, I'm happy to > combine or re-think the spots if someone else wants to hold a > discussion in Hong Kong. > > Application Developer Resources Everett Toews > Automated Doc Tooling - status & plans Tom Fifield > Status and future of the restructure Tom Fifield > Publishing translated documentation Anne Gentle > I'm trying to get Todd Morey to do a short show-n-tell of a new > design for the docs site at the Summit, will keep you all posted. > > I don't see any specific API talks here, guess we'll look for those > in the nova v3 sessions. > > I'm also working on hosting a post-Summit "live" review event online > where we go over what the plans are for Icehouse. > > Thanks, > Anne_______________________________________________ > Openstack-docs mailing list > Openstack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

2 1

Release notes
by Ying Chun Guo 22 Oct '13

22 Oct '13

https://wiki.openstack.org/wiki/ReleaseNotes/Havana#OpenStack_Documentation I feel the release notes should be translated too. Who has the same feeling ? Regards Ying Chun Guo (Daisy)

9 39

Translation Wikipage
by SungJin Kang 22 Oct '13

22 Oct '13

Hi, I find translate page for wiki. img: http://goo.gl/oXDGt2 May be... This use... img: http://goo.gl/fElejJ and Img: http://goo.gl/Y0eu1w Media wiki help page : https://www.mediawiki.org/wiki/Project:Language_policy I don't know use this function. Where can ask using this function?? Thanks, Sungjin.

2 2

Collecting requirements to translation tools
by Carlos Munoz 18 Oct '13

18 Oct '13

Hi All, Parag just made me aware of this thread. I am the Team Supervisor for the Zanata project and just wanted to answer any questions you may have on the system. From what I read on the thread, below are the points you are looking for before choosing a system, so let me make a brief note about each of them. * Cross-project translation teams Zanata fully supports this. Translation teams are able to translate all projects to their assigned languages. * Cross-project translation memory Supported as well. Translators will be able to see the origin of a TM result. * Good in-browser translation interface Zanata has a rich translation editor that runs in the browser and supports an extensive set of keyboard shortcuts to make the process as quick as possible. * Good in-browser review interface We just introduced the review process into our latest version of Zanata, and are still making changes to make it as useful as possible. The review process happens in our translation editor as well, with 'Reviewers' being able to see an extended set of controls to comment, approve or reject translations. * Easy import/export of translation files Zanata has a maven, and a command line client to import and export translation files. * Support for all common translation formats Zanata supports PO, properties, and xliff. Other formats that are in experimental mode at the moment include OpenOffice, IDML, .txt, and a few others. * Git/GitHub Integration Zanta has a REST API which makes it very easy to integrate. If you look at our GitHub page, we have a small script that we are using to synchronize Git repositories with Zanata at the moment. It's on an early stage at the moment, and it's only a temporary solution as we are working on bringing a more robust solution to this requirement. * Hooks for CI infrastructure Not sure what you mean here. * Management workflows that fit OpenStack process We'll have to take a look at what those are. * Self-hosted We currently have a public instance available to everyone at http://zanata.org, but you are always welcome to donwload Zanata and start it up on your own infrastructure. * Proven success with large projects Zanata is currently used to translate projects like JBoss AS, RHEL, RHEVM, Ovirt, and countless other large projects. * API to gather statistics about translators Not yet. Zanata has the information, but it is just not exposed at the moment. * Easily see the translating context, i.g. the paragraph or section that contains the translation string. * Cross-project glossary and dictionary Zanata supports a global glossary, but not a dictionary. Let me know if you guys have any other questions. Regards, -- Carlos A. Munoz Software Engineering Supervisor Engineering - Internationalization Red Hat

1 0

Pootle test server
by jeblair＠openstack.org 17 Oct '13

17 Oct '13

Hi, In Hong Kong there will be a design summit session to discuss translation tools: http://summit.openstack.org/cfp/details/169 >From our last round of evaluating tools, Pootle was a close second to Transifex: https://docs.google.com/spreadsheet/ccc?key=0Aqevw3Q-ErDUdFgzT3VNVXQxd095bF… To help make the design summit more productive, I have set up a simple test Pootle server so that we can examine it and answer any questions we might have before the design summit. You can log into the test server here: http://translate-dev.openstack.org/ I have done very little configuration of the system, I just wanted to get something up quickly for people to look at. I have imported nova, horizon, and openstack_dashboard as projects. Note that if you look at nova, the number of translated strings Pootle reports is less than transifex -- that's because Pootle has marked all of the fuzzy-matched strings as "needs work", and strings that "need work" don't count as being fully translated. One thing that I believed has changed since the last time we looked at Pootle is translation memory. Here are the current docs: http://docs.translatehouse.org/projects/pootle/en/latest/features/translati… Since that describes how it uses an external translation memory populated with open source software by default, I believe that also means that Pootle's performance in the "crowdsource" category may have improved as well. I'm also optimistic about the integration with Git. Here's the documentation: http://docs.translatehouse.org/projects/pootle/en/latest/features/version_c… It looks like we may have options for getting nice git commits out of this; it says a typical git commit message looks like this: Commit from GNOME Pootle by user Sipho. 80 of 100 messages translated (7 fuzzy). Also, from what I've seen, it should not be very difficult to integrate Pootle into the project infrastructure -- the deployment is fairly simple. Keep in mind this isn't a fully-formed proposal for a new system -- just a test server running a basic configuration so we can look into it and discuss it more at the Summit. Please feel free to log into the test server and play with it. After you log in, just let me know if you would like me to make your user an admin. -Jim

6 5

I18n team meeting tomorrow
by Ying Chun Guo 17 Oct '13

17 Oct '13

Hi, We will have I18n team meeting at 0000UTC on Thursday (October 17th) in IRC channel #openstack-meeting. The time, we use Asia/America friendly time. Welcome to join the meeting. In the past 1 month, We have finished the busy Horizon translation. We completed 12 languages translations. That's great achievements. We will use this meeting to discuss our next work items. I have the following items in mind, and feel free to add the items in your mind too. * Evaluation of other possible translation tools * Discuss I18n policies to messages * Discuss translation timelines in a release cycle Let's meet tomorrow. Best regards Daisy

2 1