all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Wiegley <johnw@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 66503@debbugs.gnu.org
Subject: bug#66503: 29.1; Problem rendering Arabic diacriticals
Date: Thu, 12 Oct 2023 13:40:06 -0700	[thread overview]
Message-ID: <m2zg0nd17d.fsf@newartisans.com> (raw)
In-Reply-To: <83mswntzg3.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 12 Oct 2023 22:26:04 +0300")

>>>>> Eli Zaretskii <eliz@gnu.org> writes:

> Please also provide the text as text, so we could compare the rendering you
> see with what we see in other builds of Emacs. On macOS, which you seem to
> be using, Emacs uses the system text-shaping engine, which is different from
> HarfBuzz we use on most other platforms, so the rendering we see could be
> different.

I’m always surprised by how much I forget to add to a bug report.

The font is Scheherazade New (great font, btw):

  https://fonts.google.com/specimen/Scheherazade+New

Here is the text:

\ayat{زيرا مُجاهِدينِ کَعبِۀ فِينَا

به بِشارَتِ لَنَهْدِيَنَّهُمْ سُبُلَنَا

مَسرور اند}

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2

  parent reply	other threads:[~2023-10-12 20:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 17:52 bug#66503: 29.1; Problem rendering Arabic diacriticals John Wiegley
2023-10-12 19:26 ` Eli Zaretskii
2023-10-12 19:30   ` Eli Zaretskii
2023-10-12 20:40   ` John Wiegley [this message]
2023-10-13  6:20     ` Eli Zaretskii
2023-10-13 17:04       ` John Wiegley
2023-10-14  5:19       ` John Wiegley
2023-10-14  6:57         ` Eli Zaretskii
2023-10-14  8:56           ` Alan Third
2023-10-14 16:30         ` Stefan Kangas
2023-10-12 20:39 ` Alan Third
2023-10-13  6:21   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2zg0nd17d.fsf@newartisans.com \
    --to=johnw@gnu.org \
    --cc=66503@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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.