From: Reuben Thomas <rrt@sc3d.org>
To: Kenichi Handa <handa@gnu.org>
Cc: 14220@debbugs.gnu.org
Subject: bug#14220: 24.3; Odd vertical height of some glyphs in certain fonts
Date: Mon, 20 May 2013 23:21:48 +0100 [thread overview]
Message-ID: <CAOnWdogFhZOOV+bBVGhmxDKp+oAgs2AyzRuNtXanpe=9kmRKrg@mail.gmail.com> (raw)
In-Reply-To: <CAOnWdoiyqiSd3wpdHccDieBzONm3AstfPtF=pSCiYLi_+JVybQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
On 17 April 2013 15:14, Reuben Thomas <rrt@sc3d.org> wrote:
> On 17 April 2013 12:45, Kenichi Handa <handa@gnu.org> wrote:
>
>> In article <87obddd13n.fsf@sc3d.org>, Reuben Thomas <rrt@sc3d.org>
>> writes:
>>
>> > If I set variable-pitch-face to Droid Serif, the right arrow → is much
>> > taller than most other glyphs, effectively forcing extra space after
>> > lines containing it. In DejaVu Serif, this does not happen.
>> Please
>> check which font is used for → in your Emacs by putting
>> cursor on that character and type C-u C-x =. If you do find
>> that your Emacs is using the Droid Serif font, could you
>> please send me that font?
>>
>
> The font being used is:
>
> xft:-unknown-Asana Math-normal-normal-normal-*-14-*-*-*-*-0-iso10646-1
> (#x1D5)
>
> The glyph is shown with the correct baseline, but a large descender space
> (the entire glyph appears to sit above the baseline). Normally, Emacs only
> makes the line taller when there's a glyph which actually needs the space.
>
Ping?
--
http://rrt.sc3d.org
[-- Attachment #2: Type: text/html, Size: 2005 bytes --]
next prev parent reply other threads:[~2013-05-20 22:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 8:15 bug#14220: 24.3; Odd vertical height of some glyphs in certain fonts Reuben Thomas
2013-04-17 11:45 ` Kenichi Handa
2013-04-17 14:14 ` Reuben Thomas
2013-05-20 22:21 ` Reuben Thomas [this message]
2015-04-07 11:59 ` Oleh Krehel
2019-11-01 16:54 ` Lars Ingebrigtsen
2019-11-01 16:42 ` Oleh Krehel
2019-11-01 17:09 ` Eli Zaretskii
2019-11-01 17:15 ` Lars Ingebrigtsen
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='CAOnWdogFhZOOV+bBVGhmxDKp+oAgs2AyzRuNtXanpe=9kmRKrg@mail.gmail.com' \
--to=rrt@sc3d.org \
--cc=14220@debbugs.gnu.org \
--cc=handa@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).