- OpenStack-I18n - lists.openstack.org

Bugs in I18n areas
by Ying Chun Guo 27 Nov '13

27 Nov '13

Hi, team I reported some I18n bugs to Horizon. I also associated these bugs with openstack-i18n in Launchpad. If you are interested in bug fix, please take a look at: https://bugs.launchpad.net/openstack-i18n. Thanks. Regards Ying Chun Guo (Daisy)

3 2

Havana - Horizon translations update
by Julie Pichon 25 Nov '13

25 Nov '13

Hi all, I was reading Daisy's summary of the Summit's i18n events - lots of great stuff happening, that is awesome! :) I would like to clarify the current status of the Transifex repository, and next translation update. I think it would be awesome to get another translation update in 2013.2.1 (first Havana stable update, planned in early December [0]), to include improved translations and maybe even new languages who may have missed the first deadline. My understanding was that we stopped updating the strings in Transifex from master around Havana RC3, to avoid the Icehouse strings sneaking in. Is this correct? Are we still tracking the Havana strings in Transifex? Kind regards, Julie [0] https://wiki.openstack.org/wiki/StableBranchRelease#Planned_stable.2Fhavana…

5 10

Translation check site (automatic Tx import is now resumed)
by Akihiro Motoki 24 Nov '13

24 Nov '13

Hi all, As we discussed in the last IRC meeting, I just resumed automatic translation import on the translation check site I am running. http://v157-7-133-23.myvps.jp:13580/ Username : demo / admin Password : opstjpHavana devstack with stable/havana release (today's latest) is running on the site. Translations are imported automatically from Transifex every hour. The list of available languages contains not only languages with Havana release but also languages with some translations on Transifex. If you don't see your language on the list, please let me know. Thanks, Akihiro

1 0

Results of the meeting with Transifex
by Stefano Maffulli 22 Nov '13

22 Nov '13

hello all, I met with Transifex CEO yesterday as a follow up to the i18n tools and processes session in Hong Kong. As we agreed, I let them know that we're not happy with their decision to stop developing the Open Source version of Transifex and that because of that we've decided to look into alternatives for the medium term. For the short term we're still going to use Transifex, therefore the meeting was to understand how we can get some features we need. Below are some notes from the meeting. I have put Daisy in touch with Dimitris so they can talk directly from now on. I'm waiting for Dimitris to send us an estimate of the costs for the enterprise features that the i18n team needs. We'll keep the conversation going once we get that proposal. Cheers, Stef Notes ----- - Openstack interested in Sharing Teams and Reports/Analytics on translations. - Transifex will have a member of its team to handle OpenStack questions. Questions from OpenStack team ----------------------------- - How are PO files merged when translated offline and online at the same time. Requested docs from Tx team. Dimitris notes that with time more and more translators will work online. - In-context for docs: Need a way to see the text with the images for QA. Transifex is working on new technologies which will fully support this. - Managing multiple versions of a product. Dimitris shared 3 ways, best one was: Have one Project on Tx which is rolling release. When a maintenance version needs to be released, create a separate project temporarily. If the two projects share teams, TM, Glossary and have "Auto-fill 100% matches from Translation Memory" it will work great. Drawing: https://www.dropbox.com/s/lyjulmut1qtr5n6/IMG_20131121_123037.JPG - Add support to login via OpenID: Doable. -- Ask and answer questions on https://ask.openstack.org

2 1

RFC: [Horizon translation] string "%(action)s %(data_type)s"
by Akihiro Motoki 20 Nov '13

20 Nov '13

Hi Horizon translators, I have a plan to make a small fix in Horizon strings in upstream code and if possible backport to Havana. Don't you have difficulties when translating a string "%(action)s %(data_type)s" in Horizon? It is used in two places: - to generate "action name" in the table (e.g. "Delete Network" in the pull-down menu and "Confirm Delete Network") - to generate "success message" (e.g. "Deleted Network: net2" in a success message pop-up) In Japanese we would like to use different translated strings for these strings (they are called "present" and "past" message respectively). Otherwise we can't get natural strings in translations. gettext has a mechanism called "message context", which allows us to translate a same string in different contexts. I have a plan to add a context to this string and allow us to use different translated words for the string. Once my fix is merged, we have the following entries in the PO file. The entries will become fuzzy, but we can reuse the existing translations so I believe the impact is small and we can get a benefit. Thought? Before proposing a patch, I would like to know feedbacks from I18N community. ---- #: tables/actions.py:562 #, python-format msgctxt "past" msgid "%(action)s %(data_type)s" msgstr "" #: tables/actions.py:564 #, python-format msgctxt "present" msgid "%(action)s %(data_type)s" msgstr "" --- Thanks, Akihiro Motoki <amotoki(a)gmail.com> / <motoki(a)da.jp.nec.com>

3 3

I18n team meeting tomorrow
by Ying Chun Guo 20 Nov '13

20 Nov '13

Hi, all There will be OpenStack I18n team meeting at 0000UTC on Thursday (Nov 21th) in IRC channel #openstack-meeting. The time, we use Asia/America friendly time. Welcome to join the meeting. This is the first I18n meeting after Icehouse design summit. Summarize of the design summit in I18n areas can be found here: http://lists.openstack.org/pipermail/openstack-i18n/2013-November/000294.ht…. This time, we will cover following topics this time: * Horizon translation update * I18n team structure discussion * Reorganize wiki page * Blueprints & bugs tracking * Plans in Icehouse cycle * Open discussion For more details, please look into https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting. You can also contact us through IRC channel #openstack-translation, or mailing address: openstack-i18n(a)list.openstack.org. Please refer to our wiki page for more details in the I18n area: https://wiki.openstack.org/wiki/I18nTeam Regards Ying Chun Guo (Daisy)

1 0

What's up and what's next? I18n team
by Ying Chun Guo 18 Nov '13

18 Nov '13

