Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-Authentication-Warning: hp2.xraylith.wisc.edu: khan owned process doing -bs Date: Mon, 5 Feb 2001 12:37:41 -0600 (CST) From: Mumit Khan To: Cygwin Users List Subject: Re: Special chars inside filename In-Reply-To: <4.3.1.2.20010205114010.024e7bc0@pop.ma.ultranet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 5 Feb 2001, Larry Hall (RFK Partners, Inc) wrote: > 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. DJ also pointed out that djtar handles this situation, and before anyone reinvents the wheel, s/he should look into that first. I at one point needed it and hacked up tar to use a map file, and it worked *for me* and *for that particular task*; however, doing it right would require some design. This is too low a priority for me, so I'll just sit back and watch. Regards, Mumit -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple