From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 65803@debbugs.gnu.org, wl@gnu.org, shingo.fg8@gmail.com
Subject: bug#65803: 29.1; Noto Sans Mono CJK JP has doubled-width on Windows
Date: Sat, 09 Sep 2023 17:45:03 +0300 [thread overview]
Message-ID: <83sf7ntngw.fsf@gnu.org> (raw)
In-Reply-To: <87sf7nbgzt.fsf@yahoo.com> (message from Po Lu on Sat, 09 Sep 2023 21:42:14 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: Werner LEMBERG <wl@gnu.org>, 65803@debbugs.gnu.org, shingo.fg8@gmail.com
> Date: Sat, 09 Sep 2023 21:42:14 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > How does one know, using the OpenType specification info, whether a
> > given font is fixed-pitch or proportional? I seem to be unable to
> > find this in the spec, but maybe I need new glasses.
>
> This information is not available within the font file, at least in the
> TrueType specification which is the basis for OpenType. Programs which
> read TrueType fonts are obliged to judge for themselves, customarily by
> taking measurements of each font's glyphs, or by searching for ``Mono''
> within the font's family name. I don't know which approach Windows
> employs.
MS-Windows seems to report it in the data it holds about the font.
See the lfPitchAndFimily attribute in the LOGFONT structure:
https://learn.microsoft.com/en-us/windows/win32/api/wingdi/ns-wingdi-logfontw
and the tmPitchAndFamily attribute of the TEXTMETRIC structure:
https://learn.microsoft.com/en-us/windows/win32/api/wingdi/ns-wingdi-textmetricw
I have no idea how these attributes are determined by Windows.
next prev parent reply other threads:[~2023-09-09 14:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 13:38 bug#65803: 29.1; Noto Sans Mono CJK JP has doubled-width on Windows Shingo Tanaka
2023-09-07 13:50 ` Eli Zaretskii
2023-09-07 14:24 ` Shingo Tanaka
2023-09-07 14:40 ` Eli Zaretskii
2023-09-07 14:57 ` Eli Zaretskii
2023-09-07 23:19 ` Shingo Tanaka
2023-09-08 6:25 ` Eli Zaretskii
2023-09-07 22:26 ` Shingo Tanaka
2023-09-08 12:18 ` Eli Zaretskii
2023-09-08 13:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 14:49 ` Werner LEMBERG
2023-09-09 12:51 ` Eli Zaretskii
2023-09-09 13:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-09 14:45 ` Eli Zaretskii [this message]
2023-09-09 12:17 ` Eli Zaretskii
2023-09-09 13:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-09 14:39 ` Eli Zaretskii
2023-09-09 14:57 ` Eli Zaretskii
2023-09-10 1:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-10 5:22 ` Eli Zaretskii
2023-09-10 5:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-10 5:42 ` Eli Zaretskii
2023-09-10 5:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-10 6:48 ` Eli Zaretskii
2023-09-10 7:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-10 7:53 ` Eli Zaretskii
2023-09-10 7:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-10 8:01 ` Eli Zaretskii
2023-09-10 8:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-10 8:19 ` Eli Zaretskii
2023-09-10 8:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-10 8:50 ` Eli Zaretskii
2023-09-10 9:30 ` Eli Zaretskii
2023-09-10 11:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-10 11:44 ` Eli Zaretskii
2023-09-10 12:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-10 12:43 ` Eli Zaretskii
2023-09-10 12:39 ` Shingo Tanaka
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=83sf7ntngw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65803@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=shingo.fg8@gmail.com \
--cc=wl@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).