- OpenStack-I18n - lists.openstack.org

Help with RST translation tool chain needed
by Andreas Jaeger 22 Jun '15

22 Jun '15

The Japanese translation of the User Guide should be complete according to transifex but looking at docs.openstack.org/draft/ja/user-guide/ I see only a few words in Japanese. Building the guide locally, I see po files that are completely translated but somehow the sphinx tools are not picking these up properly. I'm puzzled on what's going wrong here. Is there anybody that can look at the RST building and tell us what's wrong - and fix if possible ;), please? Note to build the document locally yourself, you can run: tox -e buildlang -- ja Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 4

Terminologies
by Ying Chun Guo 19 Jun '15

19 Jun '15

Hello, In Vancouver translation workshop, we decided to compose the translation terminologies. I merged the terminologies used by Japanese team, German team and French team and made out the first version of translation terms. When we generate it, terminology will be the first contents to be translated in any translation teams. It is a good way to get the consistency among different translators and different translation resources. Please take a look and let me know if you have any comments and suggestions. https://docs.google.com/spreadsheets/d/1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9I… Best regards Ying Chun Guo (Daisy)

7 9

What's Up, Doc? 19 June 2015
by Lana Brindley 18 Jun '15

18 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, This week, I've been working on helping out the Ironic team to sort out their Install Guide (thanks have to go to Gauvain and Nick, who have offered to help out with writing assistance here), and trying to come up with some better ways to work with the i18n team, and our docs liaisons. More on all of that further in. == Progress towards Liberty == * RST conversion: ** Install Guide: Spec is merged, stand by for conversion to start ** Cloud Admin Guide: is well on the way. Get in touch with Brian or Joe, or sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… ** HA Guide: is also underway. Get in touch with Meg or Matt: https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update ** Security Guide: In planning. Stand by for more info. * User Guides information architecture overhaul ** Waiting on the RST conversion of the Cloud Admin Guide to be complete * Greater focus on helping out devs with docs in their repo ** We now have a team starting to form to work on Ironic docs. Contact me if you want to know more, or are willing to help out. * Improve how we communicate with and support our corporate contributors ** No progress this week * Improve communication with Docs Liaisons ** I have now reached out to liaisons. More later in this newsletter. * Clearing out old bugs ** Thanks to Tom for closing bug 1195875. Let's keep up the great work! == RST Migration == The next books we are focusing on for RST conversion are the Install Guide, Cloud Admin Guide, HA Guide, and the Security Guide. If you would like to assist, please get in touch with the appropriate speciality team: * Install Guide: ** Contact Karin Levenstein <karin.levenstein(a)rackspace.com> ** Spec: https://review.openstack.org/#/c/183138/ ** Watch this space: https://wiki.openstack.org/wiki/Documentation/Migrate#Installation_Guide_Mi… * Cloud Admin Guide: ** Contact Brian Moss <kallimachos(a)gmail.com> & Joseph Robinson <joseph.r.email(a)gmail.com> ** Blueprint: https://blueprints.launchpad.net/openstack-manuals/+spec/reorganise-user-gu… ** Sign up to help out here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… * HA Guide ** Contact Meg McRoberts <dreidellhasa(a)yahoo.com> or Matt Griffin <me(a)mattgriffin.com> ** Blueprint: https://blueprints.launchpad.net/openstack-manuals/+spec/improve-ha-guide * Security Guide ** Contact Nathaniel Dillon <nathaniel.dillon(a)hp.com> ** Bug: https://bugs.launchpad.net/openstack-manuals/+bug/1463111 ** Blueprint+Spec: TBD For books that are now being converted, don't forget that any change you make to the XML must also be made to the RST version until conversion is complete. Our lovely team of cores will be keeping an eye out to make sure loose changes to XML don't pass the gate, but try to help them out by pointing out both patches in your reviews. == Docs Tools == Andreas will shortly be updating openstack-docs-tools to 0.29. == Docs Liaisons == Don't forget that we have subject matter experts to help you with documentation questions that you might have. As you're working on bugs, feel free to give them a quick ping or an email to ask questions. They promise not to laugh at you! https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation == i18n Team == At Summit, I spent a lot of time with Ying Chun Guo (Daisy) from the translation team, to try and come up with a way we can make sure our teams are working together better. To that end, we've got a few ideas we're going to be implementing over the next few weeks. First of all, this newsletter now goes direct to the the translation mailing list, as well the dev and doc lists (hi translators!). Secondly, Daisy is going to poll her team to identify an i18n documentation liaison, who will be the go-to person for all questions about translation for docs. The other thing we're going to do is to make sure we're helping the i18n team to keep their status page up to date: https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categori… If you're working on a doc that is translated, please check that table and make sure the translation team know what you're up to! This will help prevent needless effort on their part, which benefits us all in the end. == Doc team meeting == The US meeting was held this week, see the minutes here to catch up: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-06-17 Apologies for the timing confusion on that one, it seems as though daylight savings changes took us by surprise. For now, the meeting will remain at 1400UTC. If you would prefer it to be at a different time, bring it up on the mailing list, or in the next US meeting. Next meetings are: APAC: Wednesday 24 June, 00:30:00 UTC US: Wednesday 1 July, 14:00:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… == Spotlight bugs for this week == Of the three bugs we spotlighted last week, one of them got marked as invalid (thanks Tom!), and another is in progress with SME assistance (thanks Olga!). That's great! Here's another three dusty old bugs that could use a polish up: https://bugs.launchpad.net/openstack-manuals/+bug/1330005 Glance image properties and values (low hanging fruit) https://bugs.launchpad.net/openstack-manuals/+bug/1394397 Nova notification_driver https://bugs.launchpad.net/openstack-manuals/+bug/1205402 iPXE ISO boot support - -- Remember, if you have content you would like to add to this newsletter, or you would like to be added to the distribution list, please email me directly at openstack(a)lanabrindley.com, or visit: https://wiki.openstack.org/w/index.php?title=Documentation/WhatsUpDoc Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVg34hAAoJELppzVb4+KUyBWcIAM+914bjuU/6BwFQqWUwTiEA Ed5wAfdr55kE4QT6OZgaBWUH7e3qyjk6VHmfIKXKyoYaMXq82oT0gBEsJYH4PY46 q/lOYG9tkDUuPjA3i4ibPYClGfLC3Ku0zOdwG9alg/2AystOqW/VbGLRQLhHQavD JgZs5/iB8S1JvBhHEiAixMyRgM5NMuXiM/j6TXVTw1tSm3Iz1KRnm2z8RiYVxBYj 9HKHKNy50PFXpubnYYu+B6iBqWv2JggkeCYOL2G0MiQubdnoXekNCKxNlHKiaPPU xCTj3qzUNW/UJZHVLpQskuD736kli2pqkEbiCeuNcqd3VQicE6VvY3QV31kGU5c= =IC4Z -----END PGP SIGNATURE-----