Hi, all The openstack summit was held last week. There were 4 sessions in total related with OpenStack I18n. I had chances to discuss with Doc team, Oslo team, Infra team and release management team about I18n tools and processes. I got very positive results. It turns out that leaders in OpenStack community think I18n as a very important area ( which is great ). I summarize what happened in the summit here. 1. Publishing translated documentation (https://etherpad.openstack.org/p/icehouse-doc-translation) The translated document publish process was discussed in this session. The decision was to have two servers to publish translated documents: official server and staging server. The official server will be used to publish the well translated documents. Staging server will be used to host the ongoing translated documents, which will help the review process. 2. Translation tools and scripts (https://etherpad.openstack.org/p/icehouse-summit-translation-tools-and-scri…) This discussion was held to decide whether we went away from Transifex (because of some well known reasons, if you don't know, please contact me) and moved to another translation platform. After comparing with several famous translation platforms, we figured out Transifex was the best one till now. As Transifex won't trun off in a short time, we will continue to use Transifex. At the same time, we will contact Transifex as well as other translation tool communities, to raise the feature requirements and see how they can satisfy us. Then we make decision in several months. 3. I18n policies of messages (https://etherpad.openstack.org/p/icehouse-oslo-i18n-policies) This session was to discuss the messages translation policies. The result was to separate messages ( log messages, API response messages, and etc ) into different po files, and let translation teams/coordinators to decide the translation priorities. Another result was to introduce message IDs to log messages, which will enable searching and bug diagnosis if log messages are not in English. (It's a great change from the software architecture view.) 4. Icehouse release schedule & coordination I had chance to explain our translation process with "big guys" in Openstack community. This session is more related with messages translation than documents translation. In a release cycle, message translations will be continuously imported into git repository. At last, the translation teams can decide which languages should be shipped with release. (None translation team supported languages will be removed.) Havana was called a conclusion, and Icehouse was just kicked off. We shall also make our plans in this release cycle. I have the following items in my mind: 1. Publish Japanese operation guide in the website. Operation guide in other languages are welcomed too. For translation teams, if you have plans to translate, please let me know. We can figure out a reasonable plan for the translation work. 2. Re-organize the I18n wiki page. Clearly list our team structure. I plan to use "I18n team" and "L10n teams" to manage. I18n team will be responsible for OpenStack I18n, which means to help OpenStack to become a software that can be localized. I18n includes setting up translation process, changing code infrastructure, and so on. L10n teams will be responsible for OpenStack L10n, including translation and localization. People can join both I18n team and his/her L10n team. People can join only 1 team also. The wiki page shall list clearly these information. Here are good samples: https://l10n.gnome.org/teams/ and http://loco.ubuntu.com/teams/. 3. Use Launchpad to manage bugs and blueprints. Find a way to track the contributors. If we are not able to track them automatically, let's track them manually. Coordinators please help to track the contributors to your language translations. At least, remember and display their names. 4. Enable translation function in MediaWiki If we want to translate wiki page, we will use the translation function in MediaWiki itself to manage. 5. Separate log messages into different po files & enable messages IDs This work may need more developers to join. 6. Contact with Transifex, Pootle, Zanata, TranslationWiki to raise feature requirements. 7. Set up staging server for translated document review. 8. Continue translations in documents and messages. Surely I'm not able to do all these works myself and I need all kinds of help. If you are suggests/comments to these items, please speak out. If you are interested in some, please sign up. Let's start the discussion in the mailing list. We missed 1 IRC meeting because of the summit. We will have next IRC meeting next week on Nov 21th. At that time, hope we can have a clear plan at that time. Regards Ying Chun Guo (Daisy)

5 5

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 03 Nov '13

03 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 30 Oct '13

30 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 28 Oct '13

28 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

Re: [Openstack-i18n] [openstack-dev] [oslo] i18n Message improvements
by Łukasz Jernaś 16 Oct '13

16 Oct '13

On Wed, Oct 16, 2013 at 12:40 AM, Mathew R Odden <mrodden(a)us.ibm.com> wrote: > As requested in the last Oslo meeting, I created a blueprint for further > discussion on the i18n work in Icehouse here: > > https://blueprints.launchpad.net/oslo/+spec/i18n-messages > > There were some ideas from the meeting that I'm sure I wasn't quite fully > understanding, so please take a look and let me know if there is any > feedback. Hi, If I may include my 0.02€. I'm still trying to wrap my head around the need for translating API messages and log messages as IMHO it adds a lot more problems for app developers and log analysis tools, eg. a log analysis tool would be usable only for the locale it was developed for and break with _every_ update of the translations. As a translator myself I don't really want to check every system in existence if it uses my messages to do some sort analysis and often change the strings to more proper form in my language as reviews and feedback on the translation comes in - even though the original English string doesn't change at all. I feel that translating mostly computer facing stuff is just crying for bugs, weird issues popping up for users, API-s should be readable by humans, but translating them is a bit too far in my opinion. If I get it right the Message objects are supposed to move stuff around internally in a C/en locale, but we will still end up dropping translated messages to computers if the don't explicitly specify the locale which the request should use... Regards, -- Łukasz [DeeJay1] Jernaś P.S. Of course I may be wrong with all of that ;)

1 0

Fwd: [openstack-dev] [oslo] i18n Message improvements
by Tom Fifield 16 Oct '13

16 Oct '13

-------- Original Message -------- Subject: [openstack-dev] [oslo] i18n Message improvements Date: Tue, 15 Oct 2013 17:40:56 -0500 From: Mathew R Odden <mrodden(a)us.ibm.com> Reply-To: OpenStack Development Mailing List <openstack-dev(a)lists.openstack.org> To: OpenStack Development Mailing List <openstack-dev(a)lists.openstack.org> As requested in the last Oslo meeting, I created a blueprint for further discussion on the i18n work in Icehouse here: _https://blueprints.launchpad.net/oslo/+spec/i18n-messages_ There were some ideas from the meeting that I'm sure I wasn't quite fully understanding, so please take a look and let me know if there is any feedback. Also, just to try to recap the discussion and try to state where *I think* we want to head with i18n/Messages, this is where I think we want to go in Icehouse. Make Message objects in oslo less magical by removing a lot of the magic string methods/operators from the class. This doesn't necessarily mean removing all of the "magic" operators (I think __mod__ is still necessary, as pointed out in the whiteboard of the blueprint.) I think some of the functionality is useful to developers when dealing with Messages and strings (unicode strings only hopefully.) The overall shift in direction should be to make projects more aware of the Message objects, and we need to change those to utilize them better instead of trying to make Messages work in all project cases. This was one of the biggest challenges of how it works today; trying to make a Message into a "string". Changing projects to expect/use Messages instead of strings/unicode is necessary if our goal is to make Messages less magical. Some of the changes that need to be done to realize this are outlined in the blueprint, but the big ones are: - needing a better defined public API for messages like the translate() function - needing to utilize unicode (more likely six.text_type) in all areas in OpenStack projects instead of strings (although we should be trying to do this already) - catch any Messages and resolve to unicode before they exit any OpenStack code Any feedback on the blueprint or ML would be appreciated. Thanks, Mathew Odden, Software Developer IBM STG OpenStack Development

1 0

Fw: [Openstack-translation] Free pass to OpenStack HongKong Summit
by Ying Chun Guo 12 Oct '13

12 Oct '13

Hi, team The free passes are still available. If translators from your team or yourself would like to join the HongKong summit in Nov, Please send me email. Hope to see more I18n people in the summit. (feel free to forward below email to your translation team) Thanks and regards Ying Chun Guo (Daisy) ----- Forwarded by Ying Chun Guo/China/IBM on 2013/10/12 14:28 ----- "Openstack-translation" <openstack-translation-bounces +guoyingc=cn.ibm.com(a)lists.launchpad.net> wrote on 2013/06/18 16:22:10: > Ying Chun Guo/China/IBM@IBMCN > Sent by: "Openstack-translation" <openstack-translation-bounces > +guoyingc=cn.ibm.com(a)lists.launchpad.net> > > 2013/06/18 16:22 > > To > > openstack-translation(a)lists.launchpad.net, > > cc > > Subject > > [Openstack-translation] Free pass to OpenStack HongKong Summit > > Hi, team > > The OpenStack Summit will be held in HongKong in Nov, 2013. All > active technical contributors can get a free registration code to > the summit. I think, translations are another kind of contribution > and should be recognized. But since the translations in the code > repository that are not marked with our names, some of you might not > receive emails with registration codes. I talked with the community > manager - Tom Fifield about this. Now the community agreed to give > us free registration code by a special process. > > If you and people in your translation team don't have the free > registration code but want to attend the summit, please let me know > the Transifex registration email and ID. I will get the free pass for you. > > To get more information about the summit, please refer to http:// > openstacksummitnovember2013.eventbrite.com/. > > Regards > Ying Chun Guo (Daisy)-- > Mailing list: https://launchpad.net/~openstack-translation > Post to : openstack-translation(a)lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack-translation > More help : https://help.launchpad.net/ListHelp

2 2

Regarding OpenStack Manuals
by Tom Fifield 11 Oct '13

11 Oct '13

Hi, Just to let you know, I have just marked the following books to no longer accept translations: openstack-api-programming openstack-block-storage-admin openstack-compute-admin openstack-network-connectivity-admin openstack-object-storage-admin These books have been restructured during the Havana release. A lot of the content is the same, so we can keep them for translation memory - don't worry about any lost work! :) Will need to make some new "resources" in transifex. Regards, Tom

1 1

Patch proposed to import translations for Havana
by Akihiro Motoki 10 Oct '13

10 Oct '13

Hi I18N team, I just proposed a patch to import Horizon translations for Havana. https://review.openstack.org/#/c/50698/ Please check it if your languages is included. If you find some issues, please let us know or add a comment on gerrit. On The I18N check site by Japanese team, Horizon with the proposed patch is available. You can check it here using a live Horizon. http://v157-7-133-23.myvps.jp:13580/ Username : demo or admin Password: opstjpHavana Cheers! Akihiro MOTOKI <amotoki(a)gmail.com>

3 2

Horizon translation status update for Havana
by Akihiro Motoki 09 Oct '13

09 Oct '13

Hi all, Thanks for your translation effort for Havana RC1 release. RC1 release starts and Horizon RC1 is coming soon. It contains translations of ~100% translated languages. I really appreciate your work!! == Extra translation request == Horizon made several number of fixes in RC1 phase and there are several changes in translation strings. I just synced POT files with the latest Horizon master repository and pushed them to Transifex. == Schedule for Havana Horizon RC2 (not determined yet) == I will request another Release Candidate (RC2) to import translations. The exact plan will be discussed with Gabriel, Horizon PTL from now. My current plan is to import translation updates at the middle next week. I will let you all know if there is an update. Thanks, Akihiro MOTOKI <amotoki(a)gmail.com>

7 20

Action item: Transifex statistics API
by Gabriel Wainer 08 Oct '13

08 Oct '13

Hi All, Unfortunately I won't be able to participate in the next meeting, due to timezone it will be 4 AM here. Anyway, from the last meeting, I have the following item: ACTION: gabrielcw to take a look at Transifex API to see if it's able to get the translators information. I searched the API docs and as Daisy and Katomo mentioned in the last meeting, there's the API to retrieve some information for projects, but not yet for translators work. http://help.transifex.com/features/api/#statistics So I asked their help desk about what we want, and happily they will soon be rolling out support for that: http://support.transifex.com/customer/portal/questions/1326867-translators-… In fact, by the answer it should be already available but is not. I will keep an eye on that, and let you know! Hope that helps, Regards, Gabriel.

2 3

Introducing Reports in Transifex
by Gabriel Wainer 08 Oct '13

08 Oct '13

Hi all, This new feature may be helpful to gather some statistics. Not exactly what we need. Just a heads up. http://bit.ly/1bRR7hf Thanks, Gabriel.

1 0

No meeting next Thursday
by Ying Chun Guo 29 Sep '13

29 Sep '13

Hi, team I will start my vacation today and be back to office on Oct. 8th. So I'm going to cancel the meeting on Oct. 3th (next Thursday). We can discuss through email for any topics, like the Havana release, the log message I18n policy, the coming design summit, and etc. We will meet on Oct. 17th on 0000 UTC then. Hope to talk to you there. Regards Ying Chun Guo (Daisy)

1 0

Log messages translation
by Gabriel Wainer 29 Sep '13

29 Sep '13

I saw this in another post, so to avoid confusion I'll ask here. How can we know what are log messages and what aren't in the translation strings? I ended up translating all messages, even logs I believe. Sure that some technical words and var names should be copied but i think it's ok to translate logs. Any guidelines on that? Thanks, Gabriel Wainer

4 6

How to use partially completed languages for devstack horizon?
by Tom Fifield 29 Sep '13

29 Sep '13

Hi i18n, I'm potentially giving a dashboard demo in Moscow next week, and thought it would be cool if I could change the language settings to use our almost-complete Russian translation. Does anyone have some easy steps I can follow to download the PO file from transifex and then configure devstack to use it? Regards, Tom

3 9

String changes in master
by Łukasz Jernaś 27 Sep '13

27 Sep '13

Hi! I've noticed string changes in master introduced in commit 21eaa8fa58d635c62f531c66c6c831fe7fbcdbb6 I've created a bug https://bugs.launchpad.net/horizon/+bug/1229749 and posted a review request with updated strings: https://review.openstack.org/#/c/48056/ Someone please take a look at it. Regards, -- Łukasz [DeeJay1] Jernaś

3 4

Vote results - translation importing policy
by Ying Chun Guo 27 Sep '13

27 Sep '13

Hi, I got 13 answers for this vote. ( I'm very happy to see so many active people in this mailing list. That's great. ) Here is the result: 1. importing policy Vote results: 5a | 3b | 9c | 1d 2. Whether to keep the old translations in Horizon Vote results: 4a | 6b | 2c (language coordinator decided) So the final answer to these 2 questions are: 1. language coordinator decided 2. No @ Coordinators of completed translation teams: If you are NOT comfortable to import the translations of your language in Havanna RC1, please let us know. @ Coordinators of other translation teams: If you want to import your translations in RC1, please let us know. I see the translations of Spanish and Russian are very active. If you are not comfortable to import your translations in RC1, you still have chance to import them in RC2 and the final release. Please let us know your decision as soon as possible, so that Akihiro Motoki can start the importing. Thank you for your hard work! ---vote answers--- 1. importing policy c - language coordinator decided d - All b - 90% translated. a/c - 100% translated, or language coordinator decided (maybe not 100%) b - only if 90% translated is possible, otherwise A a/c - 100% translated, or language coordinator decided (maybe not 100%) c - language coordinator decided c - language co-ordinator decided a/b/c - but if around 95-100%, coordinator decided. c - Language coordinator decided a/c - 100% translated or coordinator decided (or active translator if no coordinator) a - I think 100 %translated should be our goal c - language coordinator decided 2. Whether to keep the old translations in Horizon b – No a - Older versions of translations if in the past had become part of any release should be kept. a - But 100% translated. If Long term support version, All keep. :) c - If no language coodinator b> No, else language coordinator decided a - c - If no language coordinator b> No, else language coordinator decided a - if no coordinator, else language coordinator decided b - b - b - "Yes" in general, but **NO** for Havana. b - b - No if there is such a technical reason as Akihiro mentioned. ------------ Regards Ying Chun Guo (Daisy) > Ying Chun Guo/China/IBM > 2013/09/25 17:03 > > To > > openstack-i18n(a)lists.openstack.org, > > cc > > Subject > > Call for vote: translation importing policy > > Hi, team > > We are just before the translation importing, and we haven't gotten > a consensus to the importing policy. > Let's do a vote then. > The vote will be opened for 24 hours. > I only open this vote to i18n mail list yet. > But I will publish the vote results to public mail list and ask for comments. > The result of this vote will be used for Havanna RC1. > If we got strong opposition from the public mail list, > we still have chance to change it in Havanna RC2 and Havanna offical release. > > Please let us know your opinion. > > ------------------------------------------------- > 1. Which importing policy do you choose? (the policy to be used to > import translations from Transifex to Horizon ) > > a> 100% translated > b> 50% translated, ( or you can specify another percentage number ) > c> language coordinator decided > d> All languages in Transifex > e> others ____________ > > 2. Whether to keep the old translations in Horizon? > (There are some old translation po/mo files in Horizon. > They are old version. Most of them are not completed. ) > > a> Yes > b> No > > Regards > Ying Chun Guo (Daisy)

