unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: handa <handa@gnu.org>
Cc: nimawebgard@gmail.com, 28339@debbugs.gnu.org
Subject: bug#28339: 25.2; Emacs shows ZWNJ character (Zero Width non-Joiner) as Space
Date: Wed, 13 Sep 2017 18:02:33 +0300	[thread overview]
Message-ID: <83wp52od4m.fsf@gnu.org> (raw)
In-Reply-To: <87d16usnfi.fsf@gnu.org> (message from handa on Wed, 13 Sep 2017 23:06:25 +0900)

> From: handa <handa@gnu.org>
> Cc: nimawebgard@gmail.com, 28339@debbugs.gnu.org
> Date: Wed, 13 Sep 2017 23:06:25 +0900
> 
> > And why do we need to tell Emacs that ZWNJ has a 1-pixel width?
> > Should ZWNJ be at all displayed in this case?
> 
> I'm not sure.  As I wrote in the previous mail, as an editor, isn't it
> better to notify a user the existence of ZWNJ?

I thought that the shaping engine returns to us a series of grapheme
clusters that completely replaces ZWNJ and the neighboring characters,
and that therefore we only need to display the glyphs returned by the
shaper.  If one of the glyphs returned by the shaper is ZWNJ, then
isn't the shaper doing a poor job?

Or maybe I misunderstand something about this situation?

Thanks.





  reply	other threads:[~2017-09-13 15:02 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-03 15:57 bug#28339: 25.2; Emacs shows ZWNJ character (Zero Width non-Joiner) as Space Nima Aryan
2017-09-03 17:06 ` Eli Zaretskii
2017-09-03 17:11   ` Eli Zaretskii
2017-09-03 19:31     ` Nima Aryan
2017-09-04  4:26       ` Eli Zaretskii
2017-09-04  5:05         ` sadid sahami
2017-09-04  9:15           ` Eli Zaretskii
2017-09-04 11:43             ` Nima Aryan
2017-09-04 11:49               ` Nima Aryan
2017-09-04 12:11               ` Eli Zaretskii
2017-09-06 23:25           ` handa
2017-09-07  2:40             ` Eli Zaretskii
     [not found] ` <CALp2H_0RgoW6NL-N3yLA_io38-y8noymU4gGwEbLGcDV4AX9_g@mail.gmail.com>
2017-09-10 23:08   ` handa
2017-09-11 16:19     ` Eli Zaretskii
2017-09-13 14:06       ` handa
2017-09-13 15:02         ` Eli Zaretskii [this message]
2017-09-14 12:24           ` handa
2017-09-14 17:15             ` Eli Zaretskii
2017-09-16  1:32               ` handa
2017-09-16  4:05                 ` Nima Aryan
2017-09-16  7:24                 ` Eli Zaretskii
2017-09-16 17:30               ` Benjamin Riefenstahl
2017-09-16 17:42                 ` Eli Zaretskii
2017-09-16 18:05                   ` Benjamin Riefenstahl
2017-09-16 18:23                     ` Eli Zaretskii
2017-09-16 18:20                   ` Eli Zaretskii
2017-09-18  1:52                   ` handa
2017-09-18 15:16                     ` Eli Zaretskii
2017-09-19 12:18                       ` handa
2017-09-20  7:25                         ` Eli Zaretskii
2017-09-18 15:22                     ` Benjamin Riefenstahl
2017-09-14 21:13           ` Nima Aryan
     [not found] ` <CALp2H_2w50RrBiaWV1dpg760cUpamy1nZdRgrwJKAjESq3no3Q@mail.gmail.com>
2017-09-13 14:02   ` handa
     [not found] ` <CALp2H_3tLC71X6-jvH2XD-6qX8O=KE5wHa561QPk-w2OoCX9HA@mail.gmail.com>
2017-09-16 12:36   ` handa
     [not found] ` <CALp2H_2MWgjoEEm6Rp5+5uOdMk-RbFWzaCrweo=pbdzAaq8btA@mail.gmail.com>
2017-10-06 10:05   ` handa
2017-10-06 12:14     ` Eli Zaretskii
2017-10-07  1:11       ` handa
2020-09-04  5:12       ` Lars Ingebrigtsen

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=83wp52od4m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=28339@debbugs.gnu.org \
    --cc=handa@gnu.org \
    --cc=nimawebgard@gmail.com \
    /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).