Re: Not able to display \u110BD and \u110CD in Emacs

I suggest to use font-at to get the font-object you need for
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.

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 =" say when
the cursor is on that thin 1-pixel space?

position: 89 of 89 (99%), column: 0

character: 𑂽 (displayed as 𑂽) (codepoint 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)

Character code properties: customize what to show
name: KAITHI NUMBER SIGN
general-category: Cf (Other, Format)
decomposition: (69821) ('𑂽')

There is an overlay here:
From 89 to 90
face hl-line
priority -50
window #<window 3 on *scratch*>

There are text properties here:
fontified t

rear-nonsticky t

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

On Fri, Apr 29, 2022 at 9:43 PM Eli Zaretskii <eliz@gnu.org> wrote:

> From: समीर सिंह Sameer Singh <lumarzeli30@gmail.com>
> Date: Fri, 29 Apr 2022 20:56:56 +0530
> Cc: emacs-devel@gnu.org
>
> 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:
> #<font-object "-GOOG-Noto Sans Kaithi-regular-normal-normal-*-23-*-*-*-*-0-iso10646-1">
> "-GOOG-Noto Sans Kaithi-regular-normal-normal-*-23-*-*-*-*-0-iso10646-1"
> "#<font-object -GOOG-Noto Sans Kaithi-regular-normal-normal-*-23-*-*-*-*-0-iso10646-1>"
> "Noto Sans Kaithi"
> "/usr/share/fonts/noto/NotoSansKaithi-Regular.ttf"

I suggest to use font-at to get the font-object you need for
font-get-glyphs.

> 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.

No, that's not possible, sorry.

> 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.

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 =" say when
the cursor is on that thin 1-pixel space?

From:	समीर सिंह Sameer Singh
Subject:	Re: Not able to display \u110BD and \u110CD in Emacs
Date:	Sat, 30 Apr 2022 10:22:00 +0530