Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Sun, 8 May 2005 19:07:31 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: i18n: readdir API implementation Message-ID: <20050508230731.GE3896@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <427CAB04.9040704@msa.hinet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i On Sun, May 08, 2005 at 12:55:39PM -0700, Joshua Daniel Franklin wrote: >On 5/7/05, Shaddy Baddah wrote: >>Primarily, I am interested in the rationale behind using the ASCII >>variants of the w32api system calls, FindFirstFileA and FindNextFileA, >>as opposed to using the wide-character variants FindFirstFileW and >>FindNextFileW. > >I believe the reason is simply that the Cygwin implementation predates >good Unicode support in Windows and so it wasn't an option in the first >place. I'm sure that patches would be carefully considered, though I >vaguely remember someone (Japanese?) having a patched >Unicode-supporting Cygwin DLL that did not fail gracefully on Win9x. >It ought to fail gracefully. It's more than that. You can't just change readdir, wipe your hands together and say "that's done!" Changing readdir means changing the rest of cygwin, too. That is not a trivial undertaking. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/