- OpenStack-I18n - lists.openstack.org

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

New meeting time tomorrow?
by Julie Pichon 30 Apr '14

30 Apr '14

Hi Daisy and all, At the meeting at the beginning of April [1] we talked about moving the 0700UTC meeting to one hour later. The wiki page [2] hasn't been updated yet though, so I'd like to confirm at what time the meeting is planned tomorrow? Thanks, Julie [1] http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2014/opensta… [2] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting

2 2

https://www.transifex.com/projects/p/openstack/language/<lang> links broken
by Tom Fifield 30 Apr '14

30 Apr '14

Hi, The latest update of Transifex broken the links to the language team pages showing all resources. eg https://www.transifex.com/projects/p/openstack/language/id used to show all of the things you could translate into Indonesian. These were really useful, since they provided a "home" for the particular language team. So far, I haven't been able to find an alternative to this, so we will need to send people to specific projects eg manuals or horizon. On the API side of things, we probably need to make the following change: - “outsource”: openstack, + “team”: 670, Regards, Tom

2 2

API-Quick Starts ready in French and Spanish
by Andreas Jaeger 29 Apr '14

29 Apr '14

Looking at the api-site project, I see that some teams have done great progress and translated 100 per cent. Congratulations! API-Quick-start: French, Spanish API-Guide: Chinese, German Unfortunately, the API Guide is not ready to publish (in English), so this allows us only to publish the API-Quick-Start. I'll setup some jobs to publish these soon so that the teams can review their work and we can decide how to link them from docs.openstack.org, 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

1 0

django_openstack_auth translation setup?
by Andreas Jaeger 27 Apr '14

27 Apr '14

Hi translation team, I'm trying to fix some more translation jobs and run into a issue with the django_openstack_auth setup. django_openstack_auth setup looks broken, the job fails to run since it expects: django_openstack_auth/locale/django_openstack_auth.pot but the repository uses: openstack_auth/locale/openstack_auth.pot I can fix this but need a bit of guidance here. Where this should get added for translation - will this be a resource in the horizon project in transifex - as it was in havana? And is the name django.po for the LC_MESSAGES file really correct in the repo? Btw. Jenkins output: https://jenkins.openstack.org/job/django_openstack_auth-upstream-translatio… 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 10

Re: [Openstack-i18n] [horizon] contextual-markers for better translations
by François Bureau 24 Apr '14

24 Apr '14

Hello all, Today, we have talked with Yves-Gwenaël about this e-mail. He didn’t' received any answers and I think we need to discuss about it. I would like to know one thing, if we change a marker for a string are we going to lose the related current translation ? For example : currently I have somewhere month = gettext("May") So in transifex I have a string May I have translated in "Mai" (in French) If tomorrow you change into the code month = pgettext("month name", "May") Do we lost the translation already done in Transifex ? Or is it just going to add the context in the string already translated ? If we lost the translation already, for me adding the context into already translated string is a bad idea. We are going to lose too much work. And in this case the context markup has to be used only for new strings. I prefer to keep the legacy for old strings. Thanks a lot for your answers :) Best regards, François Bureau Responsable Centre de Contact E-mail : francois.bureau(a)cloudwatt.com Mobile : 06 40 76 18 01 http://www.cloudwatt.com ----- Mail transféré ----- De: "Yves-Gwenaël Bourhis" <yves-gwenael.bourhis(a)cloudwatt.com> À: openstack-i18n(a)lists.openstack.org Envoyé: Lundi 14 Avril 2014 17:13:27 Objet: [Openstack-i18n] [horizon] contextual-markers for better translations Hi all, I noticed that translating to certain languages requires some compromises in both grammar and syntax to often have a deceiving result... This is due to the fact that we do not use contextual-markers: https://docs.djangoproject.com/en/dev/topics/i18n/translation/#contextual-m… except in one unique place: https://bugs.launchpad.net/horizon/+bug/1307476 The context is required because a word which is spelled the same in English may be 2 different words in an other language. Even less trivial, a same word with the same meaning can be spelled differently depending on the way it is used in a sentence, and there the context is really important. Some work was already done with https://bugs.launchpad.net/horizon/+bug/1253678 But contextual-markers need to be added to many translatable strings. The issue about changing translatable strings to contextual translatable strings implies redoing all those translations. Do not PANIC :-) , the current translations will remain as is for Icehouse, the impact of using contextual-markers will be for Juno. My concern is that many other languages than my 2 native ones have a richer syntax, so I may not be aware of all possible contexts required for other languages to be properly translatable. Concerning the example I gave in https://bugs.launchpad.net/horizon/+bug/1307476 any comment on the "context" you would need to help you make a better translation will be welcomed, and I'll need your feedback on what context "you" need and in which place in the dashboard, in order to help you make the best translations. So feel free to drop a reply to this mail with all the places where your struggle to provide a translation due to lack of context and where a context and reformulation would really help you do your translations. Thank you all. -- Yves-Gwenaël Bourhis _______________________________________________ Openstack-i18n mailing list Openstack-i18n(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

2 1