ISO-8859-1 Support Missing

Bug #34667 reported by Adam Kane
8
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Archives of files with ISO-8859-1 encoded filenames with special characters are not extracted correctly into the default UTF-8 encoded Ubuntu ext3 file system.

For example, björk.ogg -> bj?rk.ogg (invalid encoding) after extraction from an archive with ISO-8859-1 filenames.

The UTF-8 migration tool does not rectify this problem, and the migration tool does not work at all on partitions outside /home.

Within a UTF-8 encoded file system, File-Roller should be able to seemlessly extract files with non-UTF-8 encoded filenames, so that the user does not have to manually convert the filenames as a second step.

Many users are needlessly shocked to learn that they seem to have lost all their filename encoding after migrating to Ubuntu.

If Dapper is to be a platform for business users, then this issue must be rectified.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. Do you have an example to attach to the bug about that issue?

Changed in file-roller:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
KarlGoetz (kgoetz) wrote :

I was unable to reproduce the problem with a test archives i created.
tar.bz2 and tar.gz (file inside called 07 - Zerstören.mp3) and the last had a file called "björk.ogg" inside.
I'm not sure what my encodings are, so i cant be sure if the test is relevent or not.
kk

Revision history for this message
Adam Kane (kane-adam) wrote : Re: [Bug 34667] Re: ISO-8859-1 Support Missing

Sorry for the poorly worded bug report. Here's a step-by-step way to
reproduce the issue.

Convert a filename to iso-8859-1. Archive it. Extract it.

This will simulate the scenario where a user archives an iso-8859-1 file,
sends it to their friend, who is using a utf-8 encoded filesystem. The
friend extracts the file and is unable to view the filename correctly.

The ubuntu utf8-migration-tool is supposed to fix this problem, but it is a
one-use tool, and does not fix filenames that a user comes across during
their everyday work.

------------------------------------
Add the universe repository:
http://easylinux.info/wiki/Ubuntu#How_to_add_extra_repositories

sudo apt-get install convmv
cd ~/Desktop
mkdir testdir
cd testdir
gedit björk.txt

Save the file, and close gedit.

convmv -f utf-8 -t iso-8859-1 -r --notest björk.txt
cd ..
tar -czf fûnkyarchive.tar.gz testdir
convmv -f utf-8 -t iso-8859-1 -r --notest fûnkyarchive.tar.gz
rm -r testdir
------------------------------------

Use Nautilus and File-Roller to extract the file. The result is that the
archive and the archived file both have iso-8859-1 encoded filenames, which
are unviewable in the default ubuntu utf-8 encoded filesystem, and must be
manually converted to view correctly.

File-roller and Nautilus should be able to view alternate encoded filenames
and convert extracted filenames on the fly. Note that Rox-Filer is currently
able to view multiple filename encodings.

I've created a Nautilus-script that performs the conversion, but this is a
cumbersome tool for most users.

Thank you for looking into this!

Adam Kane

On 4/6/06, KarlGoetz <email address hidden> wrote:
>
> I was unable to reproduce the problem with a test archives i created.
> tar.bz2 and tar.gz (file inside called 07 - Zerstören.mp3) and the last
> had a file called "björk.ogg" inside.
> I'm not sure what my encodings are, so i cant be sure if the test is
> relevent or not.
> kk
>
> --
> ISO-8859-1 Support Missing
> https://launchpad.net/malone/bugs/34667
>

Revision history for this message
Sebastien Bacher (seb128) wrote :

Reopening according to new comment. You can't say from a filename what is the encoding used for it, do you have any suggestion on how to make it better for such case? Note that GTK has a G_FILENAME_ENCODING variable to use to specify than a different encoding should be used

Changed in file-roller:
status: Needs Info → Unconfirmed
Revision history for this message
KarlGoetz (kgoetz) wrote :

Hi, Adam, can you provide some more details over the next few weeks, or i will reject this bug.
Thanks.

Changed in file-roller:
status: Unconfirmed → Needs Info
Revision history for this message
Daniel Holbach (dholbach) wrote :

Your bug lacks information we would need to investigate further. We
are now going to close the bug - please reopen if you have more
information at hand.

Changed in file-roller:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.