From: Eli Zaretskii <eliz@gnu.org>
To: Kenichi Handa <handa@m17n.org>
Cc: list-general@mohsen.1.banan.byname.net, emacs-devel@gnu.org
Subject: Re: bidi and shaping problems in describe-input-method
Date: Mon, 12 Mar 2012 19:42:41 +0200 [thread overview]
Message-ID: <8362e9yaum.fsf@gnu.org> (raw)
In-Reply-To: <tl7boo2ntvk.fsf@m17n.org>
> From: Kenichi Handa <handa@m17n.org>
> Cc: list-general@mohsen.1.banan.byname.net, emacs-devel@gnu.org
> Date: Mon, 12 Mar 2012 16:47:11 +0900
>
> In article <8362eczr73.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
>
> > Yes. But surrounding each `lower' and `upper' key labels in the
> > layout with LRE..PDF inserts even more bidirectional control
> > characters than just inserting LRM. By contrast, using LRO..PDF
> > around the whole row of keys inserts just 2 such characters, so if it
> > were not for the need to reorder the individual key labels, LRO..PDF
> > would be a better alternative. I mentioned it because it does exactly
> > what you originally asked for: it effectively disables
> > bidi-display-reordering inside the embedded text, while still leaving
> > the rest of the buffer reordered as usual.
>
> I mixed up with LRE and LRO, sorry. Anyway, if LRO..PDF
> works, it is surely better than many LRMs. I've just
> installed a proper change including the magic of
> compose-string. Please try the latest code.
It works fine for me, thanks.
However, using LRO..PDF means that no label on a key can use a string
that needs to be reordered. That's because the LRO overrides the
bidirectional properties of all the following characters to be strong
L. If we can live with this limitation, I agree that this is better.
But I think you said earlier that such a restriction is more than we
can bear.
next prev parent reply other threads:[~2012-03-12 17:42 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 22:17 bidi and shaping problems in describe-input-method Mohsen BANAN
2012-03-07 4:05 ` Eli Zaretskii
2012-03-07 18:49 ` Eli Zaretskii
2012-03-07 21:32 ` Mohsen BANAN
2012-03-08 15:30 ` Kenichi Handa
2012-03-08 18:24 ` Eli Zaretskii
2012-03-08 23:48 ` Kenichi Handa
2012-03-09 8:11 ` Eli Zaretskii
2012-03-09 14:03 ` Kenichi Handa
2012-03-09 16:12 ` Eli Zaretskii
2012-03-10 2:55 ` Kenichi Handa
2012-03-10 10:27 ` Eli Zaretskii
2012-03-12 7:47 ` Kenichi Handa
2012-03-12 17:42 ` Eli Zaretskii [this message]
2012-03-13 0:58 ` Kenichi Handa
2012-03-13 3:58 ` Eli Zaretskii
2012-03-22 4:26 ` Kenichi Handa
2012-03-22 17:23 ` Eli Zaretskii
2012-03-23 1:41 ` Kenichi Handa
2012-03-23 10:12 ` Eli Zaretskii
2012-03-22 21:59 ` Mohsen BANAN
2012-03-13 5:46 ` Mohsen BANAN
2012-03-09 8:17 ` Eli Zaretskii
2012-03-08 18:30 ` Eli Zaretskii
2012-03-08 18:53 ` Eli Zaretskii
2012-03-08 23:27 ` Kenichi Handa
2012-03-08 23:19 ` Kenichi Handa
2012-03-09 8:15 ` Eli Zaretskii
2012-03-09 9:01 ` Juanma Barranquero
2012-03-09 9:45 ` Eli Zaretskii
2012-03-09 10:02 ` Eli Zaretskii
2012-03-09 14:11 ` Kenichi Handa
2012-03-09 11:19 ` Juanma Barranquero
2012-03-09 11:41 ` Eli Zaretskii
2012-03-09 14:56 ` Juanma Barranquero
2012-03-09 13:54 ` Kenichi Handa
2012-03-09 16:15 ` Eli Zaretskii
2012-03-08 4:30 ` Miles Bader
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=8362e9yaum.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=list-general@mohsen.1.banan.byname.net \
/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).