[Desktop-packages] [Bug 495880] Re: File Roller cannot handle archive that doesn't encode filenames in UTF-8

2016-05-16 Thread Sebastien Bacher
** Changed in: file-roller (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: file-roller (Ubuntu)
 Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/495880

Title:
  File Roller cannot handle archive that doesn't encode filenames in
  UTF-8

Status in File Roller:
  Confirmed
Status in file-roller package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: file-roller

  I have received a zip containing a file with a german "Umlaut" in the
  filename. I cannot extract the file because I get the following error
  message:

  caution: filename not matched:  Liste Verwaltung und Verk\?ndigung
  Dezember 2009.xls

  I have no possibility to change the filename and eliminate the
  "Umlaut" in the filename...

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: e27141b8feed9a0134eefdd87f008818
  CheckboxSystem: 558fbfb2a1258711a37bb7e23c5d4e6e
  Date: Sat Dec 12 11:48:49 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/file-roller
  NonfreeKernelModules: nvidia
  Package: file-roller 2.28.1-0ubuntu1
  ProcEnviron:
   LANGUAGE=de_DE.UTF-8
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-386
  SourcePackage: file-roller
  Uname: Linux 2.6.31-16-386 i686
  XsessionErrors:
   (gnome-settings-daemon:3121): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:3121): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:3161): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:3155): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/495880/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 495880] Re: File Roller cannot handle archive that doesn't encode filenames in UTF-8

2016-05-16 Thread Bug Watch Updater
** Changed in: file-roller
   Status: Unknown => Confirmed

** Changed in: file-roller
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/495880

Title:
  File Roller cannot handle archive that doesn't encode filenames in
  UTF-8

Status in File Roller:
  Confirmed
Status in file-roller package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: file-roller

  I have received a zip containing a file with a german "Umlaut" in the
  filename. I cannot extract the file because I get the following error
  message:

  caution: filename not matched:  Liste Verwaltung und Verk\?ndigung
  Dezember 2009.xls

  I have no possibility to change the filename and eliminate the
  "Umlaut" in the filename...

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: e27141b8feed9a0134eefdd87f008818
  CheckboxSystem: 558fbfb2a1258711a37bb7e23c5d4e6e
  Date: Sat Dec 12 11:48:49 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/file-roller
  NonfreeKernelModules: nvidia
  Package: file-roller 2.28.1-0ubuntu1
  ProcEnviron:
   LANGUAGE=de_DE.UTF-8
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-386
  SourcePackage: file-roller
  Uname: Linux 2.6.31-16-386 i686
  XsessionErrors:
   (gnome-settings-daemon:3121): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:3121): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:3161): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:3155): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/495880/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 495880] Re: File Roller cannot handle archive that doesn't encode filenames in UTF-8

2016-05-15 Thread Mathew Hodson
** Bug watch added: GNOME Bug Tracker #306403
   https://bugzilla.gnome.org/show_bug.cgi?id=306403

** Also affects: file-roller via
   https://bugzilla.gnome.org/show_bug.cgi?id=306403
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/495880

Title:
  File Roller cannot handle archive that doesn't encode filenames in
  UTF-8

Status in File Roller:
  Unknown
Status in file-roller package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: file-roller

  I have received a zip containing a file with a german "Umlaut" in the
  filename. I cannot extract the file because I get the following error
  message:

  caution: filename not matched:  Liste Verwaltung und Verk\?ndigung
  Dezember 2009.xls

  I have no possibility to change the filename and eliminate the
  "Umlaut" in the filename...

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: e27141b8feed9a0134eefdd87f008818
  CheckboxSystem: 558fbfb2a1258711a37bb7e23c5d4e6e
  Date: Sat Dec 12 11:48:49 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/file-roller
  NonfreeKernelModules: nvidia
  Package: file-roller 2.28.1-0ubuntu1
  ProcEnviron:
   LANGUAGE=de_DE.UTF-8
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-386
  SourcePackage: file-roller
  Uname: Linux 2.6.31-16-386 i686
  XsessionErrors:
   (gnome-settings-daemon:3121): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:3121): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:3161): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:3155): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/495880/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 495880] Re: File Roller cannot handle archive that doesn't encode filenames in UTF-8

