Date: Mon, 24 Sep 2001 12:10:41 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: djgpp AT delorie DOT com Subject: Re: Possible bug In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Precedence: bulk On 24 Sep 2001, A. Sinan Unur wrote: > Mostly because DJGPP only implements the C and POSIX locales as Eli pointed > out some time ago. By the way, I have looked at the source code, and looked > into how *nix systems as well as cygwin implements this, and it seems like > more work than I can do at this time. It's a _lot_ of work. Even the minimal support, only for UTF-8, needs large tables and non-trivial code to get it right. I really wish we could add that, but it will take motivated individual(s) with enough resources to make it happen. Unfortunately, I don't have such resources, and won't have them any time soon... Volunteers are welcome, as usual. > i don't know what those characters are and i am curious to understand what > specifically the problem is. can you post an example? > > sample program to test toupper and isalpha below: Yes, it all works in DJGPP v2.03. A few subtle bugs were fixed between v2.02 and v2.03, as the "What's Changed" node in the Knowledge Base document describes.