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: Fri, 29 Apr 2022 20:56:56 +0530 Message-ID: References: <83bkwkbfn1.fsf@gnu.org> <837d78bct1.fsf@gnu.org> <83zgk49n9l.fsf@gnu.org> <83v8us9j6p.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000efb10705ddccacb8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17750"; 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 Fri Apr 29 17:58:45 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 1nkT12-0004P8-Dk for ged-emacs-devel@m.gmane-mx.org; Fri, 29 Apr 2022 17:58:44 +0200 Original-Received: from localhost ([::1]:35852 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nkT10-00059v-4A for ged-emacs-devel@m.gmane-mx.org; Fri, 29 Apr 2022 11:58:42 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45042) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nkSWV-0006Qj-Kj for emacs-devel@gnu.org; Fri, 29 Apr 2022 11:27:11 -0400 Original-Received: from mail-qv1-xf2c.google.com ([2607:f8b0:4864:20::f2c]:46750) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nkSWT-0006mc-Gu; Fri, 29 Apr 2022 11:27:11 -0400 Original-Received: by mail-qv1-xf2c.google.com with SMTP id jt15so5562094qvb.13; Fri, 29 Apr 2022 08:27:08 -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=trvavg9VW7/rGdWgJoF5nnb1eHjou2huLeuQTu5P6ms=; b=MV70ViJFXZZJIdmBtBTGs47slLZMIUpTk1GxIzKHaZaI69+Gn0n7ZE819zVYwMe8Ig 28ZI8RtYeBrWK+Ltuj4JPd9/PvoHNeW4AZql/SmCVKKk+24qjop1wAhquVzJdjeCzpFM IX50o9D91wnDUngsaJHaOIA4h2cidtQnJLhy+6mdWhex4Ui1VcDJC0EgWqx6ENlf/ZR9 wFzjcyv4cs6/ivNCxtc9X7+HSuQBrMgYmoLwrlSGjmltjJnZ3uCfe8Kc5C5vx6/dAvST kxN01W9XXvN2KD3NXxQB1bf7UHVtG/sYces97aZpvJFbGiLaF2JO05RptNaIdSbCuPwJ ugGA== 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=trvavg9VW7/rGdWgJoF5nnb1eHjou2huLeuQTu5P6ms=; b=vxQ0zrCVUfOSqY1LwVo8iU+gDQbgEEq912e9W0k2tdMhjQyGsmd//e147nnPE0VXlI IvZZvSXJWS9DaUywDWTqBcnC0pZ34ING4vPC3FrDAn7PCCYAcNlWHN6pTtVRi81f4rbD l4iRu6d7DYrvDMNhtUwlXvh5afJ590EYQGKAfdXO4/Rfgo+l1GtZVQyGv9RsLmmmNVeQ 6MZMH8yHyWdM/IcIjc6Ss4ThM2rcQrL4N23SoR/WMqwev/iNh85cQ4/7SZCs+p/EuCaC Sqc5Ud3TIVypsZXM3idOZiyzAImyZeZoNMBgj9xbsKvr2CYfr896ziC9PxK8F2VV8Scx CUuQ== X-Gm-Message-State: AOAM530/PgeHxvBhZXutdi232f5C8q5EgoxS0+NqPsuLAX8jtOKDgBuz Rq88IujmfcrJCfR8Gm+Rma7IrcCAloSXSX6nySp4q1kgQSfMIg== X-Google-Smtp-Source: ABdhPJxQBQPv9gjyOr/2nSj+8HYE2lQJkHi7VjlQU5anoFpXfwpXGyr5Zllasc14Vkkj+eD6inOG0bL+K6q3Gav4cy4= X-Received: by 2002:a05:6214:248f:b0:456:3892:29b with SMTP id gi15-20020a056214248f00b004563892029bmr18854813qvb.47.1651246028008; Fri, 29 Apr 2022 08:27:08 -0700 (PDT) In-Reply-To: <83v8us9j6p.fsf@gnu.org> Received-SPF: pass client-ip=2607:f8b0:4864:20::f2c; envelope-from=lumarzeli30@gmail.com; helo=mail-qv1-xf2c.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:289002 Archived-At: --000000000000efb10705ddccacb8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > > 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]+")) It is working fine now, Thank You! 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? > I am an extreme novice, so please bear with me, but I cannot get the function to work. I tried to enter the following as the argument FONT OBJECT but none worked: # "-GOOG-Noto Sans Kaithi-regular-normal-normal-*-23-*-*-*-*-0-iso10646-1" "#" "Noto Sans Kaithi" "/usr/share/fonts/noto/NotoSansKaithi-Regular.ttf" Though they do appear alone in Firefox and LibreOffice Writer. 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. > I want the font of devanagari and kaithi to be different, but since kaithi uses devanagari numerals and a devanagari font other than Noto Sans Kaithi does not render the number signs, I was asking that is it possible to only change the devanagari font to Noto Sans Kaithi if it is around a number sign. Though this is a very specific problem of no significance, so it is fine if you don't answer. I will not even use the number signs very much. When you put the cursor at the number sign character, don't you see a > thin 1-pixel space there? > Yes, when the character is not visible in Emacs and whenI put the cursor in its place there is a thin 1-pixel space there. On Fri, Apr 29, 2022 at 5:48 PM 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: 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: =F0=91=82=BD > > KAITHI NUMBER SIGN + DEVANAGARI 0: =F0=91=82=BD=E0=A5=A7 > > > > KAITHI NUMBER SIGN ABOVE: =F0=91=83=8D > > KAITHI NUMBER SIGN ABOVE + DEVANAGARI 0: =F0=91=83=8D=E0=A5=A6 > > When you put the cursor at the number sign character, don't you see a > thin 1-pixel space there? > --000000000000efb10705ddccacb8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The rege= xp in 'numerals' will match only a single character, so just
one character after number-sign will be composed.=C2=A0 if you want to
compose several ones, you need to say this instead:

