What feature or improvement do you think would benefit Files?
7z container can support third-party/non-standard codecs for compressing with plugins. For example tc4shell with Modern7z supports compressing with zstd (zstandard), brotli, ecc.
I have some 7z archives compressed with zstd used as a codec. Obviously I don't share these (normally), they are for personal use.
Files right now open these 7z files and displays them, because 7z headers remain the same. However I think that Files should warn the user that those files can't be effectively extracted (in fact, they are not extracted, and when opened directly they are empty). Also, Files could show in properties of these 7z files and others archive types, the codec actually used and not only "7z archive".
If non-standard codec support I can understand is a low-priority, at least a warning should be there to make the user not attempt to modify these archives and therefore corrupting files in them.
Requirements
This proposal will accomplish the "support" of non-standard codecs in 7z archive container either by implementing them OR warn the user to not extract and modify these archives to avoid corruption.
And also displaying correct information in archives properties by showing the codec (e.g. deflate, lzma, zstd, etc.)
Files Version
3.0.5.0
Windows Version
Windows 11 23H2 22635.2771 Feature Experience Pack: 1000.22679.1000.0
What feature or improvement do you think would benefit Files?
7z container can support third-party/non-standard codecs for compressing with plugins. For example tc4shell with Modern7z supports compressing with zstd (zstandard), brotli, ecc. I have some 7z archives compressed with zstd used as a codec. Obviously I don't share these (normally), they are for personal use. Files right now open these 7z files and displays them, because 7z headers remain the same. However I think that Files should warn the user that those files can't be effectively extracted (in fact, they are not extracted, and when opened directly they are empty). Also, Files could show in properties of these 7z files and others archive types, the codec actually used and not only "7z archive".
If non-standard codec support I can understand is a low-priority, at least a warning should be there to make the user not attempt to modify these archives and therefore corrupting files in them.
Requirements
Files Version
3.0.5.0
Windows Version
Windows 11 23H2 22635.2771 Feature Experience Pack: 1000.22679.1000.0
Comments
No response