File and folder name limitations
In order to make sure that both Macintosh and Windows users have a seamless experience, the DOQMIND asset system imposes some restrictions on the file and folder names used in the system.
When uploading a file with invalid characters, the following rules are applied:
Non printable characters are removed
Non-printable characters are special characters that cannot be seen, but influence the behaviour of the text. An example is a non-breakable space. Windows allows some non printable characters, Apple allows a different subset of non-printable characters. This results in files that cannot be copied from one system to an other. DOQMIND will remove non-printable characters.
Illegal characters are replaced
Special characters will cause problems in file and folder structure. As an example / is valid in a filename on Apple, but will break the zip files we generated when using baskets or sending files. In the case of an upload, DOQMIND will replace these characters with an underscore '_'. When renaming a file, or creating a folder, a message will be shown asking to rename the file or folder. The following characters are considered illegal:
< > : " / \ | ? * ' ; =Dots at the end of a filename
A dot (.) is not allowed at the end of a file or folder name. Dots will be removed during upload, or a message will be shown when trying to rename or create a folder.
White spaces are trimmed
Leading and trailing spaces from file and folder names will be automatically trimmed.
Reserved file names are sanitized
Some operating systems, mainly Windows, have reserved filenames. It is not possible to create files with these reserved names. In the case of an upload, DOQMIND will prepend these characters with an underscore '_'. When renaming a file, or creating a folder, a message will be shown asking to rename the file or folder.
These reserved names are:
COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9
LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9Some examples:
CON becomes _CON
PRN becomes _PRN
…