- OpenStack-I18n - lists.openstack.org

(no subject)
by Danilo Ingami 26 May '14

26 May '14

1 0

Complete translations are big
by Douglas Fish 26 May '14

26 May '14

I've come across this review for automated translations coming into Horizon https://review.openstack.org/#/c/91523/ It concerns me that it has over a half million LOC in it, and many of these languages have near 0 translation. (I checked here: https://www.transifex.com/projects/p/horizon/) 0 translation languages have just as many lines as full translations; they are just shorter. I can't give you a specific well-defined issue about why this concerns me, but I'm worried about things like how big it might make our distributions, or adding time to how long it takes to clone a new Horizon instance, or use devstack. I've chatted a bit about this in #openstack-horizon. ajaeger has pointed out to me that this isn't the biggest patch we've had for translations. This one, for example, is 5 million lines: https://review.openstack.org/#/c/67521/ This doesn't entirely satisfy me because git clone https://review.openstack.org/openstack/openstack-manuals is taking several minutes for me this morning (full disclosure: I am having some network flakiness today). I'd hate for Horizon to take anywhere near that long to clone. Also in #openstack-horizon jpich has shared that we intend to prune some of these langauges out of Horizon as we approach the release. Maybe it would be best to begin that pruning now, to avoid late dev cycle churn? Does anyone else share my concern about the large size of these translations? Particularly the translations that have near 0 translated strings. Doug Fish

6 15

Korean and Japanese Translations of openstack-manuals broken
by Andreas Jaeger 24 May '14

24 May '14

Please see: http://logs.openstack.org/84/95084/1/check/gate-openstack-manuals-tox-check… 2014-05-23 06:27:40.010 | checksyntax runtests: commands[1] | bash -c find doc -type f -regex '.*\.pot?' -print0|xargs -0 -n 1 msgfmt --check-format -o /dev/null 2014-05-23 06:27:40.041 | /home/jenkins/workspace/gate-openstack-manuals-tox-checksyntax$ /bin/bash -c find doc -type f -regex '.*\.pot?' -print0|xargs -0 -n 1 msgfmt --check-format -o /dev/null 2014-05-23 06:27:40.386 | doc/common/locale/ja.po:14398: end-of-file within string 2014-05-23 06:27:40.386 | doc/common/locale/ja.po:14397: missing `msgstr' section 2014-05-23 06:27:40.387 | msgfmt: found 2 fatal errors 2014-05-23 06:27:40.672 | doc/security-guide/locale/ja.po:2920: end-of-file within string 2014-05-23 06:27:40.672 | msgfmt: found 1 fatal error 2014-05-23 06:27:40.739 | doc/install-guide/locale/ja.po:4335: end-of-file within string 2014-05-23 06:27:40.739 | doc/install-guide/locale/ja.po:4332: missing `msgstr' section 2014-05-23 06:27:40.739 | msgfmt: found 2 fatal errors 2014-05-23 06:27:40.768 | doc/install-guide/locale/ko_KR.po:5278:25: incomplete multibyte sequence at end of file 2014-05-23 06:27:40.768 | doc/install-guide/locale/ko_KR.po:5278: end-of-file within string 2014-05-23 06:27:40.768 | msgfmt: found 2 fatal errors Patch: https://review.openstack.org/95084 Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 4

Translatable strings rules
by Yves-Gwenaël Bourhis 23 May '14

23 May '14

I made a first draft about Translatable strings rules: https://wiki.openstack.org/wiki/I18n/TranslatableStrings Please feel free to comment :-) -- Yves-Gwenaël Bourhis

1 0

Translation gate for doc jobs
by Andreas Jaeger 22 May '14

22 May '14

Inspired by some discussions here at the summit, I'd like to setup some translation gate for jobs. Patch https://review.openstack.org/93526 (merged) sets up a test that can be invoked with "tox -e checklang" which builds all "supported" manuals. I propose the following: * Setup checking/gating jobs that runs this test and mark it as non-voting. * Create policy on how to handle failures. Proposed policy: * We only gate on manual/language combinations that are translated sufficiently. Right now that's for openstack-manuals Japanese with the Security Guide, HA Guide and Install Guides only. * If an import from transifex fails, creates a failure, we do not approve the import. * If any other patch fails, the failure might get ignored. * In any case of failure, let's send an email to the openstack-i18n mailing list asking them to investigate and fix. What do you think? Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 5

Japanese Security Guide fails to build
by Andreas Jaeger 22 May '14

22 May '14

We now check the translations in the gate and I noticed that the Security Guide fails to build: https://bugs.launchpad.net/openstack-i18n/+bug/1322224 This looks some tools issue, any help on how to fix this is welcome! Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 0

Japanese install-deploy guide failing
by Andreas Jaeger 13 May '14

13 May '14

Hi, I noticed that the Japanese Install Guide is failing, e.g.: https://jenkins05.openstack.org/job/openstack-install-deploy-guide-ja/102/ could somebody help, please? Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 4

Icehouse release note translation?
by Akihiro Motoki 02 May '14

02 May '14

Hi, When Havana release, some language teams translated the release notes. Is there a language team who is translating Icehouse Release Notes [1]? Japanese team is now translating the release note [2] and it is almost completed. Once it is available, I would like to add a link to the translated page as we did for Havana. I am not sure the way we use is best or not, but it works so far. [1] https://wiki.openstack.org/wiki/ReleaseNotes/Icehouse [2] https://wiki.openstack.org/wiki/ReleaseNotes/Icehouse/ja Akihiro

4 7

Including the final : with strings
by Douglas Fish 02 May '14

02 May '14

There is a bug and associated code review open for Horizon regarding how to handle the trailing ":" on some messages: The Bug: https://bugs.launchpad.net/horizon/+bug/1296075 The Code Review: https://review.openstack.org/#/c/84342/ The bug and existing code advocate removing the final ":" from strings that have it for consistency. While I understand the need for consistency, I just got a request from a French translator to do the opposite implementation. The translator for French shared with me that including the punctuation as part of the translatable material makes it much easier to create a correct translation. In French, a space is expected between the final word and the final punctuation, including a colon. When the translators are looking at "Image Details:", its much easier from them to recognize where the space should go so they can create "Détails de l'image :". Without the colon as part of the message its hard to know if they should add a trailing space or not. What's the feeling from the i18n community about how we should treat the final punctuation on our strings? Doug Fish

5 8

I18n meeting tomorrow
by Ying Chun Guo 02 May '14

02 May '14

Hello, all At the meeting at the beginning of April, we decided to move the Europe/India friendly meeting time 1 hour later. So let's meet on at UTC 0800 tomorrow in the channel "#openstack-meeting". We could discuss following items: * Including the final : with strings (http://lists.openstack.org/pipermail/openstack-i18n/2014-April/000573.html) * contextual-markers for better translations (http://lists.openstack.org/pipermail/openstack-i18n/2014-April/000528.html) * I18n related sessions in design summit * Open discussions See you there. Best regards Ying Chun Guo (Daisy)

3 5