X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_50 X-Spam-Check-By: sourceware.org X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.0 c=1 a=ybQFKeYjodAA:10 a=kCKDY91tEBMc+hi4YtGk8Q==:17 a=JW-fan9trPW_be3kl-wA:9 a=A5PdlmdAivBotMewv4t-xtdoK94A:4 Message-ID: <4AF38062.2040700@monai.ca> Date: Thu, 05 Nov 2009 17:48:18 -0800 From: Steven Monai User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-63 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Corinna Vinschen wrote: ... > Bugfixes: > ========= ... > - Improve the roundtrip capability when converting singlebyte chars to > the UNICODE prvate use area U+F0xx and vice versa. Fantastic! I just upgraded from 1.7.0-62 to -63, and my daily rsync backup script can now see that handful of files on my system with "weird" names [containing Unicode char U+F020] that were previously untouchable by Cygwin. Just wondering: What limitations, if any, are there now on the chars from the U+F0xx range that can be used in filenames? -SM -- -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple