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

Re: [Openstack-i18n] Fw: [OpenStack-doc] Add Korean fonts for 'coluddoc-maven-plugins'
by Ying Chun Guo 18 Mar '14

18 Mar '14

Hi, Sungjin Can you give the font file or the link to download the font file to David Cramer? He can add it to the plugin and cut a release. @ the whole team If you have font issue with the Maven plugin, please send your font file to David Cramer. @ David Will the Maven plugin become very big if it contains so many font files? Is it possible to use system font instead? Is it possible to configure which font to download when downloading the binary plugin files? Regards Ying Chun Guo (Daisy) David Cramer <david.cramer(a)rackspace.com> wrote on 2013/08/13 03:13:14: > David Cramer <david.cramer(a)rackspace.com> > 2013/08/13 03:13 > > To > > Ying Chun Guo/China/IBM@IBMCN, > > cc > > Subject > > Re: Fw: [Openstack-i18n] [OpenStack-doc] Add Korean fonts for > 'coluddoc-maven-plugins' > > Hi Daisy, > So I'm surprised that those steps would work. You'd really have to do > "mvn clean install" to make a changed version of the plugin available > for local builds (and also be sure that your project depends on the > version you just built). > > In the thread below, Sungjin Gang had a message to me offering to > provide a Korean font file. I think I'd replied saying that if I were > given the file , I could add it to the plugin. Is there an open source > font file available somewhere that I can download? If so, I'll add it > immediately and cut a release. > > For each language that requires a special font, we'll have to add the > font to the plugin for it to work. > > Regards, > David > > On 08/12/2013 11:46 AM, Ying Chun Guo wrote: > > Hi, David > > > > Sungjin Gang is a Korean translator. When he was trying to generate the > > translated Korean documents, he found the Korean characters cannot be > > displayed and #### was displayed instead of Korean font. > > > > After several tests, he tried follow steps and had Korean font work. > > > >> Edit 'clouddoc-maven-plugins'[1]. > >> Recompiling plugin. > >> Edit 'openstack-manuals/[docs-name]/pom.xml', plugin dir. > >> and exe 'mvn clean generate-sources'. > >> Create PDF[2]. > > > > As I remembered, there was the same problem to Chinese and Japanese > > characters, and now there was problem for Korean characters. I wonder if > > there are same problems to other languages. I'd like to check with you > > if you have any thoughts to resolve the root of this issue, other than > > using this tricky way. > > > > Thanks and regards > > Ying Chun Guo (Daisy) > > > > ----- Forwarded by Ying Chun Guo/China/IBM on 2013/08/13 00:39 ----- > > > > Sungjin Gang <gang.sungjin(a)gmail.com> wrote on 2013/08/10 15:04:57: > > > >> Sungjin Gang <gang.sungjin(a)gmail.com> > >> 2013/08/10 15:04 > >> > >> To > >> > >> Ying Chun Guo/China/IBM@IBMCN, > >> > >> cc > >> > >> openstack-i18n(a)lists.openstack.org > >> > >> Subject > >> > >> Re: [Openstack-i18n] [OpenStack-doc] Add Korean fonts for 'coluddoc- > >> maven-plugins' > >> > >> Hi, ~~~ > >> > >> :)) > >> > >> View Korean font!!!!! > >> :)) > >> > >> Edit 'clouddoc-maven-plugins'[1]. > >> > >> Recompiling plugin. > >> > >> Edit 'openstack-manuals/[docs-name]/pom.xml', plugin dir. > >> > >> and exe 'mvn clean generate-sources'. > >> > >> Create PDF[2]. > >> > >> Um.. hahahahahahaaaaaaa~ :)) > >> > >> But not think to do it. hahahahahahahaaaaaaaaaa :-( > >> > >> [image removed] > >> > >> [1]: https://github.com/ujuc/clouddocs-maven-plugin/commit/ > >> cb0743a14ece9e86cdcb190e778a9f38319b5b9a > >> [2]: http://os.ujuc.kr/openstack-manuals/generated/ko_KR/basic- > >> install/target/docbkx/webhelp/grizzly/basic-install/apt/openstack- > >> basic-install-apt-grizzly.pdf > >> > >> Thanks, > >> Sungjin. > >> > >> Jul 30, 2013, 5:34 PM, Ying Chun Guo <guoyingc(a)cn.ibm.com> $)C작성: > >> > >> 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" > > youmanages. > >> > > >> > 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 > >> _______________________________________________ > >> Openstack-i18n mailing list > >> Openstack-i18n(a)lists.openstack.org > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > >

3 7

Status of OpenStack Operations Guide in Chinese & Japanese
by Tom Fifield 28 Nov '13

28 Nov '13

Hi, Just wondering what the current status of OpenStack Operations Guide in Chinese & Japanese is? Regards, Tom

2 4

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

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

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