The iFolder client imposes naming conventions that consider the collective restrictions of the Linux, and Windows file systems. An iFolder, folder, or file must have a valid name that complies with the naming conventions before it can be synchronized.
Use the following naming conventions for your iFolders and the folders and files in them:
iFolder supports the Unicode* character set with UTF-8 encoding.
Do not use the following invalid characters in the names of iFolders or in the names of folders and files in them:
iFolder creates a name conflict if you use the invalid characters in a file or folder name. The conflict must be resolved before the file or folder can be synchronized.
The maximum name length for single path component depends upon the client file system. For filenames, the maximum length includes the dot (.) and file extension.
When you attempt to download or synchronize an iFolder whose name length exceeds the maximum limit supported by the file system, iFolder displays an error message.
Names of iFolders, folders, and files are case insensitive; however, case is preserved. If filenames differ only by case, iFolder creates a name conflict. The conflict must be resolved before the file or folder can be synchronized.
If you create iFolders on a FAT32 file system on Linux, avoid naming files in all uppercase characters. The VFAT or FAT32 file handling on Linux automatically changes the filenames that are all uppercase characters and meet the MS-DOS 8.3 file format from all uppercase characters to all lowercase characters. This creates synchronization problems for those files if the iFolder is set with the Read Only access right.