[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: bashisms and i18n

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 that the latter is much better than the former.  As result, what do
> you think about splitting gettext package into two?  The one that could still
> be called `gettext', while second one could be called something like
> `gettext-dev'.

Yes, this could be done, but only if it is strictly necessary.

[ 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 ].

> > Or maybe the right thing to do here is to do everything in C (?)
> You mean to rewrite the post*, pre* scripts in C?

Well, that would be ugly... I was thinking about "things to be
internationalized" in general, not package maintainer scripts.

BTW: If we plan to internationalize and localize everything, including
maintainer scripts, we would have a chicken and egg problem for the
preinst scripts, because the message catalogs for them would not
be installed yet when they run...

 "2e27c842901e6235732e46e70019610d" (a truly random sig)

Reply to: