From: Eli Zaretskii <eliz@gnu.org>
To: Sineau Gh <sineaugh@gmail.com>
Cc: 42562@debbugs.gnu.org
Subject: bug#42562: Problem with rendering Persian text still exists in minibuffer and dired
Date: Fri, 31 Jul 2020 08:13:47 +0300 [thread overview]
Message-ID: <83sgd8e06s.fsf@gnu.org> (raw)
In-Reply-To: <CADVejcQENqBaG2oWQ92u17U1ZPTuvqVxXSUUOFXWdVZN4RbfMQ@mail.gmail.com> (message from Sineau Gh on Fri, 31 Jul 2020 00:35:13 +0430)
> From: Sineau Gh <sineaugh@gmail.com>
> Date: Fri, 31 Jul 2020 00:35:13 +0430
> Cc: 42562@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.
next prev parent reply other threads:[~2020-07-31 5:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 19:21 bug#42562: Problem with rendering Persian text still exists in minibuffer and dired Sineau Gh
2020-07-28 2:26 ` Eli Zaretskii
2020-07-29 15:50 ` Sineau Gh
2020-07-29 18:32 ` Eli Zaretskii
2020-07-30 12:57 ` Sineau Gh
2020-07-30 13:30 ` Eli Zaretskii
2020-07-30 19:12 ` Sineau Gh
2020-07-30 20:05 ` Sineau Gh
2020-07-31 5:13 ` Eli Zaretskii [this message]
2020-07-31 5:38 ` Sineau Gh
2020-07-31 6:06 ` Eli Zaretskii
2020-07-31 6:32 ` Sineau Gh
2020-07-31 12:56 ` Eli Zaretskii
2020-07-31 13:32 ` Sineau Gh
2020-07-31 14:31 ` Eli Zaretskii
2022-03-22 15:37 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83sgd8e06s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42562@debbugs.gnu.org \
--cc=sineaugh@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.