From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: emacs-27 60c84ad: ; * etc/TODO: Fix last change.
Date: Thu, 05 Mar 2020 15:46:34 +0100 [thread overview]
Message-ID: <m2zhcusvud.fsf@gmail.com> (raw)
In-Reply-To: <83o8tbunzh.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 05 Mar 2020 11:53:22 +0200")
[-- Attachment #1: Type: text/plain, Size: 706 bytes --]
>>>>> On Thu, 05 Mar 2020 11:53:22 +0200, Eli Zaretskii <eliz@gnu.org> said:
Eli> The u+2XXX and U+3XXX characters are not Emoji by default, they are
Eli> supposed to be displayed as Emoji only if followed by the Emoji-style
Eli> variation selector. Otherwise, they should be displayed in text
Eli> representation.
Ok, so based on emoji-data.txt, my awk script produces the attached
.el file. It excludes U+2XXX and U+3XXX, plus U+A9 and U+AE and
anything ASCII. Note that there are duplicates in there, since some
codepoints have multiple Emoji-type properties. Of course, we could
just decide a bunch of ranges from Block.txt that we want to treat as
emoji, and hardcode that.
Robert
[-- Attachment #2: emoji-fontset.el --]
[-- Type: application/emacs-lisp, Size: 5506 bytes --]
next prev parent reply other threads:[~2020-03-05 14:46 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200229173124.11831.98476@vcs0.savannah.gnu.org>
[not found] ` <20200229173125.E2D3A21167@vcs0.savannah.gnu.org>
2020-03-02 10:40 ` emacs-27 60c84ad: ; * etc/TODO: Fix last change Robert Pluim
2020-03-02 11:36 ` Eli Zaretskii
2020-03-02 14:08 ` Robert Pluim
2020-03-02 14:24 ` Eli Zaretskii
2020-03-02 14:36 ` Eli Zaretskii
2020-03-02 15:06 ` Robert Pluim
2020-03-02 15:25 ` Eli Zaretskii
2020-03-02 15:42 ` Robert Pluim
2020-03-02 15:58 ` Eli Zaretskii
2020-03-02 16:40 ` Robert Pluim
2020-03-02 15:34 ` Eli Zaretskii
2020-03-02 16:58 ` Stefan Monnier
2020-03-02 20:12 ` Robert Pluim
2020-03-02 20:21 ` Eli Zaretskii
2020-03-02 20:55 ` Robert Pluim
2020-03-03 12:51 ` Robert Pluim
2020-03-03 16:06 ` Eli Zaretskii
2020-03-04 7:23 ` Robert Pluim
2020-03-04 9:25 ` Robert Pluim
2020-03-04 16:04 ` Eli Zaretskii
2020-03-04 16:54 ` Robert Pluim
2020-03-04 17:19 ` Eli Zaretskii
2020-03-05 7:29 ` Robert Pluim
2020-03-05 7:56 ` Eli Zaretskii
2020-03-05 8:13 ` Robert Pluim
2020-03-05 9:38 ` Eli Zaretskii
2020-03-05 9:48 ` Robert Pluim
2020-03-05 9:53 ` Eli Zaretskii
2020-03-05 14:46 ` Robert Pluim [this message]
2020-03-05 14:59 ` Eli Zaretskii
2020-03-05 15:11 ` Robert Pluim
2020-03-05 15:24 ` Eli Zaretskii
2020-03-05 16:08 ` Robert Pluim
2020-03-05 19:04 ` Eli Zaretskii
2020-03-06 16:32 ` Robert Pluim
2020-03-06 17:05 ` Eli Zaretskii
2020-03-06 17:35 ` Robert Pluim
2020-03-09 23:12 ` chad
2020-03-10 7:33 ` Robert Pluim
2020-03-22 5:18 ` YAMAMOTO Mitsuharu
2020-03-04 15:51 ` Eli Zaretskii
2020-03-04 16:58 ` Robert Pluim
2020-03-04 17:24 ` Eli Zaretskii
2020-03-03 17:22 ` Eli Zaretskii
2020-03-04 7:26 ` Robert Pluim
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2zhcusvud.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).