From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Madhu Newsgroups: gmane.emacs.devel Subject: Re: Not able to display \u110BD and \u110CD in Emacs Date: Fri, 06 May 2022 09:29:45 +0530 Message-ID: References: <83bkwkbfn1.fsf@gnu.org> <837d78bct1.fsf@gnu.org> <83zgk49n9l.fsf@gnu.org> <83v8us9j6p.fsf@gnu.org> <83levnamv1.fsf@gnu.org> <837d779kgx.fsf@gnu.org> <835ymk2afp.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23219"; mail-complaints-to="usenet@ciao.gmane.io" To: emacs-devel@gnu.org Cancel-Lock: sha1:n8hdPJAzCVer8eMB28AlwC13xko= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri May 06 06:01:07 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 1nmp9P-0005vd-3c for ged-emacs-devel@m.gmane-mx.org; Fri, 06 May 2022 06:01:07 +0200 Original-Received: from localhost ([::1]:55940 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nmp9M-000873-T9 for ged-emacs-devel@m.gmane-mx.org; Fri, 06 May 2022 00:01:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46074) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nmp83-0007Os-JJ for emacs-devel@gnu.org; Thu, 05 May 2022 23:59:43 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:53314) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nmp82-0004bA-43 for emacs-devel@gnu.org; Thu, 05 May 2022 23:59:43 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1nmp7y-0004GB-RV for emacs-devel@gnu.org; Fri, 06 May 2022 05:59:38 +0200 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action 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:289295 Archived-At: * Eli Zaretskii <835ymk2afp.fsf@gnu.org> : Wrote on Thu, 05 May 2022 19:47:38 +0300: >> From: Madhu >> Date: Thu, 05 May 2022 21:23:50 +0530 >> > 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. >> I believe there is a similar problen with composition of devanagari >> stress accents with devanagari numerals: > > AFAIU, it's definitely NOT the same problem. I'm sure you're right. [bear with me: I downloaded NotoSansKaithi-Regular.ttf and tried to replicate what Sameer had done: First I was not able to get hb-view to produce the output shown in the first post: the #x110bc number sign doesn't span the following numbers. Then After mutating the composition-function-table as indicated, i had to set (set-fontset-font "fontset-default" '(#x11080 . #x110cf) (font-spec :name "Noto Sans Kaithi" ;; :otf '(kthi nil (rphf)) :registry "iso10646-1" )) is this incorrect? if i add the :otf key then "find-font doesn't find the font", but then i still see no span-composition, and only see the thin white space with #x110bd (even after using this font for devanagri numerals (#x966 . #x96f)) - so I haven't understood what the resolution was] >> The devanagari numerals 1 >> (#x967) & 3 (#x969) can be combined with the svarita (#x951, incorrectly >> named in unicode as DEVANAGARI STRESS SIGN UDATTA) and the anudatta >> (#x952) to form the 4 different accents. > > I see no sign of such composition rules for Devanagai in > lisp/language/indian.el. So it isn't a surprise that Emacs doesn't > display those sequences like you expect. > > I will take a look at this when I have time, but please file a bug > report about this issue. If you can include in the report the results > of running hb-view (from the HarfBuzz distribution) on the text > sequences you describe, that would help. I'll try to this by the following week.