From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Composed Sequences (was: Manually parsing char-tables)
Date: Sat, 26 Feb 2022 08:33:35 +0200 [thread overview]
Message-ID: <83r17qp268.fsf@gnu.org> (raw)
In-Reply-To: <20220226002837.699ae2b1@JRWUBU2> (message from Richard Wordingham on Sat, 26 Feb 2022 00:28:37 +0000)
> Date: Sat, 26 Feb 2022 00:28:37 +0000
> From: Richard Wordingham <richard.wordingham@ntlworld.com>
>
> I still haven't found the code where the difference occurs, but I now
> have a better idea of what is going on. It seems that runs with the
> same value of the composition property ('composed sequences') are
> sequences of clusters for the font that match a regular expression
> given in composition-function-table.
(Please don't use "composition property" in this context, because it's
confusing: the 'composition' text property does exist in Emacs (it's
an old and now deprecated way of composing characters), but it is not
relevant to this discussion, which instead focuses on what is known in
Emacs as "automatic composition".)
> Different renderers give different clusters, and thus, by default,
> different cursor motion!
Not "different renderers", but "different fonts".
And yes, the grapheme clusters produced by the text shaping engine
(HarfBuzz etc.) and displayed by the Emacs display code indeed
crucially depend on the font.
> The reason Arabic seemed different is that when lam+hah appears to
> ligate, what is happening (at least with Amiri) is that substitutions
> are made which give the effect of a ligature, while remaining two
> distinct glyphs.
Yes, I see that as well. "C-u C-x =" should tell you whether ligation
happened or not. What you see is normal, I think: Emacs obeys the
decisions of the font designers.
next prev parent reply other threads:[~2022-02-26 6:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 11:09 Manually parsing char-tables Richard Wordingham
2022-02-20 12:50 ` Eli Zaretskii
2022-02-21 1:39 ` Richard Wordingham
2022-02-26 0:28 ` Composed Sequences (was: Manually parsing char-tables) Richard Wordingham
2022-02-26 6:33 ` Eli Zaretskii [this message]
2022-02-26 15:11 ` Composed Sequences Richard Wordingham
2022-02-26 15:35 ` Eli Zaretskii
2022-02-26 19:46 ` Richard Wordingham
2022-02-26 20:02 ` 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=83r17qp268.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).