Message-Id:	<200007181916.VAA09092@mailgw3.netvision.net.il>
Date:	Tue, 18 Jul 2000 22:16:04 +0200
To:	"Tim Van Holder" <zastai AT hotmail DOT com>
X-Mailer:	Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
CC:	djgpp AT delorie DOT com, ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De
In-reply-to:	<F272GXix4A2DreBBsQw00003715@hotmail.com> (zastai@hotmail.com)
Subject:	Re: ANNOUNCE: DJGPP port of GNU gettext-0.10.35
References:	<F272GXix4A2DreBBsQw00003715 AT hotmail DOT com>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: "Tim Van Holder" <zastai AT hotmail DOT com>
> Date: Tue, 18 Jul 2000 12:09:34 GMT
>
> I do not feel it is excessive to ask of the people making 
> the DJGPP distributions to have perl, autoconf, and automake.

I do feel that this is excessive.

> In any case, true out-of-the box NLS support would be impossible anyway; the 
> translation project almost always uses latin1 as charset for its PO files 
> (or the relevant charset for non-latin text). So the maintainer would have 
> to use recode to convert the PO file to, say, code pages 437 and 850 (they 
> seem the most widespread) before formatting them (and preferably update the 
> PO file header to reflect the charset change).

Juan's port has a provision for this, so this problem is not an issue
anymore.

> the PO files would need to be available in pretty much every IBM
> codepage

No, you only need to translate each .po file into the codepage that
supports the same locale.

- Raw text -