From: Visuwesh <visuweshm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 54646@debbugs.gnu.org
Subject: bug#54646: 29.0.50; set-fontset-font and font clipping issues
Date: Thu, 31 Mar 2022 19:14:23 +0530 [thread overview]
Message-ID: <87v8vu5j9k.fsf@gmail.com> (raw)
In-Reply-To: <83fsmy793g.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 31 Mar 2022 12:41:07 +0300")
[வியாழன் மார்ச் 31, 2022] Eli Zaretskii wrote:
>> From: Visuwesh <visuweshm@gmail.com>
>> Cc: 54646@debbugs.gnu.org
>> Date: Thu, 31 Mar 2022 14:59:47 +0530
>>
>> > Also, what version of HarfBuzz do you have there? Can you try
>> > upgrading to a newer version?
>>
>> Emacs is linked against HarfBuzz 3.0.0. I will see if I can update it,
>> and report back in the evening. (P.S., maybe we should look into
>> including this info in the text that M-x report-emacs-bug prepares?)
>
> HarfBuzz is remarkably compatible, and its version until now was never
> important. I asked about that because it is the source of the
> composition data which seems to be incorrect in the wrong display
> cases. I'm not yet sure it's a HarfBuzz problem.
>
I compiled an Emacs that is linked against HarfBuzz 3.3.2, and it shows
the same problem.
>> [ I will also check if I can reproduce this in emacs -Q but with
>> M-: (set-fontset-font t 'tamil "Kurinto Seri") RET. ]
I managed to reproduce this in an emacs -Q session with that evaled but
it took me some time [*]. For each buffer that has Tamil text, I have
to zoom in (or none in the case of eww's header-line) different amounts
to see the clipping issue:
· In init.el, I have to zoom in 7x times
· In eww, I have to zoom in 1x time
· In dired, I have to zoom in ~15x times
In the problematic emacs -Q session, current-iso639-language is 'en'.
[*] As in, it literally took me half an hour to observe the issue, and I
cannot seem to figure out a quick way to reproduce it.
>
> Thanks.
>
> One more question: what is the value of current-iso639-language, and
> is it different between the "bad" and the "good" cases?
next prev parent reply other threads:[~2022-03-31 13:44 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8vu5j9k.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=54646@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).