Unicode Emoji 5.0 characters now final

Philippe Verdy verdy_p at wanadoo.fr
Mon Mar 27 15:39:10 CDT 2017

Note also that ISO3166-2 is far from being stable, and this could
contradict Unicode encoding stability: it would then be required to ensure
this stability by only allowing sequences that are effectively registered
in http://www.unicode.org/Public/emoji/5.0/emoji-sequences.txt
(independantly of the registration ins ISO3166-2), and nothing is said if
ever ISO3166-2 obsoletes some codes and then some years later decide to
reassign these codes to new entities: it should not be possible to do the
same thing in Emoji sequences, and specific assignments will need to be
made in the Unicode database.

Note also that most rencetly created administrative divisions do not really
adopt any flag, but if flags are used they may be reusing flags from older
historic entities... or they could adopt only a logo (with legal
protection, not really suitable from encoding in the UCS as it won't be
possible to define any "representative glyph" without asking for permission
to the relevant authorities for displaying some design, possibly simplified)

We still lack an encoding standard for vexillologists. And for now only
"Flags of the World" proposes some encoding (not based strictly and only on
ISO3166). I think that the UTC should try contacting authors of Flags of
the World and seek for advice there: we are speaking here about regional
flags (we can exclude some graphical variants such as civil vs. navy flags
vs honorific flags)

2017-03-27 22:30 GMT+02:00 Philippe Verdy <verdy_p at wanadoo.fr>:

> 2017-03-27 21:17 GMT+02:00 Doug Ewell <doug at ewellic.org>:
>> announcements at Unicode dot org wrote:
>> > — and new regional flags for England, Scotland, and Wales.
>> It's not clear from this text, nor from the table in Section C.1.1 of
>> the draft, what the status is of flag emoji tag sequences other than the
>> three above.
> Right, we've got them encoded as [GBENG], [GBSCT] and [GBWLS], but the
> codes used do not specify clearly about which region code standard they are
> refering to. We just see that it's an ISO3166-1 country/territory code
> followed directly (without separator) by sequences of letter/digits, all of
> them converted to RIS and surrounded by a the same initial emeoji code and
> the DEL from RIS.
> The problem is how to choose the codes for the letter/digits in the second
> part, if they ever come from ISO3166-2 after dropping the hypen separator
> (this is the case here, see https://en.wikipedia.org/wiki/ISO_3166-2:GB)
> or somewhere else.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/unicode/attachments/20170327/76c1ec3c/attachment.html>

More information about the Unicode mailing list