3 ms·
>would expanding that space really be such a burden? It would require dropping UTF-16, which is the limiting factor. That, or defining planes that aren't avail
by mcdonje 4y ago
>would expanding that space really be such a burden?
It would require dropping UTF-16, which is the limiting factor. That, or defining planes that aren't available to all encodings. Don't hold your breath.
I don't know who is using UTF-16 or UTF-32. It seems like most of the world has adopted UTF-8. So, maybe one day UTF-16 and UTF-32 will be dropped and more planes will be defined. That's a big maybe. If it happens at all, it's decades away. There are no conversations to do so that I'm aware of.
There are currently 10 planes that are completely unassigned, and there are no current proposals to put anything on them. The Unicode Consortium is very deliberate. Those planes will probably be empty for a long time. And while there are empty planes, they won't be talks about adding new ones. That's my impression. I keep up a bit, but I'm unaffiliated.
- colejohnson66 4y ago> I don't know who is using UTF-16 or UTF-32. Java, JavaScript, Win32's "wide" API, C#, and many more. As for actual file storage, UTF-8 is indeed the most common, but UTF-16 still lingers on.