From: Radical DOT NetSurfer AT delorie DOT com Newsgroups: comp.os.msdos.djgpp Subject: Re: Possible bug Date: Mon, 24 Sep 2001 08:37:46 -0400 Organization: Posted via Supernews, http://www.supernews.com Message-ID: <2v9uqtoj5j7l6qkt8ql3313rjusephclg3@4ax.com> References: X-Newsreader: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: newsabuse AT supernews DOT com Lines: 54 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com I should try to unbury that old FileRename program and see if it works now... I think we finally converted it to borland 16 and 32-bit just to get the proper (expected) behavior from it. wouldn't of even gotten into it if websites and usenet users didn't use such funky characters (deliberately). and I wouldn't of mentioned it here at all, except, honestly, I really do get Emails on occasion (last month) concerning this issue. And not everyone has upgraded to 2.03 (I have )!! It was never my intention to "scare" anyone at all... infact, if users are moving over to 2.03 (and I hear a later update is on the horizon), then any special code they have in their projects to fix "quirks" in 2.01 should probably be removed __if__ things are fixed now. And I say, it never hurts to be cautious. (even in Borland...) DJGPP is awesome! No one is putting it down; just suggesting testing things thoroughly, which never hurts. //the Radical NetSurfer Kind of Guy// On Mon, 24 Sep 2001 12:10:41 +0200 (IST), Eli Zaretskii wrote: > >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.