From: Kenichi Handa <handa@m17n.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: list-general@mohsen.1.banan.byname.net, emacs-devel@gnu.org
Subject: Re: bidi and shaping problems in describe-input-method
Date: Fri, 09 Mar 2012 08:48:35 +0900 [thread overview]
Message-ID: <877gyuwt64.fsf@m17n.org> (raw)
In-Reply-To: <83ipif0x46.fsf@gnu.org> (message from Eli Zaretskii on Thu, 08 Mar 2012 20:24:25 +0200)
In article <83ipif0x46.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> > just setting bidi-paragraph-direction to 'left-to-right is
> > not enough, because keyboard cells in a row are still
> > re-ordered.
> Right. I didn't notice it because I don't read Arabic.
That's re-ordering happens for Hebrew input method too. :-p
> > For this, the easiest fix is to set bidi-display-reordering to nil.
> > But, then we can't use actual Arabic and Hebrew words in the
> > docstrings of those input methods. What we want is to display bidi
> > reordering only for the keyboard layout part. Eli, don't you have
> > any good idea?
> Revision 107535 is the best I can do. I'll let Mohsen judge if it's
> good enough.
If possible, I'd like to avoid inserting LRM
unconditionally. Is it possible to have this kind of
function?
(defun quail-help-require-LRM (char)
(or (eq (get-char-code-property char 'bidi-class) 'L)
...))
Then, we can use it in quail-insert-kbd-layout as below:
(if (quail-help-require-LRM (if (stringp lower) (aref lower 0) lower))
(insert #x200e))
(insert lower)
(if (quail-help-require-LRM (if (stringp upper) (aref upper 0) upper))
(insert #x200e))
(insert upper)
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2012-03-08 23:48 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 [this message]
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
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=877gyuwt64.fsf@m17n.org \
--to=handa@m17n.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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).