unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nicholas Drozd <nicholasdrozd@gmail.com>
Cc: 37683@debbugs.gnu.org
Subject: bug#37683: Eww doesn't render Arabic script correctly
Date: Thu, 10 Oct 2019 09:36:55 +0300	[thread overview]
Message-ID: <83k19dt8c8.fsf@gnu.org> (raw)
In-Reply-To: <CABAiW0qTJw8s2xbyAZB3nO4cJKVFvEQUbJ8P8tLLHcYUhtGpgw@mail.gmail.com> (message from Nicholas Drozd on Wed, 9 Oct 2019 12:16:16 -0500)

> From: Nicholas Drozd <nicholasdrozd@gmail.com>
> Date: Wed, 9 Oct 2019 12:16:16 -0500
> 
> Here is the Persian Wikipedia page for Emacs:
> https://fa.wikipedia.org/wiki/%D8%A7%DB%8C%D9%85%DA%A9%D8%B3
> 
> When I open it in Eww, the cursive Perso-Arabic characters are not
> strung together properly. For example, the article mentions the
> "editor war", جنگ ویرایشگرها. In Eww, this is rendered as جنگ
> ویرایشگرها with wrong forms (initial vs middle vs final vs isolated).
> `D` runs `eww-toggle-paragraph-direction`, but that doesn't have any
> effect on the problem. I think this might be a cursive issue rather
> than a directionality issue, but I could be wrong.
> 
> (As I prepare to send this, I notice that Gmail won't render that
> phrase incorrectly, so the issue might not be communicated clearly
> here.)

Thank you for your report.

First, you cannot effectively report text-shaping (and in general,
rendering) problems by pasting the problematic text into an email
message, because most Emacs maintainers use Emacs to read email, so
any problems you report will be invisible to them, especially if you
show two similar segments of text that are supposed to be rendered
differently.  The only reliable way of reporting such rendering
problems is by including screenshots of the wrong and the correct
rendering (the latter from some other application or from a different
Emacs version, if that's applicable).

And second, you didn't provide any details about the Emacs version you
used and how it was built (i.e. the features it can support) -- this
information is collected by "M-x report-emacs-bug" when you invoke
it.  My first suspicion is that you are using Emacs 26 or older and/or
an outdated version of the libm17n library.  Emacs 27 uses HarfBuzz by
default (if available on the system), and I cannot imagine that
HarfBuzz doesn't render Farsi text correctly.  (If you send
screenshots, I can verify that on my system, as I don't read Farsi, so
I need an image of correct display to compare to.)





  reply	other threads:[~2019-10-10  6:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09 17:16 bug#37683: Eww doesn't render Arabic script correctly Nicholas Drozd
2019-10-10  6:36 ` Eli Zaretskii [this message]
2019-10-10 16:55   ` Nicholas Drozd
2019-10-10 17:44     ` Eli Zaretskii
2019-10-21 20:55       ` 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

  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=83k19dt8c8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=37683@debbugs.gnu.org \
    --cc=nicholasdrozd@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).