New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trying to compress a file with "≠" in it's filename causes an error #322

Open
MaxPower85 opened this Issue Nov 11, 2018 · 10 comments

Comments

3 participants
@MaxPower85

MaxPower85 commented Nov 11, 2018

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.

@issuelabeler issuelabeler bot added lzip zip labels Nov 11, 2018

@aonez aonez self-assigned this Nov 12, 2018

@aonez aonez added this to the 1.1.6 milestone Nov 12, 2018

@aonez aonez added more info needed and removed lzip zip labels Nov 12, 2018

@aonez

This comment has been minimized.

Owner

aonez commented Nov 12, 2018

Thanks for the feedback @MaxPower85! I can't seem to reproduce this one. Tried to compress and extract with all the formats without issue. There's any change you can upload here a file that reproduces this issue?

@MaxPower85

This comment has been minimized.

MaxPower85 commented Nov 12, 2018

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.

@no-response no-response bot removed the more info needed label Nov 12, 2018

@aonez

This comment has been minimized.

Owner

aonez commented Nov 12, 2018

I've tested it in High Sierra also with HFS+. I'll do some more tests.

@aonez

This comment has been minimized.

Owner

aonez commented Nov 21, 2018

@MaxPower85 replicated this one on Sierra.

@aonez aonez added bug p7zip labels Nov 21, 2018

@aonez aonez modified the milestones: 1.1.6, 1.1.7 Nov 21, 2018

@aonez

This comment has been minimized.

Owner

aonez commented Nov 21, 2018

So it is OS dependent also. Does not affect 10.13+, at least in my tests with external HFS+ disks.

@aonez

This comment has been minimized.

Owner

aonez commented Nov 21, 2018

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:

screen shot 2018-11-21 at 13 44 15

In Finder, same symbol, first created in 10.9 and second on 10.12. Stored in a HFS+ DMG r/w image.

screen shot 2018-11-21 at 13 42 53

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.

@aonez aonez added the Apple SDK label Nov 21, 2018

@gingerbeardman

This comment has been minimized.

Contributor

gingerbeardman commented Nov 21, 2018

Can you share the DMG? I'd like to inspect encodings and attributes.

≠, not equal to, Unicode: 2260

Maybe it could be related to system font? San Francisco (if so I have a friend on that team)

@aonez

This comment has been minimized.

Owner

aonez commented Nov 21, 2018

@gingerbeardman I'm trying to replicate the test without luck 😅 But I'm sharing with you a DMG containing the two characters I got before. They are in the "First test" folder: test.dmg.zip

@gingerbeardman

This comment has been minimized.

Contributor

gingerbeardman commented Nov 22, 2018

Very odd. If I copy one at a time out of "First test" to a writable directory, they overwrite each other (with confirmation).

Finder also acts oddly when trying to copy "First test" folder to a writable directory.

screen shot 2018-11-22 at 02 19 32

And also when compressing:
screen shot 2018-11-22 at 02 19 20

@aonez

This comment has been minimized.

Owner

aonez commented Nov 23, 2018

Yep, @MaxPower85 found the damned symbol.

@aonez aonez modified the milestones: 1.1.7, Look at Nov 23, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment