From: Robert Pluim <rpluim@gmail.com>
To: Amin Bandali <bandali@gnu.org>
Cc: valizadeh.ho@gmail.com, 41005@debbugs.gnu.org,
Pip Cet <pipcet@gmail.com>
Subject: bug#41005: problem with rendering Persian text in Emacs 27
Date: Tue, 21 Jul 2020 15:34:37 +0200 [thread overview]
Message-ID: <m2pn8png9e.fsf@gmail.com> (raw)
In-Reply-To: <87mu3txcpz.fsf@gnu.org> (Amin Bandali's message of "Tue, 21 Jul 2020 08:40:56 -0400")
>>>>> On Tue, 21 Jul 2020 08:40:56 -0400, Amin Bandali <bandali@gnu.org> said:
Amin> Hi Eli, Pip,
Amin> Thank you for working on this and fixing it on emacs-27 per the reports.
Amin> I have not been able to keep a close eye on GNU lists and trackers for a
Amin> while now, but I was wondering if there's been any more progress/updates
Amin> on this issue on master? I sometimes read/write in Persian, and this
Amin> bug is quite an annoyance. :-) Changing the text scale (C-x C-=) and/or
Amin> filling the paragraph (M-q) seems to sometimes help, but not always; and
Amin> the issue remains.
emacs-27 gets merged to master on a regular basis, and the relevant
commit is present in both:
$ git branch --contains 30a7ee505a
* emacs-27
+ master
Are you still seeing issues with the latest master?
Robert
next prev parent reply other threads:[~2020-07-21 13:34 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 18:02 bug#41005: problem with rendering Persian text in Emacs 27 hossein valizadeh
2020-05-01 18:51 ` Eli Zaretskii
[not found] ` <CAMyfNNp7FiFgAN5EVcVauawiy8ZB7U+eKY7qOeqZOnbMQfs5iQ@mail.gmail.com>
2020-06-03 14:34 ` Eli Zaretskii
2020-06-03 17:24 ` Nicholas Drozd
2020-06-03 18:01 ` Eli Zaretskii
2020-06-04 2:39 ` hossein valizadeh
2020-06-04 3:01 ` hossein valizadeh
2020-06-04 4:01 ` Eli Zaretskii
2020-06-04 4:10 ` Eli Zaretskii
2020-06-04 6:27 ` hossein valizadeh
2020-06-04 8:28 ` Pip Cet
2020-06-04 13:15 ` Eli Zaretskii
2020-06-04 19:52 ` Pip Cet
2020-06-05 4:46 ` hossein valizadeh
2020-06-05 6:21 ` Eli Zaretskii
2020-06-05 11:07 ` Basil L. Contovounesios
2020-06-05 12:32 ` hossein valizadeh
2020-06-05 12:53 ` Eli Zaretskii
2020-06-05 13:05 ` Pip Cet
2020-06-05 14:13 ` Eli Zaretskii
2020-06-06 8:38 ` Pip Cet
2020-06-06 9:04 ` Eli Zaretskii
2020-06-06 9:11 ` Pip Cet
2020-06-06 9:24 ` Eli Zaretskii
2020-06-06 13:09 ` Pip Cet
2020-06-05 14:23 ` hossein valizadeh
2020-06-05 14:25 ` Eli Zaretskii
2020-06-05 6:39 ` Pip Cet
2020-06-05 8:01 ` Eli Zaretskii
2020-06-05 8:41 ` Pip Cet
2020-06-05 11:42 ` Eli Zaretskii
2020-07-21 12:40 ` Amin Bandali
2020-07-21 13:34 ` Robert Pluim [this message]
2020-07-21 17:53 ` Amin Bandali
2020-07-21 18:27 ` Eli Zaretskii
2020-07-22 2:12 ` Amin Bandali
2020-07-22 14:20 ` Eli Zaretskii
2020-07-24 4:11 ` Amin Bandali
2020-07-24 6:09 ` Eli Zaretskii
2020-07-25 4:19 ` Amin Bandali
2020-07-25 6:48 ` Eli Zaretskii
2020-07-25 15:53 ` Amin Bandali
2020-07-25 16:28 ` Eli Zaretskii
2020-07-25 16:44 ` Amin Bandali
2020-07-25 16:56 ` Eli Zaretskii
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=m2pn8png9e.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=41005@debbugs.gnu.org \
--cc=bandali@gnu.org \
--cc=pipcet@gmail.com \
--cc=valizadeh.ho@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).