Bug 345519 - ark has problems working with some archives with files in them with some unusual characters in them. like 'ê'
Summary: ark has problems working with some archives with files in them with some unu...
Status: RESOLVED DUPLICATE of bug 240727
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: 2.19
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Raphael Kubo da Costa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-25 17:36 UTC by rezad1393
Modified: 2015-09-24 13:55 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
the zip file (44.62 KB, application/zip)
2015-03-25 17:38 UTC, rezad1393
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rezad1393 2015-03-25 17:36:55 UTC
if I open some files that have unusual characters in their names ark doesn't show the filename correctly and shows a square shape in place of that character.
and dragging that file to dolphin file manager wont extract it there and doesn't give an error message either.
extracting the archive content changes the filename character that gives this error to the square shape.
extracting the same archive with gnome equivalent app,file-roller,doesn't have these issues.
nor this occurs with 7zip app.

this happens with a certain zip files not all of them.specifically I see this happening with zip file downloaded from opensubtitle website.

and if I extract the file with 7zip then compress to zip format with ark the issue disappers so probabely this occurs with that specific version of zip file .

Reproducible: Always

Steps to Reproduce:
1.open the attacheted zip file with ark.
2.file name is not correctly shown.
3.

Actual Results:  
this is the name shown
Tavernier, Bertrand - (1974) - Que la F+
Comment 1 rezad1393 2015-03-25 17:38:06 UTC
Created attachment 91736 [details]
the zip file
Comment 2 Ragnar Thomsen 2015-09-24 13:55:29 UTC
This is caused by bad unicode support of infozip.

*** This bug has been marked as a duplicate of bug 240727 ***