Bug 2938 - Escape Colons in Filenames
Escape Colons in Filenames
Status: ASSIGNED
Product: rsync
Classification: Unclassified
Component: core
2.6.3
x86 Windows XP
: P3 enhancement
: ---
Assigned To: Wayne Davison
Rsync QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-08-01 11:49 UTC by Roland Schulz
Modified: 2008-02-06 21:24 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roland Schulz 2005-08-01 11:49:50 UTC
It would be very nice, if one could escape colons in filenames. This is because
those aren't allowed under windows.
Comment 1 Roland Schulz 2005-08-01 17:20:18 UTC
The same applies to old DOS names like AUX, COM1, LPT1 or PRN.
Comment 2 Wayne Davison 2005-08-03 17:10:29 UTC
This seems like something that cygwin should support, but they haven't wanted to
instigate an escaping mechanism for this.  So, maybe this should be a patch that
the cygwin folks apply (perhaps shipped in the "patches" dir) that would
transform certain names and characters when opening/creating a file, and
untransforming them when reading the names via readdir or parsing the
command-line args.  Someone would need to choose a reasonable escape
char/sequence.  Any suggestions?
Comment 3 Lapo Luchini 2006-01-02 03:03:15 UTC
Cygwin doesn't "translate" filenames in its default configuration. In order to use names that are non Windows-compatible the managed mounts are to be used: search "man mount" for "-o managed" option. Warning: managed mode CAN'T be used on directories whose files were not ALL created using managed mode itself.
Comment 4 Matt McCutchen 2008-02-06 21:24:08 UTC
The transliterate patch provides a way to delete the offending colons or replace them with another character:

http://rsync.samba.org/ftp/rsync/patches/transliterate.diff