X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <47FF8C1F.5070309@wpkg.org> Date: Fri, 11 Apr 2008 18:04:47 +0200 From: Tomasz Chmielewski User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061110 Mandriva/1.5.0.8-1mdv2007.1 (2007.1) Thunderbird/1.5.0.8 Mnenhy/0.7.4.666 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: using rsync with Win32/UNC pathnames? References: <47F229BD DOT 2060507 AT byu DOT net> <47F22BD6 DOT 3040801 AT wpkg DOT org> <47F22DF5 DOT 6020108 AT byu DOT net> <20080401124823 DOT GQ4468 AT calimero DOT vinschen DOT de> <47F23164 DOT 8040604 AT wpkg DOT org> <23fce8e60804011425q1342c521y6849a8e405480389 AT mail DOT gmail DOT com> <47F371B6 DOT 3050107 AT wpkg DOT org> <47F539B6 DOT 3961D2ED AT dessent DOT net> <20080403204802 DOT GE4468 AT calimero DOT vinschen DOT de> <47FF58DE DOT 2010800 AT wpkg DOT org> <20080411141809 DOT GJ23852 AT calimero DOT vinschen DOT de> In-Reply-To: <20080411141809.GJ23852@calimero.vinschen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 schrieb: > On Apr 11 14:26, Tomasz Chmielewski wrote: >> Corinna Vinschen schrieb: >>> On Apr 3 13:10, Brian Dessent wrote: >>>> Tomasz Chmielewski wrote: >>>> >>>>> So once Cygwin learns how to speak UTF-8, I will finally be able to >>>>> backup all Windows files... :) >>>> Set CYGWIN=codepage:utf8 to enable UTF-8 support. >>> ...and set LC_CTYPE=C-UTF-8, otherwise multibyte/wide char aware >>> application don't convert UTF-8 strings correctly from multibyte to >>> wide char and vice versa. >> Although it helped greatly, I'm still unable to open some files with Cygwin >> apps. > > One reason could be that you're accessing a remote samba share which > has filenames with characters which are invalid utf-8 chars. In this > case there's nothing Cygwin can do. You will have to fix that on the > server side. I'm accessing the file locally. >> Windows tools have no problems accessing them. >> >> Some Windows tools say for example "this directory contains file names from >> a different code page" (i.e., Total Commander will say this when entering a >> directory which contains such a file). >> >> >> Is there a setting which will enable Cygwin apps to open all files, >> irrespective of their name encoding? > > utf-8 is supposed to be able to convert all wide chars to a multibyte > sequence. If it's *not* the above server-side problem, we would need a > simple, self-contained, reproducible testcase, preferrably in plain C. Is a file in an archive enough? It looks like it looses the special character in tar or zip, but 7zip can store it just fine. If you want, download http://wpkg.org/test.7z You will need 7zip to extract it (or something compatible). The archive contains a "test" directory and an empty file in it. That filename contains a strange character. Then, try to access this file with any Cygwin program - it won't work. Mind that I use a German language Windows version - if the above doesn't work for you, I can give you remote access if you want. -- Tomasz Chmielewski http://wpkg.org -- 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/