GNU bug report logs - #42562
Problem with rendering Persian text still exists in minibuffer and dired

Previous Next

Full log

View this message in rfc822 format

From: Sineau Gh <sineaugh <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 42562 <at> debbugs.gnu.org
Subject: bug#42562: Problem with rendering Persian text still exists in minibuffer and dired
Date: Fri, 31 Jul 2020 10:08:43 +0430

[Message part 1 (text/plain, inline)]

This can't be the problem, because even if I don't set a font on my
config, the font which selected automatically by emacs is also rendered
disjointed. But to make sure this isn't the case, I removed two
compatible fonts that are automatically selected (namely, Vazir and
Noto, both of which have great Persian support). The default font is now
DejaVu
Mono, which is again rendered disjointed.

On Fri, 31 Jul 2020 at 09:44, Eli Zaretskii <eliz <at> gnu.org> wrote:

> > From: Sineau Gh <sineaugh <at> gmail.com>
> > Date: Fri, 31 Jul 2020 00:35:13 +0430
> > Cc: 42562 <at> debbugs.gnu.org
> >
> > 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.
>
> If the problem comes and goes as you change fonts, then the problem is
> not with Emacs, it is with the fonts you are using: they should
> support Arabic shaping.  Emacs by default chooses suitable fonts for
> the Arabic script, but if you force Emacs to use certain font, you can
> disrupt the automatic font selection algorithm and choose a font that
> doesn't support Arabic shaping.
>
> The problems reported earlier existed with any font, and didn't
> disappear when a font was changed.
>

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.