Sender: root AT delorie DOT com
Message-ID: <39075832.E26FAD3F@inti.gov.ar>
Date: Wed, 26 Apr 2000 17:57:22 -0300
From: salvador <salvador AT inti DOT gov DOT ar>
Organization: INTI
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.38 i686)
X-Accept-Language: es-AR, en, es
MIME-Version: 1.0
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC: djgpp-workers AT delorie DOT com
Subject: Re: GNU Gettext and NLS support for DJGPP
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1000425111640 DOT 23128D-100000 AT is> <3905A626 DOT CFC761CB AT inti DOT gov DOT ar> <200004261100 DOT HAA23646 AT indy DOT delorie DOT com> <3906EC04 DOT 71A8982D AT inti DOT gov DOT ar> <200004262010 DOT QAA24178 AT indy DOT delorie DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Eli Zaretskii wrote:

> > Date: Wed, 26 Apr 2000 10:15:49 -0300
> > From: salvador <salvador AT inti DOT gov DOT ar>
> >
> > > Perhaps.  All I know is the encoding is in the .po and .gmo files, so
> > > you could use that info if you wanted.
> >
> > Do you have any idea of how can it be? I generate the .mo (.gmo)  files without
> > giving any information about encoding, and I generate PC437 and ISO-1 versions.
>
> I never looked close enough at this, so perhaps you know more than I
> do.
>
> We could ask the people involved in the Translation Project for some
> help, though.  In particular, Francois Pinard, the author of recode
> and a co-author of gettext, is a very helpful guy,

I agree any suggestion should be tried with Francois first.
I got very different replies from Francois and Ulrich when I complained about a
xgettext "feature".

> and he *does* have
> sympathies for DJGPP.

I don't know about it, but I can say Francois takes the things in a very different
way.

> > I think the better way is to just modify the compilation process. I'm not too
> > familiar with autoconf/automake but I think it can be achieved using these tools.
> > You just need to modify the rules to create a .mo. Instead of just calling the
> > tool that converts .po to .mo you just recode the .po file into a temporal file
> > and then generate the .mo from the temporal.
>
> In the short run this is probably easier.
>
> But Someone (tm) needs to do the actual work ;-)

:-)), yeap. I don't know much about auto* tools but I have some experience with the
gettext tools.

SET

--
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Visit my home page: http://welcome.to/SetSoft or
http://www.geocities.com/SiliconValley/Vista/6552/
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
                    set AT ieee DOT org set-soft AT bigfoot DOT com
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013