Bug #2032

Restrict the characters allowed in file names and paths

Added by drbits over 10 years ago. Updated over 8 years ago.

Status:ClosedStart date:07/08/2010
Priority:LowDue date:
Assignee:-% Done:


Category:GUIEstimated time:4.00 hours
Target version:010 - Next Major Public Release 1.xxx


Each OS has characters that may not occur in file names and paths or is restricted in its use.

Users should be warned when they try to use what appears to be an illegal character sequence in a file name or path. Special exceptions such as Windows allowing \\ (two backslashes, not a quoted backslash) at the beginning of a path need not be excluded from the warning.

In Windows, the following should cause a warning: [&%!|<>?*/,=] and any characters not representable as UNICODE.
The linux regex could depend on the shell, but would probably be the same.

Related issues

Related to Bug #3609: [Add errorhandling][Windows] Filenames starting with "Con... Closed 07/26/2011

Also available in: Atom PDF