Bug 329573 - Ark can't manage Spanish characters (ñ, á, é, ú...)
Summary: Ark can't manage Spanish characters (ñ, á, é, ú...)
Status: RESOLVED DUPLICATE of bug 240727
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: 2.19
Platform: Chakra Linux
: NOR normal
Target Milestone: ---
Assignee: Raphael Kubo da Costa
URL: https://dl.dropboxusercontent.com/u/2...
Depends on:
Reported: 2014-01-03 19:00 UTC by demonmusic
Modified: 2015-09-24 14:07 UTC (History)
1 user (show)

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


Note You need to log in before you can comment on or make changes to this bug.
Description demonmusic 2014-01-03 19:00:18 UTC
Ark GUI can't manage Spanish characters. I can't extract a zip file because invalid characters inside (https://dl.dropboxusercontent.com/u/2135959/ark.png).  On the other hand, peazip shows a wrong character but can extract it. (https://dl.dropboxusercontent.com/u/2135959/Peazip.png)

Moreover, doing it by cli with "ark -b 'filename'" extracts the .zip showing a wrong character (like peazip). 

I think Ark can't manage those characters when file is not compressed with Linux system.

Reproducible: Always

Steps to Reproduce:
1. Download this file: http://www.hhgroups.com/albumes/dr.-loncho/el-libro-de-la-vida-37301/ clicking blue arrow next to "Dr. Loncho - El libro de la vida (Descarga completa)" bold text. (it's a legal one)
2. Open .zip file and extract files. 

Actual Results:  
You won't see (in your folder) track number 2, which contains an 'ñ'.

Expected Results:  
Show correct character inside Ark and extract all files. 

As a workaround I created a new entry in menu with "LC_ALL=es_ES@euro" prefix to extract those files with wrong characters. Works too with "LC_ALL=en_US@euro".

"LC_ALL=es_ES@euro" and "LC_ALL=es_ES@euro" prefix will break compressed files by Linux with Spanish characters.
Comment 1 Ragnar Thomsen 2015-09-24 14:07:10 UTC
This is probably caused by the bad unicode support of infozip.

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