From: Visuwesh <visuweshm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rpluim@gmail.com, 54646@debbugs.gnu.org
Subject: bug#54646: 29.0.50; set-fontset-font and font clipping issues
Date: Sun, 12 Jun 2022 10:19:24 +0530 [thread overview]
Message-ID: <877d5mwkob.fsf@gmail.com> (raw)
In-Reply-To: <87tu8rs3uf.fsf@gmail.com> (Visuwesh's message of "Sat, 11 Jun 2022 19:24:16 +0530")
[Saturday June 11, 2022] Visuwesh wrote:
> [வெள்ளி ஏப்ரல் 22, 2022] Eli Zaretskii wrote:
>
> I think this might be a cairo+pango problem. My suspicion is due to
> this bug report https://github.com/harfbuzz/harfbuzz/issues/1892 --
> although I don't see the problem with English text as shown in the
> screenshots.
>
> I tried to turn off font metrics in cairo by applying the following
> patch,
>
>
>
> but that did not solve the issue.
>
> However, I have been using the xft+harfbuzz combo for a ~week now and I
> can say with confidence that I don't experience this strange issue. I
> would highly appreciate it if the decision to remove the xft backend
> could be delayed until a solution comes up [1]. Although the font
> rendering is worse, the text stays readable at all font sizes.
>
>
> [1] ./configure --with-cairo says,
>
> configure: WARNING: This configuration uses libXft, which has a number of
> font rendering issues, and is being considered for removal in the
> next release of Emacs. Please consider using Cairo graphics +
> HarfBuzz text shaping instead (they are auto-detected if the
> relevant development headers are installed).
I forgot to mention: I tried the patch with cairo 1.17.4 to no avail either.
next prev parent reply other threads:[~2022-06-12 4:49 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
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 [this message]
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=877d5mwkob.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=54646@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rpluim@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 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).