Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 9 Jun 2005 10:05:06 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Unicode in filenames support? (FAQ update needed) Message-ID: <20050609080506.GB19050@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <94BF3137C62D3E4CAED7E97F876585F09DA9B7 AT pauex2ku08 DOT agere DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <94BF3137C62D3E4CAED7E97F876585F09DA9B7@pauex2ku08.agere.com> User-Agent: Mutt/1.4.2i On Jun 8 18:20, Williams, Gerald S (Jerry) wrote: > (I don't necessarily expect that there will be any interest > in my solution, but I thought that I should mention it just > in case. As I said, there are other ways to deal with this > without imposing path length limitations, and I don't even > know how much of a concern such limits are in general.) Of course we would be glad to have more people working on the DLL (and sign the copyright assignment, sigh), but what you wrote sounds somewhat like a special solution which requires lots of new "if (is_ntfs)" tests, roughly. Sure it only works on file systems supporting that (which is NTFS, basically), but the code already contains way too many different routes due to OS/FS differences. Our vague ideas how to implement this are more along the lines of "always use the fooW (on Win32 level) or _U (on NT level) functions and drop back to something else only on 9x, if necessary". This would also automatically cover the managed mounts in terms of path length. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/