unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Marco Wahl <marcowahlsoft@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: 𝜖 implies large line spacing
Date: Tue, 21 Mar 2017 15:13:53 +0100	[thread overview]
Message-ID: <84fui6ra3i.fsf@tm6592> (raw)
In-Reply-To: 87var52vxh.fsf@mid.deneb.enyo.de

Florian Weimer <fw@deneb.enyo.de> writes:

>>>> Actually I'm not so happy with those large line spacings.
>>             character: 𝜖 (displayed as 𝜖) (codepoint 120598, #o353426, #x1d716)
>>     preferred charset: unicode (Unicode (ISO10646))
>> code point in charset: 0x1D716
>>                script: mathematical
>>                syntax: w 	which means: word
>>              category: .:Base, L:Left-to-right (strong)
>>              to input: type "C-x 8 RET 1d716" or "C-x 8 RET MATHEMATICAL ITALIC EPSILON SYMBOL"
>>           buffer code: #xF0 #x9D #x9C #x96
>>             file code: #xF0 #x9D #x9C #x96 (encoded by coding system utf-8-unix)
>>               display: by this font (glyph code)
>>     xft:-PfEd-Latin Modern Math-normal-normal-normal-*-15-*-*-*-*-0-iso10646-1 (#x112)
>> ...
>
> After an upgrade to Debian stretch, I now get this font instead:
>
>       xft:-unknown-DejaVu Math TeX Gyre-normal-normal-normal-*-16-*-*-*-*-0-iso10646-1 (#x64A)
>
> And the problem is gone.  The extended height for the original font
> (TeX Gyre Termes Math) no longer shows up in LibreOffice Writer either
> (where it did before).  So there has been a bug fix, likely not in
> Emacs, but I don't know if it's the font metrics which have been
> fixed, or some shared part of font rendering.

Okay.  For now I simply try to avoid characters which lead to huge line
spacing with my settings.

BTW: Accidentially I found ε which does not disturb the line size as
much as 𝜀 does here.




  parent reply	other threads:[~2017-03-21 14:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 12:39 𝜖 implies large line spacing Marco Wahl
2017-03-12 14:03 ` tomas
2017-03-12 15:04 ` Eli Zaretskii
2017-03-12 21:07 ` Florian Weimer
2017-03-14 13:46   ` Marco Wahl
2017-03-14 14:21     ` Gian Uberto Lauri
2017-03-14 14:41     ` HASM
2017-03-14 16:08     ` Eli Zaretskii
2017-03-14 21:52     ` Florian Weimer
2017-03-15  7:25       ` Marco Wahl
2017-03-19 14:16         ` Florian Weimer
2017-03-20 11:44           ` Alexis
2017-03-21 14:13           ` Marco Wahl [this message]
2017-03-14 16:49 ` Felipe Salvador

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=84fui6ra3i.fsf@tm6592 \
    --to=marcowahlsoft@gmail.com \
    --cc=help-gnu-emacs@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.
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).