X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Fri, 28 Jan 2011 11:57:23 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: 3.Using Cygwin, Special filenames, Invalid filenames Message-ID: <20110128105723.GU28470@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20110128190112.A396.2AEBBFCD@soarsystem.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Jan 28 11:14, Csaba Raduly wrote: > 2011/1/28 Masaki_Takasu : > > Hello; > > > > Cygwin1.7.7 has a problem that incorrect to interpret the files created by Macintosh. > > > > Steps > > (1) Create a '"' in name of a file using Macintosh.(Mac OS X 10.6.6) > > (2) To transfer file(created at step (1)) to Windows from Macintosh by SMB protocol. > > (3) '"' in name of a file is converted to Unicode 0xF020 according to SMB protocol. > > (4) To verify the file transferred to Windows using Cygwin "ls"command. > > (5) Cygwin interprets Unicode 0xF020 as ' '(Spaces) in name of a file. > > > >  ※ Character conversion table mapping code in SMB protocol > >     References   http://support.microsoft.com/kb/q117258/ > > > >     Macintosh ANSI  Unicode > >     -------------------------------- > >     0x01-0x1F       0xF001-0xF01F > >     "               0xF020 > >     *               0xF021 > >     /               0xF022 > >     <               0xF023 > >     >               0xF024 > >     ?               0xF025 > >     \               0xF026 > >     |               0xF027 > > Deja vu. You may be out of luck: > http://sourceware.org/ml/cygwin/2005-12/msg00178.html > > See also: http://sourceware.org/ml/cygwin/2008-04/msg00410.html > Macintosh. Think different! It's kind of idiotic that SFM uses another, incompatible mapping than SFU. Cygwin supports the SFU mapping, so you have to do a second mapping using some perl script or so. For the mapping used in Cygwin, see http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars Like SFU, Cygwin just transposes the charatcers into the 0xf0XX range by adding 0xf000 to the ASCII value. Note that you're out of luck when using slashes or backslash. You have to convert these filenames into names with different chars. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple