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 Message-ID: Date: Sun, 8 May 2005 12:55:39 -0700 From: Joshua Daniel Franklin Reply-To: Joshua Daniel Franklin To: cygwin@cygwin.com Subject: Re: i18n: readdir API implementation In-Reply-To: <427CAB04.9040704@msa.hinet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <427CAB04.9040704@msa.hinet.net> X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j48KuKGn020643 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. -- 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/