From: Eli Zaretskii <eliz@gnu.org>
To: Shingo Tanaka <shingo.fg8@gmail.com>
Cc: 65803@debbugs.gnu.org
Subject: bug#65803: 29.1; Noto Sans Mono CJK JP has doubled-width on Windows
Date: Fri, 08 Sep 2023 09:25:21 +0300 [thread overview]
Message-ID: <83jzt1xju6.fsf@gnu.org> (raw)
In-Reply-To: <CAH4H2-zS0d+sod+squthwLCiTRMFH_osRQ7_Yq=7tNYwaB6M_Q@mail.gmail.com> (message from Shingo Tanaka on Fri, 8 Sep 2023 08:19:29 +0900)
> From: Shingo Tanaka <shingo.fg8@gmail.com>
> Date: Fri, 8 Sep 2023 08:19:29 +0900
> Cc: 65803@debbugs.gnu.org
>
> I'm not an expert on fonts either, but the reason why I reported is because
> I don't see this issue on Ubuntu as attached with exactly the same font
> (NotoSansMonoCJKjp-VF.ttf). So the difference looks like coming from OS
> difference but not emacs version difference.
Could be: the way Emacs handles fonts on Windows is very different
from what we do on GNU/Linux. For example, it seemed to me that the
session using this font on Windows actually used the bold variant of
the font, which might have something to do with the very partial
support for font families on MS-Windows.
Please also tell what does (frame-char-width) return with each of the
two fonts on Windows.
Is your Ubuntu build with Cairo, btw?
next prev parent reply other threads:[~2023-09-08 6:25 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 [this message]
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
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=83jzt1xju6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65803@debbugs.gnu.org \
--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 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).