all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: A question about emojis - like \N{HEAVY BLACK HEART}
Date: Sat, 04 Feb 2023 08:50:52 +0200	[thread overview]
Message-ID: <83a61tvs8j.fsf@gnu.org> (raw)
In-Reply-To: <CADs++6j81JWJa-8UwiDZ5O_L9i0xecXjFmoK6yrmw2LtdOkwpA@mail.gmail.com> (message from Eduardo Ochs on Fri, 3 Feb 2023 23:15:50 -0300)

> From: Eduardo Ochs <eduardoochs@gmail.com>
> Date: Fri, 3 Feb 2023 23:15:50 -0300
> 
>   Heavy black heart:        (E2)(9D)(A4)
>   White frowning face:      (E2)(98)(B9)
> 
> This _may be_ the reason why "\N{HEAVY BLACK HEART}" and
> "\N{WHITE FROWNING FACE}" are generating uglier versions of
> the emojis.

What is? what do you see in the last 2 sequences which tells you that
they should display differently?

> What's the recommended way to fix this?

Append u+FE0F to each one of those.

These characters are not by default considered Emoji, because that's
what Unicode says about them.  If you evaluate, for example,

   M-: (aref char-script-table ?❤) RET

you will see that it yields 'symbol', not 'emoji'.  To ask Emacs to
display the Emoji appearance of these two characters, you must follow
them with u+FE0F.  The other characters yield 'emoji' from the above
expression, so they are displayed as Emoji by default.

The reason for this behavior is that many symbol characters have dual
purpose, both as "normal" symbol and as Emoji, and we don't want them
to display as Emoji by default, which will surprise and perhaps annoy
when this happens in plain text.  Emacs behaves here as Unicode
mandates, by displaying each symbol according to its default
appearance, and by supporting the alternate appearance when the
character sequence requests that.



  reply	other threads:[~2023-02-04  6:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-04  2:15 A question about emojis - like \N{HEAVY BLACK HEART} Eduardo Ochs
2023-02-04  6:50 ` Eli Zaretskii [this message]
2023-02-04  9:00   ` Eduardo Ochs

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=83a61tvs8j.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.