if you could standardise a file format for a specific task what would you pick and why
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.
Permanently Deleted
Epub isn't supported by browsers
So you want EPUB support in browser and you have the ultimate document file format?
Permanently Deleted
Weasyprint kinda is that, except that it's meant to be rendered to PDF.
Can you explain why you need browser support for epub?
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.
Permanently Deleted
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.