From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Display of decomposed characters
Date: Wed, 23 Dec 2020 17:44:21 +0200 [thread overview]
Message-ID: <83v9csplwq.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkRrKWd+5RVyTj5o6jZXJaZ5=YjS1nLeygJ=CQsPKQOvGw@mail.gmail.com> (message from Philipp Stephani on Wed, 23 Dec 2020 11:05:13 +0100)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Wed, 23 Dec 2020 11:05:13 +0100
>
> Before filing a bug, I wanted to ask whether the following Emacs
> behavior is intentional: Even with Cairo and Harfbuzz, Emacs displays
> decomposed Unicode characters (e.g. "a" followed by U+0308 COMBINING
> DIAERESIS) as separate glyphs. While that's not technically wrong, I
> think it would be better to display them as a single glyph, in other
> words, not distinguish between canonically equivalent Unicode strings.
They are (or should be) displayed as a composed glyph if you are using
a font that supports both a and COMBINING DIAERESIS. Emacs cannot
compose characters that aren't supported by the same font (because
composition processing stops at face boundaries, and each font defines
internally a separate face).
next prev parent reply other threads:[~2020-12-23 15:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 10:05 Display of decomposed characters Philipp Stephani
2020-12-23 13:00 ` Janusz S. Bień
2020-12-23 15:44 ` Eli Zaretskii [this message]
2020-12-25 17:14 ` Philipp Stephani
2020-12-25 19:01 ` Eli Zaretskii
2021-01-24 18:58 ` Philipp Stephani
2021-01-24 19:48 ` Eli Zaretskii
2021-01-24 19:57 ` Eli Zaretskii
2021-02-28 18:10 ` Philipp
2021-02-28 18:42 ` Eli Zaretskii
2021-03-18 14:16 ` Philipp
2021-03-18 14:37 ` Philipp
2021-03-18 15:01 ` Eli Zaretskii
2021-03-19 16:37 ` Philipp
2021-03-19 16:44 ` Eli Zaretskii
2021-03-21 11:43 ` Philipp
2021-03-21 12:10 ` Eli Zaretskii
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=83v9csplwq.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.
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).