From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Sineau Gh Newsgroups: gmane.emacs.bugs Subject: bug#42562: Problem with rendering Persian text still exists in minibuffer and dired Date: Fri, 31 Jul 2020 00:35:13 +0430 Message-ID: References: <835za8gyth.fsf@gnu.org> <83ime6f9zp.fsf@gnu.org> <83zh7hdt9x.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000655ee605abae318a" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17011"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 42562@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jul 30 22:06:50 2020 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 1k1EpF-0004LH-Di for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 30 Jul 2020 22:06:49 +0200 Original-Received: from localhost ([::1]:36776 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k1EpE-0005fB-HD for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 30 Jul 2020 16:06:48 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36950) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k1EoU-00055m-JP for bug-gnu-emacs@gnu.org; Thu, 30 Jul 2020 16:06:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:53463) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1k1EoU-00011o-8T for bug-gnu-emacs@gnu.org; Thu, 30 Jul 2020 16:06:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1k1EoT-0000BI-SP for bug-gnu-emacs@gnu.org; Thu, 30 Jul 2020 16:06:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Sineau Gh Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 30 Jul 2020 20:06:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 42562 X-GNU-PR-Package: emacs Original-Received: via spool by 42562-submit@debbugs.gnu.org id=B42562.1596139536661 (code B ref 42562); Thu, 30 Jul 2020 20:06:01 +0000 Original-Received: (at 42562) by debbugs.gnu.org; 30 Jul 2020 20:05:36 +0000 Original-Received: from localhost ([127.0.0.1]:36776 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k1Eo3-0000Ab-Fa for submit@debbugs.gnu.org; Thu, 30 Jul 2020 16:05:35 -0400 Original-Received: from mail-pj1-f47.google.com ([209.85.216.47]:34781) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k1Eny-0000AL-VP for 42562@debbugs.gnu.org; Thu, 30 Jul 2020 16:05:34 -0400 Original-Received: by mail-pj1-f47.google.com with SMTP id c10so2684452pjn.1 for <42562@debbugs.gnu.org>; Thu, 30 Jul 2020 13:05:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=B0r/6FKVmQUlxuUmTl3FJeSeqOyXK4LofBJCnNPfKnU=; b=Uz5DslC7caC5mx0Zewm6zgXZomLlxJWNW+PxC7ixUEcqg0TbF8BXkfT/xqMWKRvfYn EQP/lNi/Krwd0xZLbm+3ZJLH7yI9NwzJ+FO8R4kHJE62aShDphSElbBNeSfUBXVY6Uj/ 7+2Z/mThretD0vTS5e7BC7yGFGPRytU0ieNO1aNYAzXyDq7abIsiTIpg8+FVyP7Qo/BZ ULRUXYWJ07ZT8IK00tFkf1H8nyJP3h3jaUYRL1eH5hA7+hvo9PFZIsnmuhYkvYFczZTL 40+tvHhP8z+hYoJR1B56C5UqJL98IHuHMxOm1N79l4ikle4PBDaBuOAV81HJPNcmpGft +Iqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=B0r/6FKVmQUlxuUmTl3FJeSeqOyXK4LofBJCnNPfKnU=; b=pxeOygazwPfW1riugjiIcgTMhPA3Wk61HyMeZMxBQgOc8L5UOkkvA3lcgnxFvl26NN SebCkZwNtlhaeftzl7Apo857zwQLEwsW0IFFa+zIWFTq5d9+RYAMvet8tdMmv0jylyls FyEmjhzzQSGZjGuCtrUT8yFKJj0zXTNGZY/9tx9MG6FtMI7k/yOHHrjXb9QdxMb8JrF9 ZZLhdCA8PDTaM4jxWyAv2YlR46R/fj9JYt04eBhTSikKmraV9m+h+0fJPSELA++7yRSQ cN2slnWNL9Nsvp7jYT2BOKpE2uUSuvgGjPDaceHomJA2yuR83kZu4Bu+vtpZvaLkrJ0o yDLg== X-Gm-Message-State: AOAM533azNDm0L5ICFaGCuOnDEoDkEelZEkiJS2DFjP4KbcBBtJLiSfy mgE/j1uS6PUcDTQK8Mme/sjE3fokCVMr633KsuEoUY8PF8U= X-Google-Smtp-Source: ABdhPJzv2Hu33EjJMEbPDLY0JH4tUeqc+AnOP+gUDQe+KRfyCmcKzC+3qRU9kBGS1b0hexDBtXhAQ3ChBy74TMwAVhs= X-Received: by 2002:a63:935c:: with SMTP id w28mr526688pgm.174.1596139524937; Thu, 30 Jul 2020 13:05:24 -0700 (PDT) In-Reply-To: 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:183713 Archived-At: --000000000000655ee605abae318a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi again, Here's some more info I have gathered. If I haven't set the default font in my config file, `M-x set-frame-font` only works if there's already an open buffer in the frame. And if I visit a new file, the ligatures are rendered broken again, although the font is the same. So I have to change the font again. On Thu, 30 Jul 2020 at 23:42, Sineau Gh wrote: > > > > > From: Sineau Gh >> > Date: Thu, 30 Jul 2020 17:27:36 +0430 >> > Cc: 42562@debbugs.gnu.org >> > >> > The problem I originally reported was not concerned with typing text, >> but text rendered in read-only buffers >> > (ie. dired and minibuffer). >> >> Then please describe the steps to reproduce this with one such >> read-only buffer. >> >> > > > Also here's the bad news. Just now I realized that bug#41005 is not >> solved yet. At certain combinations of >> > characters, the ligatures are still disjointed. Also I tried to change >> the font family, but that didn't help either. >> > This doesn't happen when I compiled emacs using --without-harfbuzz >> option. I don't know if it helps but I can >> > try to find if there's a pattern to the combinations of characters I >> mentioned. >> >> Here also we would need a recipe to reproduce the problem. >> >> These problems are highly context dependent, and cannot be debugged >> without a reproducer. > > > >> Thanks. >> > > >> > Upon further investigation, I realized that in my config I have used a > combination of `default-frame-alist` and `set-fontset-font` that I forgot > about. So here's a reproduction I hope can be useful for you. First of al= l > the case is the same for both editable buffers and read-only ones so I'm > just using a file with following content: > =D8=AA=D8=B3=D8=AA > =D8=AA=D8=AD=D9=82=DB=8C=D9=82 > =D8=A8=D9=87 > =D8=A7=D8=B5=D8=A7=D9=84=D8=AA > > =D8=B4=D8=B1=D8=AA=D8=A7=D9=84=DA=A9=D9=88 > =D8=AD=D9=82=DB=8C=D9=82 > =D8=AD=D9=82=DB=8C=D9=82=D8=AA > =D8=B3=D9=86=D8=AA > =D8=AA=D8=A7=D9=84=DA=A9=D9=88 > =D9=85=D8=AF=D8=B1=D9=86 > =D9=85=D8=AF=D8=B1=D9=86=DB=8C=D8=B2=D8=A7=D8=B3=DB=8C=D9=88=D9=86 > I have tested this in three cases. Please note they are basically the sam= e > with some minor differences, but I mention them for completeness. > 1- If I have not set a default font in my config, the text is rendered > with broken ligatures. And if I set the font using `M-x set-frame-font` > then everything is okay (even if I set it again to the default font used > for Persian / Arabic text). > > 2- If I use something like the following in my config files: > `(add-to-list 'default-frame-alist '(font . "DejaVu Sans Mono-12"))` > on init the font is rendered broken. And if I set the font using `M-x > set-frame-font` then everything is okay. Now if I set it again to DejaVu > Sans Mono (the font I have used in my config file), it still shows broken > text. I have to first set it to another font and then set it again to > DejaVu so it renders correctly. > > 3- If I use the following line in my config: > `(set-frame-font "DejaVu Sans Mono-12" t t)` > on init the font is broken. And if I set the font using `M-x > set-frame-font` then everything is okay (like previous cases). But I can'= t > set it to DejaVu Sans Mono using `M-x set-frame-font` in any way. That > means I first tried to change the font to something different and then ba= ck > to DejaVu and still it didn't work. > > I should note that I have tested this with various fonts and the result i= s > the same. Also I have tested this in Org and Fundamental modes and the > result is the same. Also I didn't add `set-fontset-font` to the mix but I > supposed it's not going to make a difference. > > I hope this helps, and excuse me if it's not. Thanks for your patience. > --000000000000655ee605abae318a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi again,
Here's some more info I have = gathered. If I haven't set the default font in my config file, `M-x set= -frame-font` only works if there's already an open buffer in the frame.= And if I visit a new file, the ligatures are rendered broken again, althou= gh the font is the same. So I have to change the font again.