3 3

Call for vote: translation importing policy
by Ying Chun Guo 26 Sep '13

26 Sep '13

Hi, team We are just before the translation importing, and we haven't gotten a consensus to the importing policy. Let's do a vote then. The vote will be opened for 24 hours. I only open this vote to i18n mail list yet. But I will publish the vote results to public mail list and ask for comments. The result of this vote will be used for Havanna RC1. If we got strong opposition from the public mail list, we still have chance to change it in Havanna RC2 and Havanna offical release. Please let us know your opinion. ------------------------------------------------- 1. Which importing policy do you choose? (the policy to be used to import translations from Transifex to Horizon ) a> 100% translated b> 50% translated, ( or you can specify another percentage number ) c> language coordinator decided d> All languages in Transifex e> others ____________ 2. Whether to keep the old translations in Horizon? (There are some old translation po/mo files in Horizon. They are old version. Most of them are not completed. ) a> Yes b> No Regards Ying Chun Guo (Daisy)

11 15

(no subject)
by Danilo Ingami 25 Sep '13

25 Sep '13

Sent from mobile

1 0

final push before Havanna RC1
by Ying Chun Guo 24 Sep '13

24 Sep '13

Hi, team With the hard work of translation team, we have 100% finished 6 languages translations. They are: Chinese, Japanese, Korean, Polish, English (Australia) and English (United Kingdom). Portuguese (Brazil) and French translations are finished 98% and 99%, almost reach the goal now. If you have time, please do a final check through the Horizon test website. Akihiro Motoki will import our translations to Horizon in these two days. Then we can broadcast our result to the whole openstack community with much proud! Thank you all for your hard work ! Regards Ying Chun Guo (Daisy)

