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 sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Date: Wed, 19 Apr 2000 16:12:47 +0300 From: Paul Sokolovsky X-Mailer: The Bat! (v1.32) S/N AB51B607 Reply-To: Paul Sokolovsky X-Priority: 3 (Normal) Message-ID: <13675.000419@is.lg.ua> To: DJ Delorie CC: cygwin AT sourceware DOT cygnus DOT com Subject: Re[2]: 3 bugs In-reply-To: <200004172231.SAA31685@envy.delorie.com> References: <200004172231 DOT SAA31685 AT envy DOT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello DJ, DJ Delorie wrote: DD> It sounds like this is a "feature" of the Win32 file system, in that DD> it doesn't *quite* preserve the file name correctly. If so, there's DD> not much we can do about it. Except, perhaps, to MIME encode the DD> problem file names :-( Cool idea! ;-) But what about mere urlencoding filenames? Here problem arises: what to do with '%' itself. At least 3 following choices are available: 1. Be formally correct: replace '%' with '%25'. But this will lead to incompatibility with native apps. E.g.: script, native apps delivers filename and cygwin apps tries to open it. 2. Don't touch '%' at all. 3. Oversafing: try filename with '%' urlencoded, if it fails, try original. For me, 1 is not acceptable, and 3 way to complicated. So, I've chosen 2 - I don't know about any app using % in filenames consistently, so to come upon filename with '%' followed by two uppercase hex digits is very low probability for me. -- Paul Sokolovsky, IT Specialist http://www.brainbench.com/transcript.jsp?pid=11135 -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com