On Fri, Jul 23, 2021 at 1:15 PM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Anand Tamariya <atamariya@gmail.com>
> > Date: Fri, 23 Jul 2021 13:06:57 +0530
> > Cc: emacs-devel@gnu.org
> >
> >  And what does the below display in the original case, i.e. with Hebrew
> >  points in the text:
> >
> >    M-: (find-composition (point) nil nil t) RET
> >
> >  when point is on the SHIN character?
> >
> > (10 13 [[#<font-object "-PfEd-Linux Libertine Display
> O-normal-normal-normal-*-78-*-*-*-*-0-iso10646-1">
> > 1513 1473 1464] 47 [0 2 1464 967 0 6 20 -5 17 [8 0 0]] [0 2 1473 976 0
> 24 32 52 -45 [9 0 0]] [0 2 1513 1005
> > 48 2 46 44 0 nil]])
>
> That's the correct font, which is unexpected: the above
> find-composition call is from describe-char, so if that returns the
> correct font, how come describe-char winds up reporting an incorrect
> font?


My bad. I mixed up the test. After applying the text property on SHIN, the
result is:
(10 13 [[#<font-object "-PfEd-DejaVu
Sans-bold-oblique-normal-*-78-*-*-*-*-0-iso10646-1"> 1513 1473 1464] 63 [0
2 1464 1305 0 8 35 0 17 nil] [0 2 1473 1314 0 63 73 56 -48 nil] [0 2 1513
1344 58 6 67 43 0 nil]])