If I learned anything as I wrote about emoji, it is that emoji is as dynamic as any “real” language. Here’s a recent development that demonstrates exactly that.
From the latest edition of Jennifer Daniel’s always-entertaining newsletter, “Did Someone Say Emoji?”,* comes the news that Unicode is shutting down the pipeline of new flag emoji. Jennifer is the chair of the Unicode Emoji Subcommittee, so this comes straight from the 🐴’s mouth.
This is not a small change. Flags are the largest homogenous subspecies of emoji, and a special one at that, with the Unicode Consortium careful to ensure that there is always an official flag emoji for each of the countries defined by the ISO 3166 standard. (There are also some non-country flags, but more about them later.) But despite this special status, there is a long list of reasons for the cauterisation of one of emoji’s major limbs.
First, and probably most obvious, is that international boundaries, politics, and identities are constantly in flux. Flags change, countries change; even whether a particular geographic entity is a country or not is sometimes a matter of perspective. Taiwan, of course, is the flag-bearer (sorry) for this particular type of disagreement: in order to prevent offence to one party or another, Taiwanese flag emoji do not appear on some devices.†
In the same vein, flags for “subdivisions” of countries — the UK’s home nations, the USA’s constituent states, and so on — can be equally problematic. Thus, although the Unicode standard technically supports subdivision flags, only a handful are officially blessed to appear as emoji: the flags of Scotland, England and Wales are uncontroversial enough to be supported on most platforms, but for Unicode to sanction a flag for Northern Ireland would be to wade into a political quagmire that has endured for more than a century. For another difficult case, consider Spain’s independence-minded region of Catalonia.
And then there are those flags that represent something other than countries and regions, and they can be just as troublesome. Should historical flags be supported, for example? Or organisational flags such as those of NATO or the UN? What about indigenous peoples, such as Australia’s Indigenous Peoples and New Zealand’s Maori, who have flags different to those of their colonisers? And what about the flags of such slippery things as movements, like the rainbow LGBT flag or the skull-and-crossbones of the pirate flag? Some of these have emoji flags, others do not, and it is not at all clear whether the correct choices have been made.
Beyond all this, Jennifer notes that flag emoji are just not very popular; the vertigo-inducing emojitracker, for instance, shows that not a single flag regularly cracks the top 100 emoji on Twitter. Such is the dearth of interest that, as Keith Broni points out over on Emojipedia, Microsoft Windows has never supported flag emoji. Every flag emoji sent to a Windows machine ends up as either a pair of “regional indicator symbol letters”, such as “🇺🇸” or “🇬🇧” or simply a featureless black flag (🏴).
In future, then, Unicode’s Emoji Subcommittee will not accept any new proposals for flags. There will still be new national flags from time to time, as the ISO 3166 Maintenance Agency adds new entries to its more-or-less-canonical list of countries, but anything else is likely to be rejected out of hand. Fly your 🏴s at half mast: the book is closed on new emoji flags.
Comment posted by Steven S Minniear on
The “Party” comment was very appropriate and clever. Thanks.
Comment posted by Keith Houston on
Hi Steven — thanks!
Comment posted by David Edward Lane on
Greetings from committedly democratic and free Taipei, Taiwan . Indeed there is but one single entity, in the whole of the world, that takes offense to this.
Comment posted by Thy on
Hi Keith, thanks for the blog post! I found it really interesting :) just a note re: language use, the term “aborigines” is considered insensitive & offensive to large communities of the Indigenous Peoples of Australia.
Comment posted by Keith Houston on
Hi Thy — thanks, and thanks for the note! I’ll take care of that.
Comment posted by Danir on
Hi Keith, indeed this can be a thorny but very interesting topic.
My Country too seems does not have the right to have his flag on the emoji palette of fame, even if is the Country who create, just to name a very few, the concept of paperback and—three century before Italy exist as a Country—the style that the world of today call italic.
It’s always a pleasure reading you. Sorry for my horrible english.
Comment posted by Keith Houston on
Hi Danir — thanks for the comment! The Venetian flag is a good one, although perhaps a little difficult to reduce to emoji scale…
Comment posted by Rowan Tommins on
Your mention of “Microsoft” not supporting flag emoji confuses me. Do you just mean that the fonts which ship with Windows don’t contain them?
My confusion wasn’t helped by the fact that your sentence mentioning ‘… a pair of “regional indicator symbol letters”, such as “” or “” …’ shows the actual flags for me, in Firefox on Windows; although Chrome does indeed fail to show them. Perhaps it would make sense to put a Zero-Width Non-Joiner between the two code-points, so that everyone will see the broken version, regardless of platform? Thus: “”
Comment posted by Keith Houston on
Hi Rowan — thanks for the comment! My (perhaps imperfect) understanding of the situation is that MS Windows’ native text-rendering widgets will not show flags. Whether that’s because Windows’ default emoji fonts lack them, or because Windows’ text rendering engine ignores regional indicator letters, I don’t know. The net result, though, is that most text controls on Windows will not render flags. Where a program provides its own custom text rendering, such as (in my experience) Twitter.com in any browser, or (in your experience), Firefox, that default behaviour is replaced by whatever the program wants to do.
Also, thanks for the ZWNJ suggestion! I’ve added that to the post.