@Yuan,
For example "王妃.zip" you posted, it has short file names in the archive. Even
with unar/lsar it fails to detect encoding (you expect CP932, but lsar shows
it's ISO-8859-8). Auto detection of encoding is not 100% reliable especially
with short file names (less hints for encoding detector).
====
$ lsar -l -pe 王妃.zip
王妃.zip: Zip
Flags File size Ratio Mode Date Time Name
===== ========== ===== ==== ========== ===== ====
0. ----- 40344 82.9% Defl 2014-10-03 13:40 %cd%f5%e5%fa_A.ust
1. ----- 20311 80.4% Defl 2014-10-03 13:40 %cd%f5%e5%fa_B.ust
(Flags: D=Directory, R=Resource fork, L=Link, E=Encrypted, @=Extended
attributes)
(Mode: Defl=Deflate)
Encoding: ISO-8859-8 (76% confidence)
====
Anyway enabling auto-detection or specifying encoding in file-roller is
out of scope of this bug report. You need to open separate bugs if
needed. I would like to proceed with fallback setting in the attached
branch for vivid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422290
Title:
Default charsets handling for Windows archives in CJKV+th locale
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unzip/+bug/1422290/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
