On 04/12/2019 18.05, Per Jessen wrote:
James Knott wrote:
On 2019-12-04 11:47 AM, Per Jessen wrote:
AFAIK, the only thing gained with exFAT is support for large files,
And long file names. You may recall using the dir command and seeing all the short file names containing a ~.
Right, I forgot about that one.
Maybe also UTF8 in filenames?
From a quick read, some fields are ASCII and some Unicode. «3.1.2 FileSystemName Field The FileSystemName field shall contain the name of the file system on the volume. The valid value for this field is, in ASCII characters, "EXFAT ", which includes three trailing white spaces.» ... «7.7.3 FileName Field The FileName field shall contain a Unicode string, which is a portion of the file name. In the order File Name directory entries exist in a File directory entry set, FileName fields concatenate to form the file name for the File directory entry set. Given the length of the FileName field, 15 characters, and the maximum number of File Name directory entries, 17, the maximum length of the final, concatenated file name is 255. The concatenated file name has the same set of illegal characters as other FAT-based file systems (see Table 35). Implementations should set the unused characters of FileName fields to the value 0000h.» ... «Implementations may wish to restrict file and directory names to just the ASCII character set. If so they should limit their character use to the range of valid characters in the first 128 Unicode entries. They must still store file and directory names in Unicode on the volume and translate to/from ASCII/Unicode when interfacing with the user.» There are a few invalid chars. <https://docs.microsoft.com/en-us/windows/win32/fileio/exfat-specification> -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)