unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Frederik Fouvry via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 55256@debbugs.gnu.org
Subject: bug#55256: Writing direction
Date: Wed, 4 May 2022 11:02:50 +0200	[thread overview]
Message-ID: <CABANGDe+veoX9kkPjTXrgYDF-yTd-FOLRownna2FsEsoEDpcJQ@mail.gmail.com> (raw)
In-Reply-To: <834k254sez.fsf@gnu.org>

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

On Wed, 4 May 2022 at 10:23, Eli Zaretskii <eliz@gnu.org> wrote:

> > Date: Wed, 04 May 2022 09:20:05 +0200
> > From: frederik.fouvry--- via "Bug reports for GNU Emacs,
> >  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> >
> >
> > I forgot to add:
> >
> > The Unicode noncharacters should not cause a change in writing
> > direction, since they are not Arabic characters, but a set of characters
> > for internal use only (no exchange between different parties).
>
> That is not entirely true, because Unicode assigns default Bidi Class
> properties to some unassigned codepoints, and Emacs obeys that.  So an
> unassigned codepoint (which is AFAIU what "noncharacter" stands for in
> your terminology) for which Unicode says that its Bidi Class should
> be, for example, AL, _will_ cause change of text directionality.
>
> If you use those unassigned codepoints for private use, you will have
> to override the default properties by manually modifying the relevant
> Emacs char-tables at run time.
>

That sounds fair enough. I admit that my statement was generalising too
much.

The odd name "noncharacter" is Unicode terminology, not mine (see e.g. Spec
v14, Ch. 2, p.30).
<https://www.facebook.com/Acrolinx-127089923970436/>

[-- Attachment #2: Type: text/html, Size: 3047 bytes --]

  reply	other threads:[~2022-05-04  9:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04  7:06 bug#55256: 27.1; Unicode noncharacters may change writing direction frederik.fouvry--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-04  7:20 ` bug#55256: Writing direction frederik.fouvry--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-04  8:24   ` Eli Zaretskii
2022-05-04  9:02     ` Frederik Fouvry via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-06-02 13:09       ` bug#55256: 27.1; Unicode noncharacters may change writing direction Lars Ingebrigtsen
2022-05-04  8:17 ` 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=CABANGDe+veoX9kkPjTXrgYDF-yTd-FOLRownna2FsEsoEDpcJQ@mail.gmail.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=55256@debbugs.gnu.org \
    --cc=frederik.fouvry@acrolinx.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).