X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <49D9EA9B.8080903@gmail.com> Date: Mon, 06 Apr 2009 12:42:19 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Reverting from 1.7.0-45 [was Re: [1.7]: For the love of god, don't update!] References: <49D97797 DOT 9080902 AT gmail DOT com> <49D9913B DOT 7030708 AT cwilson DOT fastmail DOT fm> <49D99981 DOT 4030503 AT gmail DOT com> <49D99A02 DOT 7070407 AT gmail DOT com> <49D99D65 DOT 8040304 AT cwilson DOT fastmail DOT fm> <49D9C684 DOT 8030201 AT gmail DOT com> <20090406101604 DOT GA3978 AT calimero DOT vinschen DOT de> In-Reply-To: <20090406101604.GA3978@calimero.vinschen.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: > This happens if the symlink has been created with Cygwin 1.7.0-45 > and you revert back to 1.7.0-44 or earlier. Yeh, it all went quiet for a while while I've been re-reading the recent release announcements. Thanks for the pointers. > I explained what I did to new symlinks in > http://cygwin.com/1.7/cygwin-ug-net/highlights.html#ov-hi-files, > 9th paragraph: > > Starting with Cygwin 1.7, symbolic links are using UTF-16 to encode > the filename of the target file, > I hope it's clear what the advantage is. The disadvantage is also > clear, as you just found out. > > Of course, what we could do is to store symlinks in UTF-8. Yeh, I understand. I certainly wouldn't suggest making it the least bit less efficient or backward compatible just in order to ease something as infrequent as downgrading across an abi break. The thing I haven't yet established (and don't really want to have to get sidetracked onto right now because I have other hippos to fry) is whether the new unicode and locale support is having some odd knock-on effect on m4 processing, or whether I've run into something /else/ (and had a hard time seeing the wood for the i18n trees). I'm trying not to fall into the trap of assuming that "whatever just changed" will be the source of the problems I ran into. cheers, DaveK -- 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/