2015-04-14 Thread Misaki
Along with the command-line version of unzip with the -O option, you can
also use the convmv command to change filenames of previously extracted
files. This works on an ext3 filesystem, but NTFS may give an error
because filenames are invalid. ext3 says the encoding is invalid but
still lets them be renamed to that.

So for anyone who encounters this bug report and is concerned
specifically with extracting filenames from shift-jis encoded archives,
these are the commands you can use:

(navigate to directory, and...)
unzip -O shift-jis 
or
convmv * -f utf8 -t iso8859-1 -r
convmv * -f utf8 -t iso8859-1 --notest -r ; convmv -f shift-jis -t utf8 * 
--notest -r

One of the other bug reports links to this, which lists solutions and problems:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483290

One consideration might be if files in the same archive use different
encoding types. It seems reasonable that they appeared that way to the
archive's creator, and thus they shouldn't be interpreted separately,
but it could lead to the wrong conversion method being selected.

The patch linked in that bug report describes the options -O and -I,
which aren't documented in unzip's manual pages, so it's possible that
patch is already applied. But it still didn't detect 'proper' encodings
for me when I tested file-roller, using unzip, on several archives after
uninstalling p7zip.

The patch also talks the current locale charset. Making assumptions
about the encoding used on files could be correct for many people, most
of the time, but will be incorrect for other people, and so is at best
only a partial solution. I don't know what the patch does after that
though.

Just for reference, these are other Debian bugs mentioned in that
report:

> Bug#197427: unzip: chinese filenames unwrapped on unix wrongly
> Bug#197428: unzip: zipinfo (and unzip) can't deal with chinese filenames like 
> miniunzip can
> Bug#339021: unzip: incorrectly converts cyrillic file names from 
> Windows-created ZIPs

** Bug watch added: Debian Bug tracker #483290
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483290

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/495880

Title:
  File Roller cannot handle archive that doesn't encode filenames in
  UTF-8

Status in file-roller package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: file-roller

  I have received a zip containing a file with a german "Umlaut" in the
  filename. I cannot extract the file because I get the following error
  message:

  caution: filename not matched:  Liste Verwaltung und Verk\?ndigung
  Dezember 2009.xls

  I have no possibility to change the filename and eliminate the
  "Umlaut" in the filename...

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: e27141b8feed9a0134eefdd87f008818
  CheckboxSystem: 558fbfb2a1258711a37bb7e23c5d4e6e
  Date: Sat Dec 12 11:48:49 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/file-roller
  NonfreeKernelModules: nvidia
  Package: file-roller 2.28.1-0ubuntu1
  ProcEnviron:
   LANGUAGE=de_DE.UTF-8
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-386
  SourcePackage: file-roller
  Uname: Linux 2.6.31-16-386 i686
  XsessionErrors:
   (gnome-settings-daemon:3121): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:3121): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:3161): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:3155): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/495880/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 495880] Re: File Roller cannot handle archive that doesn't encode filenames in UTF-8

2015-04-14 Thread Misaki
The undocumented -O/-I option~

So unzip can handle different encodings, at least when I tested it. But
it doesn't handle them automatically. p7zip doesn't work because, as
noted in Bug #269482, it only handles UTF-8 and ASCII (or maybe
ISO-8859).

When I uninstalled p7zip and p7zip-full and looked at archives, some had
the pattern of mojibake that I'm used to, and some had a new type. None
of them were correct. So it's possible there is some automatic
correction and this is why Bug #580961 for unzip has been marked as
fixed.

Automatic detection can probably usually be correct, but it could also
sometimes be wrong. Either file-roller or unzip could probably improve
their automatic detection, and in case certainty is low communicate this
to users so they know there might be a problem.

Two other bugs, #592109 and #1199239, refer to non-ASCII filenames
encoded in UTF-8, which is likely to be the output from Unix-like
systems.

