From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>, Kenichi Handa <handa@gnu.org>
Cc: clement.pitclaudel@live.com, 26742@debbugs.gnu.org
Subject: bug#26742: Display bug with composed strings
Date: Tue, 02 May 2017 23:01:05 +0300 [thread overview]
Message-ID: <83y3ufgha6.fsf@gnu.org> (raw)
In-Reply-To: <871ss7oz7f.fsf@linux-m68k.org> (message from Andreas Schwab on Tue, 02 May 2017 21:06:44 +0200)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: clement.pitclaudel@live.com, 26742@debbugs.gnu.org
> Date: Tue, 02 May 2017 21:06:44 +0200
>
> On Mai 02 2017, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Also, what happens if you replace 8804 in your test file with 10877?
>
> Interestingly, this is also shows the effect, even though both
> characters are taken from the same font (not the default font).
So this conclusion:
> So the conclusion this far is that the feature only works reliably
> when both characters are displayed by the same font.
appears to be incorrect, and there's some other factor at work here.
next prev parent reply other threads:[~2017-05-02 20:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 6:58 bug#26742: Display bug with composed strings Clément Pit--Claudel
2017-05-02 8:15 ` Eli Zaretskii
2017-05-02 15:40 ` Clément Pit--Claudel
2017-05-02 16:46 ` Eli Zaretskii
2017-05-02 17:18 ` Andreas Schwab
2017-05-02 17:53 ` Eli Zaretskii
2017-05-02 19:02 ` Andreas Schwab
2017-05-02 19:08 ` Eli Zaretskii
2017-05-02 17:22 ` Clément Pit--Claudel
2017-05-02 17:57 ` Eli Zaretskii
2017-05-02 18:20 ` Eli Zaretskii
2017-05-02 19:06 ` Andreas Schwab
2017-05-02 20:01 ` Eli Zaretskii [this message]
2017-05-03 5:15 ` Clément Pit--Claudel
2017-05-03 5:20 ` Clément Pit--Claudel
2017-05-03 14:50 ` Eli Zaretskii
2017-05-03 3:50 ` YAMAMOTO Mitsuharu
2017-05-03 14:42 ` Eli Zaretskii
2017-05-03 16:53 ` Andreas Schwab
2017-05-04 5:39 ` YAMAMOTO Mitsuharu
2017-05-04 6:30 ` YAMAMOTO Mitsuharu
2017-05-04 16:21 ` Andreas Schwab
2017-05-04 22:40 ` Clément Pit--Claudel
2017-05-07 23:41 ` mituharu
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=83y3ufgha6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=26742@debbugs.gnu.org \
--cc=clement.pitclaudel@live.com \
--cc=handa@gnu.org \
--cc=schwab@linux-m68k.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.
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.