From: Eli Zaretskii <eliz@gnu.org>
To: frederik.fouvry@acrolinx.com
Cc: 55256@debbugs.gnu.org
Subject: bug#55256: Writing direction
Date: Wed, 04 May 2022 11:24:04 +0300 [thread overview]
Message-ID: <834k254sez.fsf@gnu.org> (raw)
In-Reply-To: <8735hpepcq.fsf@acrolinx.com> (bug-gnu-emacs@gnu.org)
> 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.
next prev parent reply other threads:[~2022-05-04 8:24 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 [this message]
2022-05-04 9:02 ` Frederik Fouvry via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834k254sez.fsf@gnu.org \
--to=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.