3 2

Fwd: Horizon translation importing policy for Havana RC1
by Parag N(पराग़) 24 Sep '13

24 Sep '13

Hi, Looks like my initial reply was missed to mailing list hence forwarding this to list. ---------- Forwarded message ---------- Hi all, I am totally new to this Openstack project but would like to provide my opinion. On Mon, Sep 23, 2013 at 12:07 PM, Akihiro Motoki <amotoki(a)gmail.com> wrote: > Hi all, > > We discussed the criteria of importing Horizon translation for Havana RC1 > and agreed that we will import only 100% translations at the last I18N > meeting. > > I have several questions to clarify. > What do you think? I would like to know opinions from I18N team? > > (1) What is 100% translated? > Does 100% mean that all **three** resources (Horizon, Horizon > JavaScript, > OpenStack Dashboard) are completed? > I think any project when get 100% translated status for all their po files in it, one can say that language is 100% supported. > (2) Do we remove translations not completed (<100%) from Horizon repo? > RC1 release is created from the repo. This means that if we don't > remove > them non-completed translations will be shipped in RC1. > I don't thing we should ignore the efforts of language translators by not including partial translations. At least I see that can be a start for localized user to get familiar with those translated strings in UI. But yes assessing the translation quality is a different topic here. > > (3) What should the language list of the user preference form be? > I believe the default language list is important. > - All 100% translated languages should be listed. > Some languages needs to be added. > - Non 100% translated languages should be removed or listed? > If so what is the criteria? Over 50% on Transifex? > Let all languages be listed there. If decision need to be taken for removal of partial translated languages then better remove all and have only 100% translated languages else list all. Regards, Parag Nemade

1 0

Horizon translation importing policy for Havana RC1
by Akihiro Motoki 24 Sep '13

24 Sep '13

Hi all, We discussed the criteria of importing Horizon translation for Havana RC1 and agreed that we will import only 100% translations at the last I18N meeting. I have several questions to clarify. What do you think? I would like to know opinions from I18N team? (1) What is 100% translated? Does 100% mean that all **three** resources (Horizon, Horizon JavaScript, OpenStack Dashboard) are completed? (2) Do we remove translations not completed (<100%) from Horizon repo? RC1 release is created from the repo. This means that if we don't remove them non-completed translations will be shipped in RC1. (3) What should the language list of the user preference form be? I believe the default language list is important. - All 100% translated languages should be listed. Some languages needs to be added. - Non 100% translated languages should be removed or listed? If so what is the criteria? Over 50% on Transifex? I would like to take care of importing translation into Horizon repo as a Horizon core member. Thanks, Akihiro Motoki <amotoki(a)gmail.com>

3 4

Log messages and translations
by Łukasz Jernaś 23 Sep '13

23 Sep '13

Hi, What's the policy on translating log messages in OpenStack? Especially the case of api/neutron.py (tried to find something on the wiki, but I may be wrong) IMHO they shouldn't be marked as translatable as usually that breaks stuff working on them and the general standard I've found on most of the projects that they aren't translated... Regards, -- Łukasz [DeeJay1] Jernaś

1 0

Re: [Openstack-i18n] Horizon (arabic translation)
by kamélia BENCHEKROUN 21 Sep '13

21 Sep '13

Hi, Thank you for replying. Actually, my problem is that we write Arabic from right to left, and I don't know How I should translate sentences like: Unable to modify domain "%s". I have 2 possibilities: 1/ "s%" لا يمكن تعديل النطاق (accepted by transifex) 2/ "%s" لا يمكن تعديل النطاق (got error with transifex) I think that the second solution will work, but I need to test before going ahead with the translation. Regards, Kamélia. 2013/9/16 Tom Fifield <tom(a)openstack.org> > Hi, > > Thanks for the excellent question. > > Shall we perhaps take this discussion to the > OpenStack-Internationalisation mailing list: > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > ? I think it would be more appropriate there. > > Regards, > > > Tom > > On 15/09/13 19:02, kamélia BENCHEKROUN wrote: > > Hi, > > > > I have a question about translating some sentences like: > > *ALLOW* %(from)s:%(to)s *from* %(group)s > > How should we translate them ? > > > > Regards, > > Kamélia. > > > > > > 2013/9/13 Yelu <yeluaiesec(a)gmail.com <mailto:yeluaiesec@gmail.com>> > > > > thank you Daisy~ > > we will work on it > > > > > > On Fri, Sep 13, 2013 at 2:14 PM, Ying Chun Guo <guoyingc(a)cn.ibm.com > > <mailto:guoyingc@cn.ibm.com>> wrote: > > > > Thank you, Yelu. > > I think we need people to review the translations too. > > Run Dashboard in Chinese will be an easy way to find out the > > inappropriate translation. > > Here is a guideline: > > > https://github.com/OpenStack-I18n/Translation/wiki/HorizonI18nTest > > > > Regards > > Ying Chun Guo (Daisy) > > > > Yelu <yeluaiesec(a)gmail.com <mailto:yeluaiesec@gmail.com>> wrote > > on 2013/09/13 13:41:27: > > > > > Yelu <yeluaiesec(a)gmail.com <mailto:yeluaiesec@gmail.com>> > > > 2013/09/13 13:41 > > > > > > To > > > > > > Shinobu Kinjo <shinobu.kinjo(a)oist.jp > > <mailto:shinobu.kinjo@oist.jp>>, > > > > > > cc > > > > > > OpenStack Mailing List <openstack(a)lists.openstack.org > > <mailto:openstack@lists.openstack.org>>, > > > "community(a)lists.openstack.org > > <mailto:community@lists.openstack.org>" > > <community(a)lists.openstack.org > > <mailto:community@lists.openstack.org>> > > > > > > Subject > > > > > > Re: [Openstack] Translation Push - get the dashboard in your > > > language by Sep 24 > > > > > > > > > > hey Tom, > > > > > > Chinese version is 100% done, now it's under review > > > > > > I think it's gonna be a great way have a call on local SNS, in > > > China, I post a weibo > > > http://weibo.com/2153224205/A9fSFFNxh > > > and the efficiency shocked me! > > > > > > and I will follow up the other translation work also. > > > > > > > > On Fri, Sep 13, 2013 at 8:17 AM, Shinobu Kinjo > > <shinobu.kinjo(a)oist.jp <mailto:shinobu.kinjo@oist.jp>> wrote: > > > Tom, > > > > > > I can be Japanese translator. > > > How can I join? > > > > > > -- Kinjo > > > > > > ---- > > > O I S T > > > Okinawa Institute of Science and Technology Graduate School > > > 1919-1 Tancha, Onna-son, Kunigami-gun > > > Okinawa, Japan 904-0495 > > > T: +81-98-966-2093 <tel:%2B81-98-966-2093> > > > M: +81-80-6800-6447 <tel:%2B81-80-6800-6447> > > > shinobu.kinjo(a)oist.jp <mailto:shinobu.kinjo@oist.jp> > > > www.oist.jp <http://www.oist.jp> > > > > > > ________________________________________ > > > From: Tom Fifield [tom(a)openstack.org <mailto:tom@openstack.org > >] > > > Sent: Thursday, September 12, 2013 17:16 > > > To: OpenStack Mailing List; community(a)lists.openstack.org > > <mailto:community@lists.openstack.org> > > > Subject: [Openstack] Translation Push - get the dashboard in > your > > > language by Sep 24 > > > > > > Do you write Spanish, Italian, Russian, German or Dutch? > > > > > > How about Portuguese? Indonesian? Arabic? Hindi? > > > > > > Actually, if you can write in any language other than English, > > you have > > > the ability to help get the OpenStack Dashboard into your > > language. > > > > > > Find your language on: > > > > > > https://www.transifex.com/projects/p/horizon/ > > > > > > and join the team. > > > > > > > > > It's actually a lot of fun, all done through an easy web > > interface. > > > > > > If we can get 100% completion in your language by September > > 24th, your > > > text will be included in the next release of OpenStack for > > thousands > > > around the world to see. > > > > > > So, why not get your friends together and make it happen? :) > > > > > > > > > Thanks, > > > > > > from your friendly Internationalisation Team > > > https://wiki.openstack.org/wiki/I18nTeam > > > > > > _______________________________________________ > > > Mailing list: > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > > Post to : openstack(a)lists.openstack.org > > <mailto:openstack@lists.openstack.org> > > > Unsubscribe : > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > > > > > _______________________________________________ > > > Mailing list: > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > > Post to : openstack(a)lists.openstack.org > > <mailto:openstack@lists.openstack.org> > > > Unsubscribe : > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > > _______________________________________________ > > > Mailing list: > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > > Post to : openstack(a)lists.openstack.org > > <mailto:openstack@lists.openstack.org> > > > Unsubscribe : > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > > > > > > > _______________________________________________ > > Community mailing list > > Community(a)lists.openstack.org <mailto:Community@lists.openstack.org> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/community > > > > > > > > > > -- > > Kamélia. > > > > > > _______________________________________________ > > Community mailing list > > Community(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/community > > > > -- Kamélia.

