Message-ID: <4B39363E.4050402@rosi-kessel.org>
Date: Mon, 28 Dec 2009 17:50:38 -0500
From: Adam Rosi-Kessel <adam@rosi-kessel.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: rsync no longer preserves extended ASCII characters after 1.7   	upgrade
References: <4B3828E1.4090004@rosi-kessel.org> <4B382C69.20706@rosi-kessel.org> 	 <4B383DCD.80907@monai.ca> <416096c60912272312p59392560j297422825c5720a3@mail.gmail.com>
In-Reply-To: <416096c60912272312p59392560j297422825c5720a3@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Andy Koppe wrote, on 12/28/2009 2:12 AM:
> Yes, that's one way. Specifying e.g. 'LC_CTYPE=en_US rsync ...' (i.e.
> a language without an explicit character set) will give you the ANSI
> codepage.

Thanks! This fixes it perfectly for me.

> But I think the --iconv option is the better way. Assuming you want to
> stick with ISO-8859-1 on the Linux side, '--iconv utf8,iso88591'
> should do the job.

This doesn't seem to work. I think I need utf-8 rather than utf8. 
Otherwise I get:

iconv_open("UTF-8", "utf8") failed

But if I set RSYNC_ICONV='utf-8,iso8859-1' (or 'utf-8,iso88591', which 
also seems to work) I get errors like this:

[generator] cannot convert filename: [path with extended chars] (Invalid 
or incomplete multibyte or wide character)

The LC_CTYPE thing seems to work, so I'm satisfied, but I thought I 
should report out that iconv per your suggestion didn't work.

Adam


--
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