-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, Jul 16, 2005 at 12:44:05PM +0200, Damir Perisa wrote: > Le Friday 15 July 2005 14:41, Scott a ??crit??:
> | I think that kinput2 and canna are fairly common still. ??If scim only > | works without configuration in the GTK apps, it's another reason some > | of we older geeks still prefer kinput and canna as they require no > | worries about whether it's a KDE or Gnome app. ??:) > > the configuration for scim to work for x apps (as XIM) is i think the same > as with gcin or other IM's. (you have to export the vars (XMODIFIERS, > LANG_* ...) to make X know that scim is the IM for XIM to be used). for > gtk2 apps, this is not needed. and for qt it will not be needed after we > update to qt4. I actually found that when I tried the scim anthy package it didn't work for me. The other fellows had it work out of the box, but when I started X, after adding the suggested XMODIFIERS lines I would get failed to initialize front end. As work has been very busy, I didn't have time to research it further--I plan to add mention of it to my page in the Arch section, but I'd like to at least get it working for me first. In contrast, building with my tarball as mentioned on my page worked without problem. > | Linux that doesn't have an available package for it. ) ??I realize that > | sounds like boasting, to say they're going to be directed to my page, > | but it's sort of the big fish in small pond thing. ??:) > > your site is very detailed and a good help for learners. once we have the > new wiki up (the one cactus is preparing - mediawiki based) then i hope > you will contribute hopefully some lines to the i18n pages i plan to > construct. I would be glad to do so. > > has nobody tried to make a package out of kinput2? I tried awhile back, but not being a coder or even a good scripter, it didn't build. This was some time ago. As mentioned on my page, two programming friends actually created my vanilla Japanese tarball. > know (pacman -Qo) what every file came part of. this is not so, if you > install from source directly. that's why i would prefer to have kinput2 > or other apps like this as packages and not installed from source. i > probably will never use kinput2 regularly, but maintaining it would be no > problem, if there is a need and the project is still under dev/maintaince > and not running out-of-date (as you probably mentioned the so called > "technical" problems. the biggest one would be if it would not compile > with newest gcc or something like that) This I don't know. I don't think it's been upgraded for quite awhile--scim-anthy are coming into favor with newcomers, but, especially as my need for Japanese is less than it used to be, the only time I ever got the scim-anthy combo working was on Berry Linux, a Japanese distro with it reinstalled. However, that package of mine has been around for a few years and still works on everything (that is, every distro where I've tried it.) - -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Kendra: I call it Mr. Pointy. Buffy: You named your stake? Kendra: Yes. Buffy: Remind me to get you a stuffed animal. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC2RYV+lTVdes0Z9YRAurPAKC+3fyTSLt2ozc9Ur6wMxAG/TblnwCfSUCP l8WOlpg39iY5iWoCNeSFds0= =tbvl -----END PGP SIGNATURE----- _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