2 3

Horizon test website
by Ying Chun Guo 20 Sep '13

20 Sep '13

Hi, Akihiro Motoki has a live Horizon test website to check the translation strings. You can use it to verify your translations without installing your own Horizon. 1. Go to website: http://v157-7-133-23.myvps.jp:13580/ 2. Log in as: demo, password is "opstjpHavana" 3. Click "Setting" in the right top corner, and choose your own language. Then you can see the translated strings in your language are displayed. You can verify them. Enjoy your translation results! Many thanks for Akihiro Motoki! Ying Chun Guo (Daisy)

5 7

Strange source string on Transifex
by Akihiro Motoki 18 Sep '13

18 Sep '13

Hi all, I experienced a strange problem in Horizon translation on Transifex. "Horizon translations" has a string "Select a period of time to query its usage" in horizon/locale/en/LC_MESSAGES/django.po. However I can't see the string and instead I see "Select a month of time to query its usage". The screenshot is here: http://i.imgur.com/pk1KNpA.png Does anyone see the same thing? (1) Open https://www.transifex.com/projects/p/horizon/ (2) Visit your language (3) Goto "Horizon - Horizon Translations" (4) Click the query form at upper left -> Specify "text: select" I am not sure what is the reason. One point I am afraid of is that English PO file in Horizon repository has the following (fuzzy) entry. It may cause this issue. Thanks, Akihiro The following are extracted from Horizon latest repository. horizon/locale/en/LC_MESSAGES/django.po ----- #: templates/horizon/common/_usage_summary.html:5 #, fuzzy msgid "Select a period of time to query its usage" msgstr "Select a month to query its usage" ----- horizon/locale/en/LC_MESSAGES/django.po ----- #: templates/horizon/common/_usage_summary.html:5 msgid "Select a period of time to query its usage" msgstr "使用量を確認する月を選択してください" ----- -- Akihiro MOTOKI <amotoki(a)gmail.com>

4 6

I18n (translation) team meeting at 0000UTC this Thursday
by Ying Chun Guo 18 Sep '13

18 Sep '13

Hi, all We will have the I18n team meeting at 0000 UTC on Sep. 19th in the IRC channel #openstack-meeting. We will focus on the Horizon I18n in this meeting, and address below topics: Action items from the last meeting Horizon translation progress report The merging time and criteria of Horizon translations Design summit session proposals in I18n areas Open discussion We have made a good progress on Horizon I18n now. From the dashboard of Transifex, we can see 4 languages translations (Japanese, Simple Chinese, Portuguese (Brazil),English (Australia)) of Horizon are almost 100% completed, 5 languages translations (Korean, French, Polish, Spanish, and Traditional Chinese) are more than 50% completed. There are a big number of languages, e.g. Czech, Finnish, Spanish, Russian, Hungarian, and German, which have a good start now. We also ran the I18n test of Horizon and reported 12 bugs around I18n during the passed two weeks. Havana release will come soon. If we work together on a final sprint, we can make a good internationalized OpenStack Dashboard in this release. If you have interests or questions or problems around Horizon I18n, welcome to join the meeting. If the time is not appropriate for you, welcome to join the mailing list: openstack-i18n(a)lists.openstack.org and discuss with I18n team. Our wiki is here: https://wiki.openstack.org/wiki/I18nTeam The Transifex website is here: https://www.transifex.com/projects/p/horizon/ Welcome to join. Regards Ying Chun Guo (Daisy)

1 0

IRC meeting this week
by Ying Chun Guo 17 Sep '13

17 Sep '13

Hi, I'm going to address below topics in the IRC meeting this week. * Horizon translation progress report * Merging time and criteria * Design summit session proposals in I18n areas The meeting time should be 0100 UTC this Thursday. I wonder if we can move it 1 hour earlier this time, because I have a conflict this week. That is: UTC 0000 Beijing 0800 Tokyo 0900 Melbourne 1000 San Francisco 1700 Guayaquil 1900 New York 2000 Sao Paulo 2100 Paris 0200 Bangalore 0530 If you want to attend the meeting and the time is not appropriate for you, please let me know. Thanks and regards Ying Chun Guo (Daisy)

1 0

Horizon I18n update
by Ying Chun Guo 16 Sep '13

16 Sep '13

Hi, team The strings of Horizon in Transifex have been updated. A new resource "OpenStack Dashboard Authentication" is added which includes the strings in the login page. Although the string frozen day was passed, there may be string updates in the future. I will have you noticed when the strings are updated. Based on the wiki page "https://wiki.openstack.org/wiki/Havana_Release_Schedule", Sep 26th is OpenStack RC1 day. So we will make Sep 24 as our deadline of translation work. We will look into Transifex to see which languages are 100% translated and ready to be merged. And then hope we can finish the merge with the help of Horizon team in 2 days. Thus our translations will be released together with RC1. I hope to pick out at least two languages and do the Horizon I18n test, in order to verify the strings in web UI are correctly displayed as its translation. The I18n test should be done as early as possible, in order to save enough time for developers to fix bugs if we can find any. I have written down the guidelines for Horizon I18n test. https://github.com/OpenStack-I18n/Translation/wiki/Horizon-I18n-Test If you are interested in that, if you want to see how Horizon run in your own language, you can try. And, Don't forget to report bugs if you find any. Feel free to discuss within the mailing list if you meet with problems or have questions. Regards Ying Chun Guo (Daisy)

4 14

