Calling 7z e file.zip on Windows automatically mangles filenames with unsupported characters so they are writable to the filesystem. Duplicate/existing files are also handled nicely. Would you like to replace the existing file: Path: .\tes_.t_t Size: 7 bytes (1 KiB) Modified: 2022-05-30 11:05:46 with the file from archive: Path: tes<.t>t Size: 7 bytes (1 KiB) Modified: 2022-05-30 11:05:46 Unfortunately the output filename/mapping from listing to disk is hard to predict (and it might change with 7z...
-bb switch not referenced in commands documentation
While I haven't dug deep into these, as I understand it, each file comes prefixed with a pax extended header. (there's an IBM z/OS article on these and I've seen a Microsoft C# implementation here. the spec is here) When iterating you're supposed to parse the pax header and apply its attributes to the next file, as some of them are not appropriate for/extend on the standard tar/ustar header. I believe in this specific case that the idea is that the tar header will only allow an integer modification...
While I haven't dug deep into these, as I understand it, each file comes prefixed with a pax extended header. (there's the spec on these and I've seen a Microsoft C# implementation here. the spec is here) When iterating you're supposed to parse the pax header and apply its attributes to the next file, as some of them are not appropriate for/extend on the standard tar/ustar header. I believe in this specific case that the idea is that the tar header will only allow an integer modification timestamp,...
While I haven't dug deep into these, as I understand it, each file comes prefixed with a pax extended header. (there's an IBM z/OS article on these and I've seen a Microsoft C# implementation here ) When iterating you're supposed to parse the pax header and apply its attributes to the next file, as some of them are not appropriate for/extend on the standard tar/ustar header. I believe in this specific case that the idea is that the tar header will only allow an integer modification timestamp, but...
Tars with pax headers not parsed