On Th= u, 30 Jul 2020 at 23:42, Sineau Gh <sineaugh@gmail.com> wrote:



> From: Sineau Gh <sineaugh@gmail.com>=
> Date: Thu, 30 Jul 2020 17:27:36 +0430
> Cc: 42562@d= ebbugs.gnu.org
>
> The problem I originally reported was not concerned with typing text, = but text rendered in read-only buffers
> (ie. dired and minibuffer).

Then please describe the steps to reproduce this with one such
read-only buffer.



> Also here's the bad news. Just now I realized that bug#41005 is no= t solved yet. At certain combinations of
> characters, the ligatures are still disjointed. Also I tried to change= the font family, but that=C2=A0 didn't help either.
> This doesn't happen when I compiled emacs using --without-harfbuzz= option. I don't know if it helps but I can
> try to find if there's a pattern to the combinations of characters= I mentioned.

Here also we would need a recipe to reproduce the problem.

These problems are highly context dependent, and cannot be debugged
without a reproducer.
=C2=A0
Thanks.



Upon further investigation, I realized that in my config I have used= a combination of `default-frame-alist` and `set-fontset-font` that I forgo= t about. So here's a reproduction I hope can be useful for you. First o= f all the case is the same for both editable buffers and read-only ones so = I'm just using a file with following content:
=D8=AA=D8= =B3=D8=AA
=D8=AA=D8=AD=D9=82=DB=8C=D9=82
=D8=A8=D9=87
=D8=A7=D8=B5= =D8=A7=D9=84=D8=AA

