Date: Wed, 17 Jan 2001 13:13:50 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Jason Green <news AT jgreen4 DOT fsnet DOT co DOT uk>
cc: djgpp-workers AT delorie DOT com
Subject: Re: strftime patch
In-Reply-To: <h8k96tcnnlq0b90tduvefu93ds6vj61m2j@4ax.com>
Message-ID: <Pine.SUN.3.91.1010117130918.18768A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


On Tue, 16 Jan 2001, Jason Green wrote:

> > Yes, the C locale is the only one really supported by DJGPP.
> 
> FYI, there was also a URL for some patches posted to c.o.m.d recently
> to add locale support to DJGPP, in case you missed it.

Yes, I saw it (and saved it for future references).  But those patches 
are only part of the job.  They lay down the infrastructure for 
supporting other locales, by providing low-level functions for 
communicating with DOS/Windows and getting/setting the locale-dependent 
options maintained by the OS.  But the larger and more problematic part 
of supporting locales---the one which makes library functions such as 
strcmp, tolower, strftime, strcoll, etc. honor the locale---this part is 
still awaiting motivated individuals.

> FWIW, the test program I gave with the patches, has exact same
> behaviour on my Linux setup as with DJGPP with the first patch only.

So you are in effect saying that glibc, at least the version you use, is 
incompatible with C9x?