3.Using Cygwin, Special filenames, Invalid filenames

3.Using Cygwin, Special filenames, Invalid filenames

[Masaki_Takasu]

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

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

Thanks.

---
Masaki_Takasu
  mailto:takasu_masaki@soarsystem.co.jp
---

[-- Attachment #2: cygcheck.out --]
[-- Type: application/octet-stream, Size: 27857 bytes --]

[-- Attachment #3: Type: text/plain, Size: 218 bytes --]

--
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

Re: 3.Using Cygwin, Special filenames, Invalid filenames

[Csaba Raduly]

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!

Csaba
-- 
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds

--
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

Re: 3.Using Cygwin, Special filenames, Invalid filenames

[Corinna Vinschen]

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

filenames with BANG

[pen]

Need help, Cant access html file from lynx, even though its readable by other
commands.

$ ls -l "test bay#, wwid"
-rw-r--r--+ 1 test Users 50999 Nov 17 03:22 test bay#, wwid
$ file "test bay#, wwid"
test bay#, wwid: HTML document, ASCII text, with very long lines
$ head -2 "test bay#, wwid"
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"
>
$ lynx -dump "test bay#, wwid"

Can't Access `file://localhost/cygdrive/e/test%20bay#,%20wwid'
Alert!: Unable to access document.

lynx: Can't access startfile

Played around and found that if i create any file with "#, " lynx cant
understand it. 

Appreciate your help.
-- 
View this message in context: http://old.nabble.com/3.Using-Cygwin%2C-Special-filenames%2C-Invalid-filenames-tp30785462p32858452.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
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

Re: filenames with BANG

[Eric Blake]

[-- Attachment #1: Type: text/plain, Size: 425 bytes --]

On 11/16/2011 04:35 PM, pen wrote:
> 
> Played around and found that if i create any file with "#, " lynx cant
> understand it. 

Not answering your question, but it would help if your subject matched
your body: BANG is !, not # (the latter is hash, sharp, pound, or
octothorpe, depending on who you ask).

-- 
Eric Blake   eblake@redhat.com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]

Re: filenames with BANG

[pen]

Oops sorry made a mistake.

eblake wrote:
> 
> On 11/16/2011 04:35 PM, pen wrote:
>> 
>> Played around and found that if i create any file with "#, " lynx cant
>> understand it. 
> 
> Not answering your question, but it would help if your subject matched
> your body: BANG is !, not # (the latter is hash, sharp, pound, or
> octothorpe, depending on who you ask).
> 
> -- 
> Eric Blake   eblake@redhat.com    +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
> 
> 
>  
> 

-- 
View this message in context: http://old.nabble.com/3.Using-Cygwin%2C-Special-filenames%2C-Invalid-filenames-tp30785462p32858516.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
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

filenames with BANG

[pen]

Need help, Cant access html file from lynx, even though its readable by other
commands. 

$ ls -l "test bay#, wwid" 
-rw-r--r--+ 1 test Users 50999 Nov 17 03:22 test bay#, wwid 
$ file "test bay#, wwid" 
test bay#, wwid: HTML document, ASCII text, with very long lines 
$ head -2 "test bay#, wwid" 
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" 
> 
$ lynx -dump "test bay#, wwid" 

Can't Access `file://localhost/cygdrive/e/test%20bay#,%20wwid' 
Alert!: Unable to access document. 

lynx: Can't access startfile 

Played around and found that if i create any file with "#, " lynx cant
understand it. 

Appreciate your help. 

-- 
View this message in context: http://old.nabble.com/filenames-with-BANG-tp32858508p32858508.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
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