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: Khaled Hosny <dr.khaled.hosny@gmail.com>,
	behdad@behdad.org, 35721@debbugs.gnu.org
Subject: bug#35721: 27.0.50; Strange Arabic shaping behavior
Date: Thu, 16 May 2019 21:54:10 +0100	[thread overview]
Message-ID: <87y336ce8d.fsf@tcd.ie> (raw)
In-Reply-To: <83bm02cvp3.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 16 May 2019 17:36:56 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> tags 35721 notabug
> thanks
>
>> Date: Thu, 16 May 2019 16:20:00 +0200
>> From: Khaled Hosny <dr.khaled.hosny@gmail.com>
>> Cc: behdad@behdad.org, contovob@tcd.ie, handa@gnu.org,
>> 	35721@debbugs.gnu.org
>> 
>> On Thu, May 16, 2019 at 05:08:47PM +0300, Eli Zaretskii wrote:
>> > The main point of this bug report is about the other part, though: how
>> > sheen should be displayed when using DejaVu Sans Mono.
>> 
>> I don’t think there is a right answer here. Glyphs can have -ve right or
>> left side bearings, so if the graphics context has no room on the either
>> side then I think it is expected that the glyph would be truncated. This
>> is not Arabic specific (e.g. italic f often have -ve right side
>> bearing, in variable width fonts at least).
>
> OK, thanks.
>
> Basil, is it okay with you to close this bug, given these comments?

Thanks to everyone for your explanations.  I now understand why the
truncation happens, and why mark activation is expected to affect
character composition.

The issue that prompted this report, however, is the alternating
toggling of certain character compositions while typing in a separate
part of the buffer (steps 9 and 10 in the OP), where no face change is
involved.  I'm sorry for not making this clearer from the outset.

If you think this is unsurprising behaviour given the display engine's
current implementation, I don't mind if you close this issue.
Otherwise, perhaps either this issue can be retitled, or I can submit a
new issue focussing only on that part of the OP.

Sorry for the confusion, and thanks again.

-- 
Basil





  reply	other threads:[~2019-05-16 20:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-13 22:09 bug#35721: 27.0.50; Strange Arabic shaping behavior Basil L. Contovounesios
2019-05-14 15:10 ` Eli Zaretskii
2019-05-14 18:23   ` Eli Zaretskii
2019-05-15 23:02     ` Behdad Esfahbod
2019-05-16 13:28       ` Eli Zaretskii
2019-05-16 13:45         ` Khaled Hosny
2019-05-16 14:08           ` Eli Zaretskii
2019-05-16 14:20             ` Khaled Hosny
2019-05-16 14:36               ` Eli Zaretskii
2019-05-16 20:54                 ` Basil L. Contovounesios [this message]
2019-05-17  6:31                   ` Eli Zaretskii
2019-05-20 19:07                     ` Basil L. Contovounesios
2019-05-16 20:47   ` Basil L. Contovounesios

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=87y336ce8d.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=35721@debbugs.gnu.org \
    --cc=behdad@behdad.org \
    --cc=dr.khaled.hosny@gmail.com \
    --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).