Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have many zip-files where there are encoding errors for the German umlauts (äüöÄÜÖß). They show up in both the as well as in the included directories and files like this:

  • Fünf = Fu╠ênf
  • Räuber = Ra╠êuber
  • Überfall = U╠êberfall

and so on. Usually I use Linux, but because of this issues I also tried a Windows7 VM but it results in the same encoding mess up. On Linux I played around with convmv and detox, but with no success.

When I use

  • convmv -f iso-8859-1 -t utf8 --replace --notest -r *

I get "Skipping, already UTF-8".

Any thoughts about this?

share|improve this question
What antique system are you using ? All current Linux distributions uses UTF-8 now. – BatchyX Jan 13 '13 at 15:51
Could this be a filesystem problem? Perhaps it is not mounted in UTF? – terdon Jan 13 '13 at 15:59
I use Linux Mint 13 (based on Ubuntu 12.04 LTS with Kernel 3.2.0-23), so this is far from antique. And as I already wrote I also tried that files on a Windows 7 VM. But of course I don't know what the one who created the zip files used. – cider Jan 13 '13 at 15:59
This encoding seems some kind of DOS encoding. Usually if I see issues with UTF8 encoding the German umlauts look like ä = ä or Ü = Ãœ – cider Jan 13 '13 at 16:05
@cider try find -type f -print0 |xargs -r -n1 -0 convmv -f WINDOWS-1252 -t UTF-8 --notest This find files from current dir forward and runs convmv separately on each file. Filename is encoed as nullterminated list. – Manwe Jun 26 '15 at 21:35

My guess is the filesystem that you are attempting to decompress or manipulate the files. FAT32 isn't going to like your umlauts. Try copying these files off of the flash drive (or what have you) and then decompress the zip file to see what kind of characters the filenames produce.

Both NTFS (Windows) and Ext4 (Mint) shouldn't have a problem with the name encoding.

The name encoding of the zip files themselves on the FAT32 system are most likely not going to change or be fixed when you copy them to a proper supporing filesystem, but the subdirectories when decompressed should be fine.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.