Comment 18 for bug 371167
Revision history for this message
| Alexander Melnichuk (ama-land) wrote | #18 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Same thing here with unzipping archives with Russian filenames.
It seems that unzip converts filenames by default from cp850 to cp1252. And this conversion ruins every other encoding. I'm trying to unzip a Windows-created zip archive with Russian filenames (cp866). Now, to restore the correct filenames I have to use the following set of commands as a workaround:
unzip filename.zip
convmv --nosmart --notest -f cp1252 -t cp850 *
convmv --nosmart --notest -f cp866 -t utf8 *
And this works.
It would be much more handy to have unzip autodetect the proper conversion based on the system locale (i.e. cp866->utf8 for Russian, CP936->utf8 for Chinese, etc.) or to be able to specify an unzip command line parameter to override the default conversion of cp850->cp1252 in case autodetection fails.
--------
Tried on Lucid Lynx 10.04 LTS, unzip 6.0-1build1, convmv 1.12
See an example zip with cp866 filenames attached.