From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eric S Fraga <e.fraga@ucl.ac.uk>, ding@gnus.org
Subject: Re: replacing some utf-8 characters on display
Date: Wed, 03 Nov 2021 11:33:16 +0100 [thread overview]
Message-ID: <87o871msur.fsf@gmail.com> (raw)
In-Reply-To: <87zgqs24hx.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 29 Oct 2021 00:01:30 +0200")
>>>>> On Fri, 29 Oct 2021 00:01:30 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:
Lars> Robert Pluim <rpluim@gmail.com> writes:
>> If the math symbol + VS-16 results in an emoji glyph, itʼs not a math
>> symbol, itʼs an emoji :-) But there are emoji for things like
>> 'multiply', 'divide' that you might not want to turn into fruit salad
>> in your email. How likely those are to be used instead of the 'normal'
>> characters I donʼt know.
Lars> So that's... ➗? But it's its own separate code point, so I guess it
Lars> shouldn't be a problem.
Lars> I think it's worth trying (i.e., adding a washing function that adds
Lars> VS-16 after all symbol glyphs) and see whether that leads to anything
Lars> annoying.
If you do that, then you will end up with a bunch of symbol codepoints
followed by VS-16 when those codepoints aren't emoji. And I donʼt
think you can let-bind glyphless-char-display to make them disappear.
Does your recent emoji input work result in anything that could give
us a list of 'emoji where Emoji Presentation = No' codepoints?
Robert
--
next prev parent reply other threads:[~2021-11-03 10:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 15:53 Eric S Fraga
2021-10-27 16:00 ` Lars Ingebrigtsen
2021-10-27 16:04 ` Eric S Fraga
2021-10-27 16:10 ` Lars Ingebrigtsen
2021-10-27 16:21 ` Eric S Fraga
2021-10-27 16:39 ` Robert Pluim
2021-10-28 22:01 ` Lars Ingebrigtsen
2021-11-03 10:33 ` Robert Pluim [this message]
2021-11-04 5:14 ` Lars Ingebrigtsen
2021-11-04 5:38 ` Lars Ingebrigtsen
2021-11-04 5:51 ` Lars Ingebrigtsen
2021-11-04 5:55 ` Lars Ingebrigtsen
2021-11-10 15:12 ` Eric S Fraga
2021-11-10 15:15 ` Eric S Fraga
2021-11-10 15:17 ` Eric S Fraga
2021-11-04 12:26 ` Eric S Fraga
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=87o871msur.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=ding@gnus.org \
--cc=e.fraga@ucl.ac.uk \
--cc=larsi@gnus.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.
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).