Show threadGiuseppe BilottaJul 23, 2025

I would rather NOT rewrite our .zip archive code to do the «unpack in separate directory and then remove» thing. So does anybody know of a different C++ library to access zip archive contents directly that DOES support #Zip64?

#askFedi #fediHelp #CPlusPlus #askMastodon #mastoHelp

Giuseppe BilottaJul 23, 2025
Oh well that's just peachy. #EUMETSAT switched to #Zip64 for its zipped data archives even when standard zip worked fine (I assume for consistency with situations where it didn't?), and #Zipios, the C++ library we're using to access the file inside the zip without unpacking the archive, does not support Zip64.
Neustradamus :xmpp: :linux:Jun 3, 2025
#libzip 1.11.4 has been released (#LZMA / #ZIP / #Zip64 / #zstd / #Zstandard / #bzip2 / #AES / #PKWARE / #FileArchiver / #DataCompression) https://libzip.org/
libzip

Show threadThomas TempelmannFeb 25, 2024
@nicklockwood The reason why Apple doesn't set this information is, I suspect, because they can compress > 4 GB of data into a single stream, something that's officially not supported by original zip, and that's why some other zip tools can't uncompress Apple-generated zip files with data > 4 GB in them (it's a smart work-around the problem to support the #zip64 standard, which isn't very popular). However, Apple's zip should still set these header values if they can, but they don't :(
Collabora OfficeJun 16, 2023

Watch Attile Szűcs' talk on 𝗛𝘂𝗴𝗲 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝘀 𝗶𝗻 @libreoffice and hear about the capabilities and challenges of the #Zip64 support implementation.

#CollaboraOnline #COOLdays #opensource

https://youtu.be/GZPmcpfXIhg

Huge Documents in LibreOffice (Zip64 support) by Attila Szűcs 🆒 #COOLDays 2023

YouTube