1 0

Specialty teams connecting to translation team
by Anne Gentle 18 Jun '15

18 Jun '15

Hi all, I'm sitting here in Vancouver next to Daisy (Ying Chun Guo) who leads the i18N efforts for OpenStack. She would like each specialty team lead to connect with the i18N team to communicate the amount of change expected so that they can evaluate the timing of translation, and how much is done that can be translated. We also had a session with the i18N team and want to work on more communication with each team, and I think the specialty team leads are a great way to start that effort. Thoughts or ideas? Let us know. Thanks, Anne -- Anne Gentle annegentle(a)justwriteclick.com

4 6

common (RST) translation
by KATO Tomoyuki 17 Jun '15

17 Jun '15

Hi team, I'm translating User Guides (RST) recently. I found a below problem. Any thought? Problem: Each message catalog "pot" file contains all strings of the RST document, including "common" files (glossary and so on). In particular, "user-guide" and "user-guide-admin" resource at Transifex have same strings in "common" files respectively. This causes unintended inconsistency of translation. In fact, Japanese "user-guide" and "user-guide-admin" have different translated strings, which need to sync manually. Solution (just my idea): As is: 1. Sphinx(?) generates the "pot" file. 2. translate at Transifex. 3. Sphinx(?) merge the translated strings. To be: 1. Sphinx(?) generates the "pot" file. 2. A new script split message stringss for "common". (maybe, based on "msgcat") So, generate 2 resources (main document resource and "common" resource). 3. translate at Transifex. 4. merge the 2 resources for Sphinx(?). 5. Sphinx(?) merge the translated strings. Regards, KATO Tomoyuki

