ok, this explains some of the odd behaviour...
had no idea about that :|

the thing that bugs me is that i had this input working already, in
kde, on arch - but after a reboot it didn't work anymore.
now, it deems to me that the time it was working, i was using
'startx', after i put kdm into the daemons it failed...
i need to investigate that further, it just came to my mind - maybe
there is some difference with the .xinitrc between gdm and kdm wich
causes trouble later?
ok, too late today - you hear from me tomorrow

~~~~manveru

2006/2/26, Damir Perisa <[EMAIL PROTECTED]>:
> thank you Scott for giving this nice explaination. everything very
> nice explained! i want to extend it by this:
>
> Saturday 25 February 2006 04:54, Scott wrote:
>  | You might have to set QT_IM_MODULE as well, since you're in KDE.
>  | (I don't use KDE, so I'm not sure about that. )
>
> the problem with kde is that it uses qt and our qt3 does not contain
> the qt-im-module so the only way kde works with scim/skim is by using
> XIM and not qt. most kde-apps unfortunately don't know how to use XIM
> but try qt-im-module instead that is missing.
>
> some time ago, we tried to patch qt3 to include qt-im-module but it
> gave other problems... for now unfortunately there is no good
> solution for scim+kde in arch. the easiest would be of course when we
> have kde compiled against qt4 because qt4 provides qt-im-module
> built-in. now we have faced xorg7, we may think on working on qt4...
>
> i would suggest you to try to avoid kde apps, if you need scim input.
>
> hope this is fixed in some near future...
>
> greetings,
> Damir
>
> --
> Mark's Dental-Chair Discovery:
>         Dentists are incapable of asking questions that require a
>         simple yes or no answer.
>
>
> _______________________________________________
> arch mailing list
> [email protected]
> http://www.archlinux.org/mailman/listinfo/arch
>
>
>
>
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to