2 ms·
The first thing I think of there is browsing the web. Different image formats have different use cases and substantial advantages over each other. And it's of
by Dylan16807 5y ago
The first thing I think of there is browsing the web.
Different image formats have different use cases and substantial advantages over each other. And it's often impossible to convert without losing quality.
But everything gets to be HTML. Or the compatible variant of XHTML. Nothing else has any real support, and when it did, like flash web pages, that was not good.
For text unicode wins out easily, with UTF-8 and UTF-16 far above the other encodings, and the differences are minor enough that we should just use the better one.
> we should have OOB encoding info (whether in a filesystem config or whatever). This is the only possible path to robust handling of encoding
I don't know about that. Old files, which represent almost all the non-unicode non-ascii text we have, are unlikely to ever be properly tagged. For new files, are those tags really needed? If you have a firewall where you mandate tagging behind it, you're already mandating a format for attaching tags, so why not mandate utf-8 instead?