On Fri, 9 Jul 2004, Denis Barbier wrote:
> On Thu, Jul 08, 2004 at 02:47:10PM -0700, Martin Quinson wrote:
> > Package: gettext
> > Version: 0.14.1-2
> > Severity: normal
> >
> > Hi there,
> >
> > When asked to extract the following line:
> > INVALID_BASENAME=$(gettext 'Invalid basename: %s.\n')
>
Olaf Meeuwissen wrote:
> I think I like the /bin/sh solution by Santiago Vila better for
> portability reasons, but this one seems to offer a handle for
> integration in my automake/autoconf/gettext build machinery.
> Any ideas? Does gettext support shell scripts out of the box?
On 16 May 2002, Olaf Meeuwissen wrote:
> I'd swear I saw it fly by on one of the debian lists I subscribe to,
> but now I can't find it for the life of me.
>
> How do I internationalize my shell scripts?
>
> The C parts of the package are already using AM_GNU_GETTEXT if that
> makes a diference.
On Thu, 7 Mar 2002, Jordi Mallach wrote:
> On Thu, Mar 07, 2002 at 01:23:15PM -0600, Manoj Srivastava wrote:
> > I note that Debian has .po files for 2.5.4a, whereas the
> > translation project only has translations for version 2.5,2. Since
> > you were the maintainer when the i18n patches w
On Thu, 7 Mar 2002, W. L. Estes wrote:
> > The work it would take to update the .po files should not be an issue.
>
> My main concern is this: the i18n work on flex was done for the debian
> distribution and is not a part of the main flex tree. I am unfamiliar
> with gettext and how to incorporate
Manoj Srivastava wrote:
> Will> I'm not familiar with gettext but I would like the flex distribution
> Will> to have i18n support and any pointers you can offer in this regard
> Will> would be greatly appreciated.
>
>I'll have to call in some other folks who did the heavy
> lifting for
Gustavo Noronha Silva wrote:
> Martin Quinson <[EMAIL PROTECTED]> wrote:
> > That's the sh (inefficient) way. In bash, you can use the
> > following shorthand: $"My message"
> great that is just what I wanted! thank you very much, thanks too,
> Javier!
Just what I don't want: People adding more an
On Thu, 22 Jul 1999, Wichert Akkerman wrote:
> Previously Ian Jackson wrote:
> > Is i18n support currently enabled or disabled in the stable and
> > unstable versions of dpkg ? There have been a number of problems with
> > it, I know - coredumps in some i18n function.
>
> Enabled for unstable an
On Tue, 3 Nov 1998, Petr Kolar wrote:
>There is the question how to set locale's environment variables. If you
> use short form (cs, fr, de, ...) the glibc locale files from cs_CZ, fr_FR,
> etc. will be ignored. If you use longer form (cs_CZ, fr_FR, de_DE), the
> locales are taken from xx_XX
On Sun, 1 Nov 1998, Ian Jackson wrote:
> Over the next weeks and months I expect to be un-reorganising dpkg's
> build system to look more like the way it used to. As part of this
> I'm considering dropping gettext in favour of catgets.
Well, I don't know much about catgets but gettext manual say
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" p
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&quo
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
On Wed, 19 Aug 1998, Michael Sobolev wrote:
> Yes, this helps. Thank you.
>
> Before posting my question, I have checked all documentation avaiable. I
> could not find any reference to TEXTDOMAIN environment variable. Where have
> you learned about that?
Good question :-)
Maybe in bash sourc
On Mon, 17 Aug 1998, Michael Sobolev wrote:
> I am trying to figure out how to localize bash scripts. Can anybody give me a
> hint where I could look for the information? The info files for bash only
> speak about $"..." construct, which permits to use appropriately localized
> strings. But whe
-BEGIN PGP SIGNED MESSAGE-
On 29 Jul 1998 [EMAIL PROTECTED] wrote:
> [...]
> Then we can localize an internationalized package. For many languages
> And everybody agrees that there is no reason to keep in one package
> all localized versions.
I disagree. The FSF also disagrees. All GNU
-BEGIN PGP SIGNED MESSAGE-
On Thu, 19 Mar 1998, Nicolás Lichtmaier wrote:
> > > > But putting the .pot files as a part of the ordinary binary package
> > > > would
> > > > not be the right thing to do.
> > >
> > > Look:
> > >
> > > -rw-r--r-- 1 root root 5824 Mar 14 23:45
-BEGIN PGP SIGNED MESSAGE-
On Thu, 19 Mar 1998, Nicolás Lichtmaier wrote:
> > But putting the .pot files as a part of the ordinary binary package would
> > not be the right thing to do.
>
> Look:
>
> -rw-r--r-- 1 root root 5824 Mar 14 23:45
> /usr/doc/lftp/lftp.pot.gz
I
-BEGIN PGP SIGNED MESSAGE-
On 18 Mar 1998, Milan Zamazal wrote:
> If I could find *.po files somewhere on my disk (no, I don't
> have time to bother with fetching and exploring source packages), I'd
> consider to translate several of them myself.
We could make then a .deb package of all
-BEGIN PGP SIGNED MESSAGE-
On Tue, 17 Mar 1998, Nicolás Lichtmaier wrote:
> gettext already must be in main. Without it,, dpkg, shellutils, bash,
> etc are non-free software.
What are you saying? gettext is free software, but it is not finished, so
its author asked me not to distribut
-BEGIN PGP SIGNED MESSAGE-
On Tue, 10 Mar 1998, Nicolás Lichtmaier wrote:
> > > I have done so with xinvaders. This way we can encourage users to
> > translate
> > >it and send it to the maintainer.
> > I believe this is a waste of disk space. Translators can get it as well
> > from th
-BEGIN PGP SIGNED MESSAGE-
I need help on this.
In pine-3.96L/pico/composer.c, should I replace ^D in
{"^D", "Del Char", KS_NONE}
by something else?
Thanks.
*-- Forwarded message --
Date: Fri, 31 Oct 1997 22:09:26 + (GMT)
From: Mark Baker <[EMAIL PROTECTED]>
To: [E
-BEGIN PGP SIGNED MESSAGE-
Jeroen van der Most:
> So both flavors are possible and used. We should decide which of these two
> possibilities makes the most sense.
We could also ask bash upstream maintainer about this.
-BEGIN PGP SIGNATURE-
Version: 2.6.3ia
Charset: latin1
iQCVAg
23 matches
Mail list logo
