From: Mohsen BANAN <list-general@mohsen.1.banan.byname.net>
To: emacs-devel@gnu.org
Subject: Re: bidi and shaping problems in describe-input-method
Date: Wed, 07 Mar 2012 13:32:07 -0800 [thread overview]
Message-ID: <yx262eg9jxk.fsf@mohsen.1.banan.byname.net> (raw)
In-Reply-To: 83aa3t9hts.fsf@gnu.org
>>>>> On Wed, 07 Mar 2012 06:05:19 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> From: Mohsen BANAN <list-general@mohsen.1.banan.byname.net>
Mohsen> In the case of 'arabic note how the entire
Mohsen> keyboard is flipped to the right.
Eli> That's easy to fix.
Great! Thanks for having taken care of that.
Mohsen> The second problem is shaping related:
Mohsen>
Mohsen> Inside of a cell on the keyboard layout, when
Mohsen> there are two characters that can be joined, they
Mohsen> are joined -- be default. They should not be.
Eli> How can one know when they should be joined and when not?
I think the simple answer is: always isolated -- never joined.
For Persian and Arabic I am sure that they should
never be joined -- always isolated.
For other shaped languages, it is hard to imagine
an input method designer would ever want them joined.
For non-shaped languages (e.g., latin keyboards)
the insertion of an zero width non-joiner between
lower and upper case is harmless and invisible.
So, the simplest fix (and perhaps
the-right-thing-to-do) is to ALWAYS insert a
(ucs-insert 8204) -- zero width non-joiner --
between the two characters in each and every
keyboard cell.
Thanks,
...Mohsen
next prev parent reply other threads:[~2012-03-07 21:32 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 [this message]
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
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=yx262eg9jxk.fsf@mohsen.1.banan.byname.net \
--to=list-general@mohsen.1.banan.byname.net \
--cc=emacs-devel@gnu.org \
/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).