Bug 254966 - Non-ASCII filenamess created with MS Windows cannot be used by KDE applications
Summary: Non-ASCII filenamess created with MS Windows cannot be used by KDE applications
Status: RESOLVED DUPLICATE of bug 165044
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-22 16:51 UTC by Dotan Cohen
Modified: 2013-12-29 21:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Zip file containing three text files that have Hebrew filenames (5.12 KB, application/zip)
2010-10-22 16:51 UTC, Dotan Cohen
Details
Screenshot of Dolphin error relating to bug (92.37 KB, image/png)
2010-11-08 16:45 UTC, Dotan Cohen
Details
RAR version of ZIP file from first post. (6.72 KB, application/rar)
2010-11-13 20:15 UTC, Dotan Cohen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dotan Cohen 2010-10-22 16:51:57 UTC
Created attachment 52766 [details]
Zip file containing three text files that have Hebrew filenames

Version:           unspecified (using KDE 4.5.1) 
OS:                Linux

Files with non-ASCII filenames created by MS Windows cannot be used with KDE applications. These files are displayed in Dolphin as the Unicode Unknown Character (diamond with question mark), and in Ark archives as simple question marks.

Attached is a zip file created on Windows including files with Hebrew filenames to demonstrate.

Reproducible: Always
Comment 1 Christoph Feck 2010-10-22 16:57:48 UTC
Does the ZIP format allow to specify the encoding of the file names?
Comment 2 Dotan Cohen 2010-10-22 17:13:15 UTC
Googling your question, it appears that such functionality was added in 2007 but it is up to the zip encoder, not the decoder, to implement it. Naturally, the Windows internal encoder does not!

I suggest in this case that Ark give an option to specify a default encoding (most user that I know use one language in addition to English) and also to let the user override this on a per-archive and per-file basis.

So should I break this bug into three separate RFEs? They would be:
1) Specify default filename encoding
2) Override default per-archive
3) Override default per-file

That last one may or may not be necessary: I have two users who work with Russian/Arabic filenames in addition to Hebrew _and_ English. I assume that in this case (the case of three different language alphabets' filenames) the filenames are UTF-8, though, and thus the same encoding at least.
Comment 3 Dotan Cohen 2010-10-23 13:38:20 UTC
The problem is not limited to zip files. Here is a government webpage with files critical to my wife's work, which have Hebrew filenames and cannot be opened, renamed, or deleted in KDE 4.5:
http://www.orianit.edu-negev.gov.il/matyabs/files/default.asp?d=E:\orianit\matyabs\files\%FA%EC%E0+%E5%FA%E7%E9\

This bug is critical enough that I have to remove KDE from the wife's computer so that she could use these files.
Comment 4 Christoph Feck 2010-10-28 01:01:13 UTC
Can you check if Qt 4.7.0 fixes this problem? A related bug 255016 seems to indicate it might be a Qt bug.
Comment 5 Dotan Cohen 2010-10-28 09:38:56 UTC
Qt 4.7 does not fix this problem. In fact, I was on Qt 4.7 at the time of filing.
Comment 6 Dotan Cohen 2010-11-08 16:45:11 UTC
Created attachment 53249 [details]
Screenshot of Dolphin error relating to bug

Attached is a screenshot of trying to delete one of the files mentioned. No KDE application can delete them, I had to install Nautilus (Gnome) to delete the files.
Comment 7 Dotan Cohen 2010-11-13 20:15:25 UTC
Created attachment 53401 [details]
RAR version of ZIP file from first post.

To help clarify that the issue is not only with ZIP archives as the first few posts imply, I had the foresight to make both ZIP and RAR archives of the files. Attached find the RAR version. Notice that it, too, has problems with the filename encoding when used in KDE, however, instead of the Unicode Unknown Character (diamond with question mark) it gives question marks in place of Hebrew characters.
Comment 8 Dotan Cohen 2010-11-15 12:49:18 UTC
Note that the files from the website mentioned in Comment #3 work fine in Gnome.
Comment 9 Christoph Feck 2013-12-29 21:52:41 UTC

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