if you could standardise a file format for a specific task what would you pick and why

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
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 (this one is causing a bloodbath so i picked randomly) .tar.zst
configuration files toml
typesetting typst
interchange format .ora
models .gltf / .glb
daw session files .dawproject
otdr measurement results .xml

You're viewing a single thread.

287 comments

I'd setup a working group to invent something new. Many of our current formats are stuck in the past, e.g. PDF or ODF are still emulating paper, even so everybody keeps reading them on a screen. What I want to see is a standard document format that is build for the modern day Internet, with editing and publishing in mind. HTML ain't it, as that can't handle editing well or long form documents, EPUB isn't supported by browsers, Markdown lacks a lot of features, etc. And than you have things like Google Docs, which are Internet aware, editable, shareable, but also completely proprietary and lock you into the Google ecosystem.
- Epub isn't supported by browsers
  So you want EPUB support in browser and you have the ultimate document file format?
  
  It would solve the long-form document problem. It wouldn't help with the editing however. The problem with HTML as it is today, is that it has long left it's document-markup roots and turned into an app development platform, making it not really suitable for plain old documents. You'd need to cut it down to a subset of features that are necessary for documents (e.g. no Javascript), similar to how PDF/A removes features from PDF to create a more reliable and future proof format.
  
  Weasyprint kinda is that, except that it's meant to be rendered to PDF.
  
  Can you explain why you need browser support for epub?
- https://xkcd.com/927/
- EPubs are just websites bound in xhtml or something. Could we just not make every browser also an epub reader? (I just like epubs).
  
  They're basically zip files with a standardized metadata file to determine chapter order, index page, … and every chapter is a html file.
  
  That's the idea, and while at it, we could also make .zip files a proper Web technology with browser support. At the moment ePub exists in this weird twilight where it is build out of mostly Web technology, yet isn't actually part of the Web. Everything being packed into .zip files also means that you can't link directly to the individual pages within an ePub, as HTTP doesn't know how to unpack them. It's all weird and messy and surprising that nobody has cleaned it all up and integrated it into the Web properly.
  So far the original Microsoft Edge is the only browser I am aware of with native ePub support, but even that didn't survive when they switched to Chrome's Bink.
  
  Microsoft Edge's ePub reader was so good! I would have used it all the time for reading if it hadn't met its demise. Is there no equivalent fork or project out there? The existing epub readers always have these quirks that annoy me to the point where I'll just use Calibre's built in reader which works well enough.

287 comments