if you could pick a standard format for a purpose what would it be and why?
e.g. flac for lossless audio because…
(yes you can add new categories)
summary:
- photos .jxl
- videos .av1 (someone mentioned mka or something like that, cant recall but thet mentiomed it being a ‘container’)
- daw session files .dawproject
- documents .odt
- archive files (this one is causing a bloodbath so i picked randomly) .tar.zst
- models .gltf / .glb
- plain text utf-8
- interchange format .ora
- configuration files toml OR yaml (disagreement)
- typesetting typst
- open domain image data .exr
- lossless audio .flac
- lossy audio .opus
- subtitles srt/ass
- container mkv
But it’s not a tarxz, it’s an xz containing a tar, and you perform operations from right to left until you arrive back at the original files with whatever extensions they use.
If I compress an exe into a zip, would you expect that to be an exezip? No, you expect it to be file.exe.zip, informing you(and your system) that this file should first be unzipped, and then should be executed.
So what? When you zip 5 documents together do you name it .zip or .config.lib.sh.deb.zip?
Double extensions are not conventional on Windows, so no, I do not.
Dots in filenames are commonly used in any operating system like name_version.2.4.5.exe or similar… So I don’t see a problem.
Dots yes, nested extensions no.
The expected behavior is: you have a .exe binary called Example.exe. This is an executable.
Now you zip it. It’s no longer an executable binary, it’s a zip archive. Yes, the data can be reconstructed into the original file - but it is not the original file. It should now be called Example.zip, as it is a zip file.
This is important both for user mental models, but also because operating systems that use extensions as the primary indicator of file type often will hide known extensions by default, and the nested extensions in the name can create trouble.