On Wednesday, 28 October 2026 09:55:37 Central European Standard Time Jonathan
Wakely via SG16 wrote:
> We have utf-8 now. If a new encoding gets created and gets used for a
> significant amount of content, then browsers and other applications
> probably *should* handle it.

Now that we have UTF-8 (and WTF-8), there shouldn't be a need for a new
encoding. I doubt we'll be defining new ones that have any relevance in the
future.

The problem is all the old ones.

For Qt 6.0, we dropped QTextCodec and added a simple QStringConverter that
supported *only* the UTF codecs (not including UTF-7), plus Latin1 and
"System", which we forced to be UTF-8 everywhere except Windows) A few
releases later, we added support for other codecs back using ICU because
people still need to read old content and sometimes write it too. This is
recent experience: 2022.

> > And it doesn’t even cover a fraction of
> > https://www.iana.org/assignments/character-sets.
>
> Yes. But most of those are even more legacy than the legacy ones in the
> WhatWG spec.

Indeed. But no less relevant.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Principal Engineer - Intel Data Center - Platform & Sys. Eng.