> > Mark any internationalizable string this way:
> > before: echo "Hello"
> > after : echo $"Hello"
> great. Can we put the necessary code into an essential package so that
> all scripts can source the additional code!?
Which extra code? All you need is already built into bash >2.0 !
We may
Nicolás Lichtmaier <[EMAIL PROTECTED]> writes:
> Mark any internationalizable string this way:
>
> before: echo "Hello"
> after : echo $"Hello"
great. Can we put the necessary code into an essential package so that
all scripts can source the additional code!?
Thanks
Christian
--
Christ
Sven Rudolph <[EMAIL PROTECTED]> writes:
> Enrique Zanardi <[EMAIL PROTECTED]> writes:
>
> > On Sun, 14 Dec 1997, Nicolás Lichtmaier wrote:
> >
> > > Bash scripts can now easily internationalized with gettext.
> >
> > Ha! If we have known that a few months ago perhaps we wouldn't have
> > sta
Enrique Zanardi <[EMAIL PROTECTED]> writes:
> On Sun, 14 Dec 1997, Nicolás Lichtmaier wrote:
>
> > Bash scripts can now easily internationalized with gettext.
>
> Ha! If we have known that a few months ago perhaps we wouldn't have
> started rewriting the boot-floppies dinstall script in C. :-)
On Sun, 14 Dec 1997, Nicolás Lichtmaier wrote:
> Bash scripts can now easily internationalized with gettext.
Ha! If we have known that a few months ago perhaps we wouldn't have
started rewriting the boot-floppies dinstall script in C. :-)
Well, now that ~60% has been rewritten it's not appeali
Bash scripts can now easily internationalized with gettext.
Here's how:
Indicate the package's name when the scripts starts by adding a...
TEXTDOMAIN=package_name
Mark any internationalizable string this way:
before: echo "Hello"
after : echo $"Hello"
That tells bash (2.0) to look for th
6 matches
Mail list logo
