From sosipiuk at gmail.com  Fri Jun  6 18:21:51 2025
From: sosipiuk at gmail.com (=?UTF-8?Q?S=C5=82awomir_Osipiuk?=)
Date: Fri, 6 Jun 2025 19:21:51 -0400
Subject: What is the origin of the OCR characters U+244[3,4,5]?
Message-ID: <CAM+ijLgGG1Kefguou9RN6-drAqZc=BCkx46dNQD6jQuUUQWS3A@mail.gmail.com>

The Optical Character Recognition Block includes these characters:
U+2440 ? OCR HOOK
U+2441 ? OCR CHAIR
U+2442 ? OCR FORK
U+2443 ? OCR INVERTED FORK
U+2444 ? OCR BELT BUCKLE
U+2445 ? OCR BOW TIE

Wikipedia claims (wrongly, I believe) that these all originate in the
OCR-A font specified by ISO 1073. However, ISO 1073-1:1976 and ISO
2033:1983 only contain the first three of these, as does ANSI
X3.17-1981 and the much older ECMA-19.

The latter three characters ? inverted fork, belt buckle, and bow tie
? do not appear in any of those standards and don?t seem to be an
official part of OCR-A according to any reliable document I can find.

Where do they come from?

Cheers,
S?awomir Osipiuk


From richard.wordingham at ntlworld.com  Sat Jun  7 09:43:04 2025
From: richard.wordingham at ntlworld.com (Richard Wordingham)
Date: Sat, 7 Jun 2025 15:43:04 +0100
Subject: IPA-ish Tone Diacritics
Message-ID: <20250607154304.7beb12c8@JRWUBU2>

