Bug#320223: rsync should use UTF-8 encoding internally and transform to local locale
close 320223 3.0.0-1 thanks There is now an --iconv option in rsync 3.0.0 that specifies how to convert filenames. Paul Slootman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320223: rsync should use UTF-8 encoding internally and transform to local locale
Paul Slootman wrote: On Wed 27 Jul 2005, David Ayers wrote: rsync should read the file name in the locale of the local user but transfer it to UTF-8 for file name comparison with the remote system. Then when writing the file name it should again transform from UTF-8 to the encoding specified by the local locale. (Of course this Sounds good... I just wonder how easy it is to determine what charset is in use on each system (also consider windows and OS/X). Even every filesystem could have a different charset in use. I wouldn't be surprised if there are systems where a directory could have its own charset :-( I think it should simply use the charset of the locale of the current rsync process. Different processes can have there own differing locale settings each creating / reading there own files each with different representations. The file system itself doesn't have a locale IIUC. It would be up to the user to setup the correct LANG setting as much is it is up to the user to insure the rsync is in his path. Cheers, David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320223: rsync should use UTF-8 encoding internally and transform to local locale
On Wed 27 Jul 2005, David Ayers wrote: rsync should read the file name in the locale of the local user but transfer it to UTF-8 for file name comparison with the remote system. Then when writing the file name it should again transform from UTF-8 to the encoding specified by the local locale. (Of course this Sounds good... I just wonder how easy it is to determine what charset is in use on each system (also consider windows and OS/X). Even every filesystem could have a different charset in use. I wouldn't be surprised if there are systems where a directory could have its own charset :-( Thanks, Paul Slootman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320223: rsync should use UTF-8 encoding internally and transform to local locale
Package: rsync Version: 2.6.4-6 Severity: wishlist rsync should read the file name in the locale of the local user but transfer it to UTF-8 for file name comparison with the remote system. Then when writing the file name it should again transform from UTF-8 to the encoding specified by the local locale. (Of course this transformation could be lossy and there is nothing rsync can do about it. But in the average case people will try to sync between systems with file names that can be handled in the less expressive locale setting like the latin variants and a UTF-8 locale). -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-2-386 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) Versions of packages rsync depends on: ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libpopt01.7-5lib for parsing cmdline parameters -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
