rsync - Jul 2007 - DO NOT REPLY [Bug 4791] New: Invalid character translation feature request

https://bugzilla.samba.org/show_bug.cgi?id=4791

           Summary: Invalid character translation feature request
           Product: rsync
           Version: 3.0.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P3
         Component: core
        AssignedTo: wayned@samba.org
        ReportedBy: edmundrhudy@mac.com
         QAContact: rsync-qa@samba.org


This is a feature request for something that plagues me often when rsyncing
from UNIX (Linux and OS X) systems to Windows.  NTFS has several invalid
characters that are valid under ext3 and HFS+, which often requires
time-consuming and tedious renaming operations on the source systems to fix
filenames and directory names before rsyncing.  In addition, Windows silently
strips extraneous whitespace from the beginning and end of file and directory
names, but rsync fails when trying to copy files or directories that have this
extra whitespace in their names.


-- 
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.

https://bugzilla.samba.org/show_bug.cgi?id=4791


matt@mattmccutchen.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Invalid character           |Invalid character
                   |translation feature request |translation feature request




------- Comment #1 from matt@mattmccutchen.net  2007-12-14 21:42 CST -------
There is a very basic implementation of invalid character translation in the
"transliterate" branch of the current development rsync:

http://gitweb.samba.org/?p=rsync.git;a=commitdiff;h=04dd165c17a8cdc32c74a0e86164c40ab2646ad9


-- 
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.