I've been trying to decipher the tone diacritics used in from jounralk
page 157 onwards (page 10 onwards of
https://kyoto-seas.org/pdf/7/2/070201.pdf).  After massively increasing
the magnification of the PDF, I see that three of them (numbers 6
'high-rise', 7 'low-rise' and 8 'high fall') are simply side-by-side
combinations of U+0300 COMBINING GRAVE ACCENT 'low', U+0301 COMBINING
ACUTE ACCENT, U+0302 COMBINING CIRCUMFLEX ACCENT 'fall' and U+030C
COMBINING CARON 'rise'.  Does this mean that they *are* encoded, but
one 'simply' has to induce the renderer to choose to render them
side-by-side rather than stacking them vertically?

I'm struggling with number 9 'low-fall', which sometimes resembles
U+1AB0 COMBINING DOUBLED CIRCUMFLEX ACCENT, but may just be a
pixellation effect for for side-by-side <U+0302, U+0300>.

Number 4 'high-dip' could be U+0303 COMBINING TILDE.

The other marks were easy to identify.

Richard.

From junicode at jcbradfield.org  Sat Jun  7 10:53:14 2025
From: junicode at jcbradfield.org (Julian Bradfield)
Date: Sat,  7 Jun 2025 16:53:14 +0100 (BST)
Subject: IPA-ish Tone Diacritics
References: <20250607154304.7beb12c8@JRWUBU2>
Message-ID: <slrn1048o3a.1shjk.jcb@high.jcbradfield.org>

On 2025-06-07, Richard Wordingham via Unicode <unicode at corp.unicode.org> wrote:
> I've been trying to decipher the tone diacritics used in from jounralk
> page 157 onwards (page 10 onwards of
> https://kyoto-seas.org/pdf/7/2/070201.pdf).  After massively increasing
> the magnification of the PDF, I see that three of them (numbers 6
> 'high-rise', 7 'low-rise' and 8 'high fall') are simply side-by-side
> combinations of U+0300 COMBINING GRAVE ACCENT 'low', U+0301 COMBINING
> ACUTE ACCENT, U+0302 COMBINING CIRCUMFLEX ACCENT 'fall' and U+030C
> COMBINING CARON 'rise'.  Does this mean that they *are* encoded, but
> one 'simply' has to induce the renderer to choose to render them
> side-by-side rather than stacking them vertically?

TUS says (?3.6) says that by default combining marks above the base
stack vertically, but they may be side-by-side for a number of
reasons. So I guess "yes".

> I'm struggling with number 9 'low-fall', which sometimes resembles
> U+1AB0 COMBINING DOUBLED CIRCUMFLEX ACCENT, but may just be a
> pixellation effect for for side-by-side <U+0302, U+0300>.

I think it's obvious that it's circumflex and grave - in 6-9 the
notation is prefixing an acute to indicate a high register, and
suffixing a grave to indicate low, apart from:

> Number 4 'high-dip' could be U+0303 COMBINING TILDE.

Typographically, it clearly is a tilde. Probably on the grounds that
acute acute-hacek is too fiddly to typeset



From moyogo at gmail.com  Sat Jun  7 11:05:30 2025
From: moyogo at gmail.com (Denis Jacquerye)
Date: Sat, 7 Jun 2025 18:05:30 +0200
Subject: IPA-ish Tone Diacritics
In-Reply-To: <slrn1048o3a.1shjk.jcb@high.jcbradfield.org>
References: <20250607154304.7beb12c8@JRWUBU2>
 <slrn1048o3a.1shjk.jcb@high.jcbradfield.org>
Message-ID: <CAJKta0x69yV+y7TxYDQA7hAWG2TWKyVPEbV_+D1zhSV+skGb4A@mail.gmail.com>

Hi,

Number 6 was proposed in
https://www.unicode.org/L2/L2024/24232-compound-tone-diacritics.pdf as
U+1AEC COMBINING CARON ACUTE and has been provisionally assigned (
https://www.unicode.org/L2/L2024/24221.htm#181-C34).
The other numbers 7, 8, 9 seem like candidates for a proposal.

While the sequences of already encoded combining marks can look identical,
they do not always do so and may in fact be in a confusing order,
semantically they are different as well.

Kind regards

On Sat, 7 Jun 2025 at 17:55, Julian Bradfield via Unicode <
unicode at corp.unicode.org> wrote:

> On 2025-06-07, Richard Wordingham via Unicode <unicode at corp.unicode.org>
> wrote:
> > I've been trying to decipher the tone diacritics used in from jounralk
> > page 157 onwards (page 10 onwards of
> > https://kyoto-seas.org/pdf/7/2/070201.pdf).  After massively increasing
> > the magnification of the PDF, I see that three of them (numbers 6
> > 'high-rise', 7 'low-rise' and 8 'high fall') are simply side-by-side
> > combinations of U+0300 COMBINING GRAVE ACCENT 'low', U+0301 COMBINING
> > ACUTE ACCENT, U+0302 COMBINING CIRCUMFLEX ACCENT 'fall' and U+030C
> > COMBINING CARON 'rise'.  Does this mean that they *are* encoded, but
> > one 'simply' has to induce the renderer to choose to render them
> > side-by-side rather than stacking them vertically?
>
> TUS says (?3.6) says that by default combining marks above the base
> stack vertically, but they may be side-by-side for a number of
> reasons. So I guess "yes".
>
> > I'm struggling with number 9 'low-fall', which sometimes resembles
> > U+1AB0 COMBINING DOUBLED CIRCUMFLEX ACCENT, but may just be a
> > pixellation effect for for side-by-side <U+0302, U+0300>.
>
> I think it's obvious that it's circumflex and grave - in 6-9 the
> notation is prefixing an acute to indicate a high register, and
> suffixing a grave to indicate low, apart from:
>
> > Number 4 'high-dip' could be U+0303 COMBINING TILDE.
>
> Typographically, it clearly is a tilde. Probably on the grounds that
> acute acute-hacek is too fiddly to typeset
>
>
>

-- 
Denis Moyogo Jacquerye
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://corp.unicode.org/pipermail/unicode/attachments/20250607/eeb73951/attachment.htm>

From t.b.y.taoboyu at foxmail.com  Fri Jun 13 02:20:44 2025
From: t.b.y.taoboyu at foxmail.com (=?utf-8?B?6Zm26ZOC546J?=)
Date: Fri, 13 Jun 2025 15:20:44 +0800
Subject: Assistance with REDO SYMBOL
Message-ID: <tencent_D1A33D8638A078C2024C36B6120E9E9A9209@qq.com>

Unicode mail list:
I am seeking the REDO SYMBOL (assumed corresponding with UNDO SYMBOL) in the Miscellaneous Technical block but have not found it. The character seems having not been encode. I will write a proposal if so.


???
t.b.y.taoboyu at foxmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://corp.unicode.org/pipermail/unicode/attachments/20250613/c9b67b62/attachment.htm>

From jukkakk at gmail.com  Sat Jun 14 13:16:31 2025
From: jukkakk at gmail.com (Jukka K. Korpela)
Date: Sat, 14 Jun 2025 21:16:31 +0300
Subject: Assistance with REDO SYMBOL
In-Reply-To: <tencent_D1A33D8638A078C2024C36B6120E9E9A9209@qq.com>
References: <tencent_D1A33D8638A078C2024C36B6120E9E9A9209@qq.com>
Message-ID: <CAGHxYa4E3jb5=LW3q9WHp0CNTDFXhtFheaKHHMNAKg_1Nxkr1Q@mail.gmail.com>

I had never noticed U+238C UNDO SYMBOL ? before, still less seen it in
text, To me, the common icon for undo in user interfaces is more like an
anticlockwise arrow (like U+21BA ANTICLOCKWISE OPEN CIRCLE ARROW ?), with a
clockwise arrow as its counterpart for redo. I would first ask why UNDO
SYMBOL was included, and then whether similar arguments apply to a redo
symbol. Specifically, where do they appear in texts? Perhaps in manuals
where they refer to user interface icons, but this is hardly sufficient for
characterhood.

If UNDO SYMBOL was included due to its appearance in some user interfaces
(and manuals related to them) decades ago. Grok says it cannot find any
examples of its use in texts. It would probably be difficult to find any
use of a similar symbol for redo. Mere symmetry (?when you have undo, you
should also have redo?) would hardly suffice

Yucca, https://jkorpela.fi


pe 13.6.2025 klo 20.14 ??? via Unicode (unicode at corp.unicode.org) kirjoitti:

> Unicode mail list:
> I am seeking the REDO SYMBOL (assumed corresponding with UNDO SYMBOL) in
> the Miscellaneous Technical block but have not found it. The character
> seems having not been encode. I will write a proposal if so.
> ???
> t.b.y.taoboyu at foxmail.com
>
> <https://wx.mail.qq.com/home/index?t=readmail_businesscard_midpage&nocheck=true&name=%E9%99%B6%E9%93%82%E7%8E%89&icon=https%3A%2F%2Fp.qlogo.cn%2Fqqmail_head%2FPNxwfzqY7uibvJIcrVNuj5byQLOFhnkNFnrP1QM4xJPWHxmGEs5xInib5Rz6oUmoJf%2F%3Frand%3D1655732634%2F&mail=t.b.y.taoboyu%40foxmail.com&code=GUxtDZQgov6AXQoUeXnNvdYbm0KwwV-sfEiYaB6vP8HuzHdxq5HPf2Okt0z5e8-zPVEFwNzCkUz5s-All7YqM4H2XgQNZGXh_CaLGTIoGGY>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://corp.unicode.org/pipermail/unicode/attachments/20250614/2f3f6d20/attachment.htm>

From markus.icu at gmail.com  Sat Jun 14 13:47:30 2025
From: markus.icu at gmail.com (Markus Scherer)
Date: Sat, 14 Jun 2025 11:47:30 -0700
Subject: Assistance with REDO SYMBOL
In-Reply-To: <CAGHxYa4E3jb5=LW3q9WHp0CNTDFXhtFheaKHHMNAKg_1Nxkr1Q@mail.gmail.com>
References: <tencent_D1A33D8638A078C2024C36B6120E9E9A9209@qq.com>
 <CAGHxYa4E3jb5=LW3q9WHp0CNTDFXhtFheaKHHMNAKg_1Nxkr1Q@mail.gmail.com>
Message-ID: <CAN49p6qLirpm2TDbVP-cA36hMBXp9ppD6sSSaK2kH2=sJZFDtw@mail.gmail.com>

On Sat, Jun 14, 2025 at 11:19?AM Jukka K. Korpela via Unicode <
unicode at corp.unicode.org> wrote:

> I would first ask why UNDO SYMBOL was included
>

It was encoded in 1998 in ISO 10646 Amendment 22 Keyboard Symbols, and then
published in 1999 in Unicode 3.0.
The first documents about "keyboard symbols" appear in 1997:
https://www.unicode.org/L2/L1997/Register-1997.html
https://www.unicode.org/L2/L1998/Register-1998.html
https://www.unicode.org/wg2/docs/n2100.htm

Many of these documents were on paper and don't have online versions.

In general, user interfaces do just fine with symbols as images, not
needing encoded characters, and not wanting to rely on variable font
support and glyph design.

markus

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://corp.unicode.org/pipermail/unicode/attachments/20250614/13153d93/attachment-0001.htm>

From karl-pentzlin at acssoft.de  Sun Jun 15 15:52:59 2025
From: karl-pentzlin at acssoft.de (Karl Pentzlin)
Date: Sun, 15 Jun 2025 22:52:59 +0200
Subject: U+238C UNDO SYMBOL (was: Re: Assistance with REDO SYMBOL)
In-Reply-To: <CAN49p6qLirpm2TDbVP-cA36hMBXp9ppD6sSSaK2kH2=sJZFDtw@mail.gmail.com>
References: <tencent_D1A33D8638A078C2024C36B6120E9E9A9209@qq.com>    
 <CAGHxYa4E3jb5=LW3q9WHp0CNTDFXhtFheaKHHMNAKg_1Nxkr1Q@mail.gmail.com>
 <CAN49p6qLirpm2TDbVP-cA36hMBXp9ppD6sSSaK2kH2=sJZFDtw@mail.gmail.com>
Message-ID: <1463682784.20250615225259@acssoft.de>

The symbol U+238C UNDO SYMBOL is the symbol #30 from the standard ISO/IEC 9995-7 in its editions at least since the 1990s.
That standard is named "Information technology ? Keyboard layouts for text and office systems ?
Part 7: Symbols used to represent functions".
In that standard, the symbol is named "Undo" and described "To return to the state prior to that of the last executed action".
There, the symbol appears in this form:
?
?
It is also contained in ISO 7000 "Graphical symbols for use on equipment" as symbol #2106, with name "Undo", description "To identify the control that deletes the most recently taken action and returns the document to its immediately preceding status." and release date 2004-01-15:
?
The glyph in the current Unicode charts (Version 16.0):
?
is erroneous, as the right circle is not filled and therefore not distinctive from the left circle, as it obviously was intended in the original symbol design.
(I will file a glyph correction request within the next days.)
?
Best wishes
Karl Pentzlin
?
?
--
Am Samstag, 14. Juni 2025 um 20:47 schrieb Markus Scherer via Unicode:

> On Sat, Jun 14, 2025 at 11:19?AM Jukka K. Korpela via Unicode <
> unicode at corp.unicode.org> wrote:

>> I would first ask why UNDO SYMBOL was included

> It was encoded in 1998 in ISO 10646 Amendment 22 Keyboard Symbols, and then
> published in 1999 in Unicode 3.0.
> The first documents about "keyboard symbols" appear in 1997:
> https://www.unicode.org/L2/L1997/Register-1997.html
> https://www.unicode.org/L2/L1998/Register-1998.html
> https://www.unicode.org/wg2/docs/n2100.htm

> Many of these documents were on paper and don't have online versions.

> In general, user interfaces do just fine with symbols as images, not
> needing encoded characters, and not wanting to rely on variable font
> support and glyph design.

> markus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://corp.unicode.org/pipermail/unicode/attachments/20250615/42753faf/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 414325387.png
Type: image/png
Size: 680 bytes
Desc: not available
URL: <https://corp.unicode.org/pipermail/unicode/attachments/20250615/42753faf/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2040513729.png
Type: image/png
Size: 6438 bytes
Desc: not available
URL: <https://corp.unicode.org/pipermail/unicode/attachments/20250615/42753faf/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 838227940.png
Type: image/png
Size: 1371 bytes
Desc: not available
URL: <https://corp.unicode.org/pipermail/unicode/attachments/20250615/42753faf/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 680 bytes
Desc: not available
URL: <https://corp.unicode.org/pipermail/unicode/attachments/20250615/42753faf/attachment-0003.png>

From pgcon6 at msn.com  Mon Jun 16 10:53:25 2025
From: pgcon6 at msn.com (Peter Constable)
Date: Mon, 16 Jun 2025 15:53:25 +0000
Subject: Assistance with REDO SYMBOL
In-Reply-To: <CAN49p6qLirpm2TDbVP-cA36hMBXp9ppD6sSSaK2kH2=sJZFDtw@mail.gmail.com>
References: <tencent_D1A33D8638A078C2024C36B6120E9E9A9209@qq.com>
 <CAGHxYa4E3jb5=LW3q9WHp0CNTDFXhtFheaKHHMNAKg_1Nxkr1Q@mail.gmail.com>
 <CAN49p6qLirpm2TDbVP-cA36hMBXp9ppD6sSSaK2kH2=sJZFDtw@mail.gmail.com>
Message-ID: <SJ2PR10MB7671B87CE96374A12A531D4F8670A@SJ2PR10MB7671.namprd10.prod.outlook.com>

FYI, ?variable font support? has a different meaning that will be more familiar to font developers than the meaning you had in mind.


Get Outlook for Mac <https://aka.ms/GetOutlookForMac>

From: Unicode <unicode-bounces at corp.unicode.org> on behalf of Markus Scherer via Unicode <unicode at corp.unicode.org>
Date: Saturday, June 14, 2025 at 11:52?AM
To: Jukka K. Korpela <jukkakk at gmail.com>
Cc: ??? <t.b.y.taoboyu at foxmail.com>, unicode <unicode at corp.unicode.org>
Subject: Re: Assistance with REDO SYMBOL
On Sat, Jun 14, 2025 at 11:19?AM Jukka K. Korpela via Unicode <unicode at corp.unicode.org<mailto:unicode at corp.unicode.org>> wrote:
I would first ask why UNDO SYMBOL was included

It was encoded in 1998 in ISO 10646 Amendment 22 Keyboard Symbols, and then published in 1999 in Unicode 3.0.
The first documents about "keyboard symbols" appear in 1997:
https://www.unicode.org/L2/L1997/Register-1997.html
https://www.unicode.org/L2/L1998/Register-1998.html
https://www.unicode.org/wg2/docs/n2100.htm

Many of these documents were on paper and don't have online versions.

In general, user interfaces do just fine with symbols as images, not needing encoded characters, and not wanting to rely on variable font support and glyph design.

markus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://corp.unicode.org/pipermail/unicode/attachments/20250616/d2b7033c/attachment.htm>

From ndoiron at mapmeld.com  Wed Jun 25 09:50:42 2025
From: ndoiron at mapmeld.com (Nick Doiron)
Date: Wed, 25 Jun 2025 09:50:42 -0500
Subject: Seeking feedback: flag emoji for autonomous ISO 3166-2 regions
Message-ID: <CALG_m-XRjP4AjV6F8NND0eWAz7hPGOA=76uw=NZXdcDMGUQeLg@mail.gmail.com>

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/935d9f01/attachment-0001.htm>

From irgendeinbenutzername at gmail.com  Wed Jun 25 12:58:51 2025
From: irgendeinbenutzername at gmail.com (Charlotte Eiffel Lilith Buff)
Date: Wed, 25 Jun 2025 19:58:51 +0200
Subject: Seeking feedback: flag emoji for autonomous ISO 3166-2 regions
In-Reply-To: <CALG_m-XRjP4AjV6F8NND0eWAz7hPGOA=76uw=NZXdcDMGUQeLg@mail.gmail.com>
References: <CALG_m-XRjP4AjV6F8NND0eWAz7hPGOA=76uw=NZXdcDMGUQeLg@mail.gmail.com>
Message-ID: <CAKLR3Aop+PY7ZFvUF62u8W51eWaP-9E=QFwuuW3QRL0Rdg+StA@mail.gmail.com>

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>

From unicode.org at sl.neatnit.net  Wed Jun 25 14:42:54 2025
From: unicode.org at sl.neatnit.net (Nitai Sasson)
Date: Wed, 25 Jun 2025 19:42:54 +0000
Subject: Seeking feedback: flag emoji for autonomous ISO 3166-2 regions
In-Reply-To: <CAKLR3Aop+PY7ZFvUF62u8W51eWaP-9E=QFwuuW3QRL0Rdg+StA@mail.gmail.com>
References: <CALG_m-XRjP4AjV6F8NND0eWAz7hPGOA=76uw=NZXdcDMGUQeLg@mail.gmail.com>
 <CAKLR3Aop+PY7ZFvUF62u8W51eWaP-9E=QFwuuW3QRL0Rdg+StA@mail.gmail.com>
Message-ID: <175088058160.6.14686078275087379473.779779626@sl.neatnit.net>

Please someone correct me if I'm wrong, but best I can tell, these are already allowed as far as Unicode is concerned. From the blog post linked by Charlotte:

> But, did you know that there are over 5,000 geographically-recognized regions that are also ?valid?? These are known as [subdivision regions](https://www.unicode.org/reports/tr35/#unicode_subdivision_id) and are based on ISO [3166-2](https://en.wikipedia.org/wiki/ISO_3166-2). (These include [states in the US](https://www.iso.org/obp/ui/#iso:code:3166:US), [regions in Italy](https://www.iso.org/obp/ui/#iso:code:3166:IT), [provinces in Argentina](https://www.iso.org/obp/ui/#iso:code:3166:AR), and so on.)
> First, what does ?valid? mean to the Unicode Standard? Well, think of it this way. Today, anyone could make a font of 5,000 emoji flags using these sequences. They are valid sequences. They are legit sequences. They won?t break. Any platform, application, or font can implement them. The significant difference here is that valid doesn?t mean they are recommended for implementation.

So rejoice, and feel free to use these codes. But if you want them to show up universally, you'll have to take it up with operating systems and other emoji vendors, not with Unicode. And keep in mind that, for example, MS Windows does not show any country flags (not even USA), in large part because they don't want the headache of deciding which ones to include. It's a can of worms, but feel free to try your luck. It's just not up to Unicode.
On Wednesday, 25 June 2025 at 21:01, Charlotte Eiffel Lilith Buff via Unicode <unicode at corp.unicode.org> wrote:

> 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/9d95a358/attachment.htm>

From doug at ewellic.org  Fri Jun 27 15:12:54 2025
From: doug at ewellic.org (Doug Ewell)
Date: Fri, 27 Jun 2025 20:12:54 +0000
Subject: Seeking feedback: flag emoji for autonomous ISO 3166-2 regions
In-Reply-To: <CALG_m-XRjP4AjV6F8NND0eWAz7hPGOA=76uw=NZXdcDMGUQeLg@mail.gmail.com>
References: <CALG_m-XRjP4AjV6F8NND0eWAz7hPGOA=76uw=NZXdcDMGUQeLg@mail.gmail.com>
Message-ID: <BN7PR03MB3665C8868E2EB42A93D1FE1CCA45A@BN7PR03MB3665.namprd03.prod.outlook.com>

Nick Doiron wrote:

> 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.

It is already possible to create a flag emoji sequence for entities with an existing ISO 3166-2 code. See UTS #51, annexes B and C:

https://www.unicode.org/reports/tr51/#Flags
https://www.unicode.org/reports/tr51/#valid-emoji-tag-sequences

--
Doug Ewell, CC, ALB | Lakewood, CO, US | ewellic.org