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: Thu, 05 May 2022 21:23:50 +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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34792"; mail-complaints-to="usenet@ciao.gmane.io" To: emacs-devel@gnu.org Cancel-Lock: sha1:yFzi42rF0b3b4lmBoReBtXRJSZ8= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu May 05 17:56:52 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 1nmdqV-0008vC-WC for ged-emacs-devel@m.gmane-mx.org; Thu, 05 May 2022 17:56:51 +0200 Original-Received: from localhost ([::1]:58018 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nmdqU-0006Qi-O5 for ged-emacs-devel@m.gmane-mx.org; Thu, 05 May 2022 11:56:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56718) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nmdna-000461-Np for emacs-devel@gnu.org; Thu, 05 May 2022 11:53:50 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:46426) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nmdnZ-0007SK-0K for emacs-devel@gnu.org; Thu, 05 May 2022 11:53:50 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1nmdnW-0004sZ-BA for emacs-devel@gnu.org; Thu, 05 May 2022 17:53:46 +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:289247 Archived-At: * Eli Zaretskii <837d779kgx.fsf @gnu.org> : Wrote on Sat, 30 Apr 2022 09:03:10 +0300: > 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. I believe there is a similar problen with composition of devanagari stress accents with devanagari numerals: 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. numeral one + anudatta + svarita preceding anudatta + numeral three + anudatta + svarita numeral one + anudatta numeral three + anudatta + svarita e.g. (#x969 #x951 #x952), when composed, the devanagari numeral 3 should have an anudatta ("line below") and svarita ("vertical line above"), but it ends up rendering the numeral three, and two then two thin empty vertical boxes. If the boxes render the stress accents I can't see them, they just appear as boxes. name: DEVANAGARI STRESS SIGN ANUDATTA buffer code: #xE0 #xA5 #x92 display: by this font (glyph code): ftcrhb:-IITB-Shobhika-regular-normal-normal-*-17-*-*-*-*-0-iso10646-1 (#x312)