SMB should support enhanced Unicode
Updated by Gordon Ross about 1 year ago
- Status changed from New to In Progress
Customer experienced a problem when a Windows 10 user, mounting a CIFS share attempted to copy files to the folder that contained unicode characters, in this case a Fire Symbol and another file containing the Speaker Symbol.
The files do not appear in the Windows Explorer, however when the user attempts to copy the "missing" files, Windows complains that the files already exist.
Steps to Reproduce: Take the attached zip file (unicode.zip) and copy to a Windows client. Unpack the data to a local NTFS filesystem and observe the Fire and Speaker symbols in two of the filenames.
Map a share from the appliance, then copy the data across. You'll notice no error during the copy but the data is not displayed.
When I attempted to recopy the "missing" files, I got an error from Windows that said it 'Could not find this item' which is different to the customer, but still problematic.
Expected Results: Customer expects the appliance to handle files with unicode in them
Actual Results: The files end up on the ZFS filesystem, but there's no way to view these from the CIFS client.