This page was exported from phaq
[ http://phaq.phunsites.net ] Export date: Fri Apr 19 23:31:32 2024 / +0000 GMT |
A late night experience, thank good I got it fixed right away... Imagine this setup:
Imagine the fact:
Imagine the problem:
The reason for this behavious is simple: cwrsync is actually nothing else than traditional rsync compiled as win32-binary using cygwin. Now rsync has one major drawback: it's not (yet) unicode aware, which means that special characters in file names are not properly converted. Now there are two ways to fix this. Either replace the bundled cygwin library (cygwin1.dll) with another one which is unicode-aware. You find one at the UTF-8 cygwin project website. Another possibility would be the use of an alternative tool (anything else than rsync) which is unicode-aware or the .NET based rsync port. I choose to go the UTF-8 cygwin way, which did the trick for me. I just downloaded the 1.5.21-1 version (I checked the bundled cygwin1.dll version through properties dialog in explorer first to make sure they match), moved the original cygwin1.dll away and replaced it by the download version instead. By the next time I ran cwrsync my filenames would just look as supposed. Wheew, what a night...! |
Powered by [ Universal Post Manager ] plugin. HTML saving format developed by gVectors Team www.gVectors.com |