So non-UTF-8 encodings are probably from computers running Windows (?).

Some open-source programs that do automatic detection of encodings
include Firefox and, I think, gedit. Also maybe a bit similar to magic
numbers used to determine file types..?

This might be how those programs already do this, but I think the way to
detect the proper encoding is to interpret the filenames as a certain
type, and then look for characters, or character combinations, that are
unlikely to appear in a normal filename, or that can't even be output on
the file system type.

For example, the character '‚', U+0082  BREAK PERMITTED HERE,
often appears in some languages when common encodings are interpreted as
iso8859(-number?). Either file-roller or unzip could test various
combinations to see what looks valid.

This is worse than an archive file saying what encoding it uses, but
basically it seems like some regions (like Japan) don't feel like using
UTF-8. The zip format, which is probably worse than other formats in
handling filenames, is probably still used because it encodes the
contents of files separately, which means it's faster but gives worse
compression than other archive formats. Maybe there are other reasons
it's faster too.

Having a unique file suffix for a certain set of compression options or
quality means that people don't have to worry about which options to
choose, and can't argue about which ones other people should use for
that suffix. There is probably also a sort of stigma attached to having
a poor compression ratio for many types of files, compared to other
formats. (For example, some non-zip archive formats can compress a
windows bmp file so that it's smaller than a png of the same image,
especially if the image has repeating portions.)

So either people can agree on a 'low-quality' archive suffix to use in
cases where actual compression isn't important, that's also operating-
system independent, or we will continue to encounter zips from different
languages that don't tell you how to decode the file names.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/495880

Title:
  File Roller cannot handle archive that doesn't encode filenames in
  UTF-8

Status in file-roller package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: file-roller

  I have received a zip containing a file with a german "Umlaut" in the
  filename. I cannot extract the file because I get the following error
  message:

  caution: filename not matched:  Liste Verwaltung und Verk\?ndigung
  Dezember 2009.xls

  I have no possibility to change the filename and eliminate the
  "Umlaut" in the filename...

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: e27141b8feed9a0134eefdd87f008818
  CheckboxSystem: 558fbfb2a1258711a37bb7e23c5d4e6e
  Date: Sat Dec 12 11:48:49 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/file-roller
  NonfreeKernelModules: nvidia
  Package: file-roller 2.28.1-0ubuntu1
  ProcEnviron:
   LANGUAGE=de_DE.UTF-8
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-386
  SourcePackage: file-roller
  Uname: Linux 2.6.31-16-386 i686
  XsessionErrors:
   (gnome-settings-daemon:3121): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:3121): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:3161): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:3155): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/495880/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : 

[Desktop-packages] [Bug 495880] Re: File Roller cannot handle archive that doesn't encode filenames in UTF-8

2013-04-14 Thread Ma Xiaojun
As I marked some bugs as duplicate of this one.

I'd repeat the workaround for 12.04+ is using "unar" command line tool.

Since the encoding issue usually happen with ZIP archives, -O/-I option
of unzip (available 11.10+) also worth a try.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/495880

Title:
  File Roller cannot handle archive that doesn't encode filenames in
  UTF-8

Status in “file-roller” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: file-roller

  I have received a zip containing a file with a german "Umlaut" in the
  filename. I cannot extract the file because I get the following error
  message:

  caution: filename not matched:  Liste Verwaltung und Verk\?ndigung
  Dezember 2009.xls

  I have no possibility to change the filename and eliminate the
  "Umlaut" in the filename...

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: e27141b8feed9a0134eefdd87f008818
  CheckboxSystem: 558fbfb2a1258711a37bb7e23c5d4e6e
  Date: Sat Dec 12 11:48:49 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/file-roller
  NonfreeKernelModules: nvidia
  Package: file-roller 2.28.1-0ubuntu1
  ProcEnviron:
   LANGUAGE=de_DE.UTF-8
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-386
  SourcePackage: file-roller
  Uname: Linux 2.6.31-16-386 i686
  XsessionErrors:
   (gnome-settings-daemon:3121): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:3121): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:3161): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:3155): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/495880/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp