Hi translators, Clark and Doug, to translate log messages, Doug has been working on having these in separate domains. That way translators can decide what to translate: User visible strings, info log messages, warning log messages, error log messages, or critical log messages. The base work is done in oslo and now we need to setup the tools to extra these for separate domains. Based on input from Doug and Clark and the existing blueprint https://blueprints.launchpad.net/oslo/+spec/log-messages-translation-domain-... I created a first patch for our jobs that upload to and import from transifex. I would like review comments on it: https://review.openstack.org/95377/ Before this goes in, we need to add the new domains to transifex, I plan to setup everything for this properly - so this is also a heads-up for coming changes. Translators, once this is in, you will see additional domains - I suggest to ignore those for now and concentrate on the normal ones. As an example, for nova, you will see besides the current nova-translations resource additionally: nova-log-error-translations, nova-log-warning-translations, nova-log-critical-translations, nova-log-info-translations. Note that I will rework this patch if my patch for creating common functions for all translation jobs gets positive review and would appreciate your review of that one as well: https://review.openstack.org/95345 Clark, this is a followup to an IRC discussion you had with Doug on 19 Dec, 2013. Translation team, I'll inform you once everything is setup, Andreas -- Andreas Jaeger aj@{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
Hello, Andreas I think the new patch is based on the new Oslo library. So the new jobs would only be enabled after projects adopt new Oslo lib and developers make changes to their source codes. It will take a long time. But we could select a project to do the first PoC. Which project could be the best choice for the first Poc? Best regards Ying Chun Guo (Daisy) Andreas Jaeger <aj@suse.com> wrote on 2014/05/26 01:39:17:
Andreas Jaeger <aj@suse.com> 2014/05/26 01:39
To
"openstack-i18n@lists.openstack.org" <openstack- i18n@lists.openstack.org>, Doug Hellmann <doug.hellmann@dreamhost.com>, Clark Boylan <clark.boylan@gmail.com>,
cc
Subject
[Openstack-i18n] Translation of log messages
Hi translators, Clark and Doug,
to translate log messages, Doug has been working on having these in separate domains. That way translators can decide what to translate: User visible strings, info log messages, warning log messages, error log messages, or critical log messages. The base work is done in oslo and now we need to setup the tools to extra these for separate domains.
Based on input from Doug and Clark and the existing blueprint https://blueprints.launchpad.net/oslo/+spec/log-messages- translation-domain-rollout I created a first patch for our jobs that upload to and import from transifex. I would like review comments on it: https://review.openstack.org/95377/
Before this goes in, we need to add the new domains to transifex, I plan to setup everything for this properly - so this is also a heads-up for coming changes.
Translators, once this is in, you will see additional domains - I suggest to ignore those for now and concentrate on the normal ones. As an example, for nova, you will see besides the current nova-translations resource additionally: nova-log-error-translations, nova-log-warning-translations, nova-log-critical-translations, nova-log-info-translations.
Note that I will rework this patch if my patch for creating common functions for all translation jobs gets positive review and would appreciate your review of that one as well: https://review.openstack.org/95345
Clark, this is a followup to an IRC discussion you had with Doug on 19 Dec, 2013.
Translation team, I'll inform you once everything is setup,
Andreas -- Andreas Jaeger aj@{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
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 05/30/2014 05:06 AM, Ying Chun Guo wrote:
Hello, Andreas
I think the new patch is based on the new Oslo library.
So the new jobs would only be enabled after projects adopt new Oslo lib and developers make changes to their source codes.
The scripts are written in such a way that they work with projects that use this fully, partially (most do not have critical log messages) or none (like trove and cinder).
It will take a long time.
I've seen already the first (sometimes broken) patches for this.
But we could select a project to do the first PoC. Which project could be the best choice for the first Poc?
The jobs are approved and resources are created. Sahara and neutron look like quite good translated already so those come to mind, Andreas
Best regards Ying Chun Guo (Daisy)
Andreas Jaeger <aj@suse.com> wrote on 2014/05/26 01:39:17:
Andreas Jaeger <aj@suse.com> 2014/05/26 01:39
To
"openstack-i18n@lists.openstack.org" <openstack- i18n@lists.openstack.org>, Doug Hellmann <doug.hellmann@dreamhost.com>, Clark Boylan <clark.boylan@gmail.com>,
cc
Subject
[Openstack-i18n] Translation of log messages
Hi translators, Clark and Doug,
to translate log messages, Doug has been working on having these in separate domains. That way translators can decide what to translate: User visible strings, info log messages, warning log messages, error log messages, or critical log messages. The base work is done in oslo and now we need to setup the tools to extra these for separate domains.
Based on input from Doug and Clark and the existing blueprint https://blueprints.launchpad.net/oslo/+spec/log-messages- translation-domain-rollout I created a first patch for our jobs that upload to and import from transifex. I would like review comments on it: https://review.openstack.org/95377/
Before this goes in, we need to add the new domains to transifex, I plan to setup everything for this properly - so this is also a heads-up for coming changes.
Translators, once this is in, you will see additional domains - I suggest to ignore those for now and concentrate on the normal ones. As an example, for nova, you will see besides the current nova-translations resource additionally: nova-log-error-translations, nova-log-warning-translations, nova-log-critical-translations, nova-log-info-translations.
Note that I will rework this patch if my patch for creating common functions for all translation jobs gets positive review and would appreciate your review of that one as well: https://review.openstack.org/95345
Clark, this is a followup to an IRC discussion you had with Doug on 19 Dec, 2013.
Translation team, I'll inform you once everything is setup,
Andreas -- Andreas Jaeger aj@{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
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
-- Andreas Jaeger aj@{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
On Fri, May 30, 2014 at 12:25 AM, Andreas Jaeger <aj@suse.com> wrote:
On 05/30/2014 05:06 AM, Ying Chun Guo wrote:
Hello, Andreas
I think the new patch is based on the new Oslo library.
So the new jobs would only be enabled after projects adopt new Oslo lib and developers make changes to their source codes.
The scripts are written in such a way that they work with projects that use this fully, partially (most do not have critical log messages) or none (like trove and cinder).
And the translation marker functions needed are in the incubated log code, so if a project has synced a recent version of the log module they can take advantage of those functions, too.
It will take a long time.
I've seen already the first (sometimes broken) patches for this.
But we could select a project to do the first PoC. Which project could be the best choice for the first Poc?
The jobs are approved and resources are created. Sahara and neutron look like quite good translated already so those come to mind,
I am going to go ahead and document the changes and announce on the -dev mailing list that we're ready for projects to start updating, but I do like the idea of picking one small project for the translation team to focus on at first, to make sure everything is working properly and there aren't any issues with the CI jobs. Doug
Andreas
Best regards Ying Chun Guo (Daisy)
Andreas Jaeger <aj@suse.com> wrote on 2014/05/26 01:39:17:
Andreas Jaeger <aj@suse.com> 2014/05/26 01:39
To
"openstack-i18n@lists.openstack.org" <openstack- i18n@lists.openstack.org>, Doug Hellmann <doug.hellmann@dreamhost.com>, Clark Boylan <clark.boylan@gmail.com>,
cc
Subject
[Openstack-i18n] Translation of log messages
Hi translators, Clark and Doug,
to translate log messages, Doug has been working on having these in separate domains. That way translators can decide what to translate: User visible strings, info log messages, warning log messages, error log messages, or critical log messages. The base work is done in oslo and now we need to setup the tools to extra these for separate domains.
Based on input from Doug and Clark and the existing blueprint https://blueprints.launchpad.net/oslo/+spec/log-messages- translation-domain-rollout I created a first patch for our jobs that upload to and import from transifex. I would like review comments on it: https://review.openstack.org/95377/
Before this goes in, we need to add the new domains to transifex, I plan to setup everything for this properly - so this is also a heads-up for coming changes.
Translators, once this is in, you will see additional domains - I suggest to ignore those for now and concentrate on the normal ones. As an example, for nova, you will see besides the current nova-translations resource additionally: nova-log-error-translations, nova-log-warning-translations, nova-log-critical-translations, nova-log-info-translations.
Note that I will rework this patch if my patch for creating common functions for all translation jobs gets positive review and would appreciate your review of that one as well: https://review.openstack.org/95345
Clark, this is a followup to an IRC discussion you had with Doug on 19 Dec, 2013.
Translation team, I'll inform you once everything is setup,
Andreas -- Andreas Jaeger aj@{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
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
-- Andreas Jaeger aj@{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
On 05/30/2014 04:02 PM, Doug Hellmann wrote:
On Fri, May 30, 2014 at 12:25 AM, Andreas Jaeger <aj@suse.com> wrote:
On 05/30/2014 05:06 AM, Ying Chun Guo wrote:
Hello, Andreas
I think the new patch is based on the new Oslo library.
So the new jobs would only be enabled after projects adopt new Oslo lib and developers make changes to their source codes.
The scripts are written in such a way that they work with projects that use this fully, partially (most do not have critical log messages) or none (like trove and cinder).
And the translation marker functions needed are in the incubated log code, so if a project has synced a recent version of the log module they can take advantage of those functions, too.
It will take a long time.
I've seen already the first (sometimes broken) patches for this.
But we could select a project to do the first PoC. Which project could be the best choice for the first Poc?
The jobs are approved and resources are created. Sahara and neutron look like quite good translated already so those come to mind,
I am going to go ahead and document the changes and announce on the -dev mailing list that we're ready for projects to start updating, but I do like the idea of picking one small project for the translation team to focus on at first, to make sure everything is working properly and there aren't any issues with the CI jobs.
Yeah, jobs failed this morning - I uploaded dummy projects to get them working again and expect that it works tomorrow - and my goal is to have the jobs running everywhere asap. For testing, choose one of sahara or neutron - and keep in mind that there are no critical log messages translated in either of them, Andreas -- Andreas Jaeger aj@{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
participants (3)
-
Andreas Jaeger
-
Doug Hellmann
-
Ying Chun Guo