=D8=B4=D8=B1=D8=AA=D8=A7=D9=84=DA=A9=D9=88
=D8= =AD=D9=82=DB=8C=D9=82
=D8=AD=D9=82=DB=8C=D9=82=D8=AA
=D8=B3=D9=86=D8= =AA
=D8=AA=D8=A7=D9=84=DA=A9=D9=88
=D9=85=D8=AF=D8=B1=D9=86
=
=D9=85=D8=AF=D8=B1=D9=86=DB=8C=D8=B2=D8=A7=D8=B3=DB=8C=D9=88=D9=86
I have tested this in three cases. Please note they are basically th= e same with some minor differences, but I mention them for completeness.
1- If I have not set a default font in my config, the text is r= endered with broken ligatures. And if I set the font using `M-x set-frame-f= ont` then everything is okay (even if I set it again to the default font us= ed for Persian / Arabic text).

2- If I use somethi= ng like the following in my config files:
`(add-to-list 'defa= ult-frame-alist '(font . "DejaVu Sans Mono-12"))`
o= n init the font is rendered broken. And if I set the font using `M-x set-fr= ame-font` then everything is okay. Now if I set it again to DejaVu Sans Mon= o (the font I have used in my config file), it still shows broken text. I h= ave to first set it to another font and then set it again to DejaVu so it r= enders correctly.

3- If I use the following line i= n my config:
`(set-frame-font "DejaVu Sans Mono-12" t t= )`
on init the font is broken. And if I set the font using `M-x s= et-frame-font` then everything is okay (like previous cases). But I can'= ;t set it to DejaVu Sans Mono using `M-x set-frame-font` in any way. That m= eans I first tried to change the font to something different and then back = to DejaVu and still it didn't work.

I should n= ote that I have tested this with various fonts and the result is the same. = Also I have tested this in Org and Fundamental modes and the result is the = same. Also I didn't add `set-fontset-font` to the mix but I supposed it= 's not going to make a difference.

I hope this= helps, and excuse me if it's not. Thanks for your patience.
<= /div>
--000000000000655ee605abae318a--