From: Eli Zaretskii <eliz@gnu.org>
To: Anand Tamariya <atamariya@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Incorrect glyph info in describe-char
Date: Fri, 23 Jul 2021 08:52:23 +0300 [thread overview]
Message-ID: <8335s537c8.fsf@gnu.org> (raw)
In-Reply-To: <CADm7Y4n7-0UY0LZKOwkRNWcgZ4oypg-5AKPJJ=hSAbm5V7JKVA@mail.gmail.com> (message from Anand Tamariya on Fri, 23 Jul 2021 10:33:06 +0530)
> From: Anand Tamariya <atamariya@gmail.com>
> Date: Fri, 23 Jul 2021 10:33:06 +0530
> Cc: emacs-devel@gnu.org
>
> You did that only for a single character SHIN? But the image shows
> that the entire string is displayed by a font that is not DejaVu Sans
> Mono. And at least on my system, DejaVu Sans Mono doesn't have glyphs
> for the Hebrew block, so when I tell Emacs to use DejaVu Sans Mono as
> the default font, the Hebrew letters are displayed using a different
> font.
>
> If you don't apply the text property, do you see the Hebrew text
> displayed by DejaVu Sans Mono, or does Emacs use a different font for
> it? And what does describe-char say about that if you don't apply the
> text property?
>
> > Apparently, this is what is causing the issue.
>
> It could be, but I don't see how this could happen, by just looking at
> the code involved in this. I'm probably missing something.
>
> It is "emacs -Q". My default font is DejaVuSans Mono. Hence H is displayed using the same. The Hebrew
> text is using Linux Libertine Display O. For printing, I needed text with font variation. So I applied the text
> property for weight and slant - though it didn't change the appearance. After that, desc-char starts reporting
> as mentioned in OP.
Thanks, but this answers only part of my questions. Please also
answer the following:
. did you put the text property only on the single character SHIN or
on the whole Hebrew text?
. what does describe-char report for the SHIN character before you
put the text property?
TIA
next prev parent reply other threads:[~2021-07-23 5:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 7:02 Incorrect glyph info in describe-char Anand Tamariya
2021-07-22 7:18 ` Eli Zaretskii
2021-07-22 8:03 ` Anand Tamariya
2021-07-22 8:54 ` Eli Zaretskii
2021-07-22 9:12 ` Anand Tamariya
2021-07-22 10:06 ` Eli Zaretskii
2021-07-22 11:27 ` Eli Zaretskii
2021-07-23 5:03 ` Anand Tamariya
2021-07-23 5:52 ` Eli Zaretskii [this message]
2021-07-23 6:28 ` Eli Zaretskii
2021-07-23 6:41 ` Anand Tamariya
2021-07-23 6:58 ` Eli Zaretskii
2021-07-23 7:36 ` Anand Tamariya
2021-07-23 7:45 ` Eli Zaretskii
2021-07-23 8:15 ` Anand Tamariya
2021-07-23 10:25 ` 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=8335s537c8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=atamariya@gmail.com \
--cc=emacs-devel@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).