unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34035@debbugs.gnu.org, stefan@marxist.se, craven@gmx.net
Subject: bug#34035: 26.1; Arabic shadda-kasrah renders incorrectly
Date: Wed, 19 Aug 2020 17:18:36 +0100	[thread overview]
Message-ID: <87zh6qsj6r.fsf@tcd.ie> (raw)
In-Reply-To: <87y37sv38f.fsf@nexoid.at>

[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]

Eli Zaretskii <eliz@gnu.org> writes:

> Which seems to clearly indicate that this _is_ font-dependent, right?
>
> Moreover, it seems also to hint on the reason for the issue: the
> correct display uses only 2 glyphs, whereas the incorrect display uses
> 3 glyphs.  Which means -- and that matches my observations on my
> systems -- that the "good" font has a precomposed glyph for
> shadda-kasrah, while the "bad" font doesn't.  And the composition data
> in the latter case indicates that we were told to display the kasrah
> below the base character (the descent value is positive).

Makes sense.

> Can someone please see what HarfBuzz's hb-view produces from these
> glyphs, with the same fonts as you see in Emacs?  If hb-view produces
> the same display for the same fonts, then it's not an Emacs problem,
> and we should ask the HarfBuzz developers what, if anything, HarfBuzz
> can do better for the problematic fonts.  And if hb-view does better
> than Emacs, then we should ask the HarfBuzz developers to help us
> understand what we do incorrectly in this case.

Emacs and hb-view seem to be in agreement:


[-- Attachment #2: hb-view.png --]
[-- Type: image/png, Size: 25313 bytes --]

[-- Attachment #3: Type: text/plain, Size: 20 bytes --]


Thanks,

-- 
Basil

  reply	other threads:[~2020-08-19 16:18 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
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 [this message]
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=87zh6qsj6r.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=34035@debbugs.gnu.org \
    --cc=craven@gmx.net \
    --cc=eliz@gnu.org \
    --cc=stefan@marxist.se \
    /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).