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: Fri, 29 Apr 2022 15:18:38 +0300 Message-ID: <83v8us9j6p.fsf@gnu.org> References: <83bkwkbfn1.fsf@gnu.org> <837d78bct1.fsf@gnu.org> <83zgk49n9l.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="37589"; 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 Fri Apr 29 14:22:06 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 1nkPdN-0009ZE-F9 for ged-emacs-devel@m.gmane-mx.org; Fri, 29 Apr 2022 14:22:05 +0200 Original-Received: from localhost ([::1]:50936 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nkPdM-0003O2-EI for ged-emacs-devel@m.gmane-mx.org; Fri, 29 Apr 2022 08:22:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57762) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nkPa3-0008E4-JV for emacs-devel@gnu.org; Fri, 29 Apr 2022 08:18:40 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:46892) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nkPa3-0008DP-1l; Fri, 29 Apr 2022 08:18:39 -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=w2zUZtJZ1DhBAnNgKbDwMJnIA5zveGh+QhgCnxzC2Oo=; b=qt5IkHvync8L7GIvTxFU sgTjXSelVtK1L6vzVwuEOAcwBSkSlLiz575Kk8/1C+bXJv5EkR8pMTq1yfIUCbqSKj0sYITxLlrEV HWu0n7BMwyvFNaGXzBchQNKSqMhh2d0j1z7pFuk31ZbJBbspMe3OF5ZEYVqaIokW+808nPi0tXUyj 7YyzaPn2NFobzKxKXvOBOnVnu4hYJ+dFT+MHBzCx6DxHOe+73thekgqPNX/6YPhLApGhmqztjWm3t GNYc7Ntn/Rf6T5Krp5T0MJ5deENb5VCdVgNd5oiTLX4PpDLJMA0DQdQfOsS7+w3sTExa//H9oDAvZ ILVcqAtMYCSa1A==; Original-Received: from [87.69.77.57] (port=3045 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 1nkPa1-0000mz-6W; Fri, 29 Apr 2022 08:18:38 -0400 In-Reply-To: (message from =?utf-8?B?4KS44KSu4KWA4KSwIOCkuOCkv+CkguCkuQ==?= Sameer Singh on Fri, 29 Apr 2022 16:47:22 +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:288978 Archived-At: > From: समीर सिंह Sameer Singh > Date: Fri, 29 Apr 2022 16:47:22 +0530 > Cc: emacs-devel@gnu.org > > They seem to be working after changing the devanagari font to Noto Sans Kaithi but only for one digit > though But that's what the rule you wrote says: (numerals "[\x966-\x96F]")) [...] (set-char-table-range composition-function-table '(#x110BD . #x110BD) (list (vector (concat number-sign numerals) 0 'font-shape-gstring))) The regexp in 'numerals' will match only a single character, so just one character after number-sign will be composed. if you want to compose several ones, you need to say this instead: (numerals "[\x966-\x96F]+")) > also they do not appear when alone. Do they have any glyphs in the font? Did you try to use font-get-glyphs to see if the font can display those characters when they are alone? > Since the kaithi unicode does not have its own numerals and uses the devanagari ones, is there any way to > only change the devanagari font when it is near the kaithi number signs? That's what your composition rules already do: they are only triggered when the character preceding the numerals is a number sign. So I don't think I understand the problem. > > Here is the Text I entered, sorry for not including them earlier, I thought that mentioning their codepoints > should be enough. > KAITHI NUMBER SIGN: 𑂽 > KAITHI NUMBER SIGN + DEVANAGARI 0: 𑂽१ > > KAITHI NUMBER SIGN ABOVE: 𑃍 > KAITHI NUMBER SIGN ABOVE + DEVANAGARI 0: 𑃍० When you put the cursor at the number sign character, don't you see a thin 1-pixel space there?