unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34035@debbugs.gnu.org, craven@gmx.net
Subject: bug#34035: 26.1; Arabic shadda-kasrah renders incorrectly
Date: Fri, 11 Jan 2019 10:47:11 +0100	[thread overview]
Message-ID: <874lafil0g.fsf@gmx.net> (raw)
In-Reply-To: <83imyvh773.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 11 Jan 2019 11:30:56 +0200")

On Fri, 11 Jan 2019 11:30:56 +0200 Eli Zaretskii <eliz@gnu.org> wrote:

>> From: Stephen Berman <stephen.berman@gmx.net>
>> Cc: "Peter" <craven@gmx.net>,  34035@debbugs.gnu.org
>> Date: Fri, 11 Jan 2019 10:24:45 +0100
>> 
>> > Thanks.  On my system, this is displayed correctly, with kasrah above
>> > the letter.  So I don't think it's Emacs, I think it's the shaping
>> > engine you are using.  As you didn't provide the information collected
>> > by "M-x report-emacs-bug", I can only guess what is that shaping
>> > engine: XFT and libflt, right?  Maybe you could try building the
>> > harfbazz branch, which uses HarfBazz for shaping, I'd expect this
>> > problem not to exist there.
>> 
>> I believe the problem is not with the shaping engine but with the font:
>
> The OP did say he tried different fonts, to no avail.  It would be
> interesting to know which fonts were those.
>
>> I see the same problem on both builds from current master (with libotf)
>> and from the current harfbuzz branch using my default font, DejaVu Sans
>> Mono.  But when I switch the font to Symbola, the kasrah is correctly
>> displayed between the sin and the shadda, both on master and on
>> harfbuzz.  (Nevertheless, on both branches, after switching to Symbola,
>> describe-char surprisingly says this:
>> 
>> Composed with the following character(s) "ِّ" using this font:
>>   xft:-PfEd-DejaVu Sans-normal-normal-semicondensed-*-15-*-*-*-*-0-iso10646-1
>> 
>> Is this expected?)
>
> Please show the entire output of "C-x =" 

I assume you meant `C-u C-x ='

>                                          (I presume you invoke it on
> the position of sin?).

Yes.  Here's the output on master:

==============================================================================
             position: 1 of 3 (0%), column: 0
            character: س‎ (displayed as س‎) (codepoint 1587, #o3063, #x633)
              charset: unicode (Unicode (ISO10646))
code point in charset: 0x0633
               script: arabic
               syntax: w 	which means: word
             category: .:Base, R:Right-to-left (strong), b:Arabic
             to input: type "s" with arabic input method
          buffer code: #xD8 #xB3
            file code: #xD8 #xB3 (encoded by coding system utf-8-unix)
              display: composed to form "سِّ" (see below)

Composed with the following character(s) "ِّ" using this font:
  xft:-PfEd-DejaVu Sans-normal-normal-semicondensed-*-15-*-*-*-*-0-iso10646-1
by these glyphs:
  [0 2 1587 1377 16 0 16 6 4 nil]
  [0 2 0 6022 0 -15 -10 13 -11 [-16 2 0]]

Character code properties: customize what to show
  name: ARABIC LETTER SEEN
  general-category: Lo (Letter, Other)
  decomposition: (1587) ('س')
==============================================================================

On the harfbuzz branch the output is the same except for the glyphs:

  [0 2 1587 6022 0 1 6 16 -8 [0 3 0]]
  [0 2 1587 1377 16 0 16 6 4 nil]

Note the second line here is identical to the first line of glyphs on
master.

Steve Berman





  reply	other threads:[~2019-01-11  9:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 17:20 bug#34035: 26.1; Arabic shadda-kasrah renders incorrectly Peter
2019-01-10 18:55 ` Eli Zaretskii
2019-01-10 19:45   ` Peter
2019-01-10 19:52     ` Eli Zaretskii
2019-01-10 20:05       ` Peter
2019-01-11  9:24   ` Stephen Berman
2019-01-11  9:30     ` Eli Zaretskii
2019-01-11  9:47       ` Stephen Berman [this message]
2019-01-11 10:34         ` Eli Zaretskii
2019-01-11 10:54           ` Stephen Berman
2019-01-11 13:30             ` Eli Zaretskii
2019-01-11 16:14               ` Stephen Berman
2020-08-18 18:11   ` Stefan Kangas
2020-08-19  8:01     ` Basil L. Contovounesios
2020-08-19  9:07       ` Stephen Berman
2020-08-19  9:49         ` Stefan Kangas
2020-08-19 10:48           ` Basil L. Contovounesios
2020-08-19 14:54             ` Eli Zaretskii
2020-08-19 16:20               ` Basil L. Contovounesios
2020-08-19 16:58                 ` Eli Zaretskii
2020-09-18 10:02             ` Stefan Kangas
2020-08-19 14:32       ` Eli Zaretskii
2020-08-19 16:18         ` Basil L. Contovounesios
2020-08-19 17:11           ` Eli Zaretskii
2020-08-20  0:59             ` Basil L. Contovounesios
2020-08-23  6:41             ` James Cloos
2020-08-23  7:15               ` Eli Zaretskii
2020-08-23  9:26                 ` Stephen Berman
2020-08-23 11:36                   ` 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

  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=874lafil0g.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=34035@debbugs.gnu.org \
    --cc=craven@gmx.net \
    --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 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).