From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Visuwesh Newsgroups: gmane.emacs.bugs Subject: bug#54646: 29.0.50; set-fontset-font and font clipping issues Date: Sat, 08 Oct 2022 18:23:23 +0530 Message-ID: <877d1abhoc.fsf@gmail.com> References: <875ynuokqt.fsf@gmail.com> <87h77dk3zn.fsf@gmail.com> <87a6d5jyat.fsf@gmail.com> <87wng989ym.fsf@gmail.com> <83ilrt5b1v.fsf@gnu.org> <87h77cetq9.fsf@gmail.com> <831qyg6cyt.fsf@gnu.org> <87czi0eoyx.fsf@gmail.com> <83wng84rf8.fsf@gnu.org> <874k3aede0.fsf@gmail.com> <83y20m32h2.fsf@gnu.org> <87zgl2cvj8.fsf@gmail.com> <83wng630fg.fsf@gnu.org> <87v8vqcthz.fsf@gmail.com> <87wnfitrqy.fsf@gmail.com> <83zgkdpoo2.fsf@gnu.org> <87pml9tmz4.fsf@gmail.com> <83r15ppf5b.fsf@gnu.org> <87tu8rs3uf.fsf@gmail.com> <87fsfybkoz.fsf@gmail.com> <835ygulc59.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34124"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: rpluim@gmail.com, 54646@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Oct 08 14:54:16 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oh9LM-0008eE-8e for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 08 Oct 2022 14:54:16 +0200 Original-Received: from localhost ([::1]:58222 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oh9LK-000235-W7 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 08 Oct 2022 08:54:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59508) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oh9L8-00020J-8T for bug-gnu-emacs@gnu.org; Sat, 08 Oct 2022 08:54:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:39478) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oh9L7-0000xL-VY for bug-gnu-emacs@gnu.org; Sat, 08 Oct 2022 08:54:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oh9L7-0001ZF-MH for bug-gnu-emacs@gnu.org; Sat, 08 Oct 2022 08:54:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Visuwesh Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 08 Oct 2022 12:54:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 54646 X-GNU-PR-Package: emacs Original-Received: via spool by 54646-submit@debbugs.gnu.org id=B54646.16652336185991 (code B ref 54646); Sat, 08 Oct 2022 12:54:01 +0000 Original-Received: (at 54646) by debbugs.gnu.org; 8 Oct 2022 12:53:38 +0000 Original-Received: from localhost ([127.0.0.1]:38555 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oh9Kk-0001YY-8O for submit@debbugs.gnu.org; Sat, 08 Oct 2022 08:53:38 -0400 Original-Received: from mail-pj1-f65.google.com ([209.85.216.65]:36842) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oh9Ke-0001YG-Vw for 54646@debbugs.gnu.org; Sat, 08 Oct 2022 08:53:36 -0400 Original-Received: by mail-pj1-f65.google.com with SMTP id d7-20020a17090a2a4700b0020d268b1f02so42956pjg.1 for <54646@debbugs.gnu.org>; Sat, 08 Oct 2022 05:53:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:user-agent:message-id:date :references:in-reply-to:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=eWzCTLlgr9b+Bbgi+A0bqXZU2KoPazioepqUbq8PQhg=; b=JQp4i7KMQju4/c0xqB9rPKvM/xPGBYR0IAFJ/pr8F5pH0mIQGJ+JVlittF7TQ6TtgX NZU8iIxDrhTh1UOudIl3bHql+ISNvnGuMw85ycg1oa1lCJg67LxdGT4AZUWf/UQs/sAZ /rwX0ctKdBMRlm5TB1YeDpieux4cSZIZGuJ/0V36K0ct4UpJGvad19ZucpwzOKW312d/ E0LklzdL/44tlNs1D188AGdoynWf+KyLtmfDtx1LPKAbe3FP9+6GhWsI/lqkdDPn/nJq pZ+TZqw8HUFhYx8IdngmQ9n7UimcEcGp+NEpRJp27aVAtL5FsMcdVqofFzgstHpEE2JZ 1Cog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:user-agent:message-id:date :references:in-reply-to:subject:cc:to:from:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=eWzCTLlgr9b+Bbgi+A0bqXZU2KoPazioepqUbq8PQhg=; b=UmAfxgcO7vxbtOD4/o/vbtbS4i1MeNn+dIA1wL3iYjZzDfofo0KUOGLYx81A4D4FC4 TTbj/U2u2AA4sehyksdmDrJZonOIEtjv3BZAbkdTnHX1Gv4WOcCYDxDAGWDobPynqjDE oQgFe1Bu4Qoyb1RjZx7OWRNkgWBfWWzJPILfRptQBBD8LcBwusp3Eum4ouC5x6Hs8AY8 Gcf+Gja1odSdUnThzBt1Dom1w0FSOLkBSU0tCn3JBiyE0kDlviQI1ouwTF+KJZah9fAt J9d0KsWuCkkhUeSzSWl2it5p7LuxydqO5mgZx7hyG9MDc0G57lTKlf7jlMNKgnf1w9BZ SjDQ== X-Gm-Message-State: ACrzQf0lKNiRPgerjMG4XtS0TJcodRKPwIgA64jFQyWjg54ir6xu63U4 /p8zHKcOXh1MPSW9xM0gGzo= X-Google-Smtp-Source: AMsMyM61q6HeSCoYfYXjL91zhHBjFgdiIgAUmo179VNQvcM3smsJjqtiL5r1Whd4u+P8ywZb1d23hg== X-Received: by 2002:a17:90a:d14a:b0:203:7b4b:6010 with SMTP id t10-20020a17090ad14a00b002037b4b6010mr21756903pjw.237.1665233607127; Sat, 08 Oct 2022 05:53:27 -0700 (PDT) Original-Received: from localhost ([14.139.216.98]) by smtp.gmail.com with ESMTPSA id p5-20020a634f45000000b0043014f9a4c9sm3189165pgl.93.2022.10.08.05.53.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 08 Oct 2022 05:53:26 -0700 (PDT) In-Reply-To: <835ygulc59.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 08 Oct 2022 15:42:42 +0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:244894 Archived-At: [=E0=AE=9A=E0=AE=A9=E0=AE=BF =E0=AE=85=E0=AE=95=E0=AF=8D=E0=AE=9F=E0=AF=8B= =E0=AE=AA=E0=AE=B0=E0=AF=8D 08, 2022] Eli Zaretskii wrote: >> From: Visuwesh >> Cc: rpluim@gmail.com, 54646@debbugs.gnu.org >> Date: Sat, 08 Oct 2022 17:18:12 +0530 >>=20 >> [=E0=AE=9A=E0=AE=A9=E0=AE=BF =E0=AE=9C=E0=AF=82=E0=AE=A9=E0=AF=8D 11, 20= 22] Visuwesh wrote: >>=20 >> > [...] >> > 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. >>=20 >> I made some "progress" on this bug report. The misplacement goes away >> when I close _all_ frames open on the Xorg display and open a fresh new >> frame. If I only close the frame visiting the problematic buffer and >> open a new frame to visit the buffer again, the misplacement does not go >> away. >> AFAIK, this workaround is not possible in "emacs -Q" since there is no >> way to close all frames without also exiting Emacs. I tried to leave >> the "original" frame around and opening a new frame but that did not >> help. > > Could you please state what issue are you trying to discuss here? The fact that glyphs for Tamil text gets misplaced. To see what I mean, please refer to the images I attached in the OP. > This bug report had its last communication 4 months ago, and its > discussion thread is very long and includes several separate issues. > It's hard to understand to which parts are you alluding here. Sorry about that. All the separate issues eventually boiled down to "Emacs has glyph misplacement issues for Tamil text." The rest of the issue was me figuring out if my config was introducing the misplacement or whether it was a font issue, both of which aren't the case. I can reproduce it in emacs -Q and with any Tamil font I throw at Emacs. > If this is the original issue with incorrect advance width of the > glyphs, then why is it interesting whether it goes away when you close > all the frames? Because, AFAIR, the workaround of closing all the frames did not work before but it does now. > It will sooner or later appear again, and to solve the problem we > need to understand what causes that, no? Yes, the issue shows itself again later but I wondered whether the 'close all the frame' thingy gave some hints. Also, I should note that the patch for bug#50951 made this issue rarer (but still noticeable).