From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?B?4KS44KSu4KWA4KSwIOCkuOCkv+CkguCkuSBTYW1lZXIgU2luZ2g=?= Newsgroups: gmane.emacs.devel Subject: Re: Not able to display \u110BD and \u110CD in Emacs Date: Sat, 30 Apr 2022 11:40:03 +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: multipart/alternative; boundary="00000000000031bbf505ddd903ed" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34929"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Apr 30 08:13:35 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 1nkgMJ-0008x0-KP for ged-emacs-devel@m.gmane-mx.org; Sat, 30 Apr 2022 08:13:35 +0200 Original-Received: from localhost ([::1]:38854 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nkgMI-0004by-FZ for ged-emacs-devel@m.gmane-mx.org; Sat, 30 Apr 2022 02:13:34 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34956) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nkgJ9-0003in-FG for emacs-devel@gnu.org; Sat, 30 Apr 2022 02:10:19 -0400 Original-Received: from mail-qk1-x72a.google.com ([2607:f8b0:4864:20::72a]:43747) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nkgJ7-00034N-DH; Sat, 30 Apr 2022 02:10:19 -0400 Original-Received: by mail-qk1-x72a.google.com with SMTP id y6so5265043qke.10; Fri, 29 Apr 2022 23:10:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qaIVwMfgFmEgO4MpQUQ8yk+evhfzxge4mZEC5nCuADY=; b=XPP1yWSrgyHXCXs04iFRyqstsM6qrgqMbDHgc6JhOvJ050IcvyrNwL/yT0001jt/Dt GJHWlQW5tgImMu1tpwaTCJ6nYiD9DhuSSpaWuexvIuNZ1YtTgXTCI1EIFyt61D33YeX2 z3tF6cNC9T4eNAgOIzK6ShCc4KHfHmhXvhcctpuaoP3LMQ8SQsDmR7J0sGtaoGf3GKII Tk36w30vESIvW6xOZenddYO7mbLk1qTpWS0zmKannsfibWpeHsDW//sFGoS1QSCEbHZ1 mU5epn+Nr5SZy/q66JMNYMZkklnq4Dl4MKVSkj4Ay0RlZsUsax4YwSAKxbyhPg2ZpTXX P1OA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qaIVwMfgFmEgO4MpQUQ8yk+evhfzxge4mZEC5nCuADY=; b=cK52KWktYIXySx2eYjwImCTBpsioZQqpuEvjyog7MYzHnbqG3f/B56rqUpNnXI0bes 42E+UZoX13qaYggQghvyk/wKBYMWrq1FEbwL8PCoWUSHOJrCx/uQ9m4t+szdqLQ5CKxu 8BNC1L9cpS+CV8amAe4wDhlevy7klE8f6QIccdDK4wdCSfdiUjtE5NAgXQpZjcnldR8N vh0iIxKI6kDwyUoKnwjc3wCz6U/pvq6qgbvME9bbU2tbCREqSu6k+BiCrW1QPmY/LbuI JkWaXYpa55j1Ljv2M4z39RtrPvl8tyqYFSLhC4Zc2IoNCYBmL6gUS+UQT3cvcUZEomGu JSaA== X-Gm-Message-State: AOAM5331UNp7LTzPST2qTkNsCCaqnoPgVFDtBQRI8X7Kx2Vo4j6kfbhH K1NmoTW5ZDxxGF5hgYODQFxYWeBL1PHBEgfRV/B4hgrM3A7Y0g== X-Google-Smtp-Source: ABdhPJxqTGDdiqt1tlwCQjYVLE+v0oqXXi9+W20V1W6jZNsXxbbu8q90Lhm15bXYZyZdeaeDPzWjNgvb8yZdyGbvUgA= X-Received: by 2002:a37:d245:0:b0:69b:f262:bacb with SMTP id f66-20020a37d245000000b0069bf262bacbmr1898415qkj.66.1651299014784; Fri, 29 Apr 2022 23:10:14 -0700 (PDT) In-Reply-To: <837d779kgx.fsf@gnu.org> Received-SPF: pass client-ip=2607:f8b0:4864:20::72a; envelope-from=lumarzeli30@gmail.com; helo=mail-qk1-x72a.google.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham 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:289030 Archived-At: --00000000000031bbf505ddd903ed Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > > 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. Yes you are correct, I was just confused as to why it was not being displayed, but this works too. btw, is the way how I have written the composition table correct? I have copied it from the Brahmi composition one, or is it more apporpriate to do it in the way of the devanagari, bengali, malayalam ones? Also I plan to include more writing scripts in emacs, so should I send the patches one by one or in bulk? On Sat, Apr 30, 2022 at 11:33 AM Eli Zaretskii wrote: > > From: =E0=A4=B8=E0=A4=AE=E0=A5=80=E0=A4=B0 =E0=A4=B8=E0=A4=BF=E0=A4=82= =E0=A4=B9 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 > > # Kaithi-regular-normal-normal-*-23-*-*-*-*-0-iso10646-1"> > > 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 =3D" say when > > the cursor is on that thin 1-pixel space? > > > > position: 89 of 89 (99%), column: 0 > > character: =F0=91=82=BD (displayed as =F0=91=82=BD) (codepo= int 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. > --00000000000031bbf505ddd903ed Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Can you tell why you want this to be displayed differently when = it is
a lone character?=C2=A0 AFAIU, the only meaningful display of this
character is when it precedes numerals.
Yes you are correc= t, I was just confused as to why it was not being displayed, but this works= too.

