all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Visuwesh <visuweshm@gmail.com>
Cc: 54646@debbugs.gnu.org
Subject: bug#54646: 29.0.50; set-fontset-font and font clipping issues
Date: Thu, 31 Mar 2022 12:04:41 +0300	[thread overview]
Message-ID: <83h77e7as6.fsf@gnu.org> (raw)
In-Reply-To: <87czi27bnu.fsf@gmail.com> (message from Visuwesh on Thu, 31 Mar 2022 14:15:41 +0530)

> From: Visuwesh <visuweshm@gmail.com>
> Cc: 54646@debbugs.gnu.org
> Date: Thu, 31 Mar 2022 14:15:41 +0530
> 
> I have attached three text files that have the content of the *Help*
> buffer in the three cases:
> 
>     · correct: from emacs -Q which does not exhibit the problem.
> 
>     · incorrect: from an non-daemon Emacs session that exhibits the
>       problem.
> 
>     · correct_config: from a fresh Emacs session with my init.el loaded
>       that does not exhibit the problem.

For meaningful comparison, I need data for the same font size.  One of
the three samples uses a smaller font size, so it's hard to compare it
to the rest.

However, this:

> Composed with the following character(s) "்" using this font:
>   ftcrhb:-Goss-Kurinto Seri-regular-normal-normal-*-14-*-*-*-*-0-iso10646-1
> by these glyphs:
>   [0 1 2965 23479 12 0 12 8 0 nil]
>   [0 1 3021 23505 0 -1 1 11 -9 [-6 0 0]]
> with these character(s):
>   ் (#xbcd) TAMIL SIGN VIRAMA

vs this:

> Composed with the following character(s) "்" using this font:
>   ftcrhb:-Goss-Kurinto Seri-regular-normal-normal-*-14-*-*-*-*-0-iso10646-1
> by these glyphs:
>   [0 1 2965 23479 12 0 12 8 0 [0 0 20]]
>   [0 1 3021 23505 0 -1 1 11 -9 [-14 0 0]]
> with these character(s):
>   ் (#xbcd) TAMIL SIGN VIRAMA

Seems to indicate that we use incorrect composition data in the second
case: the X offset part (-14) seems to be too large, and I don't
understand why there's a non-zero WADJUST value (20) for the first
glyph of the grapheme cluster.  Very strange.  Are both cases for
exactly the same text that surrounds the problematic characters, or
does the surrounding text differ in any way?

Also, what version of HarfBuzz do you have there?  Can you try
upgrading to a newer version?





  reply	other threads:[~2022-03-31  9:04 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31  3:37 bug#54646: 29.0.50; set-fontset-font and font clipping issues Visuwesh
2022-03-31  5:34 ` Eli Zaretskii
2022-03-31  7:03   ` Visuwesh
2022-03-31  7:11     ` Eli Zaretskii
2022-03-31  7:35       ` Visuwesh
2022-03-31  8:45       ` Visuwesh
2022-03-31  9:04         ` Eli Zaretskii [this message]
2022-03-31  9:29           ` Visuwesh
2022-03-31  9:41             ` Eli Zaretskii
2022-03-31 12:16               ` Visuwesh
2022-03-31 14:04                 ` Eli Zaretskii
2022-03-31 13:44               ` Visuwesh
2022-03-31 14:10                 ` Eli Zaretskii
2022-03-31 14:12                   ` Eli Zaretskii
2022-03-31 15:07                   ` Visuwesh
2022-03-31 16:49                     ` Eli Zaretskii
2022-03-31 17:38                       ` Robert Pluim
2022-04-01  1:05                         ` Visuwesh
2022-04-01  3:08                           ` Visuwesh
2022-04-01  8:49                             ` Robert Pluim
2022-04-01 10:54                               ` Eli Zaretskii
2022-04-01 11:38                                 ` Visuwesh
2022-04-01 12:14                                   ` Eli Zaretskii
2022-04-01 13:10                                     ` Visuwesh
2022-04-01 14:19                                       ` Eli Zaretskii
2022-04-01 14:58                                 ` Visuwesh
2022-04-01 15:27                                   ` Eli Zaretskii
2022-04-01 16:40                                     ` Visuwesh
2022-04-01 17:58                                       ` Eli Zaretskii
2022-04-03  9:15                                         ` Visuwesh
2022-04-03 10:06                                           ` Eli Zaretskii
2022-04-03 10:26                                             ` Visuwesh
2022-04-03 10:50                                               ` Eli Zaretskii
2022-04-03 11:10                                                 ` Visuwesh
2022-04-21 14:50                                                   ` Visuwesh
2022-04-22  7:23                                                     ` Eli Zaretskii
2022-04-22 10:46                                                       ` Visuwesh
2022-04-22 10:48                                                         ` Eli Zaretskii
2022-06-11 13:54                                                           ` Visuwesh
2022-06-12  1:34                                                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-12  5:55                                                               ` Eli Zaretskii
2022-06-12  4:49                                                             ` Visuwesh
2022-06-12  5:53                                                             ` Eli Zaretskii
2022-06-12  7:47                                                               ` Visuwesh
2022-06-12 10:16                                                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-08 11:48                                                             ` Visuwesh
2022-10-08 12:42                                                               ` Eli Zaretskii
2022-10-08 12:53                                                                 ` Visuwesh
2022-10-08 13:00                                                                   ` Eli Zaretskii
2022-10-09 11:31                                                                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-09 11:59                                                                     ` Visuwesh
2022-03-31  7:48     ` Eli Zaretskii
2022-03-31  8:47       ` Visuwesh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83h77e7as6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=54646@debbugs.gnu.org \
    --cc=visuweshm@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.