[PATCH] Re: itrans input methods and motion keys

[James Thomas <jimjoe@gmx.net>]

Visuwesh wrote:

> Unfortunately, I'm not quite sure what it does.  I also cannot read
> Malayalam at all so I cannot try to figure it out by trial and error (I
> can at least read Devanagari a bit).  Can you explain what it does?

From the docstring:

> DETERMINISTIC non-nil means the first candidate of translation is
> selected automatically without allowing users to select another
> translation for a key.

So if we've concluded that there is only one valid candidate for
translation of the current input (upto the last key), there would be no
harm is setting it. SIMPLE simply controls one of the keyboard
mechanisms for selecting any such alternative candidates. Someone who
uses Devanagari should probably test it and weigh in, though.

In any case I'd like to throw in a patch for a similar change to
malayalam-mozhi, which I've tested. :)

diff --git a/lisp/leim/quail/indian.el b/lisp/leim/quail/indian.el
index 23204c0cd3..d8cc94c676 100644
--- a/lisp/leim/quail/indian.el
+++ b/lisp/leim/quail/indian.el
@@ -633,7 +633,7 @@ indian-mlm-mozhi-update-translation
 (quail-define-package "malayalam-mozhi" "Malayalam" "MlmMI" t
                       "Malayalam transliteration by Mozhi method."
                       nil nil t nil nil nil t nil
-                      #'indian-mlm-mozhi-update-translation)
+                      #'indian-mlm-mozhi-update-translation nil t)

 (maphash
  (lambda (key val)


--