On Mon, Jan 3, 2011 at 3:34 PM, seth vidal wrote:
> On Mon, 2011-01-03 at 07:58 +0100, tim.laurid...@gmail.com wrote:
>
> > I agree that i18n is kind of a pain sometime, much easier if
> > everybody talked danish :)
> > I think that unicode is the issue, not i18n.
> >
On Mon, 2011-01-03 at 07:58 +0100, tim.laurid...@gmail.com wrote:
> I agree that i18n is kind of a pain sometime, much easier if
> everybody talked danish :)
> I think that unicode is the issue, not i18n.
> Fine with med to do a yumutils.i18n there do a wrapper arou
On Mon, Jan 3, 2011 at 7:03 AM, tim.laurid...@gmail.com <
tim.laurid...@gmail.com> wrote:
>
>
> On Mon, Jan 3, 2011 at 4:02 AM, James Antill wrote:
>
>> On Thu, 2010-12-30 at 15:06 +0100, tim.laurid...@gmail.com wrote:
>> > I have added the first steps to get translation support into
>> > yum-util
On Mon, Jan 3, 2011 at 4:02 AM, James Antill wrote:
> On Thu, 2010-12-30 at 15:06 +0100, tim.laurid...@gmail.com wrote:
> > I have added the first steps to get translation support into
> > yum-utils.
> >
> > Currently only the yum-plugin-aliases has been modified to support
> > translations, becau
On Thu, 2010-12-30 at 15:06 +0100, tim.laurid...@gmail.com wrote:
> I have added the first steps to get translation support into
> yum-utils.
>
> Currently only the yum-plugin-aliases has been modified to support
> translations, because it already has _() wrappers.
This needs to be done, eventua
I have added the first steps to get translation support into yum-utils.
Currently only the yum-plugin-aliases has been modified to support
translations, because it already has _() wrappers.
Added translation support to another tool or plugin is done by adding
*
from kitchen.i18n import easy_gette
