unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Itai Berli <itai.berli@gmail.com>
Cc: 27544@debbugs.gnu.org
Subject: bug#27544: 25.1; Visualization of Unicode bidirectional marks
Date: Sat, 01 Jul 2017 15:16:51 +0300	[thread overview]
Message-ID: <83o9t4pd1o.fsf@gnu.org> (raw)
In-Reply-To: <CABsNJ=MX+O08UFZe7ZVCD5KB6w2Tdd=5g-Xe6G+tYHAgw=gq7w@mail.gmail.com> (message from Itai Berli on Sat, 1 Jul 2017 14:48:21 +0300)

> From: Itai Berli <itai.berli@gmail.com>
> Date: Sat, 1 Jul 2017 14:48:21 +0300
> 
> A default should be something that aligns with the expectations of a
> casual user; you cannot expect a casual user to start writing elisp
> code or tinkering with `glyphless-char-display-control`.
> 
> And how can we know what a casual user would expect?

Thank you for describing your expectations.  However, to change the
defaults, we'd need to hear from more than one user.  If we find that
the majority thinks the default should be changed, we will eventually
do that, as we do with any other default.

> 1. We can follow established standards, particularly if we claim to
> conform to them, as Emacs does to the Unicode standard. The Unicode
> bidi algorithm 8.0.0 specifications state the following about LRM, RLM
> and ALM (section 2.6 Implicit Directional Marks):
> > they do not display or have any other semantic effect
> and again, in the same section:
> >  they do not appear in the display

The UBA also allows to retain these characters, including display
them, see section 5.2 there.  This is how Emacs behaves, again in line
with general Emacs feature of allowing users to see what's in the
buffer.

> 4. We can see how Emacs implements similar constructs. The bidi marks
> are control sequences that can be inserted into the editor using `C-x
> 8 RET <Unicode hex number>`. Let's see how other control sequences are
> handled by this mechanism. If you try to insert, say, the characters
> Null character (U+0000), Bell character (U+0007) and Escape character
> (U+001B) using this method, we'll get:

There are control characters other than those which you tried, for
which Emacs does use the same display method as for bidi controls: try
ZWJ (U+200D) or ARABIC NUMBER SIGN (U+0600) -- all the characters of
Unicode General Category "Cf" that don't have an established graphic
image are by default displayed as thin spaces.  This is explained in
the doc string of glyphless-char-display-control.





  reply	other threads:[~2017-07-01 12:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-01  9:58 bug#27544: 25.1; Visualization of Unicode bidirectional marks Itai Berli
2017-07-01 10:36 ` Eli Zaretskii
2017-07-01 11:48 ` Itai Berli
2017-07-01 12:16   ` Eli Zaretskii [this message]
2017-07-01 12:36 ` Itai Berli
2017-07-01 12:51   ` Eli Zaretskii
2021-12-01  4:55 ` Lars Ingebrigtsen
2021-12-01  7:48   ` Eli Zaretskii
2021-12-01 15:51     ` bug#27544: [External] : " Drew Adams
2021-12-01 15:53     ` Lars Ingebrigtsen
2021-12-01 17:12       ` Eli Zaretskii
2021-12-01 17:36         ` Lars Ingebrigtsen
2021-12-01 17:53           ` Eli Zaretskii
2021-12-02  9:04             ` Juri Linkov
2021-12-15 18:14               ` Filipp Gunbin

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=83o9t4pd1o.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=27544@debbugs.gnu.org \
    --cc=itai.berli@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).