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 16:53:01 +0530 [thread overview]
Message-ID: <CAOR1sLxAsWh1RCxzB1+n+5kivthOrX8hwBJT+Fi1f9ogv5_DXg@mail.gmail.com> (raw)
In-Reply-To: <831qrtflg3.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 2746 bytes --]
Here are the steps to reproduce:
1. emacs -Q
2. enter these three words:
hṛṣyatha (h#x1E5B#x1E63yatha)
kṣiptaḥ (k#x1E63ipta#x1E25)
viśāmaḥ (vi#x015B#x0101ma#x1E25)
At this stage everything is fine, all of the characters use the same font
therefore all of them return the same font after evaluating (font-at
(point)) on them:
#<font-object "-ADBO-Source Code
Pro-regular-normal-normal-*-32-*-*-*-m-0-iso10646-1">
3. Now eval the following in the buffer
(set-face-attribute 'default nil
:font "JetBrains Mono"
:weight 'regular
:height 170)
Now you'll notice that the font for some of the characters above are
different from JetBrainsMono, these characters are:
ṛ (#x1e5b)
ṣ (#x1e63)
ḥ (#x1e25)
(font-at (point)) returns #<font-object "-UKWN-Latin Modern
Mono-regular-normal-normal-*-57-*-*-*-*-0-iso10646-1"> on all of them
while for the rest of the characters gives #<font-object "-JB-JetBrains
Mono-regular-normal-normal-*-57-*-*-*-m-0-iso10646-1">
Changing the weight from regular to medium also does not help, the
offending characters instead of being displayed with Latin Modern Mono are
now displayed with: #<font-object "-GOOG-Noto Serif
Display-medium-normal-normal-*-57-*-*-*-*-0-iso10646-1">
while the rest of the characters are displayed with #<font-object
"-JB-JetBrains Mono-medium-normal-normal-*-57-*-*-*-m-0-iso10646-1">
I have also included screenshots from emacs -Q before, emacs -Q after and
hb-view from JetBrains
Hope this makes things clear, if something is still missing please tell me.
Thanks
On Fri, Sep 30, 2022 at 11:33 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: समीर सिंह Sameer Singh
> > <lumarzeli30@gmail.com>
> > Date: Fri, 30 Sep 2022 04:49:37 +0530
> >
> > codepoints of faulty characters in the above mail:
> > ṣ #x1e63
> > ṇ #x1e47
> > ḍ #x1e0d
>
> Please _always_ show the actual text, not just an image of its
> display. It is practically impossible to know what text you used
> given just its display screenshot, especially when character
> compositions are involved.
>
> In any case, we will need a reproducible recipe starting from
> "emacs -Q". Also, please include in your report the output of
>
> M-: (font-at (point)) RET
>
> for the "good" and the "faulty" characters.
>
> In general, reporting issues with fonts need as many specific details
> as you can collect, because these issues are inherently
> system-specific, due to different sets of fonts installed on each
> system, and due to font customizations that are outside of Emacs (on
> the Fontconfig level). The probability of getting unreproducible
> results is very high, and each detail helps.
>
[-- Attachment #1.2: Type: text/html, Size: 3602 bytes --]
[-- Attachment #2: emacs-jetbrains.png --]
[-- Type: image/png, Size: 36978 bytes --]
[-- Attachment #3: emacs-after.png --]
[-- Type: image/png, Size: 23070 bytes --]
[-- Attachment #4: emacs-before.png --]
[-- Type: image/png, Size: 23140 bytes --]
next prev parent reply other threads:[~2022-09-30 11:23 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 [this message]
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
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=CAOR1sLxAsWh1RCxzB1+n+5kivthOrX8hwBJT+Fi1f9ogv5_DXg@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 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.