From: "समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58184@debbugs.gnu.org
Subject: bug#58184: Faulty font selection for Latin characters
Date: Fri, 30 Sep 2022 18:25:31 +0530 [thread overview]
Message-ID: <CAOR1sLwzhWSUA2YLvLEdrHGdk+Rr-2C8-kBFJ4wu4k5Hp=a9nA@mail.gmail.com> (raw)
In-Reply-To: <83bkqxdnxl.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]
It's ok, at least I found the cause of my problem.
You can close the bug report.
Thanks
On Fri, Sep 30, 2022 at 6:22 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: समीर सिंह Sameer Singh <lumarzeli30@gmail.com>
> > Date: Fri, 30 Sep 2022 18:05:02 +0530
> > Cc: 58184@debbugs.gnu.org
> >
> > I think I may have found the problem here, JetBrains Mono does not have
> the glyphs for these
> > "faulty" characters that is why Emacs chooses a different font for them,
> but the thing is these characters
> > can still be displayed in the correct font i.e. JetBrains Mono by
> combining the glyphs which made up the
> > unsupported glyph, this is why hb-view was able to display them I guess.
> > For example entering ṃ (#x1e43 Latin small letter m with a dot below)
> will result in it being displayed in a
> > different font,
> > but entering ṃ (m + #x323 Combining dot below) will result in it being
> displayed with JetBrains Mono.
> >
> > So now the question is should these characters be decomposed to better
> fit with other characters when the
> > font does not support them?
>
> We cannot do that in the buffer text, because that would mean
> modifying the text behind user's back. And doing this in display code
> woul mean activating character composition where none should happen.
>
> I think fonts that don't have glyphs for precomposed characters
> shouldn't be used in Emacs for text that could have the codepoints of
> those characters. Emacs doesn't pass every character to the shaping
> engine, and so the tricks of decomposing characters to get them
> displayed are something we cannot be expected to do. Sorry.
>
[-- Attachment #2: Type: text/html, Size: 2238 bytes --]
next prev parent reply other threads:[~2022-09-30 12: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 [this message]
2022-09-30 13:00 ` Eli Zaretskii
2022-09-30 5:55 ` Eli Zaretskii
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='CAOR1sLwzhWSUA2YLvLEdrHGdk+Rr-2C8-kBFJ4wu4k5Hp=a9nA@mail.gmail.com' \
--to=lumarzeli30@gmail.com \
--cc=58184@debbugs.gnu.org \
--cc=eliz@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).