I'd like to know if there's a way to make "-mcu" switch, which force the output ZIP format file name to be encoded in UTF-8, the default behavior when using the explorer shell extension to create a .zip file? The default behavior is only encode characters that are not found in the current code page in UTF-8, which simply doesn't work for me.
Thanks,
Frank
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks, Igor, for your quick response. I don't quite understand why the default behavior is "use UTF-8 file names only if the local code page doesn't contain required symbols." Is this a backward compatibility thing with respect to legacy unzippers?
I have one more feature suggestion: I figured out that the settings in "Add to archive..." window is automatically saved, so that when I use this dialog once again, it loads the settings I have used in the last time. Can you consider a feature for "Add to <Archive>.zip" option to take advantages of such saved setting in future versions?
Thanks,
Frank
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, it's for better compatibility. For example, ZIP from Windows doesn't understand UTF-8.
Now most users from your country can extract most .zip archives from you with current default settings.
- Can you consider a feature for "Add to <Archive>.zip" option to take advantages of such saved setting in future versions?
I'm not sure about such feature.
Some users can set some unusual options, that are not good for default archives.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
I'd like to know if there's a way to make "-mcu" switch, which force the output ZIP format file name to be encoded in UTF-8, the default behavior when using the explorer shell extension to create a .zip file? The default behavior is only encode characters that are not found in the current code page in UTF-8, which simply doesn't work for me.
Thanks,
Frank
The only way now
1) always use "Add to archive ..." item.
2) In parameters write:
cu
Thanks, Igor, for your quick response. I don't quite understand why the default behavior is "use UTF-8 file names only if the local code page doesn't contain required symbols." Is this a backward compatibility thing with respect to legacy unzippers?
I have one more feature suggestion: I figured out that the settings in "Add to archive..." window is automatically saved, so that when I use this dialog once again, it loads the settings I have used in the last time. Can you consider a feature for "Add to <Archive>.zip" option to take advantages of such saved setting in future versions?
Thanks,
Frank
Yes, it's for better compatibility. For example, ZIP from Windows doesn't understand UTF-8.
Now most users from your country can extract most .zip archives from you with current default settings.
- Can you consider a feature for "Add to <Archive>.zip" option to take advantages of such saved setting in future versions?
I'm not sure about such feature.
Some users can set some unusual options, that are not good for default archives.