Feature Request: Space (and other special character) Control
For all file-related operations (copies, make backup to, process variant, etc), please either suppress spaces in file names or make it a configurable option (e.g., let me choose to replace spaces in names with underscores or dashes).
This would bring your product in line with general Digital Asset Management best practice (refer to any of a number of resources; e.g., The DAM Book or DAM Learning Center). In general, the following should be avoided in file names, even if a given OS allows them:
I would personally add the exclamation point (!) to that list as well, as it can be especially problematic on Unix and Unix variants (which, incidentally, includes Apple's Mac OS).
In particular, for those of us who backup to Unix-based file servers (e.g., Samba), regular file maintenance can be a challenge when spaces and other special characters are present in file names and paths.
This becomes especially problematic when a disk fails and somebody will wind up at a command line trying to recover stuff (probably your user) - and spaces and special characters in file names add another layer of complexity to what's already a stressful process, regardless of the OS (the issue impacts all 3 mainstream operating systems: Windows (DOS), Unix, and Mac OS).
This would bring your product in line with general Digital Asset Management best practice (refer to any of a number of resources; e.g., The DAM Book or DAM Learning Center). In general, the following should be avoided in file names, even if a given OS allows them:
space \ / : * ? " ' < > | [ ] & $I would personally add the exclamation point (!) to that list as well, as it can be especially problematic on Unix and Unix variants (which, incidentally, includes Apple's Mac OS).
In particular, for those of us who backup to Unix-based file servers (e.g., Samba), regular file maintenance can be a challenge when spaces and other special characters are present in file names and paths.
This becomes especially problematic when a disk fails and somebody will wind up at a command line trying to recover stuff (probably your user) - and spaces and special characters in file names add another layer of complexity to what's already a stressful process, regardless of the OS (the issue impacts all 3 mainstream operating systems: Windows (DOS), Unix, and Mac OS).
0
-
I support the first part of this request. In a previous version of C1 (5 ? 6? ...) there was an underscore instead of a space for variants. This makes a difference in the order Windows will display the files.
The second part of the request makes sense too.0
Post is closed for comments.
Comments
1 comment