Replies: 1 comment 1 reply
-
It is likely a bug if that code does not conform to the comment above it. Feel free to submit a PR. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Look at mz_os.h:
MZ_PATH_SLASH_PLATFORM is used to create metadata in the zip file which stores the paths with backslashes on windows instead of slashes.
I wonder why this is the case?
Also look at mz_zip.c:
This changes the last backslash in a path to a slash. Independent of if running on windows or not.
This leads to metadata which has paths with mixed slashes and backslashes.
Also I wonder why this is done?
I also checked what happens when you use the system functionality of Windows 10 to create a zip file. Windows 10 is creating paths with slashes only.
So I guess that the reason for backslashes for zip files created with minizip on windows must be something related to an old version of windows or some old tools?
The reason why I am asking this whole questions is because we use a C# unzipping library which is unable to unzip zip files which use backslashes for paths.
I wonder if minizip should be updated to only create zip files with paths having slashes only, or the C# unzipping library should be updated to also support backslashes?
Beta Was this translation helpful? Give feedback.
All reactions