https://www.cnet.com/news/how-eight-pixels-cost-microsoft-mi...
https://devblogs.microsoft.com/oldnewthing/20030822-00/?p=42...
Instead, there are https://en.wikipedia.org/wiki/Regional_Indicator_Symbol — an symbol-alphabet where any pair of successive symbols from the alphabet are meant to be considered a ligature (so, a space of 36^2 = 1296 possible ligatures), where a subset of these ligatures are considered valid representations of a locale from the Unicode's https://en.wikipedia.org/wiki/Common_Locale_Data_Repository.
Unicode doesn't say that you should render these CLDR-valid locale meta-codepoints as flags, though. It just says they're locales. In other words, it's up to a given font to decide whether to draw these as flags, and which of them to draw as flags.
With this move, they've abdicated the political determination over to, mostly, the OS manufacturers (since right now most OSes just have one OS emoji font that gets used for the graphical-pictograph-rendering process, rather than allowing user-installed emoji font-families.)
Personally, I like this choice. No matter what any government says, Taiwan is its own locale—it has its own time zone, clock and currency display formats, etc. Locales are locales no matter who declares ownership over them. Having "locale icons" rather than geopolitical-region flags is probably the most stable arrangement we can have, even if it means that some OSes will just render a particular locale-icon as nothing.
The unicode standard doesn't care, as explained above, since it just defines an alphabet and takes no position in which country/locale codes are to be rendered with a flag.
Agreed. The only other way to draw locales would be to country outlines: which would most certainly open a Pandora's Box of socio political issues.
What Apple has effectively done by invalidating the locale, is to remove the Taiwanese language.
As an aside though: from a personal point of view there's quite a few emoji that I'd like to see hidden, such as the poop and middle finger. There's no need for such things, & yet this locale is removed? Weird politics.
Even if a dictionary didn't define a particular word, people would still use that word. You just wouldn't be able to find out what that word means from your dictionary. The word wouldn't be harmed; only the dictionary would be made less useful.
Likewise, even without an assigned codepoint for an emoji, people would still create encodings of it—in chat programs and the like. They'd just be proprietary encodings that wouldn't be able to be copied-and-pasted to other software, and would likely suffer bit-rot. (Can any program that exists today—and that runs on a modern computer—correctly parse out the emoji-like symbols from the binary transcript files of a 90s IM program like AIM or ICQ?) The emoji symbols—at least at the time—wouldn't be harmed by this (people would still use them just as often); only Unicode's goal of "one universal text encoding" would be harmed.
EDIT: seems HN removes emoji. I understand why, but it makes discussions like this one somewhat annoying.
EDIT: I've removed a somewhat vulgar reference to what those alternate meanings are, as it seems to have upset some people. I was trying to make a real point about how users will fill in the gaps when demand exists, even if Unicode omits them.