And modified version intended to non-English Windows users mainly.
Because some Windows zip file has legacy windows codepage filenames in zip files.
When archive file was made in OSX, it only has UTF-8 filenames in it except ASCII filenames.
Therefore non-English Windows user can't read non-English filenames.
If you assign Windows encoding(such as CP949 for Korean, CP850 for French which can be given libiconv encoding list) on zip format , you can make Windows or linux compatible zip archive file.
It also support Unicode zip filename in zip, if filenames are not encoded with above assigned encoding. This behavior is same as Windows's Winzip did.
So it reserves maximum compatibility. when legacy windows Archive utility open this file, it can reads non-Unicode files at least.
But for multilingual user, I recommend to use 7zip format.
In case of 7zip format, it supports Unicode normalization.
So some characters which are stored in decomposed way( such as u umlaut ) are archived into Unicode NFC(Normalization Form preComposed) way which mainly used in Windows or Linux.
I recommend you to use CleanArchiver, when you exchange files between Windows or Linux users.
Actually if you archive files in zip format, it use info-zip command utility internally.
It supports legacy obfuscation password only.
If you want AES encryption, select 7zip format with password.
Or another trick,
If you select 7zip format and give a option '-tzip -mem=AES256' into More archive option text field, you can make AES-256 encrypted zip file.
But archive file's extenstion still remains '.7z', so you need to rename it into '.zip'.
I consider adding encryption methods into my modified version.
try this
http://www.mediafire.com/file/nlnwiozndm4/CleanArchiver_2.4a...
I gave all modified source code to original CleanArchiver maker, but it haven't been implemented yet.