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: Not able to display \u110BD and \u110CD in Emacs Date: Sat, 30 Apr 2022 09:03:10 +0300 Message-ID: <837d779kgx.fsf@gnu.org> References: <83bkwkbfn1.fsf@gnu.org> <837d78bct1.fsf@gnu.org> <83zgk49n9l.fsf@gnu.org> <83v8us9j6p.fsf@gnu.org> <83levnamv1.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5358"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: =?utf-8?B?4KS44KSu4KWA4KSwIOCkuOCkv+CkguCkuSBTYW1lZXIgU2luZ2g=?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Apr 30 08:06:43 2022 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 1nkgFe-0001Gq-JJ for ged-emacs-devel@m.gmane-mx.org; Sat, 30 Apr 2022 08:06:42 +0200 Original-Received: from localhost ([::1]:34666 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nkgFd-000174-2d for ged-emacs-devel@m.gmane-mx.org; Sat, 30 Apr 2022 02:06:41 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34042) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nkgCB-00005G-Vc for emacs-devel@gnu.org; Sat, 30 Apr 2022 02:03:09 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:39846) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nkgCB-0002Lx-LA; Sat, 30 Apr 2022 02:03:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=AYTMy65CCCrh67LFnvK9fspVrWx45+sx1BcN17zCms0=; b=NuIhyQ8OTcHI6M81sG4W Jt6iVoCj/dbX2eiM3/H6FzkY9+AzVNk835LhLdwqWH48Zlstoskklv8FZQWnSVDW1Ie9OVTf7ctuP ucv393oVaXfbMeopakdbQUBeUk+p61TUluSDSwxrkPXkI3NDP/1fAG0ACcD9hEmPmPi047A8kAwG8 7sEVVNoxx2alSwIuWqm4dNIIzVVv3OQcxlqlJN/8n9DijyrNxB6Le1CRtghQGMNIDKruzVtpRpomw KzQs63uhLwlOeo+BUoEdC73NZti4nLvBNgS6bvRWgS9bmp0/YjRM5KS/ZNgnggJ8RD44TVH/zC1FJ 6v4Yv2nHzKI4qA==; Original-Received: from [87.69.77.57] (port=4920 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 1nkgCB-0001NG-5u; Sat, 30 Apr 2022 02:03:07 -0400 In-Reply-To: (message from =?utf-8?B?4KS44KSu4KWA4KSwIOCkuOCkv+CkguCkuQ==?= Sameer Singh on Sat, 30 Apr 2022 10:22:00 +0530) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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:289029 Archived-At: > From: समीर सिंह Sameer Singh > Date: Sat, 30 Apr 2022 10:22:00 +0530 > Cc: emacs-devel@gnu.org > > I suggest to use font-at to get the font-object you need for > font-get-glyphs. > > I had already used that and got > # > but font-get-glyphs was not accepting it. "Not accepting" how? It works for me, so I don't understand what goes wrong in your case. > So the character is actually visible, it is just displayed as a thin > space. Which means that either its glyph in the font is like that, or > that the font lacks a glyph for it. What does "C-u C-x =" say when > the cursor is on that thin 1-pixel space? > > position: 89 of 89 (99%), column: 0 > character: 𑂽 (displayed as 𑂽) (codepoint 69821, #o210275, #x110bd) > charset: unicode (Unicode (ISO10646)) > code point in charset: 0x110BD > script: kaithi > syntax: w which means: word > category: L:Strong L2R > to input: type "C-x 8 RET 110bd" or "C-x 8 RET KAITHI NUMBER SIGN" > buffer code: #xF0 #x91 #x82 #xBD > file code: #xF0 #x91 #x82 #xBD (encoded by coding system utf-8) > display: by this font (glyph code): > ftcrhb:-GOOG-Noto Sans Kaithi-regular-normal-normal-*-23-*-*-*-*-0-iso10646-1 (#x48) Since this shows the "by this font" part, it means the character _is_ displayed according to the font's glyph for it, and according to Emacs's rules for displaying such "format-control" characters. So now I don't think I understand why you say this character is not shown by Emacs, when the above clearly says it is displayed. > In the character section the character is not displayed in emacs but displayed in firefox, but it is displayed in > the decomposition section in emacs. I have attached the images > Opening the font file in font forge also shows their glyphs You are confusing the display of a lone codepoint with what Font Forge does and what Emacs does in the "decomposition" display. Those do not show the lone character, they show it with special characters before or after, to show how the character will look when combined with others. IOW, I think your expectations from how this character should be displayed as a lone character are incorrect. Can you tell why you want this to be displayed differently when it is a lone character? AFAIU, the only meaningful display of this character is when it precedes numerals.