(btw yes you can add new categories)
if you could standardise one file format for a task, what would it be:
- photos .jxl
- open domain image data .exr
- videos .av1
- lossless audio .flac
- lossy audio .opus
- subtitles srt/ass
- fonts .otf
- container mkv (doesnt contain .jxl)
- plain text utf-8 (many also say markup but disagree on the implementation)
- documents .odt
- archive files .tar.zst (this one is causing a bloodbath so i picked randomly)
- configuration files toml
- typesetting typst
- interchange format .ora
- models .gltf / .glb
- daw session files .dawproject
- otdr measurement results .xml
I don’t see a need, extensions are there for helping software more than helping people.
It’s actually the opposite. To my knowlegde, Windows is the only OS that I’ve used that uses the file extension to determine the contents, but then they hide it from the user. So maybe file extensions are only for windows?
How does osx know how to open a PDF not named .PDF?
Check out https://en.m.wikipedia.org/wiki/Uniform_Type_Identifier for more info.
PDFs have a MIME type of
application/pdf
per the spec, but you might still encounter some with MIME types likeapplication/x-pdf
. MacOS reads the MIME type of a file, then assigns thecom.adobe.pdf
UTI (if it wasn’t already assigned by another Mac application).Huh, TIL. Thanks!