Rsync 3.0.0pre8 and Mac OS X

[Rudolf E. Reiber]

Hi Matt,

thanks for your great help!
A look onto iconv --list told me, that the only mistake was a miss- 
spelling.
I had to write --iconv=UTF8-MAC,ISO-8859-15 and everything worked very  
well!
cheers to You!
I think, that a hint to iconv --list in the rsync man-page would be  
graet
Rudolf


Am 24.01.2008 um 19:18 schrieb Matt McCutchen:

> Please keep this on the rsync list.
>
> On Thu, 2008-01-24 at 18:32 +0100, Rudolf E. Reiber wrote:
>> I am sorry, but when I apply the --iconv=utf8mac,iso885915 option,  
>> the
>> rsync compleately fails.
>> to compile some patches or do some other things in order getting
>> utf8mac to work? Or is this feature built in Rsync 3.0.0pre8?
>
> Support for encodings such as utf8mac is determined by the Mac's
> libiconv, not by rsync.  You need to install a libiconv that supports
> the utf8mac encoding (check that utf8mac is listed when you run "iconv
> --list") and then build rsync against that libiconv.  It looks like  
> your
> best bet is the MacPorts libiconv described here:
>
> http://trac.macports.org/projects/macports/browser/trunk/dports/textproc/libiconv/Portfile
>
> In fact, rsync 3.0.0pre8 itself appears to be available through
> MacPorts:
>
> http://trac.macports.org/projects/macports/browser/trunk/dports/net/rsync-devel/Portfile
>
> Matt
>
>> Am 24.01.2008 um 16:11 schrieb Matt McCutchen:
>>
>>> I see now that *Apple's* iconv does have the necessary "utf8mac"
>>> encoding.  See:
>>>
>>> http://code.google.com/p/macfuse/issues/detail?id=139
>>> http://libiconv.darwinports.com/
>>>
>>> So just pass --iconv=utf8mac,iso885915 when the Mac is sending and
>>> --iconv=iso885915,utf8mac when it is receiving, and the problem  
>>> should
>>> go away.
>