From:	"Juan Manuel Guerrero" <ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De>
Organization:	Darmstadt University of Technology
To:	djgpp-workers AT delorie DOT com
Date:	Thu, 13 Sep 2001 19:06:38 +0200
Subject:	Re: NLS and djgpp.env
References:	<70829161ECD AT HRZ1 DOT hrz DOT tu-darmstadt DOT de>
In-reply-to:	<Pine.LNX.4.10.10109131836320.11084-100000@acp3bf>
X-mailer:	Pegasus Mail for Windows (v2.54DE)
Message-ID:	<708B8E6458B@HRZ1.hrz.tu-darmstadt.de>
Reply-To:	djgpp-workers AT delorie DOT com

On Thu, 13 Sep 2001, Hans-Bernhard Broeker wrote:

> On Thu, 13 Sep 2001, Juan Manuel Guerrero wrote:
> 
> > Assuming that NLS for DJGPP is welcome I would like
> > to propose to add the LANG and LANGUAGE env. variables
> > to the global part of djgpp.env. LANG is set to 'C' making
> > sure that always the english message are display by default.
> > LANGUAGE is unset at all.
> 
> I don't see why we would need these. Both only specify the same behaviour
> they would have if not present at all. I.e. they wouldn't make any
> difference whatsoever. LANG, if not set, defaults to "C", AFAIK, and same
> for LANGUAGE.
Yes, it is true. The goal was to make the radme files writing easier.
It is easier to explain that some particular env. variable in djgpp.env should
be changed than explaining to create a new one. IMHO, for a newbie changing
an existing entry in some file is easier than trying to create a new entry after
having found the appropiate section. Of course, all this depends of the
point of view.

> > If at all, it would be a good idea to set LC_COLLATE to "C",
> > lest users be badly surprised by 'grep' and other regex tools if they "set
> > LANG=de" and then use pattern like [a-z].
This should be seriously considerated.

Regards,
Guerrero, Juan M.

- Raw text -