X-Spam-Check-By: sourceware.org Message-ID: <456F19E2.C5AC20BF@dessent.net> Date: Thu, 30 Nov 2006 09:50:26 -0800 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Windows NTFS UCS2 characters References: <456F0E89.28B2E427@dessent.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 Igor Peshansky wrote: > > So you're limited to ANSI filenames in the current codepage, I think. > > Not sure what ANSI means in this context (if you meant ASCII, or 7-bit, > then the codepage reference makes no sense). If the codepage is set > correctly, Cygwin will read those files. I meant ANSI in the context of the win32 API, i.e. -A/-W. I realize that ANSI here is not really the proper term, but I could not think of a more compact way to say "filenames consisting entirely of code points belonging to the current 8-bit code page." http://blogs.msdn.com/oldnewthing/archive/2004/05/31/144893.aspx Brian -- 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/