[OpenStack-i18n] Edit wiki 'How to'
by Sungjin Gang 15 Sep '13

15 Sep '13

Hi, :) I edit wiki… 'How to' https://wiki.openstack.org/wiki/I18nTeam#How_to sorry, late :(. Thanks, Sungjin :)

1 0

Horizon translation
by Ying Chun Guo 09 Sep '13

09 Sep '13

Hi, team After confirming with Horizon development team, the string frozen date is September 5th. We will set Horizon translation as the first priority work in September. In September, we will: 1. Finish Horizon translation 2. Run Horizon in your local environment to verify that all the strings in Web UI are translated and displayed correctly, which I will call TVT (Translation verification test) Now Horizon in Transifex[1] has synchronized with the code base on August 23th. Please try your best to work on the translation of Horizon. At the end, those languages that finish translation and TVT will be merged and delivered with Havana release. [1] https://www.transifex.com/projects/p/horizon/ Thanks and regards Ying Chun Guo (Daisy)

5 8

Reorganizing openstack-manuals and operations-guide repos
by Anne Gentle 08 Sep '13

08 Sep '13

Hi all, I wanted to ensure you're aware of a reorganization going on for the OpenStack documentation. The openstack-manuals and operations-guide repositories under the openstack organization in Github are going to be more consistent in the placement of the pom.xml file relative to the source files. https://review.openstack.org/#/c/45490 - contains the changes to openstack-infra/config necessary for these changes https://review.openstack.org/#/c/45517/ - contains the changes to openstack-manuals https://review.openstack.org/#/c/45487/ - contains the changes to operations-guide I apologize for any inconvenience this will cause and I ask for help updating any scripts that point to source docs in these repos. Please let me know if you have any questions. We hope to complete this work today. Thanks, Anne

1 0

Japanese ops publish process
by Ying Chun Guo 08 Sep '13

08 Sep '13

KATO Tomoyuki <tomo(a)dream.daynight.jp> wrote on 2013/09/02 21:19:49: > KATO Tomoyuki <tomo(a)dream.daynight.jp> > 2013/09/02 21:19 > > To > > Anne Gentle <annegentle(a)justwriteclick.com>, > > cc > > "openstack-docs(a)lists.openstack.org" <openstack-docs(a)lists.openstack.org> > > Subject > > Re: [Openstack-docs] ops guide japanese build fails due to split repositories > > > > Hi all, > > > > > > > "error while opening "./doc/src/docbkx/openstack-ops/locale/ja.po" for > > > > reading: No such file or directory" > > > > > > I requested to merge Japanese translation file "ja.po". > > > This file is the newest translation file from Transifex. > > > Please check it. > > > > > > https://review.openstack.org/44591 > > > > > > I really appreciate your persistence. > > > > Should this file have been automatically put in by the script itself? I've > > reviewed it and given a +2 but want to be sure I understand the process. > > I think this file should be put in after completing translation > review process. > This file had completed the review by Japanese team. > > I think it is important not to put in unreviewed strings. > As of now, I think there are two methods. > > 1. automatically, ONLY "reviewed" flaged strings from Transifex. > 2. manually, gerrit review process. > Can you explain more about these two methods? What are "automatically method" and "manually method"? > I think I18N team need to discuss the publish process more. > > -- > Thanks, > KATO Tomoyuki > > _______________________________________________ > Openstack-docs mailing list > Openstack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs >

2 1

I18n meeting tomorrow
by Ying Chun Guo 04 Sep '13

04 Sep '13

Hi, There will be OpenStack I18n team meeting at 0700UTC on Thursday (September 5th) in IRC channel #openstack-meeting. The time, we use Asia/Europe friendly time. Welcome to join the meeting. During the previous several weeks, we have good progress with the infrastructure setting up in Transifex. We have the common glossary shared within all openstack projects. We have Horizon ready for translations. Tomorrow is the string frozen date. Now it's the quite important time for translating now. We want to make sure Horizon can have the high quality internationalized release for Havanna version. If you are interested in translations or tools, welcome to join us. We will cover following topics this time: Action items from the last meeting Horizon I18n version release process Translated document publish process Open discussion For more details, please look into https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting. You can also contact us through IRC channel #openstack-translation, or mailing address: openstack-i18n(a)list.openstack.org. Please refer to our wiki page for more details: https://wiki.openstack.org/wiki/I18nTeam Best regards Daisy

2 3

Self introduction
by Łukasz Jernaś 04 Sep '13

04 Sep '13

Hello i18n list! My name is Łukasz Jernaś, also going by the nickname DeeJay1 (strip the 1 usually - and no, I don't actually do any music ;) In the past I've done some translations, mainly for the GNOME project, and also various bug fixes. I hope to get more Polish into OpenStack, currently focused on Horizon and the documentation. Have a nice day, -- Łukasz [DeeJay1] Jernaś

1 0

Glossary
by Ying Chun Guo 03 Sep '13

03 Sep '13

Hi, With the help from Tom Fifield, the source languages of openstack projects in Transifex have all been changed to "en". Now they share a same glossary: https://www.transifex.com/projects/p/openstack/glossary/l/en/. This glossary has been synchronized with glossary defined in website: http://docs.openstack.org/glossary/content/glossary.html Each language team can define the glossary before translation, to get the translation consistency. You can go to a certain project, click on the "view glossary", and select your language. Then you can define the translation of glossary in your own language. For example, the glossary of zh_CN can be edited by this url: https://www.transifex.com/projects/p/horizon/glossary/l/zh_CN/. Any problems or questions with glossary, please let me know. Regards Ying Chun Guo (Daisy)

2 1

new contributor
by Surit Aryal 02 Sep '13

02 Sep '13

Hi all, My name is Surit. I am a FOSS enthusiast from Nepal. I am currently involved with different FOSS related clubs and communities in Nepal. I wanted to start contributing for openstack too. I choosed localization for starting. I have requested a new language (nepali) here https://www.transifex.com/projects/p/openstack/ please approve. Thank you. Surit Aryal Nepal

2 4

no I18n meeting tomorrow
by Ying Chun Guo 28 Aug '13

28 Aug '13

Our next meeting will be held on Sep 5th (next Thursday) at 0700 UTC (Europe/Asia/India Friendly). Daisy

1 0

[savanna] impl i18n
by Sergey Lukjanov 26 Aug '13

26 Aug '13

Hi, I'm looking on how to implement i18n in Savanna project correctly. The first two docs that I read are https://wiki.openstack.org/wiki/Translations and https://wiki.openstack.org/wiki/I18NSupport The technical side of the impl seems to be clear - we need to use gettext, babel and wrap up all strings with _(…), but there are several questions about how to create translations and that's the reason I'm here. As I see you're using transifex to manage translations. It looks like common strings are shared between the projects in one organization using the "Translation Memory" feature and AFAIU it provides oslo translation for all projects. And the first question is could be Savanna added to the organization to get access to the oslo translations, i.e. is this organization only for the integrated projects, or related/incubated could be added too? Thank you! Sincerely yours, Sergey Lukjanov Savanna Technical Lead Mirantis Inc.

2 2

Meeting minutes today
by Ying Chun Guo 16 Aug '13

16 Aug '13

Hi, all We had the IRC meeting yesterday. I pick out some useful information we discussed and found out during the meeting. I'd like to share with all the team. You can go through this email in several minutes and understand what happened, other than looking at the long meeting message history. * Glossary in Transifex A user can create multiple glossaries and attach them to the projects he owns, as long as the project and the glossary share the same source language. The glossaries can be bootstrapped by uploading a CSV file. So if we want all the OpenStack projects to share one glossary, there are two preconditions: 1. There is a user in Transifex who owns all OpenStack projects 2. All OpenStack projects have the same source language. ( Now the source language of Cinder, Glance, Horizon, and Nova are en_US, the others are en. ) I will follow up with CI team to see how these two preconditions can be satisfied. * Japanese document website Akihiro MOTOKI wrote the main page of Japanese document website, and the web page is under reviewed by Japanese team. KATO Tomoyuki and Tom Fifield wrote the publish script: https://review.openstack.org/#/c/39846. The script is specific to Japanese version of "operation guide". Tom would like to make it simple this time. When the script works, we can try to enable parameter. Many thanks to Akihiro, KATO and Tom's work. * Translation priority and deadline The top priority work for the team are "operation guide" (following the priority set by doc team) and Horizion. As to documentation translation, there is no an overall deadline. I want each translation team to decide their own plan and deadline. When the document is ready, we can publish to website. As to Horizon translation, when the code strings are frozen, there should be a deadline before the product release. So when the code strings are frozen (Sep 4th), I hope each translation team can focus their time on the Horzion translation. Again, this is not mandatory. Which team can finish on the time, which translation can be merged in the product release. I will talk with Horizon team about our plan. Regards Ying Chun Guo (Daisy)

1 0

I18n's meeting tomorrow
by Ying Chun Guo 14 Aug '13

14 Aug '13

Hi, There will be OpenStack I18n team meeting at 0100UTC on Thursday (August 15th) in IRC channel #openstack-meeting. The time, we use Asia/America friendly time. Welcome to join the meeting. We will cover following topics this time: Action items from the last meeting Progress with Japanese doc site Glossary defined in Transifex Transifex requirements/bugs collection Open discussion For more details, please look into https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting. Again, if you are interested in I18n or OpenStack, welcome to join us. We need translators and developers too. Please contact us through IRC channel #openstack-translation, or mailing address: openstack-i18n(a)list.openstack.org. Please refer to our wiki page for more details: https://wiki.openstack.org/wiki/I18nTeam Best regards Daisy

1 0

OpenStack-manual version?
by Sungjin Gang 14 Aug '13

14 Aug '13

Hi, I know OpenStack-manual Version. Folsom? Grizzly? and more? Thanks. :) Sungjin Gang

