[Bug 3299] New: rsync: now replaces non-ASCII character with
numerical values
bugzilla-daemon at dp3.samba.org
bugzilla-daemon at dp3.samba.org
Sun Dec 4 22:56:55 GMT 2005
https://bugzilla.samba.org/show_bug.cgi?id=3299
Summary: rsync: now replaces non-ASCII character with numerical
values
Product: rsync
Version: 2.6.6
Platform: Other
URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=307242
OS/Version: Linux
Status: NEW
Severity: major
Priority: P3
Component: core
AssignedTo: wayned at samba.org
ReportedBy: debian at fnen.eu.org
QAContact: rsync-qa at samba.org
Package: rsync
Version: 2.6.6-1
Followup-For: Bug #307242
I've again used two identical Sarge systems, both using UTF-8.
Using rsync (over ssh), syncing (or listing the contents) from one
system to the other, non-ASCII characters get replaced with numerical
values like '\303\245', eg:
user at system1:~$ rsync system2:~/test_åäö_test
drwxr-xr-x 72 2005/09/25 01:39:30 test_\303\245\303\244\303\266_test
The changelog states:
--------------------------------------------------------------------------
rsync (2.6.5-1) unstable; urgency=low
* Now should handle locale-specific characters better in logging output
(i.e. the correct chars should be displayed, not '?').
--------------------------------------------------------------------------
This statement is obviously not correct. The '?' has just been replaced
with a numerical value instead. (Almost as useless.)
Is this something that's being worked on upstream? Is there a workaround?
All scripts and programs depending upon the output is almost useless since
several month now.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686-smp
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)
Versions of packages rsync depends on:
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libpopt0 1.7-5 lib for parsing cmdline parameters
-- no debconf information
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
More information about the rsync
mailing list