unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Vincent Lefevre <vincent@vinc17.net>
To: Robert Pluim <rpluim@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 29078@debbugs.gnu.org
Subject: bug#29078: 25.2; font issue with FreeType 2.8; should not use the rounded ascender and descender
Date: Tue, 19 Nov 2019 12:34:25 +0100	[thread overview]
Message-ID: <20191119113425.GC1940@cventin.lip.ens-lyon.fr> (raw)
In-Reply-To: <m25zjgp4br.fsf@gmail.com>

On 2019-11-19 11:07:20 +0100, Robert Pluim wrote:
> Iʼll note that Vincent's sample file displays wrong on macOS as well
> (this is with
> mac-ct:-*-Hack-normal-normal-normal-*-14-*-*-*-m-0-iso10646-1 (#x4C7),
> although Menlo shows similar artifacts, and Inconsolata gets the
> character widths wrong as well).

It seems different: no gap, but line joining is a bit wrong.
And artifacts are also visible at column joining.

I would tend to say that this is a completely different issue:
something buggy in the rendering algorithm rather than the
interpretation of the metrics.

BTW, note that my sample file is an excerpt from Markus Kuhn's UTF-8
demo at <https://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-demo.txt>.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)





  reply	other threads:[~2019-11-19 11:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 10:12 bug#29078: 25.2; font issue with FreeType 2.8; should not use the rounded ascender and descender Vincent Lefevre
2017-10-31 10:53 ` Robert Pluim
2017-10-31 11:22   ` Werner LEMBERG
2017-10-31 13:43     ` Vincent Lefevre
2017-10-31 15:45       ` Werner LEMBERG
2017-10-31 14:00     ` Robert Pluim
2017-10-31 16:24       ` Werner LEMBERG
2019-11-17  8:02 ` Lars Ingebrigtsen
2019-11-18  7:47   ` Vincent Lefevre
2019-11-18  8:30     ` Lars Ingebrigtsen
2019-11-18 16:05       ` Eli Zaretskii
2019-11-19 10:07         ` Robert Pluim
2019-11-19 11:34           ` Vincent Lefevre [this message]
2019-11-19 16:41             ` Stefan Kangas
2019-11-19 17:33               ` Eli Zaretskii
2019-11-18 15:36     ` Eli Zaretskii
2019-11-18 16:04       ` Vincent Lefevre
2019-11-18 17:09         ` Eli Zaretskii
2019-11-18 17:23           ` Vincent Lefevre
2019-11-18 17:50             ` Eli Zaretskii
2019-11-18 17:58               ` Eli Zaretskii
2019-11-18 18:20                 ` Vincent Lefevre
2019-11-18 18:31                   ` Eli Zaretskii
2019-11-18 18:15               ` Vincent Lefevre
2019-11-18 18:32         ` Lars Ingebrigtsen
2019-11-18 20:26           ` Vincent Lefevre
2019-11-18 20:31             ` Lars Ingebrigtsen
2019-11-19 15:55               ` Eli Zaretskii

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=20191119113425.GC1940@cventin.lip.ens-lyon.fr \
    --to=vincent@vinc17.net \
    --cc=29078@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=rpluim@gmail.com \
    /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).