From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 14461@debbugs.gnu.org, stephen.berman@gmx.net, cedric.chepied@gmail.com
Subject: bug#14461: 24.3.50; bad display for 'space' + (U+0336) unicode combination
Date: Fri, 16 Aug 2019 09:55:01 +0300 [thread overview]
Message-ID: <83d0h5ppkq.fsf@gnu.org> (raw)
In-Reply-To: <87o90psyzg.fsf@mouse.gnus.org> (message from Lars Ingebrigtsen on Thu, 15 Aug 2019 18:03:31 -0700)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Thu, 15 Aug 2019 18:03:31 -0700
> Cc: 14461@debbugs.gnu.org, Cédric Chépied
> <cedric.chepied@gmail.com>
>
> Stephen Berman <stephen.berman@gmx.net> writes:
>
> > ... I assume combining characters are always displayed after a space
> > instead of over it -- at least that's what I see with e.g. U+0301
> > (COMBINING ACUTE ACCENT) and U+0302 (COMBINING CIRCUMFLEX ACCENT). That
> > makes sense to me (otherwise, you couldn't visually distinguish e.g. the
> > sequence 'aU+0301U+0302' from the sequence 'aU+0301 U+0302') and I would
> > guess some Unicode standard prescribes it.
>
> Sounds logical. Anybody know for sure?
I don't know for sure, but I will look into this soon if no one beats
me to it.
next prev parent reply other threads:[~2019-08-16 6:55 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 [this message]
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
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=83d0h5ppkq.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.