all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: larsi@gnus.org, cedric.chepied@gmail.com, 14461@debbugs.gnu.org
Subject: bug#14461: 24.3.50; bad display for 'space' + (U+0336) unicode combination
Date: Sat, 17 Aug 2019 18:09:17 +0300	[thread overview]
Message-ID: <83y2zrn80y.fsf@gnu.org> (raw)
In-Reply-To: <87o90nkg7n.fsf@gmx.net> (message from Stephen Berman on Sat, 17 Aug 2019 16:40:44 +0200)

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: handa@gnu.org,  cedric.chepied@gmail.com,  14461@debbugs.gnu.org,
>   larsi@gnus.org
> Date: Sat, 17 Aug 2019 16:40:44 +0200
> 
> >                                                   If so, I think this
> > just means that the default font you use doesn't support these
> > combining accents, because on my system I see a single grapheme
> > cluster in both of the above cases, when I select a suitable font.
> 
> My default font is DejaVu Sans Mono, but it seems there's something else
> at play here: in contrast to 'aU+0301U+0302', I do see the sequence
> 'bU+0301U+0302' as a single grapheme cluster.  Maybe the difference is
> because there is a glyph for 'a' with an acute accent and it doesn't
> support further combining.  (But I have no idea if that makes sense.)
> Here's what describe-char shows on both:

That says you have a single grapheme cluster in both cases.  Does the
cursor include all of the characters in both cases?  IOW, can you move
with C-f between these 3 characters, or do they behave as a single
character cell in both cases?  If the latter, then the composition was
done in both cases, and you simply should find a better font if you
want these displayed more nicely.





  reply	other threads:[~2019-08-17 15:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 14:30 bug#14461: 24.3.50; bad display for 'space' + (U+0336) unicode combination Cédric Chépied
2019-08-15  4:50 ` Lars Ingebrigtsen
2019-08-15  9:01   ` Stephen Berman
2019-08-15 10:02     ` Cédric Chépied
2019-08-15 12:29       ` Stephen Berman
2019-08-16  1:03         ` Lars Ingebrigtsen
2019-08-16  6:55           ` Eli Zaretskii
2019-08-17 12:00         ` Eli Zaretskii
2019-08-17 13:50           ` Stephen Berman
2019-08-17 14:14             ` Eli Zaretskii
2019-08-17 14:40               ` Stephen Berman
2019-08-17 15:09                 ` Eli Zaretskii [this message]
2019-08-17 15:39                   ` Stephen Berman
2019-08-17 15:44                     ` Eli Zaretskii
2019-08-17 17:05                       ` Stephen Berman
2019-08-17 17:29                         ` Eli Zaretskii
2019-08-17 18:11                           ` Stephen Berman
2019-08-17 18:22                             ` Eli Zaretskii
2019-08-17 18:58                               ` Stephen Berman
2019-09-07  9:21           ` Eli Zaretskii
2019-08-15 14:48   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83y2zrn80y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=14461@debbugs.gnu.org \
    --cc=cedric.chepied@gmail.com \
    --cc=larsi@gnus.org \
    --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 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.