3 10

Criteria of core members and active members
by Ying Chun Guo 17 Jun '15

17 Jun '15

Hello, In today's IRC meeting, we discussed about the criteria of core members and active members. Here are some outputs. If you don't joined the discussion, please comment here. -------- I18n Core Contributors The coordinator of active language teams, who coordinates Dashboard translation or two documents translations during the previous two release cycles and attend team meetings at least once a month, will be granted as "I18n Core Contributors" I18n Active Contributors Translators or reviewers, who translate or review more than 200 words during the previous two release cycles, will be granted as "I18n Active Contributors" Best regards Ying Chun Guo (Daisy)

6 6

IRC Meeting
by Ying Chun Guo 17 Jun '15

17 Jun '15

Hello, team We will have the IRC meeting at UTC 1300 in the channel #openstack-meeting, on June 18th. I'm going to cover following topics: * Review translation terminologies * Open discussions If you have other topics, feel free to propose. Best regards Ying Chun Guo (Daisy)

1 0

French User Guide publication
by KATO Tomoyuki 17 Jun '15

17 Jun '15

Hi fdot, I noticed draft "fr/user-guide" link is broken[1]. Do you know what is the present situation? [1] http://docs.openstack.org/draft/draft-index.html Reagards, KATO Tomoyuki

3 4

Turkish translation
by Hüseyin Çotuk 15 Jun '15

15 Jun '15

Dear All, My name is Huseyin Cotuk, and i have been using OpenStack for more than 3 years in production. I am working for the Turkish government and we operate an OpenStack cloud for governmental institutions, universities, other research institutes and internal projects. Currently we have more than 4000 cpu cores, 500 TBytes of storage and so on. I am head of cloud department at TUBITAK ULAKBIM in Turkey, and while OpenStack Days Istanbul yesterday, we met with Jonathan and Lauren. We talked about our projects and i promised for the Turkish translation of OpenStack dashboard for the Turkish community. My organization TUBITAK ULAKBIM is also coordinating national operating system (Pardus), and we already have a translation team for this OS. We will work together with this translation team, and my team will review the translations after OS team finishes. My transifex id is huseyincotuk and the project name is openstack_turkish. I am looking forward to hearing from you. Best regards, Huseyin

3 3

Thought on String Freeze
by Akihiro Motoki 15 Jun '15

15 Jun '15

Hi I18N folks, # Congratulation for the official I18N project!! I first thought to send this mail to the dev list, but it seems better to share my thought in the I18N folks first. Problems ========== I am feeling that String Freeze does not work well in the past several releases.There are several I think we should not apply String Freeze for projects for which not so many translators work on. As far as I understand, Horizon and documentations are targets for most translations in the past several releases. On the other hands, core reviewers of projects other than Horizon and docs (including keystone) were taking care of String Freeze exception WELL. My Proposal ============= Considering the current status, I think we should limit "String Freeze" only to projects which translators are interested in. My idea is to declare projects we would like to enable "String Freeze" just after Liberty-3 is cut. By doing so, other projects no longer need to take care of String Freeze exception. (Note that the freeze date of the documentation projects are different and we can apply some different policy on documentations). Thought? I cannot join the team meeting tomorrow due to LinuxCon/CloudOpen Japan, but I hope you will share your thought on this topic. Thanks, Akihiro

2 2

Fwd: [openstack-dev] [horizon][i18n] Ordering of PO files
by Tom Fifield 08 Jun '15

