From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: clement.pitclaudel@live.com, 26742@debbugs.gnu.org
Subject: bug#26742: Display bug with composed strings
Date: Tue, 02 May 2017 20:53:45 +0300 [thread overview]
Message-ID: <8360hji1qu.fsf@gnu.org> (raw)
In-Reply-To: <87shknp481.fsf@linux-m68k.org> (message from Andreas Schwab on Tue, 02 May 2017 19:18:22 +0200)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Clément Pit--Claudel <clement.pitclaudel@live.com>,
> 26742@debbugs.gnu.org
> Date: Tue, 02 May 2017 19:18:22 +0200
>
> I see the same effect, if I use Droid Sans Mono as the default font, but
> not with DejaVu Sans Mono (in the latter case both characters are
> selected from this font).
>
> The component character(s) are displayed by these fonts (glyph codes):
> ℝ: xft:-unknown-Linux Libertine O-normal-normal-normal-*-15-*-*-*-*-0-iso10646-1 (#x748)
> ≤: xft:-unknown-Droid Sans Mono-normal-normal-normal-*-15-*-*-*-m-0-iso10646-1 (#x231)
Aha, so this is somehow font-depended after all. Thanks.
For the record, on my system, the problem doesn't happen even if the
two characters are displayed using different fonts:
The component character(s) are displayed by these fonts (glyph codes):
ℝ: uniscribe:-outline-Symbola-normal-normal-normal-serif-13-*-*-*-p-*-iso10646-1 (#x471)
≤: uniscribe:-outline-Courier New-normal-normal-normal-mono-13-*-*-*-c-*-iso8859-1 (#x94)
Does anything change if you add
--eval "(setq use-default-font-for-symbols nil)"
to the Emacs command line, before the file name to visit? In my case,
this still doesn't reproduce the problem, and the two characters still
use 2 different fonts, although ≤ now uses a different font, not the
one used by the default face.
next prev parent reply other threads:[~2017-05-02 17:53 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 [this message]
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
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=8360hji1qu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=26742@debbugs.gnu.org \
--cc=clement.pitclaudel@live.com \
--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.