From:	"Juan Manuel Guerrero" <ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De>
Organization:	Darmstadt University of Technology
To:	salvador <salvador AT inti DOT gov DOT ar>
Date:	Thu, 2 Aug 2001 23:38:23 +0200
MIME-Version:	1.0
Subject:	Re: gettext port
CC:	JT Williams <jeffw AT darwin DOT sfbr DOT org>, Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>,
	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
X-mailer:	Pegasus Mail for Windows (v2.54DE)
Message-ID:	<31D25F35EBD@HRZ1.hrz.tu-darmstadt.de>
Reply-To:	djgpp-workers AT delorie DOT com

 Date:          Thu, 02 Aug 2001 17:55:36 -0300
 From:          salvador <salvador AT inti DOT gov DOT ar>

> Eli Zaretskii wrote:
>
> > On Wed, 1 Aug 2001, salvador wrote:
> > > In the past I shipped Linux version of my .mo files in ISO-8859-1 and DOS
> > > version in 850. So the installed translations match with the system.
> > > No translation needed, so no memory nor speed overhead was introduced.
> >
> > But the downside is that you need to produce a separate message
> > catalogue for each possible codepage.  For example, with Cyrillic
> > languages, there are half a dozen possible encodings, maybe more.
>
> I understand it, but in any case you need some user setup. How the program
> will know to what code page to translate? DOS have a call for it, but it could
> return a wrong value and in Linux things are even more complicated.

The possibility of a DOS call use has been descarted due some difficulties.
DOS sometimes lies about the codepage in use.

The user must _always_ set the lang environment variable in djgpp.env.
This variable is inspected by gettext and libiconv and the the appropiate codepage
is extracted from from the file: charset.alias located in DJDIR/lib.
If LANG is not set, then it defaults to `C' this ia ascii.

Regards,
Guerrero, Juan M.

- Raw text -