On Thu, 3 Sep 1998, Michael Sobolev wrote:
> On Thu, Sep 03, 1998 at 06:15:04PM +0200, Santiago Vila wrote:
> > [ There could be several ways to split it. I was thinking about a
> > somewhat radical way of splitting it: We could have a
> > "gettext-program" package containing just /usr/bin/get
On Thu, Sep 03, 1998 at 06:15:04PM +0200, Santiago Vila wrote:
> [ There could be several ways to split it. I was thinking about a
> somewhat radical way of splitting it: We could have a
> "gettext-program" package containing just /usr/bin/gettext ].
I do not think that it is practical: a progr
On Thu, 3 Sep 1998, Michael Sobolev wrote:
> On Thu, Sep 03, 1998 at 02:05:13PM +0200, Santiago Vila wrote:
> > [...]
> > The "portable" one:
> >
> > #!/bin/sh
> > export TEXTDOMAIN=fileutils
> > gettext -s "can not change to null group"
> > gettext -s "virtual memory exhausted"
>
> I believe th
On Thu, Sep 03, 1998 at 02:05:13PM +0200, Santiago Vila wrote:
> I think so. It seems we have two possible ways to make a shell script to
> talk "foreign" languages:
>
> The "easy" one:
>
> #!/bin/bash
> export TEXTDOMAIN=fileutils
> echo $"can not change to null group"
> echo $"virtual memory ex
On Tue, 25 Aug 1998, Michael Sobolev wrote:
> Now, when I know how to write localized scripts for bash, I am not sure that
> it is a good idea to create such scripts for {post,pre}{inst,rm}. I want to
> know whether my concerns are correct and would the use of `gettext' command
> be the only solu
Hi.
Now, when I know how to write localized scripts for bash, I am not sure that
it is a good idea to create such scripts for {post,pre}{inst,rm}. I want to
know whether my concerns are correct and would the use of `gettext' command
be the only solutions for any shell?
Thanks,
--
Mike
6 matches
Mail list logo
