Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Trying to compress a file with "≠" in it's filename causes an error #322
For TAR and LZIP it seems to work fine... but with other formats it seems to either just show an error "Fatal error" and not compress a file with "≠" in it's filename, or it compresses it and shows an error "Minor error, the operation may have been completed".
Not that I need to use "≠" in filenames... but while I was trying to compress some files (a group of various files), there was some file among those files that had that character in it's filename for some reason (I guess that someone probably had a Cyrillic filename on some old version of Windows and that the encoding wasn't UTF-8 and that the encoding was messed up as it was transfers to newer operating systems)... and after trying to determine what was causing an error, it turned out that it was because of that file.
So, not very important... I just renamed that file to solve the issue... but I just thought that you would like to know about it.
Just copying the "≠" sign and renaming any random file to have it in it's filename seems to cause it.
BTW... I'm on Sierra and it's on a HFS+ volume...
I just tried to see would it happened if I moved the file to an APFS volume (where Mojave is installed, but I'm still testing it under Sierra), since APFS does "normalization" differently than HFS+ even if the file is named the same in Finder, and the error doesn't appear when it's on an APFS volume.
This has something to do with the encoding of the OS. Doing more tests, I'm seeing differences with this symbol depending on where it is set or viewed:
In Finder, same symbol, first created in 10.9 and second on 10.12. Stored in a HFS+ DMG r/w image.
In the Terminal, symbols copied/pasted from the DMG below.
Opening this same DMG in 10.13+ does not show any differences in the symbols and does not cause any problem when compressing/extracting.