Cannot create zip files for Japanese Shift-JIS

[DaddyF]

Configuration

• Keka version: Version 1.3.2 (5208)
• macOS version: Ventura 13.5
• MacBook Pro 14-inch, 2021
  Chip Apple M1 Pro, Memory 16 GB

Describe the bug

I have created a zip file from Japanese folders with Japanese files. It was okay as long as someone who does not use Shift-JIS characters in Windows. However, there are still many people who use Shift-JIS in their files and folders. Their uncompress tools handles Shift-JIS code as a default. I have read some of the Keka usage in Japanese on Japanese web site and it seems that Keka supports Shift-JIS. However, the version I use on Apple Silicon will not handle it as I expected and someone who receives files from me will not be able to read Japanese file names or folder names on Windows. Do you support Shift-JIS in 1.3.2 on Apple Silicon? As long as I don't use Japanese characters, then it works fine. But in many cases, I need to modify those files and send them back to them. Original file names or folder names are in Japanese.

I also tested 7-Zip 23.01 (arm64) on Windows 11 and it handles Shift-JIS code as I expected. But they don't support one on Mac. I am not sure if Keka is related to 7-zip.
If you need any further information, please let me know.

[aonez]

Just to confirm, the issue for you is when you compress files containing Japanese characters on their names on macOS and they uncompress those files on Windows, is that right? That is reproducible on Windows 11, right?

I'm assuming you're using the ZIP format and not 7Z.

[DaddyF]

Instead of Windows 11, I used Windows 10 to unzip the folder which I zipped on Mac.

…

On Aug 6, 2023, at 19:25, aONe ***@***.***> wrote: Just to confirm, the issue for you is when you compress files containing Japanese characters on their names on macOS and they uncompress those files on Windows, is that right? That is reproducible on Windows 11, right? I'm assuming you're using the ZIP format and not 7Z. — Reply to this email directly, view it on GitHub <#1302 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJJFY3XMPCHNCLKN4QDAPQDXT5WKHANCNFSM6AAAAAA3FTO5I4>. You are receiving this because you authored the thread.

[DaddyF]

I have tested it on Windows 11 and the result is the same. But I have used LhaPlus to unzip it. This is very popular zip/unzip tool and our company use it as default. I need to explain that if I use 7-zip, then we have no problems. 7-zip understands the Japanese UTF-8 code, but LhaPlus thinks that all the code is Shift-JIS.

…

On Aug 6, 2023, at 22:50, Sadao Fukatsu ***@***.***> wrote: Instead of Windows 11, I used Windows 10 to unzip the folder which I zipped on Mac. > On Aug 6, 2023, at 19:25, aONe ***@***.***> wrote: > > > Just to confirm, the issue for you is when you compress files containing Japanese characters on their names on macOS and they uncompress those files on Windows, is that right? That is reproducible on Windows 11, right? > > I'm assuming you're using the ZIP format and not 7Z. > > — > Reply to this email directly, view it on GitHub <#1302 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJJFY3XMPCHNCLKN4QDAPQDXT5WKHANCNFSM6AAAAAA3FTO5I4>. > You are receiving this because you authored the thread. >

[DaddyF]

Again, I have tested the other way around. I created a zipped file using LhaPlus on Windows 11. I assume that the zip file name is Shift-JIS. I moved it to MacOS and unzipped it using Keka and it unzipped correctly. No problems.

…

On Aug 6, 2023, at 23:02, Sadao Fukatsu ***@***.***> wrote: I have tested it on Windows 11 and the result is the same. But I have used LhaPlus to unzip it. This is very popular zip/unzip tool and our company use it as default. I need to explain that if I use 7-zip, then we have no problems. 7-zip understands the Japanese UTF-8 code, but LhaPlus thinks that all the code is Shift-JIS. > On Aug 6, 2023, at 22:50, Sadao Fukatsu ***@***.***> wrote: > > Instead of Windows 11, I used Windows 10 to unzip the folder which I zipped on Mac. > >> On Aug 6, 2023, at 19:25, aONe ***@***.***> wrote: >> >> >> Just to confirm, the issue for you is when you compress files containing Japanese characters on their names on macOS and they uncompress those files on Windows, is that right? That is reproducible on Windows 11, right? >> >> I'm assuming you're using the ZIP format and not 7Z. >> >> — >> Reply to this email directly, view it on GitHub <#1302 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJJFY3XMPCHNCLKN4QDAPQDXT5WKHANCNFSM6AAAAAA3FTO5I4>. >> You are receiving this because you authored the thread. >> >

[DaddyF]

I have checked the header information of zipped files and results are attached. The only way to solve this issue seems to be that Keka needs to support Shift-JIS encoding in some way.
What I have found is that 7.docx

[aonez]

Thanks a lot for all the feedback @DaddyF. I'll get back to you shortly.

[aonez]

Hi again @DaddyF. Took a while but finally did some tests without an actual clear way to fix this. I understand UTF-8 is the way to go so files are universally compatible and new files should use that encoding.

Anyway I'm open to adopt an option for Shift-JIS creation, just found no way to do this with the actual state of Keka using 7Z and with all source files (from macOS) encoded in UTF-8.

[DaddyF]

Hi, I understand the situation. I tested 14 beta a few days ago. I can still move files to Windows 11 and use 7-zip to create Shift-JIS files. That is okay. Thank you very much. Sadao

…

On Mar 5, 2024, at 3:44, aONe ***@***.***> wrote: Hi again @DaddyF <https://github.com/DaddyF>. Took a while but finally did some tests without an actual clear way to fix this. I understand UTF-8 is the way to go so files are universally compatible and new files should use that encoding. Anyway I'm open to adopt an option for Shift-JIS creation, just found no way to do this with the actual state of Keka using 7Z and with all source files (from macOS) encoded in UTF-8. — Reply to this email directly, view it on GitHub <#1302 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJJFY3TNMWTFFC5MBGDYRNLYWS6I7AVCNFSM6AAAAAA3FTO5I6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZXGIZTANRSGI>. You are receiving this because you were mentioned.