08 Jun '15

-------- Forwarded Message -------- Subject: [openstack-dev] [horizon][i18n] Ordering of PO files Date: Mon, 8 Jun 2015 17:28:39 -0600 From: Thai Q Tran <tqtran(a)us.ibm.com> Reply-To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> Hi folks, In the midst of shifting to angular, we are making use of babel for extracting messages. This would then allow us to write a custom extractor for angular templates. Here's the patch that compare PO files: https://review.openstack.org/#/c/189502/ It looks worse than reality, if you compare the django vs babel makemessages, they are nearly identical, only the ordering is different. Which leads me to my next point. If the ordering of the translatable strings are not the same, how does that affect translation (if at all)?

1 0

I18n team working sessions in Vancouver
by Ying Chun Guo 05 Jun '15

05 Jun '15

Hello, all We had a great day yesterday. There were two I18n team working sessions. People from Japanese, Frech, Russian, Polish, Chinese and Chinese Taiwan team attended. Key persons from Doc team, infra team, and Horizon dev team joined the discussions too. We made good progress with glossaries, document translations, string freeze, tool migration, and etc. More details could be found in the etherpad pages [1] [2]. Yet our translators still want more face to face communications. So I organize an ad hoc meeting on Wednesday afternoon, only for translators. If you are translators and in Vancouver summit now, come to join the ad hoc meeting. The place is at a round table outside the Room 1, East Building at the Vancouver Convention Centre. The time is from 2:05pm to 5:05pm on Wednesday, May 21st. I will sit there and wait for you to join. I created an Etherpad page for us to track the discussion. Feel free to add the topics you want to cover. https://etherpad.openstack.org/p/vancouver-translation-team-workshop Thank you. Best regards Ying Chun Guo (Daisy) [1] https://etherpad.openstack.org/p/Vancouver-I18n-WG-session [2] https://etherpad.openstack.org/p/Vancouver-I18n-Translation-platform-session

3 5

I18n team, OpenStack Project Team!
by Ying Chun Guo 03 Jun '15

03 Jun '15

Hello, all I'm pleased to announce that I18n team is approved by TC to become a OpenStack Project Team. We are now under the authority of the OpenStack Technical Committee. In return, we could get some space and time to discuss our future development at the Design Summits. Our contributors could vote in the Technical Committee election. This is a great milestone after I18n team was created. Next, we need to figure out the criteria of our core members and active members, which might be different from dev team. We will initialize the core team, then grow the team and increase the contributions. Let's work together to make it a successful team. Best regards Ying Chun Guo (Daisy)

11 12

IRC meeting tomorrow
by Ying Chun Guo 03 Jun '15

03 Jun '15

Hello, team There are several responses to the mail "Review IRC meeting time"[1]. I don't see objections. So let's use them from now on. I hope active team members could have chances to join the discussion at least once a month. If these two time slots are not suitable for you, please let me know. We could still adjust the meeting times in the future. Tomorrow, we will have the IRC meeting at UTC 0600 in the channel #openstack-meeting, on June 4th. Following topics would be covered: * Briefing of I18n meetings in Vancouver summit * Criteria of I18n core members and active members * Open discussions Hope to talk to you then. Best regards Ying Chun Guo (Daisy) [1] http://lists.openstack.org/pipermail/openstack-i18n/2015-June/001107.html

1 0

Review IRC meeting time
by Ying Chun Guo 02 Jun '15

02 Jun '15

Hello, team I would like to review our IRC meeting time. Now we are using UTC 0800 and we meet on every first and third Thursday. I18n team have people from all over the world. Some people would like to use their day time, and some people prefer to use their evening time. I want to change to two time slots for the meetings. We use them alternately. Hope every team member could find a suitable time to join the team meeting. I suggest below two time slots: 1. The first Thursday every month UTC 6am, Thur Paris 08am, Thur Warsaw 08am, Thur Moscow 09am, Thur New Delhi 11:30am, Thur Beijing 14pm, Thur Seoul 15pm, Thur Tokyo 15pm, Thur Vancouver 23pm, Wed 2. The third Thursday every month UTC 13pm, Thur Paris 15pm, Thur Warsaw 15pm, Thur Moscow 16am, Thur New Delhi 18:30am, Thur Beijing 21pm, Thur Seoul 22pm, Thur Tokyo 22pm, Thur Vancouver 06am, Thur Please let me know which time slot works for you. Or if neither works for you, please suggest a time. Thank you. Best regards Ying Chun Guo (Daisy)

