On 7/17/06, Jan Willem Stumpel <[EMAIL PROTECTED]> wrote:
>> Two reasons:
>> 1 - the compose sequences. [..]
>> 2 - xim always works. [..]
> I see. For 1, I've implemented X11's equivalent compose
> mechanism in uim-xim, so it should work as if it doesn't exist
> :).
Yes; uim-xim apparently uses the actual X compose mechanism (if
that is the right term), including the user's ~/.XCompose file. It
seems SCIM has it own internal version of the Compose file. So
with SCIM, the user's customisations do not work (for instance
things I like to have, such as Compose .- -> …, Compose /\ -> ∧,
Compose \/ -> ∨). But they work with uim.
Right.
> Also I as noted in previous mail, please test uim's Latin IM
> with uim immodule [..]
The 'Latin' IM can indeed do some things which Mozilla cannot do
by itself, like ŭ. But it still does not offer all the
possibilities of the full X Compose file; only Latin combinations,
e.g. no accented Greek letters (such as these nice things with
three accents, like ᾇ). IMHO it would be a waste to duplicate them
in uim, because they are already a standard feature in X. If you
ask me, the 'Latin' IM can be removed completely.
Yep, Latin IM is still experimental one. But it is easily extensible
as it is just a compose table in a text file, as you can see in
$prefix/share/uim/latin.scm. Also user can modify it in ~/.uim.
Still, I agree with you that using X Compose file depending on working
locale and ~/.XCompose is more consistent in X11 environment.
> For 2, That's true. [..] So, just set GTK_IM_MODULE=uim and
> QT_IM_MODULE=uim environmental variable. And for the rest of
> traditional applications, just run uim-xim at startup of X and
> set [EMAIL PROTECTED] With this setting, you can use uim
> everywhere. It not so complex.
Yes, this is completely true, thanks. Ι had to install uim-qt (not
default in Debian), but then I could indeed use uim 'everywhere',
also with GTK_IM_MODULE=uim and QT_IM_MODULE=uim. But then I had
the problem with Compose in Mozilla.
See below.
So now we have three choices:
xim -> may crash Mozilla and X when used in URL field
(because of the automatic 'history' drop-down
box?).
xim --async -> crashes Tcl/tk apps with input fields (until
version 8.4.14?).
uim -> no complete compose mechanism in Mozilla (not even
with uim/Latin). I think this is pretty serious
because many people use Mozilla/Thunderbird as
mail clients. Mail is often very international..
4) uim -> implement X's equivalent compose mechanism in uim's
gtk+ immodule and Qt immodule. It is fairly easy since
we already have it in uim-xim. And I just tested to port this
in uim's gtk+ immodule, it works pretty well.
We have a release plan of uim-1.2.0 in this month, and this feature can
be put into it. If so you will be able to use uim all the environment and
all the X's compose input with it. What do you think?
The easiest, apparently, is to wait for Tcl 8.4.14. But for a
fundamental solution, I would say that xim handling in Mozilla
(or libX11?) should be fixed. Something that works across the
whole system is always to be preferred. That way, users do not get
surprises. This is just a non-programmer's opinion of course..
IMHO, XIM protocol is badly designed, and no one seems to fix it.
Cheers,
--
Etsushi Kato
[EMAIL PROTECTED]
