OpenStack-I18n

Download

openstack-i18n@lists.openstack.org

November 2014

9 participants
12 discussions

Re: [Openstack-i18n] Pootle and Zanata trial - summary of responses from translators
by Ying Chun Guo 05 Nov '14

05 Nov '14

Hello, all Till now, I got responses from 5 translators in Japanese, Korean, Spanish, French and Chinese translation team. 4 of them clearly described their preferences is Zanata. Here are some comments from them to support Zanata: "Using Zanata, cooperation with other translators is easier: chat room, listing translators who are translating at the same time, comments if a translation is rejected." "The role management of Zanata is powerful. It clearly defines translators, reviewers, and project maintainers." "I like the Project-wide search and replace feature in particular. It allows translators or maintainer to search for a word, a phrase, a sentence, or a paragraph and replace it across multiple files within a single project. It is extremely useful when you do the final editing or reviewing." "I guess the impression a translator can have is that Zanata is more user friendly, whilst Pootle looks a bit quirky makinf finding info or the right links a bir more difficult. I think Zanata is very easy to use and also promote s translator engagement." Also, there are some problems with Pootle which will block us: The support of CJK (Chinese font, Japanese font and Korean font) is poor, for example: saved translations in Korean font is ???; saved translations in CJK fonts do not seem to be recognized by the TM. No official client till now. Our current translation process (uploading, downloading and reviewing) could not be implemented. So as a summary of the translators evaluation, we would prefer to use Zanata. If you have any questions, please let me know. Best regards Ying Chun Guo (Daisy) Ying Chun Guo/China/IBM wrote on 2014/10/16 17:04:27: > Ying Chun Guo/China/IBM > 2014/10/16 17:04 > > To > > openstack-i18n(a)lists.openstack.org, > > cc > > Subject > > Pootle and Zanata trial > > Hello, team > > Pootle and Zanata trial are ready for test. > 1. Pootle > http://23.253.231.198/projects/ > 2. Zanata > http://15.126.226.230:8080/ > > I need volunteers to test features and feed back how satisfied you feel. > I use an Etherpad page to track: > https://etherpad.openstack.org/p/translation-tools-comparation > > I have gotten volunteers from Korean and Indian team. > I'm looking for volunteers from other translation teams. > > If you want to help, please let me know. > If you want to try admin features, send me emails with your account ID. > > Thank you. > > Best regards > Ying Chun Guo (Daisy)

1 1

Summaary of Paris Translators meeting
by Ying Chun Guo 05 Nov '14

05 Nov '14

Hello, team There was a session yesterday in Paris Design summit to gather translators together. There were 6 translation teams joined the meeting locally. They are French team, Spanish team, German team, Catalan team, Chinese Taiwan team, and Chinese team. Some team members were trying to join the meeting remotely through Google Hangout. Yet they failed because of a fault made by me. I'm very sorry for that. We discussed how to build translation teams, how to make a high quality translation, and how to maintain the priority definition of documents. There are some good suggestions I could collect. Feel free to add more if I miss. * how to build translation teams #1: Use local Openstack meetups to promote translations #2: Use a blog post on OpenStack planet to promote translations. #3: Give the new comers a start point #4: Give people a goal and a timeframe (a focus) #5: A overall description of translation priorities, including both docs and messages #6: Create mailing lists on OpenStack infrastructure for local translation teams #7: Improve our tools to clearly state translators contributions and teams progresses. Integrate with Stackalytics in the future. * how to make a high quality translation #1: Maintain a glossary #2: Report bugs to projects if the problems of translations are due to the source strings, with a "i18n" tag. #3: Report bugs i18n team if the problems of translations are due to the translation quality, with a tag of language code. ( https://bugs.launchpad.net/openstack-i18n) #4: Keep on the improving of "Horizon translatable strings rules" ( https://etherpad.openstack.org/p/i18n_translatable_strings) Educate our developers. * how to maintain the priority definition of documents #1: Team discussion and team decision, including both i18n team and doc team. #2: Keep up to date of the priorities defined now: https://wiki.openstack.org/wiki/I18nTeam/docs-translation Let's define some action items based on these useful suggestions. Keep on the discussion in the ML. We could make a list of actions and owners in our next I18n meeting on Nov 20th. The I18n meeting of this week will be ignored because of the summit. Thank you all for your active participation and contributions. Merci. Best regards Ying Chun Guo (Daisy)

1 0