There is definitely a problem.
The origin is complicated. All that anyone really needed were 10 characters
for emoji flags, encoded as compatibility characters. However, certain
people (I'll call Completionists) who think that if you encode one member
of a set (even for compatibility characters!), you need to encode all of
them. So the request expanded from 10 to all countries, then to all
possible countries. And I wouldn't be surprised to have them then push for
state/provincial flags for completeness, and who knows, maybe someday
municipal flags (my old town
http://en.wikipedia.org/wiki/File:Sargans-coat_of_arms.svg).
So, some people came up with a way to handle this, using combinations of
special characters. The only problem is that we didn't have lead and trail
characters separately defined, to allow for an unambiguous mapping.
------------------------------
Mark <https://plus.google.com/114199149796022210033>
*
*
*— Il meglio è l’inimico del bene —*
**
On Tue, May 29, 2012 at 2:38 AM, "Martin J. Dürst"
<duerst_at_it.aoyama.ac.jp>wrote:
>
>
>> ...
>
> On a slightly (although maybe only slightly) related matter, what about if
> Unicode didn't judge how difficult it should be to display national flags.
> Creating a way to display flags from two-tag combinations and then later
> realizing that a sequence of such tags didn't locally parse, and the whole
> thing has to be redone, doesn't seem like a very good alternative to just
> encoding these things (not that I think that just encoding these is a very
> good alternative either, though).
>
> Regards, Martin.
>
>
Received on Wed May 30 2012 - 18:29:28 CDT
This archive was generated by hypermail 2.2.0 : Wed May 30 2012 - 18:29:29 CDT
