From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 34035@debbugs.gnu.org, craven@gmx.net
Subject: bug#34035: 26.1; Arabic shadda-kasrah renders incorrectly
Date: Fri, 11 Jan 2019 12:34:12 +0200 [thread overview]
Message-ID: <83h8efh49n.fsf@gnu.org> (raw)
In-Reply-To: <874lafil0g.fsf@gmx.net> (message from Stephen Berman on Fri, 11 Jan 2019 10:47:11 +0100)
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: craven@gmx.net, 34035@debbugs.gnu.org
> Date: Fri, 11 Jan 2019 10:47:11 +0100
>
> > 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) ('س')
> ==============================================================================
This clearly says that Emacs uses DejaVu Sans for this grapheme
cluster, so I wonder what does "switch the font to Symbola" mean in
this case. Can you tell what you did to switch to Symbola?
> 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.
I would hardly call this "identical", since the offsets are also
different. But I don't think that matters at this point.
next prev parent reply other threads:[~2019-01-11 10:34 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
2019-01-11 10:34 ` Eli Zaretskii [this message]
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=83h8efh49n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34035@debbugs.gnu.org \
--cc=craven@gmx.net \
--cc=stephen.berman@gmx.net \
/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).