unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Pit--Claudel" <clement.pitclaudel@live.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 26742@debbugs.gnu.org
Subject: bug#26742: Display bug with composed strings
Date: Tue, 2 May 2017 13:22:19 -0400	[thread overview]
Message-ID: <ce46f810-f6fd-ed54-0bd5-46bd9d142ce8@live.com> (raw)
In-Reply-To: <83d1bri4vg.fsf@gnu.org>


[-- Attachment #1.1: Type: text/plain, Size: 1631 bytes --]

On 2017-05-02 12:46, Eli Zaretskii wrote:
>> Cc: 26742@debbugs.gnu.org From: Clément Pit--Claudel
>> <clement.pitclaudel@live.com> Date: Tue, 2 May 2017 11:40:08 -0400
>> 
>> On 2017-05-02 04:15, Eli Zaretskii wrote:
>>> If you change the font use for displaying ℝ and ≤, does the
>>> problem go away?
>> 
>> No: it seems to happen both in my heavily-customized Emacs and in
>> emacs -Q.
> 
> That doesn't necessarily answer my question, unless the font used to 
> display those two characters is different in "emacs -Q" and in your 
> customized session.

For ℝ, "emacs -Q" uses "Latin Modern Math" and "emacs" with customizations uses "XITS Math". 
For ≤, both use Ubuntu Mono.  I changed the default font and noticed slightly different glitches, including with a variable-pitch font multiple "!" disappearing.

> If that doesn't help, then the next question is: is this problem 
> specific to these two characters, or is it more general?

More investigation suggests that the problem only happens when both parts of the composition are not displayed with the same font.  For example, if I set my default font to Latin Modern Math, the problem goes away.

> If the latter, I suspect the shaping engine used in your case is the
> culprit, so perhaps upgrade your libotf, libm17n-flt, and m17n-db
> packages.  

Apt tells me these packages are up-to-date, but it might not be offering me the very-latest version:

$ apt show libotf0
Package: libotf0
Version: 0.9.13-3

$ apt show libm17n-0
Package: libm17n-0
Version: 1.7.0-3

$ apt show m17n-db
Package: m17n-db
Version: 1.7.0-2


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2017-05-02 17:22 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 [this message]
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

  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=ce46f810-f6fd-ed54-0bd5-46bd9d142ce8@live.com \
    --to=clement.pitclaudel@live.com \
    --cc=26742@debbugs.gnu.org \
    --cc=eliz@gnu.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 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).