From: Visuwesh <visuweshm@gmail.com>
To: 50951@debbugs.gnu.org
Cc: rahguzar@zohomail.eu, eliz@gnu.org, larsi@gnus.org
Subject: bug#50951: 28.0.50; Urdu text is not displayed correctly
Date: Tue, 06 Sep 2022 09:56:09 +0530 [thread overview]
Message-ID: <87r10pb02m.fsf@gmail.com> (raw)
In-Reply-To: <87tu5m6jrw.fsf@zohomail.eu> (Rah Guzar via's message of "Mon, 05 Sep 2022 15:03:47 +0200")
[திங்கள் செப்டம்பர் 05, 2022] Rah Guzar via "Bug reports for GNU Emacs, the Swiss army knife of text editors" wrote:
> Hi Eli,
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> It is unclear to me why this conclusion. Emacs uses HarfBuzz, and the
>> only factor that could affect that, apart from selecting the font, is
>> the setting of the current-iso639-language variable, which AFAIR
>> Rahguzar tried setting with no success.
>
> At your suggestion, I tried hb-view and it renders Noto Nastaliq fine.
> Similarly Libre Office which also uses harfbuzz as far as I understand,
> also renders it fine. Which is why I said that the problem is limited to
> emacs. My understanding of font rendering is non-existent but visually
> what seems to happen is that emacs displays all the individual atoms
> (glyphs?) but it doesn't know how to position them relative to each
> other so they overlap and obscure each other. This positioning is
> especially tricky in Nastaliq fonts since it can require moving all of
> up, down, left, right. The big fonts that emacs render correctly, take
> care of this by prepackaging all these combinations of characters that
> require anything other than right to left movement as separate shapes.
To my ears, this sounds an awful lot like bug#54646 where I faced
similar font clipping issues with Noto Serif Tamil (and other Tamil
fonts). The issues with clipping and other glyph placement issues went
away when I used the Xft+Harfbuzz backend, perhaps that might fix your
issue as well? But you might trade crisp font rendering for a slightly
blurry one though; in my case it was a trade-off I had to make.
next prev parent reply other threads:[~2022-09-06 4:26 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 20:11 bug#50951: 28.0.50; Urdu text is not displayed correctly Rah Guzar
2021-10-02 6:07 ` Eli Zaretskii
[not found] ` <CAP094xCyzg62eHeYCUkWy+eBCbEXC_AAU5YFbhTCcCR0cAOCQw@mail.gmail.com>
2021-10-02 11:43 ` bug#50951: Fwd: " Rah Guzar
2021-10-02 12:18 ` Eli Zaretskii
2021-10-02 12:47 ` Rah Guzar
2021-10-02 13:09 ` Eli Zaretskii
2021-10-02 14:19 ` Rah Guzar
2021-10-02 14:50 ` Eli Zaretskii
[not found] ` <CAP094xBq9YjL6xS56t-C3uhSH69TawhsCrF2FdSMySeDpZfGNw@mail.gmail.com>
2021-10-02 15:09 ` Eli Zaretskii
2021-10-02 15:18 ` Rah Guzar
2021-10-02 14:18 ` Andreas Schwab
2021-10-02 14:40 ` Eli Zaretskii
2021-10-02 15:07 ` Rah Guzar
2021-10-02 15:14 ` Eli Zaretskii
[not found] ` <CAP094xAoHdQZoPL9y6aZOq-WGZe0cYtNsm9Trm+yBiyjyZ4j7g@mail.gmail.com>
2021-10-02 15:54 ` Eli Zaretskii
2021-10-02 16:06 ` Rah Guzar
2021-10-02 16:09 ` Eli Zaretskii
2022-09-04 21:07 ` Lars Ingebrigtsen
2022-09-05 11:22 ` Eli Zaretskii
2022-09-05 11:57 ` Rah Guzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-05 12:29 ` Eli Zaretskii
2022-09-05 13:03 ` Rah Guzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-05 13:55 ` Eli Zaretskii
[not found] ` <87pmg97vsg.fsf@zohomail.eu>
2022-09-05 15:47 ` Eli Zaretskii
2022-09-06 4:26 ` Visuwesh [this message]
2022-09-06 11:05 ` Eli Zaretskii
2022-09-06 13:18 ` Visuwesh
2022-09-07 6:18 ` YAMAMOTO Mitsuharu
2022-09-07 11:27 ` Eli Zaretskii
2022-09-08 6:06 ` Visuwesh
2022-09-09 15:00 ` Rah Guzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-17 16:37 ` Rah Guzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-17 17:00 ` Eli Zaretskii
2022-09-20 3:41 ` YAMAMOTO Mitsuharu
2022-09-20 11:07 ` Eli Zaretskii
2022-09-21 2:20 ` YAMAMOTO Mitsuharu
2022-09-21 2:25 ` YAMAMOTO Mitsuharu
2022-09-22 5:37 ` Eli Zaretskii
2022-09-25 7:18 ` YAMAMOTO Mitsuharu
2022-09-26 7:18 ` Eli Zaretskii
2022-09-27 0:29 ` YAMAMOTO Mitsuharu
2022-09-20 12:35 ` Rah Guzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-11 10:26 ` Visuwesh
2022-09-11 11:11 ` Visuwesh
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=87r10pb02m.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=50951@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=rahguzar@zohomail.eu \
/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).