On Thu, 2008-01-24 at 10:11 -0500, Matt McCutchen wrote:
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.
Just so the above doesn't confuse people in the future: I thought
incorrectly that the
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
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
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
Hi,
I tried Rsync 3.0.0pre8 on my mac running os X 10.5.
I was very pleased about the --iconv feature, as i have to sync some
LINUX-machines and I had really trouble with some filenames.
But I found one strange thing in connection with the mac.
First of all, the translation between the
On Wed, 2008-01-23 at 16:01 +0100, Rudolf E. Reiber wrote:
I tried Rsync 3.0.0pre8 on my mac running os X 10.5.
I was very pleased about the --iconv feature, as i have to sync some
LINUX-machines and I had really trouble with some filenames.
But I found one strange thing in connection with