2 2

The Transifex '%' problem
by Gabriel Wainer 12 Aug '13

12 Aug '13

Hello everyone, Recently I faced the '%' problem from Transifex described here. https://bugs.launchpad.net/openstack-manuals/+bug/1192091 This does looks like an issue in Transifex. Have anyone talked with the Transifex guys to ask if they are aware of that? I searched their issues but there isn't any about it. https://github.com/transifex/transifex/issues?labels=&page=1&state=open Thanks, Gabriel Wainer.

2 6

Fw: [OpenStack-doc] Add Korean fonts for 'coluddoc-maven-plugins'
by Ying Chun Guo 12 Aug '13

12 Aug '13

Hi, It seems that I have met with this problem before, but I cannot remember how I resolve it. It was a long time ago. @amotoki and KATO, have you met with this problem and how did you resolve it? Regards Ying Chun Guo (Daisy) ----- Forwarded by Ying Chun Guo/China/IBM on 2013/07/30 16:32 ----- Sungjin Gang <gang.sungjin(a)gmail.com> wrote on 2013/07/21 23:01:33: > Sungjin Gang <gang.sungjin(a)gmail.com> > 2013/07/21 23:01 > > To > > david.cramer(a)rackspace.com, > > cc > > Openstack-i18n <openstack-i18n(a)lists.openstack.org>, openstack- > docs(a)lists.openstack.org > > Subject > > [Openstack-i18n] [OpenStack-doc] Add Korean fonts for 'coluddoc-maven-plugins' > > Hi, David > > This is Sungjin Kang, a coordinator of OpenStack I18N Korean Team. > Could you help me out on the following problem? > > When creating a korean document using maven, all korean characters > are displayed as "#####". > > While I was looking for the possible solution, I found out that > Korean font might need to be added in "clouddoc-maven-plugins" you manages. > > If this is the case (adding korean font), I would like to add a > korean font called "Nanum fonts[1]" > > [1] http://en.wikipedia.org/wiki/Nanum_font > > I can prepare for the actual font file. However, I don't know what I > need to do to add korean font. > > Could you help me out on this? > > Thanks, > > Sungjin Gang_______________________________________________ > Openstack-i18n mailing list > Openstack-i18n(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

4 4

Openstack German translations
by Alec Hans 12 Aug '13

12 Aug '13

Hello, I'm registred as Coordinator in the german translations of OpenStack at Transifex. I also already aded some people to the translation group. It would be great if someone would add the link to the translations on the wiki page @https://wiki.openstack.org/wiki/I18nTeam. Regards, Alec Hans -- Alec Soft Route de Nonan 1 • 1753 Matran • Switzerland www.alecsoft.net

3 2

Collect requirements/bugs of Transifex
by Ying Chun Guo 09 Aug '13

09 Aug '13

Hi, As we discussed in the IRC meeting yesterday, we begin to collect requirements and bugs of Transifex from the whole team. If you have any feature wish list, any bugs report and any comments, any suggestions to Transifex ( www.transifex.com ), please let me know. After we collect those information, we will communicate with Transifex team. Although these requirements/bugs may not be implemented/fixed very quickly, it's a way that we help to improve Transifex, to improve our "working" tools. Please feel free to say without reserve. Regards Daisy

2 1

Fw: I18n's meeting tomorrow
by Ying Chun Guo 02 Aug '13

02 Aug '13

Please feel free to add topics if you want to talk through the wiki page: https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting#Agenda_for_next_me… Regards Ying Chun Guo (Daisy) ----- Forwarded by Ying Chun Guo/China/IBM on 2013/07/17 15:41 ----- Ying Chun Guo/China/IBM wrote on 2013/07/17 15:03:08: > Ying Chun Guo/China/IBM > 2013/07/17 15:03 > > To > > openstack-i18n(a)lists.openstack.org, > > cc > > "OpenStack Development Mailing List" <openstack- > dev(a)lists.openstack.org>, OpenStack Mailing List > <openstack(a)lists.launchpad.net> > > Subject > > I18n's meeting tomorrow > > Hi, > > There is OpenStack I18n team meeting at 0100UTC on Thursday in IRC > channel #openstack-meeting. > The time, we use Asia/America friendly time. Welcome to join the meeting. > > We will cover following topics this time: > > Action items from the last meeting > Progress with Japanese doc site > Wiki page to track the translation jobs and progress > Open discussion > > For more details, please look into https://wiki.openstack.org/wiki/ > Meetings/I18nTeamMeeting. > > Again, if you are interested in I18n or OpenStack, welcome to join us. > We need translators and developers too. > Please contact us through IRC channel #openstack-translation, or > mailing address: openstack-i18n(a)list.openstack.org. > Please refer to our wiki page for more details: https:// > wiki.openstack.org/wiki/I18nTeam > > Best regards > Daisy

3 3

Not found 'api-quick-start' and 'openstack-api-site' to github repository.
by Sungjin Gang 01 Aug '13

01 Aug '13

Hi All, Not found 'Openstack Manuals/api-quick-start' and 'Openstack Manuals/openstack-api-site' to github repository. I think 'Openstack Manuals/openstack-api-site' moved 'api-site'[1]. However, Not found 'Openstack Manuals/api-quick-start' to github. What do you think of this translation???? (stop or other way?) And How to make translate page?? [1]: https://github.com/openstack/api-site Thanks, Sungjin Gang http://about.me/gnagsungjin

1 0

I18n's meeting tomorrow
by Ying Chun Guo 31 Jul '13

31 Jul '13

