ZIP format specification says that:
4.4.17 file name: (Variable)
18.104.22.168 The name of the file, with optional relative path.
The path stored MUST NOT contain a drive or device letter, or a leading slash.
All slashes MUST be forward slashes ‘/’ as opposed to backwards slashes '\'
But it seems that:
storedPathnamearguments containing backward slashes without problems. I believe they should either be converted to forward slashes (preferred), or an assertion should be triggered.
filenameis populated “as is” with the path stored in the ZIP file. The problem here is that there are ZIP tools that (especially on Windows) don’t follow the specification and store paths with backward slashes. I believe the
filenamemember should always have forward slashes used, converting them when necessary.
If that is too much of a breaking change, store the correct value in another member named e.g.
partialPath(also fixing the fact that it may not be a simple filename, but an entire partial path)
The latter would also result in a cleaner code for uncompressEntry(), which currently has to deal with the possibility that either forward or backward slashes are used, which is fundamentally wrong