ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Henning Hraban Ramm <texml@fiee.net>
Subject: Re:  Unicode 13 – save the \dodo!
Date: Wed, 5 Feb 2020 10:29:47 +0100	[thread overview]
Message-ID: <5ae51892-4ea4-5a90-5d39-eef8f1bb7ec1@xs4all.nl> (raw)
In-Reply-To: <38B3A355-748A-4AB8-9D56-256EACD46621@fiee.net>

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

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

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

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

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

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2020-02-05  9:29 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 [this message]
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

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=5ae51892-4ea4-5a90-5d39-eef8f1bb7ec1@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=texml@fiee.net \
    /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).