From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65803@debbugs.gnu.org, shingo.fg8@gmail.com
Subject: bug#65803: 29.1; Noto Sans Mono CJK JP has doubled-width on Windows
Date: Sun, 10 Sep 2023 15:55:56 +0800 [thread overview]
Message-ID: <87tts2a2cz.fsf@yahoo.com> (raw)
In-Reply-To: <83msxusbvb.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 10 Sep 2023 10:53:12 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Po Lu <luangruo@yahoo.com>
>> Cc: shingo.fg8@gmail.com, 65803@debbugs.gnu.org
>> Date: Sun, 10 Sep 2023 15:31:36 +0800
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > See above: other backends only calculate the average width for
>> > proportional fonts. So what you say doesn't fit my reading of the
>> > code.
>>
>> Because if spacing is not FC_PROPORTIONAL or FC_DUAL, we know in advance
>> that max_advance_width or max_advance are identical to the average of
>> all ASCII glyphs. Such special treatment is an optimization, nothing
>> more. max_advance_width is the advance width (in em space) of the
>> widest glyph when the font is scalable, and max_advance is that in pixel
>> space if not.
>
> So you think it's okay to do the same in the w32 font backend,
> i.e. take the average width from the font when the font is known to be
> fixed-pitch? If not, please elaborate, because that's what I
> understand from what you wrote above.
I don't think it's okay, because the W32 font backend judges fonts that
are not fixed pitch to be so; Noto Sans Mono CJK JP, for example.
next prev parent reply other threads:[~2023-09-10 7:55 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tts2a2cz.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=65803@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=shingo.fg8@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.