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/