=C2=A0 =C2=A0 =C2=A0 (numerals "[\x966-\x96F]+"))

It is working fine now, Thank You!

=C2=A0Do they have any = glyphs in the font?=C2=A0 Did you try to use
font-get-glyphs to see if the font can display those characters when
they are alone?
= =C2=A0
I am an extreme novice, so please bear with me, but I cann= ot get the function to work. I tried to enter the following as the argument= FONT OBJECT but none worked:
#<font-object "-GOOG-Noto S= ans Kaithi-regular-normal-normal-*-23-*-*-*-*-0-iso10646-1">
<= div>"-GOOG-Noto Sans Kaithi-regular-normal-normal-*-23-*-*-*-*-0-iso10= 646-1"
"#<font-object -GOOG-Noto Sans Kaithi-re= gular-normal-normal-*-23-*-*-*-*-0-iso10646-1>"
"Not= o Sans Kaithi"
"/usr/share/fonts/noto/NotoSansKaithi-Re= gular.ttf"

Though they do appear alone in Fir= efox and LibreOffice Writer.

That's what your composition rules already= do: they are only triggered
when the character preceding the numerals is a number sign.=C2=A0 So I
don't think I understand the problem.
=C2=A0
I want the font of devanagari an= d kaithi to be different, but since kaithi uses devanagari numerals and a d= evanagari font other than Noto Sans Kaithi does not render the number signs= , I was asking that is it possible to only change the devanagari font to No= to Sans Kaithi if it is around a number sign.
Though this is a ve= ry specific problem of no significance, so it is fine if you don't answ= er. I will not even use the number signs very much.

When you put the cu= rsor at the number sign character, don't you see a
thin 1-pixel space there?
=C2=A0
Yes, when= the character is not visible in Emacs and whenI put the cursor in its plac= e there is a thin 1-pixel space there.

= On Fri, Apr 29, 2022 at 5:48 PM Eli Zaretskii <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 <lumarzeli30@gmail.com>
> Date: Fri, 29 Apr 2022 16:47:22 +0530
> Cc: emacs-dev= el@gnu.org
>
> They seem to be working after changing the devanagari font to Noto San= s Kaithi but only for one digit
> though

But that's what the rule you wrote says:

=C2=A0 =C2=A0 =C2=A0 (numerals "[\x966-\x96F]"))
=C2=A0 [...]
=C2=A0 (set-char-table-range composition-function-table
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 '(#x110BD . #x110BD)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 (list (vector
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(concat number-sign numerals)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00 'font-shape-gstring)))

The regexp in 'numerals' will match only a single character, so jus= t
one character after number-sign will be composed.=C2=A0 if you want to
compose several ones, you need to say this instead:

=C2=A0 =C2=A0 =C2=A0 (numerals "[\x966-\x96F]+"))

> also they do not appear when alone.

Do they have any glyphs in the font?=C2=A0 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 d= evanagari ones, is there any way to
> only change the devanagari font when it is near the kaithi number sign= s?

That's what your composition rules already do: they are only triggered<= br> when the character preceding the numerals is a number sign.=C2=A0 So I
don't think I understand the problem.

>
> Here is the Text I entered, sorry for not including them earlier, I th= ought that mentioning their codepoints
> should be enough.
> KAITHI NUMBER SIGN: =F0=91=82=BD
> KAITHI NUMBER SIGN + DEVANAGARI 0: =F0=91=82=BD=E0=A5=A7
>
> KAITHI NUMBER SIGN ABOVE: =F0=91=83=8D
> KAITHI NUMBER SIGN ABOVE + DEVANAGARI 0: =F0=91=83=8D=E0=A5=A6

When you put the cursor at the number sign character, don't you see a thin 1-pixel space there?
--000000000000efb10705ddccacb8--