From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Unicode 13 – save the \dodo!
Date: Wed, 5 Feb 2020 10:45:46 +0100 [thread overview]
Message-ID: <6B419649-D2EB-45A7-9351-6A2B39C53928@fiee.net> (raw)
In-Reply-To: <5ae51892-4ea4-5a90-5d39-eef8f1bb7ec1@xs4all.nl>
> Am 2020-02-05 um 10:29 schrieb Hans Hagen <j.hagen@xs4all.nl>:
>
> On 2/5/2020 9:45 AM, Henning Hraban Ramm wrote:
>> Hi, I’m a bit late: Last week the Unicode consortium released the latest version of their nowadays mostly-emoji standard.
>> Besides several entries for transgender representation, there are also new animals, and most important: “my” ConTeXt mascot, the Dodo! ;D
> a never ending story i guess
We need to compensate for all the animals that become extinct.
>> see https://unicode.org/emoji/charts-13.0/emoji-released.html
>
> indeed, i already added those
👍
>> I still miss e.g.
>> - adaptible colors for everything-else-than-skintone (e.g. vehicles)
>
> and the cars should of course be recognizable as using petrol, diesel, batteries (and some ligature for hybrids, software cheats etc)
Oh yes, I didn’t think of that. You don’t need a ligature for software cheats, though, they’re default.
But if combustion engines get prohibited, does that affect the emojis?
>> - political symbols (red flag, hammer-and-sickle – of course the selection would be a political decision and would cause problems with prohibited, e.g. nazi, symbols, but maybe we can just get simple flags in several colors? adaptible would make sense...)
>
> i think emoji and choices are already political
True. E.g. the selection of national monuments. Why Fuji and not Uluru, Kibo, Matterhorn or Zugspitze? (ah, no, there are several Zugspitzen, just no Zugenden…)
>> - lots of local and/or vegetarian food (Kässpätzle, Leberkäswecken, Schupfnudeln, veg. pizza, tofu…)
> i assume that at some point there should also be a descriptive file explaining what these symbols actually represent
Recipes please.
>> - some sense…
> indeed
>> While I agree that we need some standardization in symbols, I still don’t think it was a good idea to mix them with text glyphs and bloat font technology with colors.
> lots of weird things indeed ... kind of iconic esperanto so maybe som grammar will come too
Good idea.
There are a lot of emojis that I can’t imagine using or that I don’t understand, esp. facial expressions, even if I know western comic and manga representations of feelings. And I often miss emojis for the feelings I’d like to refer to, like some of those available in old forum software: facepalm, banging your head against the wall…
Lassen wir das.
Greetlings, Hraban
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-02-05 9:45 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 [this message]
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
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=6B419649-D2EB-45A7-9351-6A2B39C53928@fiee.net \
--to=texml@fiee.net \
--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).