X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <478BD708 DOT 9020909 AT gmail DOT com> <03ae01c8571d$cfd378f0$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <000001c85724$418dcb70$020aa8c0 AT DFW5RB41> Subject: RE: [1.7.0 HEAD]: Cygwin no longer encoding/decoding names on managed mounts Date: Wed, 16 Jan 2008 18:49:31 -0000 Message-ID: <000401c85870$880e5040$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <000001c85724$418dcb70$020aa8c0@DFW5RB41> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 15 January 2008 03:11, Gary R. Van Sickle wrote: >> From: Dave Korn >> Sent: Monday, January 14, 2008 8:25 PM >> Subject: RE: [1.7.0 HEAD]: Cygwin no longer encoding/decoding names on >> managed mounts >> >> On 14 January 2008 21:41, Nicholas Wourms wrote: >> >>> I'm not sure when this cropped up, but it happened sometime after the >>> great "win 9x" code purge. The problem is that the Cygwin dll no >>> longer decodes or encodes file/directory names on managed mounts. >> >> Isn't that the whole idea? >> > > Managed mounts? They're intended to handle names with things like ":" in > them, which will choke Windows no matter what year is in its name. Oh yeh, forgot there were still a few things that can't be handled in wchar mode. And looking at it the source, it still seems like it's supposed to munge uppercase chars, so I guess this /is/ a bug rather than a work-in-progress. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/