Bug 188576

Summary: Broken encoding when opening archives
Product: [Applications] krusader Reporter: Zdeněk Zikán <zdenek.zikan>
Component: krarcAssignee: Krusader Bugs Distribution List <krusader-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: adaptee, bruce.oy, jan_lepper, krusader-bugs-null, ria.freelander, simon.persson, stumper
Priority: NOR Keywords: reproducible, testcase
Version: 2.4.0-beta3 "Single Step"   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Zdeněk Zikán 2009-03-31 23:38:31 UTC
Version:           2.0.0-SVN "Mars Pathfinder" (using 4.2.1 (KDE 4.2.1), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.28-11-generic

I have files with non-ASCII characters in names packed to tar, tar.gz or zip (haven't tried other formats). If I extract them in respective unpacking programs (tar, unzip), the file names are correct. However, if I open it in Krusader (which uses the same unpacking programs), it shows and extracts file names with wrong encoding - it interprets it as if it was in ISO-8859-1. For instance filename "Vybrané kapitoly z teorie automatů" (correct) is shown and extracted as "Vybrané kapitoly z teorie automatů" (incorrect).
Comment 1 Konstantin 2009-04-12 18:16:21 UTC
Confirm with russian Characters, zip files and Ark. Archives must be packed in windows. See for Ark: https://bugs.kde.org/show_bug.cgi?id=187201. Screenshots and tescase exists.
Comment 2 Konstantin 2009-04-12 18:20:16 UTC
But Krusader have this issue with all archive files! Not with zips. Tested with rar also - same issue.
Comment 3 Lexxa 2010-12-06 18:05:33 UTC
Version 2.2.0-beta1 "DeKade"
The bug is still there. Have to use Ark to get the encoding right.
Comment 4 haldyr 2011-08-22 21:02:34 UTC
Version 2.4.0-beta1 "Migration"
Just tested: The bug is still there.

$ touch s+ěščřžýáí.txt
$ zip archive.zip s+ěščřžýáí.txt
and in krusader I enter to the zip a see:
s?????????.txt
Comment 5 Jekyll Wu 2012-11-14 09:44:22 UTC
The testcase given in comment #4 is still reproduciable for 2.4.0-beta3
Comment 6 Jan Lepper 2013-02-27 13:19:45 UTC
*** Bug 311732 has been marked as a duplicate of this bug. ***
Comment 7 Jan Lepper 2013-02-27 13:48:45 UTC
The problem here is that krarc parses the output of external programs to list the contents of archives.
Running zipinfo -s archive.zip on the file from the testcase in comment 4 outputs:

Archive:  archive.zip
Zip file size: 194 bytes, number of entries: 1
-rw-r--r--  3.0 unx        0 bx stor 13-Feb-27 14:26 s+????????????????.txt
1 file, 0 bytes uncompressed, 0 bytes compressed:  0.0%

I have no idea what to do about this - suggestions are welcome.
Comment 8 Simon Persson 2015-07-12 01:16:41 UTC
This has been solved (I believe) by a combination of fixed unrar and unzip. Krusader now uses the tar:// protocol handler for all tar files. Closing this report as fixed, the fixes will be released in new version of Krusader based on Qt5. If any issues are present in that version, please reopen or file new report. Thanks for reporting!