rsync-3.0.0pre10 and iconv
tony at servacorp.com
Wed Feb 27 11:46:46 GMT 2008
Thankee! Thankee! Thankee!
I am definitely switching to 3.0 or the next pre.
(currently anything like that that actually gets to the other side is
(not all that bad since anything that actually matters is supposed
to be in english not chinese ;-)
This is on/to/through computers which are NOT native UTF-8
If the backups are acutally ever needed, it will be a long time
before anybody actually cares
if some Chinese words got mangled in the file names.
However it does look much better if the names are NOT mangled.
And sometime, sooner or later, it will actually matter.
> -----Original Message-----
> From: rsync-bounces+tony=servacorp.com at lists.samba.org
> [mailto:rsync-bounces+tony=servacorp.com at lists.samba.org] On
> Behalf Of sami.pitko at vaisala.com
> Sent: Wednesday, February 27, 2008 5:19 AM
> To: rsync at lists.samba.org
> Subject: RE: rsync-3.0.0pre10 and iconv
> > 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 filenames are not in UTF8 during the
> transfer, unless sending side is using UTF8 natively.
> Here's partial packet export from utf-8 to iso8859-1 transfer:
> 0060 04 18 2f 65 78 61 6d 70 6c 65 2d 66 69 6c 65 2d
> 0070 c3 b6 c3 a4 c3 a5 2e 74 78 74 00 05 00 47 2f 99
> Here's partial packet export from iso8859-1 to utf-8 transfer:
> 0060 04 15 2f 65 78 61 6d 70 6c 65 2d 66 69 6c 65 2d
> 0070 f6 e4 e5 2e 74 78 74 00 05 00 47 bd f1 c3 a4 81
> Transferred / converted filename is still "example-file-öäå.txt".
> To unsubscribe or change options:
> Before posting, read:
More information about the rsync