From: Arthur Reutenauer <arthur.reutenauer@normalesup.org>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Unicode 13 – save the \dodo!
Date: Wed, 5 Feb 2020 13:16:03 +0100 [thread overview]
Message-ID: <20200205121603.opnds3ni4mpn3ch5@phare.normalesup.org> (raw)
In-Reply-To: <4da80d6b-4784-3b06-3e9c-5d4f62021a12@xs4all.nl>
On Wed, Feb 05, 2020 at 11:22:26AM +0100, Hans Hagen wrote:
> we are waiting for you to predict the future, when do you think nofemoji
> will pass nofnonemoji (we could draw a curve of how much got added each
> version of unicode) .. visualizing your argument could help
It’s never going to happen. Since after the initial addition of over
1000 emojis from the Japanese telcos in 2010 (which few people outside
Japan took notice of at the time), the rate of new emojis has been more
or less constant at 50-100 a year (out of a total of 500-10,000 new
characters / year). This is never going to come anywhere near close the
100K+ other Unicode characters that already exist. It wouldn’t be
manageable anyway (not that I think it is now: it can only get worse).
If the pressure to add new emojis is maintained, one of the big
players is going to get tired of the slow process and solve the issue in
a technical way (by embedding emojis as images for example, that
wouldn’t be revolutionary) or -- my personal favourite, which over a
decade ago I thought was obvious, but clearly isn’t -- they’re going to
break away from the dependency on the Unicode Consortium and start
maintaining their own repository of images with code points in the
private use area. They’re plenty of space for that there.
Best,
Arthur
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2020-02-05 12:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 8:45 Henning Hraban Ramm
2020-02-05 9:29 ` Hans Hagen
2020-02-05 9:45 ` Henning Hraban Ramm
2020-02-05 10:25 ` Hans Hagen
2020-02-05 9:37 ` Arthur Reutenauer
2020-02-05 9:47 ` Henning Hraban Ramm
2020-02-05 11:57 ` Arthur Reutenauer
2020-02-05 9:49 ` luigi scarso
2020-02-05 10:22 ` Hans Hagen
2020-02-05 12:16 ` Arthur Reutenauer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200205121603.opnds3ni4mpn3ch5@phare.normalesup.org \
--to=arthur.reutenauer@normalesup.org \
--cc=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).