Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-Id:	<4.3.1.2.20010205114010.024e7bc0@pop.ma.ultranet.com>
X-Sender:	lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer:	QUALCOMM Windows Eudora Version 4.3.1
Date:	Mon, 05 Feb 2001 11:45:22 -0500
To:	tag AT ibis DOT odessa DOT ua, "Cygwin Users List" <cygwin AT cygwin DOT com>
From:	"Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject:	Re: Special chars inside filename
In-Reply-To:	<OCECJNJHOHFDNOOHJFIHOEDOFBAA.tag@ibis.odessa.ua>
Mime-Version:	1.0

At 09:36 AM 2/5/2001, Andrew G. Tereschenko wrote:
>Hi,
>
>I. Is there any environment option/proposed patch
>to support special as for Win32) chars inside POSIX filenames ?
>
>Win32 reserved for use this set of symbols:
>< > : " / \ |
>As result not all filenames allowed in Cygwin twitch allowed
>in real *nix.
>
>Currently I'm unable to decompress news archive for a leafnode
>because of filenames like "<OAlNo66RAHA DOT 444 AT CPMSBNEWSW02 DOT betanews DOT com>"
>(without double quotes). This archive was assembled under Solaris and
>this filenames was valid...
>
>Will it be Ok if Cygwin will encode this chars in valid char sequence ?
>
>II. Is it possible to change \ behavior ??
>Example:
>1. bash-2.04$ uname -a
>CYGWIN_NT-5.1 TAG 1.1.2(0.21/3/2) 2000-06-06 22:20 i686 unknown
>bash-2.04$ cat > c\\a
>bash: c\a: No such file or directory
>
>2. [tag AT tigger2 ~]$ uname -a
>SunOS tigger2 5.7 Generic_106542-02 i86pc i386 i86pc
>[tag AT tigger2 ~]$ cat > c\\a
>  ^D
>[tag AT tigger2 ~]$ ls -la c*
>-rw-r--r--   1 tag      tag            1 Feb  5 09:04 c\a
>
>I think if Cygwin will encode all possible *nix filenames
>into restricted set of win32 filenames then it will be easy
>to add unicode/localised filenames support.
>Also i think that we must strictly define which
>filenames are POSIX and which Win32.
>
>So ? What do think about this ?


This might be a useful option, but it would have to be an option, since 
it would mean that the files created would not be accessible with Win32
tools (only Cygwin-aware ones).  Alternatively, a few days back, someone
suggested a solution of creating a map from invalid characters to valid 
ones.  This alternative is probably better since it would support Win32 
tools.  I'm sure the maintainers would consider a well though-out patch.



Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -