From: Eli Zaretskii <eliz@gnu.org>
To: Rah Guzar <rahguzar@zohomail.eu>
Cc: larsi@gnus.org, 50951@debbugs.gnu.org,
mituharu@math.s.chiba-u.ac.jp, visuweshm@gmail.com
Subject: bug#50951: 28.0.50; Urdu text is not displayed correctly
Date: Sat, 17 Sep 2022 20:00:39 +0300 [thread overview]
Message-ID: <83czbu0wco.fsf@gnu.org> (raw)
In-Reply-To: <87mtayymk5.fsf@zohomail.eu> (message from Rah Guzar on Sat, 17 Sep 2022 18:37:39 +0200)
> From: Rah Guzar <rahguzar@zohomail.eu>
> Cc: Visuwesh <visuweshm@gmail.com>, Eli Zaretskii <eliz@gnu.org>, YAMAMOTO
> Mitsuharu <mituharu@math.s.chiba-u.ac.jp>, larsi@gnus.org,
> 50951@debbugs.gnu.org
> Date: Sat, 17 Sep 2022 18:37:39 +0200
>
>
> I finally tested the patches and both of them improve the situation by a
> lot but problems still remain. One word that is not rendered by
> accurately by them is
>
> ہنگام
>
> Where is problem is fourth character which is
> character: گ (displayed as گ) (codepoint 1711, #o3257, #x6af)
> charset: unicode-bmp (Unicode Basic Multilingual Plane (U+0000..U+FFFF))
> code point in charset: 0x06AF
> script: arabic
>
> This character should be rendered as a circle and two slanted lines
> which seem to get clipped.
>
> Both the patches seem to have the same effect, except that with the
> first one above a threshold I have seen a newline not getting rendered
> so what should be two lines appear as one. This doesn't happen with the
> second patch.
Thanks, I've now installed the second patch on the master branch.
next prev parent reply other threads:[~2022-09-17 17:00 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83czbu0wco.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50951@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
--cc=rahguzar@zohomail.eu \
--cc=visuweshm@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.