From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: angelo.g0@libero.it, emacs-devel@gnu.org
Subject: Re: An issue with GDI? [Windows]
Date: Thu, 14 May 2020 20:38:56 +0300 [thread overview]
Message-ID: <83tv0i4dsf.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0ST0HBoXsp2ywZ+MVRZ1g+woJ_BdEN5fV4HtUnQAm7GbpQ@mail.gmail.com> (message from Juanma Barranquero on Thu, 14 May 2020 16:53:58 +0200)
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Thu, 14 May 2020 16:53:58 +0200
> Cc: Emacs developers <emacs-devel@gnu.org>
>
> By default, master on Windows is using HarfBuzz to display characters, not GDI.
That's unrelated. HarfBuzz is used for shaping complex scripts, but
the basic low-level font APIs are still the same GDI APIs we used
before. The Uniscribe backend also used/uses them.
> Anyway, Cascadia's changelog says: " We've changed the typographic metrics a bit to align with best
> practices and move away from using legacy Windows GDI values."
>
> And has a link to https://github.com/microsoft/cascadia-code/pull/261 that says: "This change modifies the
> font vertical metrics for better consistency cross-platform. Block drawing characters adjusted to account for
> new metrics."
And they are still discussing that, since other editors are affected.
I suggest to wait until they decide what to do with this.
In any case, as I said: we don't have any code that accesses font
metrics using APIs different from GDI. To change that, someone who
knows this stuff will have to write the code, or at least tell us what
APIs to use instead. Volunteers and suggestions are welcome.
next prev parent reply other threads:[~2020-05-14 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 13:55 An issue with GDI? [Windows] Angelo Graziosi
2020-05-14 14:40 ` Eli Zaretskii
2020-05-14 14:54 ` Angelo Graziosi
2020-05-14 14:53 ` Juanma Barranquero
2020-05-14 17:38 ` Eli Zaretskii [this message]
2020-05-15 20:47 ` Juanma Barranquero
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=83tv0i4dsf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=angelo.g0@libero.it \
--cc=emacs-devel@gnu.org \
--cc=lekktu@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).