> Did upstream say anything? I've got a reply from a developer of unzip, but he is also not familiar with those charset issues. I need to discuss it more in upstream. However what I'm trying to do here is a relatively short-term solution. I believe the request in the attached branch is still valid as downstream to workaround real-life problem which users are seeing in daily-use (as non-latin charset users).
> What is "GBK" that Kylin uses and why is it different from the one we have here? I took the charset list from: https://msdn.microsoft.com/en-us/goglobal/bb964654 and msdos/msdos.c in unzip package: 1682 case 932: /* Japanese */ 1683 case 949: /* Korean */ 1684 case 936: /* Chinese, simple */ 1685 case 950: /* Chinese, traditional */ 1686 case 874: /* Thai */ 1687 case 1258: /* Vietnamese */ I'm not so familiar with Chinese charset. I thought CP936 was suitable because we were trying to solve the issue with localized Windows made zip files. GBK may have wider coverage than CP936 though. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
