From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 44784@debbugs.gnu.org, juri@linkov.net
Subject: bug#44784: Combining accent is not combining
Date: Sun, 22 Nov 2020 17:28:08 +0200 [thread overview]
Message-ID: <83k0udxvg7.fsf@gnu.org> (raw)
In-Reply-To: <87blfpvgy4.fsf@gmx.net> (message from Stephen Berman on Sun, 22 Nov 2020 11:12:03 +0100)
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: Juri Linkov <juri@linkov.net>, 44784@debbugs.gnu.org
> Date: Sun, 22 Nov 2020 11:12:03 +0100
>
> > The 2 vectors you show above, let alone the "composed with" part,
> > explicitly say they _were_ composed. So something else is going on
> > here.
>
> I think it's a display problem with DejaVu Sans Mono, as you already
> noted. I also see what Juri sees, but when the cursor appears to be
> over the separately displayed accent, `C-u C-x =' says the character at
> point is SPC.
Right. I think the discussion on the HarfBuzz list to which I pointed
explains what happens: the problematic fonts don't provide the
information necessary to correctly locate the accent over some
character (specifically, precomposed characters that are already
accented). The [0 0 0] part of the second glyph in the composition
info is a telltale sign of lack of that information: if you try the
same with a font where display is correct, you will see that the first
2 components are non-zero (notably, the first component should be
negative).
next prev parent reply other threads:[~2020-11-22 15:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 19:17 bug#44784: Combining accent is not combining Juri Linkov
2020-11-21 20:05 ` Eli Zaretskii
2020-11-21 20:13 ` Eli Zaretskii
2020-11-21 20:35 ` Juri Linkov
2020-11-22 3:35 ` Eli Zaretskii
2020-11-22 10:12 ` Stephen Berman
2020-11-22 15:28 ` Eli Zaretskii [this message]
2020-11-22 16:28 ` Stephen Berman
2020-11-22 16:52 ` Eli Zaretskii
2022-02-09 9:43 ` Lars Ingebrigtsen
2022-02-10 8:40 ` Juri Linkov
2022-02-10 10:49 ` Robert Pluim
2022-02-10 11:19 ` Lars Ingebrigtsen
2022-02-10 12:25 ` Eli Zaretskii
2020-11-21 20:08 ` Andreas Schwab
2020-11-21 20:30 ` Juri Linkov
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=83k0udxvg7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44784@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=stephen.berman@gmx.net \
/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).