Seeking feedback: flag emoji for autonomous ISO 3166-2 regions

[Charlotte Eiffel Lilith Buff]

Worrying about the exact process by which political entities could propose
their flags to be added as emoji might be putting the cart before the
horse. The Unicode Technical Committee ceased accepting proposals for flag
emoji altogether
<https://blog.unicode.org/2022/03/the-past-and-future-of-flag-emoji.html>
three years ago, no matter what they represent or which mechanism would be
used to encode them. The unavoidable first step in your endeavour is to
convince the UTC that any of this is worth their time and effort after all,
and I have a hunch that’s simply not going to happen. The restrictions on
emoji proposals have only ever gotten tighter over the years.

Am Mi., 25. Juni 2025 um 16:53 Uhr schrieb Nick Doiron via Unicode <
unicode at corp.unicode.org>:

> I'm sure everyone on the list has heard about people wanting more flag
> emoji.
>
> My suggestion / future PRI feedback is to allow semi-autonomous regions,
> with an existing ISO 3166-2 code, to make an official request for a flag
> emoji. That sounds technical, but giving regions a level of
> special/constitutional autonomy has become more common as a political
> resolution in the past ~25 years  (Aceh, Bougainville, Iraqi Kurdistan,
> Rodrigues in Mauritius)
> Key points:
>
>    - follows same ISO standard as England/Scotland/Wales emoji
>    - covers flags that are requested the most (Kurdistan, Catalonia)
>    while avoiding a jump to all states and provinces
>    - common-sense restrictions, such as flag is unchanged for 5 years
>    - governments would make an official statement to avoid issues with
>    flag design / verification
>    - Unicode, OSes, and typographers continue to choose which emoji they
>    include
>
> To avoid cluttering the email list, I welcome your comments on this Google
> Doc, or a direct email to me at ndoiron at mapmeld.com
> https://docs.google.com/document/d/1tIMEjGPFOIbctvVZckZKLOS6H-fD4QN0wPD15H3QqU8/edit?usp=sharing
>
> -- Nick Doiron
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://corp.unicode.org/pipermail/unicode/attachments/20250625/cb8a4d07/attachment.htm>