From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Rah Guzar Newsgroups: gmane.emacs.bugs Subject: bug#50951: Fwd: bug#50951: 28.0.50; Urdu text is not displayed correctly Date: Sat, 2 Oct 2021 14:47:37 +0200 Message-ID: References: <83mtnsc63i.fsf@gnu.org> <83sfxjbox7.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000502a1105cd5e1641" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10459"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 50951@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Oct 02 14:48:22 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mWeRC-0002ZH-7z for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 02 Oct 2021 14:48:22 +0200 Original-Received: from localhost ([::1]:50998 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mWeRA-0005iR-H7 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 02 Oct 2021 08:48:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60502) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mWeQt-0005iH-2n for bug-gnu-emacs@gnu.org; Sat, 02 Oct 2021 08:48:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:46630) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mWeQs-0006Vr-N6 for bug-gnu-emacs@gnu.org; Sat, 02 Oct 2021 08:48:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mWeQs-0001Ek-C1 for bug-gnu-emacs@gnu.org; Sat, 02 Oct 2021 08:48:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Rah Guzar Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 02 Oct 2021 12:48:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 50951 X-GNU-PR-Package: emacs Original-Received: via spool by 50951-submit@debbugs.gnu.org id=B50951.16331788764742 (code B ref 50951); Sat, 02 Oct 2021 12:48:02 +0000 Original-Received: (at 50951) by debbugs.gnu.org; 2 Oct 2021 12:47:56 +0000 Original-Received: from localhost ([127.0.0.1]:58176 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mWeQm-0001EQ-6W for submit@debbugs.gnu.org; Sat, 02 Oct 2021 08:47:56 -0400 Original-Received: from mail-wm1-f41.google.com ([209.85.128.41]:56177) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mWeQk-0001EA-EL for 50951@debbugs.gnu.org; Sat, 02 Oct 2021 08:47:54 -0400 Original-Received: by mail-wm1-f41.google.com with SMTP id v127so9180668wme.5 for <50951@debbugs.gnu.org>; Sat, 02 Oct 2021 05:47:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rDzx9EHMIxCe5FZr574G1jdUdwoj8/8fEqfYGGqQ+RI=; b=oufRUXJc0RozvuJ8Ft7IX5C6qSzYhQ5CItCTxh1RQ8L22dnDsXXrL2QVD4hH5oUqnz e0TH3L6+5sTi+xQLos/DFnSCv0iLxcj+Ds84FgBiU+riLNz4ndQe5UOjcuAUzU3AwvlL x7AC8lWWSb0uxHFs4X/fCroZlwQYIGdY8LkfmEwXn9X27UQllfVetOkdCFZNoy7MT7zl adcT/Xbe25nhm0m/6M4ZT0r+VTYKSqBFb5l0DoGNH7d0eIxqSkgNm9Ta9AaEV+SJ6i5R hsttxUDQz9kiCslpVIEJMKLtePP8mDFQ71r7isoOzczsUxs45b3OfYFjYe5bG6anxsqj inxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rDzx9EHMIxCe5FZr574G1jdUdwoj8/8fEqfYGGqQ+RI=; b=gF8/UD3Ls0olNz4NRFERstbj21K6AoxcHKwGSgvUfwbMruhY17ZGf8WMNqAV/wBT47 i8jeuC6PzF+vPZBkVnSF9x44Qx4QMjRS0GKYOd+x1LJW9vJpbzQO+RbuxAPZsCF4d+lW xjt8ygfCtiUlmiHtJbNRgc7rmsFEZPA/RVBN3mSXBLDyLShaSTL4KCU3EDAAQGmfquS8 L2BpFQv8e8jL5a5/i7dwJAfIkTBwTLSrpfDXZG4wAfUIjAA/Hz1FSwrEnj8EZHWOuz0O A7lgaCbtQhWY3gkh8aJE7qCRe6OX2n0ZbPzEbEuzqo+7PmBvbyI9omNaA/NHLMmjrAFD XiFg== X-Gm-Message-State: AOAM533PKXzfg5D0M/aNP9nYIHW0vfiIT4qjbgYo41R8IQlapKSR5kXW HeXo8bUSw0jOmCVUPz68NeZycbJpkCGOHiJ2D3w= X-Google-Smtp-Source: ABdhPJzT5RlYYhRRO0ZNOocrN0JaqGFltFmIh2USaH6MA9AYqCf5VgDopa/Zc8vzd3jzyChSbMjeYbZZr1YYkx4pOu4= X-Received: by 2002:a1c:1c9:: with SMTP id 192mr9217934wmb.158.1633178868524; Sat, 02 Oct 2021 05:47:48 -0700 (PDT) In-Reply-To: <83sfxjbox7.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:216139 Archived-At: --000000000000502a1105cd5e1641 Content-Type: text/plain; charset="UTF-8" On Sat, Oct 2, 2021 at 2:18 PM Eli Zaretskii wrote: > What font displays them individually? You should be able to tell that > if you type "C-u C-x =" on one of these characters. > This is the default font that `emacs -Q` chooses. Using "C-u C-x =" I see, ftcrhb:-PfEd-DejaVu Sans-normal-normal-normal-*-13-*-*-*-*-0-iso10646-1 (#x56F) > So would it be correct to say that using a proper font solves the > problem? > This is almost correct except that the font (NotoNastaliqUrdu) that causes problems with emacs works fine in libreoffice and both use harfbuzz. > I don't think the problem is with compositions, because in the 2 > examples you described above, there are no character compositions. > > Moreover, our pattern for asking HarfBuzz to shape Arabic text is > this: > > "[\u0600-\u074F\u200C\u200D]+" > > which includes all of the characters, including U+06C1 which you say > causes problems. > > You could try setting current-iso639-language to the symbol 'ur' > (without the quotes), that should tell HarfBuzz to shape the text as > appropriate for Urdu. But I think the real problem is with the font, > not with shaping. > Sorry, my lack of understanding of terminology got in the way here. I thought composition referred to joining characters together. I did try setting `current-iso639-language` to the symbol `ur`. As you expected it didn't make a difference. --000000000000502a1105cd5e1641 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sat, Oct 2, 2021 at 2:18 PM Eli Za= retskii <eliz@gnu.org> wrote:
=
What font displays them individually?=C2=A0 You should be able to tell that=
if you type "C-u C-x =3D" on one of these characters.
This is the default font that `emacs -Q` chooses. Using "C-u= C-x =3D" I see,

ftcrhb:-PfEd-DejaVu Sans-nor= mal-normal-normal-*-13-*-*-*-*-0-iso10646-1 (#x56F)
=C2=A0
So would it be correct to say that using a proper font solves the
problem?

This is almost correct except = that the font (NotoNastaliqUrdu) that causes problems with emacs
= works fine in libreoffice and both use harfbuzz.
=C2=A0
I don't think the problem is with compositions, because in the 2
examples you described above, there are no character compositions.

Moreover, our pattern for asking HarfBuzz to shape Arabic text is
this:

=C2=A0 =C2=A0"[\u0600-\u074F\u200C\u200D]+"

which includes all of the characters, including U+06C1 which you say
causes problems.

You could try setting current-iso639-language to the symbol 'ur' (without the quotes), that should tell HarfBuzz to shape the text as
appropriate for Urdu.=C2=A0 But I think the real problem is with the font,<= br> not with shaping.

Sorry, my lack of und= erstanding of terminology got in the way here. I thought composition referr= ed to=C2=A0
joining characters together.

=
I did try setting `current-iso639-language` to the symbol `ur`. = As you expected it didn't make a difference.
--000000000000502a1105cd5e1641--