Date:	Wed, 26 Apr 2000 16:10:42 -0400 (EDT)
Message-Id:	<200004262010.QAA24178@indy.delorie.com>
From:	Eli Zaretskii <eliz AT delorie DOT com>
To:	salvador AT inti DOT gov DOT ar
CC:	djgpp-workers AT delorie DOT com
In-reply-to:	<3906EC04.71A8982D@inti.gov.ar> (message from salvador on Wed, 26
	Apr 2000 10:15:49 -0300)
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>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> 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, and he *does* have
sympathies for DJGPP.

> 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 ;-)

- Raw text -