[m17n-lib:00349] Re: mim syntax: mapping XKB non-ascii to non-ascii

[Kenichi Handa <handa@xxxxxxxx>]

In article <20060419063306.GA3385@xxxxxxxxxxxxx>, VÃclav Åmilauer <eudoxos@xxxxxxxx> writes:

> I tried "acaron" for "Ã", that is what both xev and keysymdef.h say.  The
> whole file is like this:

>  (title "Latin-LOCAL")
>  (map (trans ("b" "BBB") ((dollar) ("$$$")) ((aacute) "AAA") ((nonsense) "nonsense") ))
>  (state (init (trans)))

> The map itself works (tested by b â BB), but neither "dollar" (which is
> perfectly ASCII) neither "aacute" work as expected. Apparently symbol
> existence is not checked beforehand as "nonsense" does not make the mim
> not to be loaded.

Currently, there's no standard in what kind of input-event
symbol an IM-engine (e.g. scim) gives to IM-module
(e.g. m17n-lib's input method).  So, there's no way to know
"nonsense" is an invalid input-event symbol for m17n-lib.
And, as scim gives a input-event symbol `$' (instead of
`dollar') to m17n-lib, there's no way to trigger the rule
 "((dollar) ("$$$"))".

But, `aacute' should work because, as far as I know, scim
handles X Keysym correctly.  So,

> Anyway, I noticed that I have libm17n-0 version 1.2.0 (ubuntu dapper), I
> will try to upgrade to use debian unstable 1.3.1 packages, if that can
> make a difference here. I will get back if that changes anything.

perhaps, it is a bug of 1.2.0 or your version of scim.   At
least, with 1.3.1 of m17n-lib and 1.4 of scim, I confirmed
that it works.

>> Check if you have the command "m17n-db".  If you have it,
>> you should be able to get a list of available mim files by:
>> 
>> % m17n-db -l input-method

> My version returns invalid paths (like /usr/share/unicode.mim instead of
> /usr/share/m17n/unicode.mim), but that might be version / packaging
> issue and certainly is not important for me at the moment.

Hmmm, what is return when m17n-db is called without any
argument?

---
Kenichi Handa
handa@xxxxxxxx