Bug 4791 - Invalid character translation feature request
Summary: Invalid character translation feature request
Status: NEW
Alias: None
Product: rsync (new bug reports go to github)
Classification: Unclassified
Component: core (show other bugs)
Version: 3.0.0
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---
Assignee: Wayne Davison
QA Contact: Rsync QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-16 12:11 UTC by Edmund Rhudy
Modified: 2026-05-19 09:43 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Edmund Rhudy 2007-07-16 12:11:44 UTC 
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.
Comment 1 Matt McCutchen 2007-12-14 21:42:37 UTC 
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
Comment 2 c.buhtz 2026-05-19 09:43:00 UTC 
Hello,

can you please give n update about the status of this ticket. Is there a plan to implement it?

I have some Debian tickets related to it I would like to close.

Regards,
Christian Buhtz