Re: [m17n-list] Arabic translit IME

[Iori YONEJI]

Hi,

I was impressed with your mim file that enables typing Arabic like as
typing Latin characters.
But I found some unpleasing sequences.
How about minor -updating these points below:

1. ة is always placed on last character of a word, so the sequence
<h.> is more preferable than <.h>. With this change, we can terminate
femininum word with '.'.
2. ح is now <.7>, but how ِis <.h> or <Shift+h> ? This character (and
more characters like ط or خ) is used often but typing <.7> is too
hard, and they are not related with.
3. Mainly, Arabic scripts use ‏ «…» as quotation marks (probably same
as French one). How do you think to add a rule to type them?
http://en.wikipedia.org/wiki/International_variation_in_quotation_marks
4. There are more additional characters in Persian, Darī, and other
languages. For example, گ (g), پ(p), چ(č) and ژ(ž). So I think it's
better to preserve these key(g, p..). As another option, we can assign
them as <k-> to گ (this character is a derivative of ک (k)) and پ as
<p.> and so on.
http://en.wikipedia.org/wiki/Persian_language#Additions

Also I agree with Naoto's opinions.

I attached a file as one of my attempt, but probably this isn't perfect one.
Probably (".2" "ء") is also non-associative relation, and we left some
keys that are on sweet location but not used (like 'c'), so there may
be more needs to careful consideration.

On Fri, Aug 15, 2014 at 1:45 PM, Naoto Takahashi
<address@hidden> wrote:
> On 14 August 2014 23:44, Joop Kiefte <address@hidden> wrote:
>> Here a version now with vowels added.
>
> I have three points to mention.
>
> 1.  "a" is assigned to both ALEF U+0627 and ALEF MAKSURA U+0649.
> Since the definition of ALEF comes first, there is no way to input
> ALEF MAKSURA.
>
> 2. How about adding ".e", ".i", ".u" for FATHATAN U+064B, DAMMATAN
> U+064C, KASRATAN U+064D, respectively?
>
> 3. Users would expect ARABIC COMMA U+060C and ARABIC SEMICOLON U+061B, too.
>
> --
> TAKAHASHI Naoto
>

ar-translit.mim
Description: Binary data