Date: Fri, 21 Apr 2000 03:38:27 -0400 (EDT)
Message-Id: <200004210738.DAA16970@indy.delorie.com>
From: Eli Zaretskii <eliz AT delorie DOT com>
To: "Juan Manuel Guerrero" <ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De>
CC: djgpp-workers AT delorie DOT com
In-reply-to: <18478AC39D3@HRZ1.hrz.tu-darmstadt.de>
	(ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De)
Subject: Re: ANNOUNCE: DJGPP port of GNU Gettext 0.10.35
References:  <18478AC39D3 AT HRZ1 DOT hrz DOT tu-darmstadt DOT de>
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
Precedence: bulk


> From: "Juan Manuel Guerrero" <ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De>
> Date: Thu, 20 Apr 2000 22:43:27 +0200
>
> This is a port of GNU Gettext 0.10.35 to MSDOS/DJGPP.

Thank you for your work!

Allow me a few comments.

> 1) The gettext function from libintl.a has been renamed to GetText.
>    The function is now available as GetText and also as gettext__.

Is this a good idea?  

If I understand correctly, it means that packages which use libintl.a
will not be able to be configured and built for DJGPP without tweaking
their configury stuff.

The changes you did in gettext.m4 file won't help here, since every
GNU package comes with its own copy of gettext.m4, and their configure
scripts were already produced using that copy.  So users who want to
build packages with NLS support will need to replace gettext.m4
(actually, edit it, since gettext.m4 is actively developed, and gets
new changes from time to time), then run autoconf before they can
configure.

Could you please explain why did you think such a change was
necessary?

If the problem is with gettext from conio.c, then I think this problem
could be solved with less radical means.

>    The source packages must be configured by the user because:
>    1) The configure script searches for emacs.

You could replace the references to Emacs with
$DJDIR/gnu/emacs/bin/emacs, I think.

>    2) The libtool script would contain absolute paths that make
>       reference to my installation tree.

Doesn't /dev/env/DJDIR help here?