Hi, There will be OpenStack I18n team meeting at 0700UTC on Thursday (August 1st) in IRC channel #openstack-meeting. The time, we use Asia/Europe friendly time. Welcome to join the meeting. We will cover following topics this time: Action items from the last meeting Progress with Japanese doc site Glossary table in Transifex Open discussion For more details, please look into https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting. Again, if you are interested in I18n or OpenStack, welcome to join us. We need translators and developers too. Please contact us through IRC channel #openstack-translation, or mailing address: openstack-i18n(a)list.openstack.org. Please refer to our wiki page for more details: https://wiki.openstack.org/wiki/I18nTeam Best regards Daisy

1 0

Changes in .pot file from projects
by Gabriel Wainer 29 Jul '13

29 Jul '13

Hello, I was fixing some misspelled words in the neutron project and I have a question about the .pot and .po files. I know the .po files ares generated from the .pot file, and because of that I ask: Do I have to fix the words in the .pot and .po files? Or maybe fixing the .pot, next time the .po files are generated they will be fixed? Thanks, Regards, Gabriel

3 3

About Rosetta translations
by Gabriel Wainer 25 Jul '13

25 Jul '13

Hi All, Can somebody explain to me what is this Rosetta translation in Launchpad? https://translations.launchpad.net/openstack Thanks, Gabriel

2 2

No meeting today
by Ying Chun Guo 25 Jul '13

25 Jul '13

Hi, As we discussed during the last meeting, we change the frequency to bi-weekly. Next meeting will be held on Thursday, 1st August at 0700 UTC. Please refer https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting#Agenda_for_next_me… for more details. Feel free to add topics you want to discuss during next meeting. Thank you. Daisy

1 0

[OpenStack-doc] Add Korean fonts for 'coluddoc-maven-plugins'
by Sungjin Gang 21 Jul '13

21 Jul '13

Hi, David This is Sungjin Kang, a coordinator of OpenStack I18N Korean Team. Could you help me out on the following problem? When creating a korean document using maven, all korean characters are displayed as "#####". While I was looking for the possible solution, I found out that Korean font might need to be added in "clouddoc-maven-plugins" you manages. If this is the case (adding korean font), I would like to add a korean font called "Nanum fonts[1]" [1] http://en.wikipedia.org/wiki/Nanum_font I can prepare for the actual font file. However, I don't know what I need to do to add korean font. Could you help me out on this? Thanks, Sungjin Gang

1 0

About typos in the source language
by Gabriel Wainer 19 Jul '13

19 Jul '13

Hello everyone, I would like to know if there's some way to report or what's expected to do when we find a misspelled word in the source language. I've found some but did nothing so far. I believe that the official review would catch that anyway, but I'm asking just to make sure. Thanks, Gabriel

3 7

Re: [Openstack-i18n] Full translation of the manual in French
by Ying Chun Guo 18 Jul '13

18 Jul '13

Thank you for your update. Please see my comments and answers below. Regards Ying Chun Guo (Daisy) François Bureau <francois.bureau(a)cloudwatt.com> wrote on 2013/07/18 00:57:23: > François Bureau <francois.bureau(a)cloudwatt.com> > 2013/07/18 00:57 > > To > > Ying Chun Guo/China/IBM@IBMCN, > > cc > > Subject > > Full translation of the manual in French > > Hello Daisy, > > I am sorry because I am not going to be able to available tonight for the > meeting. Unfortunately it is too early for me (03:00 AM) :( > > Cloudwatt is agree for translating the full documentation in French. We are > currently working with a translation company for translating our website in > different language (Textmaster : www.textmaster.com > <http://www.textmaster.com> ). So our marketing team is agree for adding the > OpenStack manual into this project. Great news ! > > We are going to translate the following components : > > * OpenStack Manuals » openstack-install > > * OpenStack Manuals » openstack-api-site > > * Ressource: OpenStack Manuals » openstack-ha > > * OpenStack Manuals » api-quick-start > > * OpenStack Manuals » openstack-network-connectivity-admin > > * OpenStack Manuals » openstack-compute-admin > > * OpenStack Manuals » openstack-object-storage-admin > > * OpenStack Manuals » cli-guide > > * OpenStack Manuals » openstack-block-storage-admin > > * OpenStack Manuals » common > > * OpenStack Manuals » openstack-api-programming > > The “ OpenStack Manuals » basic-install ” is already fully translated in > French. > > The Ops manual is not going to be translated for now. We are thinking about > translating it later if nobody in the community do it. > The doc team set operation guide as the first priority. Can I know the reason why you don't translate Ops? > Textmaster is not going to translate the manual into Transifex because it > is going to be too complicate. So we are going to send them the HTML and the > PDf version. Someone in Cloudwatt, after will be in charge of upstreaming > the translation into Transifex after. Please make sure the translation can be uploaded to Transifex. When publishing the translated document in doc website, the translation in Transifex will be used. > > The question is, which version of the manual can we use on Github > (https://github.com/openstack/openstack-manuals) ? Can we work on the > “Master” version or is it better to work on the “Grizzly” one ? > Currently, the translation resources in Transifex are synchronized with master branch. So I will suggest you to use the master version, because it will cause less differences when you upstream the translation to Transifex. the translation to Transifex, > Thanks a lot for your feedback :) > > Best regards, > > > > > > > François Bureau > > (Aka Fdot - https://www.transifex.com/accounts/profile/fbureau/) > > Responsable Centre de Contact > > > > E-mail : francois.bureau(a)cloudwatt.com > > Mobile : 06 40 76 18 01 > > <http://www.cloudwatt.com> http://www.cloudwatt.com > > > > > > > > [attachment "winmail.dat" deleted by Ying Chun Guo/China/IBM]

2 1

Wiki page for tools description and work tracking
by Ying Chun Guo 18 Jul '13

18 Jul '13

Hi,all My action items in the last meeting are: * Daisy to describe the i18n infra job in the wiki. I create a wiki page to describe all the tools/scripts involved in translation: https://wiki.openstack.org/wiki/I18n/Tools * Daisy to create wiki page and github project to track the translation tasks. I create a wiki page to describe all the works that we want people to help: https://wiki.openstack.org/wiki/I18n/Works I create a organization in github: https://github.com/OpenStack-I18n, and if you like, we can use the wiki page there to track the progress and contributors. Regards Ying Chun Guo (Daisy)

2 1

I18n's meeting tomorrow
by Ying Chun Guo 17 Jul '13

17 Jul '13

Hi, There is OpenStack I18n team meeting at 0100UTC on Thursday in IRC channel #openstack-meeting. The time, we use Asia/America friendly time. Welcome to join the meeting. We will cover following topics this time: Action items from the last meeting Progress with Japanese doc site Wiki page to track the translation jobs and progress Open discussion For more details, please look into https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting. Again, if you are interested in I18n or OpenStack, welcome to join us. We need translators and developers too. Please contact us through IRC channel #openstack-translation, or mailing address: openstack-i18n(a)list.openstack.org. Please refer to our wiki page for more details: https://wiki.openstack.org/wiki/I18nTeam Best regards Daisy

1 0

I18n team meeting today
by Ying Chun Guo 11 Jul '13

11 Jul '13

Hi, There is OpenStack I18n team meeting at 0700UTC on Thursday in IRC channel #openstack-meeting. The time, we use Europe/India/Asia friendly time. Welcome to join the meeting. We will cover following topics this time: Action items from the last meeting Release of document translation How to enroll more developers How to track issues and blueprints How to track contributors Open discussion For more details, please look into https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting. Best regards Daisy

2 1

Minutes from 2013-07-04 Meeting
by Tom Fifield 04 Jul '13

04 Jul '13

The minutes from todays' meeting are available online: https://wiki.openstack.org/wiki/I18N/MeetingLogs Next Meeting: Thursday, 11th July at 0700 UTC Regards, Tom

1 0