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 Message-ID: <000801c585bd$a5b20e30$6600a8c0@RossWindows> From: "Ross MacGillivray" To: References: <20050709082842 DOT GQ7507 AT calimero DOT vinschen DOT de> <20050710080521 DOT GX7507 AT calimero DOT vinschen DOT de> <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050710201331 DOT 03cee008 AT pop DOT prospeed DOT net> Subject: Re: File Naming Between Cygwin and Windows Date: Sun, 10 Jul 2005 19:09:56 -0700 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit Larry great answer. thanks /Ross ----- Original Message ----- From: "Larry Hall" To: "Ross MacGillivray" ; Sent: Sunday, July 10, 2005 5:46 PM Subject: Re: File Naming Between Cygwin and Windows > At 01:55 PM 7/10/2005, you wrote: >>Corinna Vinschen cygwin.com> writes: >> >>> >>> On Jul 10 06:03, Ross MacGillivray wrote: >>> > Corinna Vinschen cygwin.com> writes: >>> > > Usually it chokes, like the underlying OS. As a workaround you'll >>> > > find so called "managed mounts", which only work on fresh created >>> > > directories so managed mounts are no general solution. >>> > >>> > Do you know happen to know what the 'standard' solution is, when >>> > running >>> > KDE-on-Cygwin, for this incompatibility in file naming between cygwin >>> > and windows? >>> >>> There is no incompatibility in file naming between Cygwin and Windows. >>> If KDE is using filenames which are not useable on Windows, then KDE >>> is incompatibility in file naming to Windows (and Cygwin). >>> >>> Corinna >>> >> >>Yes, I agree - poor choice of words. There is no incompatibility between >>cygwin and windows. >> >>The question I was trying to raise is: >> "Is managed mounts the most appropriate work around in Cygwin for an >> issue >> which may be, admittedly, caused by KDE-on-Cygwin?" > > > It is the only way currently. > > >>Also as a future Cygwin service would it not make sense to have a >>translation >>layer in Cygwin which automatically translates conformant linux/unix names >>into >>conformant windows names. If this is what managed mounts does, I >>apologize >>in advance, since I am not familiar with managed mounts. > > > I doubt adding a translation layer to Cygwin's already complex and time- > consuming path handling code is the way to go here but I assume if someone > could come up with a patch that addressed these concerns, it might be > acceptable. But this would be a very high bar to meet. > > Managed mounts don't do a translation in the way you described. They > encode > the illegal character in a way that the Windows file system accepts. In > Windows, the file name looks quite different but in a managed mount > directory, the file looks exactly as requested. There is no mapping > of characters as you suggest in your scheme. You should look at and play > around with them a little to get a feel for how they work. > > Really, the easiest thing to do though is make the file name created be > more generally portable. This should be possible in the Cygwin port at > least, even if the upstream maintainers wouldn't consider such a change > (and I don't know that they wouldn't). > > > > -- > Larry Hall http://www.rfk.com > RFK Partners, Inc. (508) 893-9779 - RFK Office > 838 Washington Street (508) 893-9889 - FAX > Holliston, MA 01746 > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- 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/