From: Eli Zaretskii <eliz@gnu.org>
To: "समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>
Cc: 58184@debbugs.gnu.org
Subject: bug#58184: Faulty font selection for Latin characters
Date: Fri, 30 Sep 2022 08:55:38 +0300 [thread overview]
Message-ID: <8335c9flt1.fsf@gnu.org> (raw)
In-Reply-To: <CAOR1sLxLp9eszrbeS-TuJe=zXPOLSG0_n6cgyr=A7P1DY5GRcA@mail.gmail.com> (lumarzeli30@gmail.com)
> From: समीर सिंह Sameer Singh
> <lumarzeli30@gmail.com>
> Date: Fri, 30 Sep 2022 04:23:28 +0530
>
> When a font is set for the "default" face in the init.el file.
> For example, like this:
>
> (set-face-attribute 'default nil
> :font "Fira Code"
> :weight 'regular
> :height 170)
>
> This messes up the font selection for various latin and all ipa characters.
What happens if you use 'medium instead of 'regular?
> Despite the configured font supporting the characters which are typed, Emacs selects a different font for
> them, this results in visually jarring text or sometimes failed composition.
>
> For example see in 1.png
> All of the letters except ṇ (#x1E47) are in Fira Code while it is in Latin Modern Mono despite Fira Code
> supporting it.
> Below it t̪ (t + #x32A) is not composed properly because while 't' is in FiraCode #x32A is in Step Regular.
>
> Note: This does not happen with emacs -Q
I don't understand: what doesn't happen in "emacs -Q"? Can you show a
recipe starting from "emacs -Q" that reproduces the problem?
prev parent reply other threads:[~2022-09-30 5:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 22:53 bug#58184: Faulty font selection for Latin characters समीर सिंह Sameer Singh
2022-09-29 23:16 ` समीर सिंह Sameer Singh
2022-09-29 23:19 ` समीर सिंह Sameer Singh
2022-09-30 6:03 ` Eli Zaretskii
2022-09-30 11:23 ` समीर सिंह Sameer Singh
2022-09-30 11:48 ` Eli Zaretskii
2022-09-30 12:35 ` समीर सिंह Sameer Singh
2022-09-30 12:52 ` Eli Zaretskii
2022-09-30 12:55 ` समीर सिंह Sameer Singh
2022-09-30 13:00 ` Eli Zaretskii
2022-09-30 5:55 ` Eli Zaretskii [this message]
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=8335c9flt1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58184@debbugs.gnu.org \
--cc=lumarzeli30@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).