Hammer... i18n?

Support
1

I was playing around with hammer, and I noticed there are lots of
english strings… for help text, headers, and labels on output. I did
not see antying which led me to deliver they were localized. Is that
accurate? If so, I would suggest we take time now to ge that in since
the katello guys are starting to create evern more commands.

– bk

2

Sending to dev list.

··· -------- Original Message -------- Subject: Hammer... i18n? Date: Tue, 10 Dec 2013 18:18:07 -0500 From: Bryan Kearney To: foreman-users@googlegroups.com

I was playing around with hammer, and I noticed there are lots of
english strings… for help text, headers, and labels on output. I did
not see antying which led me to deliver they were localized. Is that
accurate? If so, I would suggest we take time now to ge that in since
the katello guys are starting to create evern more commands.

– bk

3

> Sending to dev list.
>
>
>
> Subject: Hammer… i18n?
> Date: Tue, 10 Dec 2013 18:18:07 -0500
> From: Bryan Kearney <bkearney@redhat.com>
> To: foreman-users@googlegroups.com
>
> I was playing around with hammer, and I noticed there are lots of
> english strings… for help text, headers, and labels on output. I did
> not see antying which led me to deliver they were localized. Is that
> accurate? If so, I would suggest we take time now to ge that in since
> the katello guys are starting to create evern more commands.
>

we were discussing how we could potentially generate all of the argument,
text etc within foreman, so we could control it from one place, and make
hammer auto adjust to presence of plugins.

I have no idea how far ahead Martin is on this topic, but if we go though
that route, we could use the same translations.
however, I would expect that it would not make it for 1.4 release timeframe.

··· On Wed, Dec 11, 2013 at 1:18 AM, Bryan Kearney wrote: > -------- Original Message --------

– bk

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

4

There's a tracker issue here, though it needs some planning:
http://projects.theforeman.org/issues/3666

··· On 10/12/13 23:18, Bryan Kearney wrote: > Sending to dev list. > > > -------- Original Message -------- > Subject: Hammer... i18n? > Date: Tue, 10 Dec 2013 18:18:07 -0500 > From: Bryan Kearney > To: foreman-users@googlegroups.com > > I was playing around with hammer, and I noticed there are lots of > english strings.. for help text, headers, and labels on output. I did > not see antying which led me to deliver they were localized. Is that > accurate? If so, I would suggest we take time now to ge that in since > the katello guys are starting to create evern more commands.

–
Dominic Cleal
Red Hat Engineering

5

In the meantime, can we add i18n feature? We can always reduce the
strings which need to be translated. I am assuming help text and some
column headings may not come from the server.

– bk

··· On 12/11/2013 02:23 AM, Ohad Levy wrote: > > > > On Wed, Dec 11, 2013 at 1:18 AM, Bryan Kearney > wrote: > > Sending to dev list. > > > > -------- Original Message -------- > Subject: Hammer... i18n? > Date: Tue, 10 Dec 2013 18:18:07 -0500 > From: Bryan Kearney <bkearney@redhat.com > > To: foreman-users@googlegroups.com > > > I was playing around with hammer, and I noticed there are lots of > english strings.. for help text, headers, and labels on output. I did > not see antying which led me to deliver they were localized. Is that > accurate? If so, I would suggest we take time now to ge that in since > the katello guys are starting to create evern more commands. > > > we were discussing how we could potentially generate all of the > argument, text etc within foreman, so we could control it from one > place, and make hammer auto adjust to presence of plugins. > > I have no idea how far ahead Martin is on this topic, but if we go > though that route, we could use the same translations. > however, I would expect that it would not make it for 1.4 release timeframe.