In my organisation, we're using a Samba storage. On this storage, due to the path size limitation, we are asking the users to avoid names with special characters (2 UTF16 words instead of 1). It would help if we could specify into the user settings the characters which are forbidden in file names.
(In reply to Jérôme from comment #0) > In my organisation, we're using a Samba storage. > > On this storage, due to the path size limitation, we are asking the users to > avoid names with special characters (2 UTF16 words instead of 1). Hmm...ideally you'd be able to fix this in SAMBA. Perhaps Windows clients have some limitations themselves... > It would help if we could specify into the user settings the characters > which are forbidden in file names. Sounds like it could have some applications. Priority -> low Status -> NEW
UX team: this is kind of niche - should it be included? I guess as an expert option, if yes.
I disagree. We should not limit our self because some protocol has restrictions. And fiddling around with the standard dialogs is always suspect. Under Linux I can save a file with the name 1:2.odt while the colon is is not a valid filename on Windows. But this error string is not present in the code so I assume it's checked on the OS. And we should keep it this way.