Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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:	<00be01c23180$eed53400$0100a8c0@wdg.uk.ibm.com>
From:	"Max Bowsher" <maxb AT ukf DOT net>
Cc:	<cygwin AT cygwin DOT com>
References:	<000601c23161$55d02bd0$0200a8c0 AT lifelesswks> <193351029193 DOT 20020722134800 AT logos-m DOT ru>
Subject:	Re: Valid file-name characters
Date:	Mon, 22 Jul 2002 14:08:54 +0100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

egor duda wrote:
> That's exactly my point. Having some fancy rules for filename encoding
> breaks interoperability with native tools. Escaping non-valid
> characters like ':' is not big problem, since native tools can't use
> such names anyway. But messing with valid characters like '%' is far
> more dangerous and error-prone.

OK, so we need to think long and hard before picking an escape character. But
surely bypassing Windows's invalid characters in filenames is worth problems in
the extremely rare corner case that filenames contain whichever weird character
we pick?

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -