Bug 137614 - Ark cannot extract non-English named files from tar archive.
Summary: Ark cannot extract non-English named files from tar archive.
Status: RESOLVED DUPLICATE of bug 131113
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Harald Hvaal
URL:
Keywords:
: 146221 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-11-20 12:12 UTC by Youngjoon Kim
Modified: 2007-05-31 23:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
patch on tar.cpp (444 bytes, patch)
2006-11-20 12:16 UTC, Youngjoon Kim
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Youngjoon Kim 2006-11-20 12:12:06 UTC
Version:           2.6.4 (using KDE KDE 3.5.5)
Installed from:    Fedora RPMs
OS:                Linux

When I open tar archive using Ark, select some non-English files, and try to extract, then Ark complains that there are not matched files, and the job fails.

With browsing some codes of Ark, I found such code in arkwidget.cpp file,

ArkWidget::action_extract()
{
   ....
   m_extractList->append(QFile::encodeName(*it));
   ....
}

but I cannot find decoding routine from codes which extract archvies. I think this is the reason why I can't extract non-English files.

So I modified tar.cpp file little bit to decode file names correctly. I modified only tar.cpp, but I think that decoding routing should be applied all file formats supported by Ark.
Comment 1 Youngjoon Kim 2006-11-20 12:16:38 UTC
Created attachment 18623 [details]
patch on tar.cpp 

I modified tar.cpp little bit to decode file names, and I cannot assure this is
good solution, but I found this works for non-English named files. 

Hope that Ark developers would provide better patches!
Comment 2 Bram Schoenmakers 2007-05-31 23:46:25 UTC
*** Bug 146221 has been marked as a duplicate of this bug. ***
Comment 3 Bram Schoenmakers 2007-05-31 23:50:18 UTC
Note: bug 131113 offers a patch as well.

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