btw, is the way how I have written the compo= sition table correct? I have copied it from the Brahmi composition one, or = is it more apporpriate to do it in the way of the devanagari, bengali, mala= yalam ones?

Also I plan to include more writin= g scripts in emacs, so should I send the patches one by one or in bulk?
=



On Sat, Apr 30, 2022 at 11:33 AM Eli Za= retskii <eliz@gnu.org> wrote:
=
> From: =E0=A4= =B8=E0=A4=AE=E0=A5=80=E0=A4=B0 =E0=A4=B8=E0=A4=BF=E0=A4=82=E0=A4=B9 Sameer = Singh <lumarz= eli30@gmail.com>
> Date: Sat, 30 Apr 2022 10:22:00 +0530
> Cc: emacs-dev= el@gnu.org
>
>=C2=A0 I suggest to use font-at to get the font-object you need for
>=C2=A0 font-get-glyphs.
>
> I had already used that and got
> #<font-object "-GOOG-Noto Sans Kaithi-regular-normal-normal-*-= 23-*-*-*-*-0-iso10646-1">
> but font-get-glyphs was not accepting it.

"Not accepting" how?=C2=A0 It works for me, so I don't unders= tand what goes
wrong in your case.

>=C2=A0 So the character is actually visible, it is just displayed as a = thin
>=C2=A0 space.=C2=A0 Which means that either its glyph in the font is li= ke that, or
>=C2=A0 that the font lacks a glyph for it.=C2=A0 What does "C-u C-= x =3D" say when
>=C2=A0 the cursor is on that thin 1-pixel space?
>
> position: 89 of 89 (99%), column: 0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0character: =F0=91=82=BD= (displayed as =F0=91=82=BD) (codepoint 69821, #o210275, #x110bd)
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0charset: unicode= (Unicode (ISO10646))
> code point in charset: 0x110BD
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 script: kaithi<= br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 syntax: w which= means: word
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 category: L:Strong L2R=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 to input: type "C= -x 8 RET 110bd" or "C-x 8 RET KAITHI NUMBER SIGN"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0buffer code: #xF0 #x91 #x82 #x= BD
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0file code: #xF0 #x91 #x= 82 #xBD (encoded by coding system utf-8)
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0display: by this= font (glyph code):
>=C2=A0 =C2=A0 =C2=A0ftcrhb:-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= .=C2=A0 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 d= isplayed 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.=C2=A0 Th= ose 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?=C2=A0 AFAIU, the only meaningful display of this
character is when it precedes numerals.
--00000000000031bbf505ddd903ed--