From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Incorrect glyph info in describe-char Date: Fri, 23 Jul 2021 08:52:23 +0300 Message-ID: <8335s537c8.fsf@gnu.org> References: <837dhi4y19.fsf@gnu.org> <83y29y3f0a.fsf@gnu.org> <83tukm3bom.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="400"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Anand Tamariya Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jul 23 07:53:17 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m6o7Z-000AUP-Q9 for ged-emacs-devel@m.gmane-mx.org; Fri, 23 Jul 2021 07:53:17 +0200 Original-Received: from localhost ([::1]:46826 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m6o7X-0001Nc-R5 for ged-emacs-devel@m.gmane-mx.org; Fri, 23 Jul 2021 01:53:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41090) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m6o6z-0000hu-B0 for emacs-devel@gnu.org; Fri, 23 Jul 2021 01:52:41 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:47192) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m6o6z-0004H8-22; Fri, 23 Jul 2021 01:52:41 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3877 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m6o6y-0001dL-Gt; Fri, 23 Jul 2021 01:52:40 -0400 In-Reply-To: (message from Anand Tamariya on Fri, 23 Jul 2021 10:33:06 +0530) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:271485 Archived-At: > From: Anand Tamariya > 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