4 3

Re: [Openstack-i18n] Specialty teams connecting to translation team
by Ying Chun Guo 21 May '15

21 May '15

Sorry, wrong wiki link in my last email. It is https://wiki.openstack.org/wiki/I18nTeam/docs-translation Best regards Ying Chun Guo (Daisy) Ying Chun Guo/China/IBM wrote on 2015/05/22 01:42:18: > From: Ying Chun Guo/China/IBM > To: Anne Gentle <annegentle(a)justwriteclick.com> > Cc: "openstack-docs(a)lists.openstack.org" <openstack- > docs(a)lists.openstack.org>, "openstack-i18n(a)lists.openstack.org" > <openstack-i18n(a)lists.openstack.org> > Date: 2015/05/22 01:42 > Subject: Re: [Openstack-i18n] Specialty teams connecting to translation team > > Thank you, Anne. > > We use a wiki page to track the status of documentation: > https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categori… > > I hope specialty team leads could keep an eye on this table. > If there is any changes of your documents, like, changing from > stable to unstable, changing from unstable to stable, > let the translation team know by sending an email to openstack-i18n > mailing list. > So that we could make a translation plan for your documents. > > Thanks. > Best regards > Ying Chun Guo (Daisy) > > Anne Gentle <annegentle(a)justwriteclick.com> wrote on 2015/05/22 01:35:14: > > > From: Anne Gentle <annegentle(a)justwriteclick.com> > > To: "openstack-docs(a)lists.openstack.org" <openstack- > > docs(a)lists.openstack.org>, "openstack-i18n(a)lists.openstack.org" > > <openstack-i18n(a)lists.openstack.org> > > Date: 2015/05/22 01:35 > > Subject: [Openstack-i18n] Specialty teams connecting to translation team > > > > Hi all, > > I'm sitting here in Vancouver next to Daisy (Ying Chun Guo) who > > leads the i18N efforts for OpenStack. She would like each specialty > > team lead to connect with the i18N team to communicate the amount of > > change expected so that they can evaluate the timing of translation, > > and how much is done that can be translated. > > > > We also had a session with the i18N team and want to work on more > > communication with each team, and I think the specialty team leads > > are a great way to start that effort. > > > > Thoughts or ideas? Let us know. > > Thanks, > > Anne > > > > -- > > Anne Gentle > > annegentle@justwriteclick.com_______________________________________________ > > Openstack-i18n mailing list > > Openstack-i18n(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

1 0

Magnum, magnumclient translations?
by Andreas Jaeger 14 May '15

14 May '15

The magnum project wants to enable translation, see https://review.openstack.org/#/c/182835/ and https://review.openstack.org/#/c/182848/ Is there any guideline from the translation team which projects get translation enabled? I know that enabling translation does not mean, something gets translated - Davanum, keep that in mind ;) Btw. magnum is an OpenStack project that provides a set of services for management of application containers in a multi-tenant cloud environment. And so far we've enabled all projects in the OpenStack project. Only the last months this was not done with each new project moving under the big tent. I'll review the requests today or tomorrow and will setup transifex for the team unless I hear otherwise from the translation team, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 2

Update on Dogri, Konkani, Manipuri, Sanskrit, Santali
by Tom Fifield 14 May '15

14 May '15

Hi all, I just wanted to let you know that Transifex has added Dogri, Konkani, Manipuri, Sanskrit and Santali to their site's code repository, and will update the code of the live site (so we can use them) before the end of this month. Regards, Tom

