On Thu, Feb 28, 2008 at 12:55:11PM +0200, [EMAIL PROTECTED] wrote:
> It would be good to add link to convmv script into rsync --iconv
> documentation. convmv can be found from http://www.j3e.de/linux/convmv/
Thanks. I have mentioned that utility on the rsync resources page.
..wayne..
--
To uns
> It was failing when communicating with a daemon due to a missing
> setup_iconv() call. The attached patch fixes this. Thanks for
> your report!
Thanks for the patch. I can confirm that --iconv option works now
from iso8859-1 to utf-8 transfer.
It would be good to add link to convmv script int
On Tue, Feb 26, 2008 at 02:14:34PM +0200, [EMAIL PROTECTED] wrote:
> Has anyone got iso8859-1 to utf-8 conversion working with rsync-3.0.0pre10?
It was failing when communicating with a daemon due to a missing
setup_iconv() call. The attached patch fixes this. Thanks for
your report!
..wayne..
lly matter.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of [EMAIL PROTECTED]
> Sent: Wednesday, February 27, 2008 5:19 AM
> To: rsync@lists.samba.org
> Subject: RE: rsync-3.0.0pre10 and iconv
>
> > I think that UTF8
> I think that UTF8 is simply used as the transport encoding.
> The sending side will ensure that the filenames "on the wire"
> are UTF8, and the receiving side will convert that UTF8 into
> whatever is required.
I checked with tcpdump what is being transmitted between the hosts and found
that fi
On Wed 27 Feb 2008, [EMAIL PROTECTED] wrote:
>
> So if I'm interpreting that right, UTF8 is hardcoded to always be one of
> the conversion charsets. If rsync is sending, the conversion is always
> to UTF8. If rsync is receiving, the conversion is always from UTF8.
I think that UTF8 is simply used
Hello,
> Has anyone got iso8859-1 to utf-8 conversion working with
rsync-3.0.0pre10?
I am answering to my own question.
I looked at the setup_iconv function in rsync.c and found following code
snippets:
...
if ((ic_send = iconv_open(UTF8_CHARSET, charset)) ==
(iconv_t)-1) {
...
...
