[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



> 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.  [â]

I tried with scim 1.4.4 and uim (1.0.0), m17n upgraded to 1.3.1 (debian
unstable); xorg 7.0. Both of them (scim and uim) behave the same, so it
doesn't seem to be IM engine issue; I use the following map (in
comments, whether it is functional or not)

("b" "[b]")                      ;; yes
((aacute) "[aacute]")            ;; no
((c) "[LATIN_SMALL_LETTER_C]")   ;; yes
((C) "[LATIN_CAPITAL_LETTER_C]") ;; yes
((space) "[SPACE]")              ;; no
((0) "[0]")                      ;; no
((at) "[@]")                     ;; no

Apparently, letters work both as strings and as symbols ("b" and (c)).
For non-letter characters, like @ (I tried both (at) and "@", not at the
same time), neither works.

Apparently, I have a rather different behavior from you; is there a way
you can think of to debug it? I don't mind rebuilding m17n with verbose
debugging output and the like, but such a thing will have to wait a few
days at least (diploma thesis deadline).

> > 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?
Never mind, it was probably package issue. It works after upgrade just
fine.

Regards,

VÃclav