2 4

Horizon translation check site
by KATO Tomoyuki 13 May '15

13 May '15

Hi team, Motoki-san, We did not have Horizon translation check site for Kilo release cycle from my understanding. We previously discussed this topic in this ML. Do we have a conclusion? Need more discussion? Thanks, KATO Tomoyuki

3 2

Separating User Guides
by Andreas Jaeger 13 May '15

13 May '15

FYI, we're separating the User Guides again into two directories. Once this is done, we will have again user-guide and user-guide-admin resources. I will copy over all content from the current user-guides to these and then remove the user-guides. Patch series: https://review.openstack.org/#/q/status:open+project:openstack/openstack-ma… Docs discussion: http://lists.openstack.org/pipermail/openstack-docs/2015-May/006581.html Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 1

I18n team working sessions in Vancouver summit
by Ying Chun Guo 11 May '15

11 May '15

Hello, We have 2 working sessions in Vancouver summit. They are: * Translation team working session [1] * Building translation platform [2] The first session is for discussions related with our translations. The second session is for discussions related with moving to Zanata. I18n team members who would go to Vancouver summit are strongly recommended to attend these sessions. You can edit Etherpad pages to add the topics you want to discuss. The links to Etherpad pages are: https://etherpad.openstack.org/p/Vancouver-I18n-WG-session https://etherpad.openstack.org/p/Vancouver-I18n-Translation-platform-session Hope to see you in Vancouver. Thank you. Best regards Ying Chun Guo (Daisy) [1] https://openstacksummitmay2015vancouver.sched.org/event/f008932bfc685abe742… [2] https://openstacksummitmay2015vancouver.sched.org/event/83ceed4873820c889e7…

1 0

website translation
by KATO Tomoyuki 10 May '15

10 May '15

Hi team, I want to translate website "www.openstack.org" as whole as possible. However, I don't understand how website are maintained. So, I will investigate. Are you interested in website translation? Does anyone help me? My Requirement(priority): 1. automatically periodic (eg:every 1H) update translation 2. use Transifex(/Zanata) for translation tool -> need to generate pot files It is easy to translate for translator. Thanks, KATO Tomoyuki

2 2

IRC meeting tomorrow
by Ying Chun Guo 06 May '15

06 May '15

Hello team I would use tomorrow's IRC meeting to prepare for the Vancouver summit meetings. People who would go to Vancouver are strongly desired to show up. Following topics would be covered: * Agenda of I18n team meetings in Vancouver summit * Open discussions Hope to see you in IRC channel of #openstack-meeting at 0800 UTC. Best regards Ying Chun Guo (Daisy)

1 0

Persian translate
by کاربرخوب لینوکس 29 Apr '15

29 Apr '15

Salam Hello I am Contributing some project to translate to farsi such as debian , ... I like to start and Contribute open stack translation for persian users. Thanks

2 1

Decreasing size of PO files
by Andreas Jaeger 23 Apr '15

23 Apr '15

Our PO files contain information about location (filename and line numbers) as well as untranslated strings. Dolph suggested to me recently to import into projects only the *translated* strings and I did some investigation and implementation. I don't expect this to have any negative impact but wanted to inform you and ask for feedback. We will continue to push the full location information to transifex and leave it in the POT files that are stored in each repository. Thus if you download a file from transifex, you have all location information. During the import from transifex into the OpenStack git repositories, our scripts remove the location information as well as any untranslated strings thus reducing the files to import significantly. This also reduces the change of an import significantly since a line number change will not cause many location information to be updated. The gettext tools we use can cope fine with this smaller PO file since it contains everything that is needed - just nothing more ;) Also, it's easy to rebuild the full PO file from the date in the repository using the msgmerge command: msgmerge POT-FILE PO-FILE -o FULL-PO-FILE As a first step, I have made this change for documentation projects like openstack-manuals only: https://review.openstack.org/176313 If this works as expected, I plan to do it for other projects as well. Please review and tell me if you have any further ideas or if I overlooked something, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 5