A number of zip-based formats encode MIME type information by storing the identifier in a special file at the beginning of the archive. For example, the OpenDocument specification specifies:
The “mimetype” file shall be the first file of the zip file. It shall not be compressed, and it shall not use an 'extra field' in its header.
Unfortunately, the Zip64 extra field is always included in the header, so it isn't possible to create a valid mimetype entry. I understand the issue was addressed once previously in #81 but reappears due to da5df36.
I'm wondering if there's some way to avoid including the Zip64 field in this scenario?
A number of zip-based formats encode MIME type information by storing the identifier in a special file at the beginning of the archive. For example, the OpenDocument specification specifies:
Unfortunately, the Zip64 extra field is always included in the header, so it isn't possible to create a valid
mimetypeentry. I understand the issue was addressed once previously in #81 but reappears due to da5df36.I'm wondering if there's some way to avoid including the Zip64 field in this scenario?