Fails to uncompress zip archive item with non-roman chars in it

[GoogleCodeExporter]

The attached zip archive was created with OSX 10.5.8's Finder from a file named 
"test äöüÄÖÜß", 
which also has a resource fork.

Unpacking this file with The Unarchiver 2.1 leads to an empty data fork, 
although the original was 
not empty. The rsrc fork get uncompressed correctly, though. Unpacking the same 
with 
BOMArchiveHelper gets correct results, of course.

If the original file does not have a rsrc fork, this bug does not surface.

Hence, the bug is probably tied to the following conditions:
- file has a resource fork
- file has non-roman chars in name

Original issue reported on code.google.com by tempelmann@gmail.com on 18 Oct 2009 at 11:10

Attachments:

• [missing data fork with unarchiver.zip](https://storage.googleapis.com/google-code-attachments/theunarchiver/issue-210/comment-0/missing data fork with unarchiver.zip)

[GoogleCodeExporter]

Original comment by paracel...@gmail.com on 18 Oct 2009 at 9:34

• Changed state: Accepted
• Added labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

I didn't think there could be a bug with those exact conditions, but it turns 
out it's a 
horrible subtle and annoying bug, and it does have exactly those conditions. 
I'll have to 
do some changes to the filename handling to get this working right.

Original comment by paracel...@gmail.com on 21 Oct 2009 at 12:55

[GoogleCodeExporter]

Ok, finally managed to work out fix. Should hopefully work better now.

Thanks for the catch.

Original comment by paracel...@gmail.com on 21 Oct 2009 at 1:30

• Changed state: Fixed

[GoogleCodeExporter]

Issue 209 has been merged into this issue.

Original comment by paracel...@gmail.com on 21 Oct 2009 at 1:33