all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>, Kenichi Handa <handa@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 15:30:55 +0200	[thread overview]
Message-ID: <83ef9jgw34.fsf@gnu.org> (raw)
In-Reply-To: <87zhs7h3ch.fsf@gmx.net> (message from Stephen Berman on Fri, 11 Jan 2019 11:54:06 +0100)

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: craven@gmx.net,  34035@debbugs.gnu.org
> Date: Fri, 11 Jan 2019 11:54:06 +0100
> 
> > 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?
> 
> I started emacs with -Q, then I selected the "Set Default Font..." entry
> from the Options menu, clicked on "Symbola Regular" and pressed the
> select button.  After doing that, `C-u C-x =' on a character in
> *scratch* shows this:
> 
> xft:-UFAS-Symbola-normal-normal-semicondensed-*-15-*-*-*-*-0-iso10646-1 (#x37)

Symbola supports only 10 characters from the Arabic block, so Emacs
selects a different font for these characters.  What I don't
understand is why the default font has any effect on how characters in
a non-default font are displayed.  CC'ing Handa-san, in the hope that
he might have some insights.

> >>   [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.
> 
> I don't know if it's significant, but it's only first glyph line from
> the harfbuzz build:
> [0 2 1587 6022 0 1 6 16 -8 [0 3 0]]
> that differs from the second glyph line from the master build:
> [0 2 0 6022 0 -15 -10 13 -11 [-16 2 0]]
> The second glyph line from the harfbuzz build:
> [0 2 1587 1377 16 0 16 6 4 nil]
> is identical to the first glyph line from the master build:
> [0 2 1587 1377 16 0 16 6 4 nil]

The identical line describes the base character (1587 is its Unicode
codepoint) in the same font, so it's small wonder that it is the same
with both shaping engines.  The different lines describe the
shadda-kasra diacritics.  (I'm mildly bothered by the fact that the
harfbuzz branch displays the information in reverse order, it might
mean some bug there.)

You can read more about the values displayed there in the doc string
of composition-get-gstring.





  reply	other threads:[~2019-01-11 13:30 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
2019-01-11 10:54           ` Stephen Berman
2019-01-11 13:30             ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ef9jgw34.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34035@debbugs.gnu.org \
    --cc=craven@gmx.net \
    --cc=handa@gnu.org \
    --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 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.