Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]XIM, kinput2 & Tk
- To: tlug@example.com
- Subject: XIM, kinput2 & Tk
- From: jwb@example.com (Jim Breen)
- Date: Fri, 6 Apr 2001 10:45:09 +0900 (JST)
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <Poi4fC.A.Xs.n-Rz6@example.com>
- Resent-Sender: tlug-request@example.com
G'day, Here is a question I have just posted on comp.lang.tcl. Perhaps someone in TLUG can throw some light on it. I have walked into a brick wall trying to get TK to engage the common Japanese "kinput2" IM. The IM works fine with other apps; I have "tk useinputmethods 1" at the front of the script, but none of the usual ways of engaging it (Ctrl + \, Shift + space) do anything. This is with RH6.2 (E). I have been discussing it with Keiichi Takahashi, who has it working OK with RH7.0(J). As far as we can tell the environments are the same apart from local and language settings. Can it be that the TK code is looking at the language/locale variables, and only activating the IM if the setting is non-English? This may sound like straw-clutching, but the standard RH xinput script only starts kinput2 if "ja_JP" appears within "LANG", so anything is possible. Needless to say, the documentation for I18N is totally silent on this. Jim -- Jim Breen [jwb@example.com http://www.csse.monash.edu.au/~jwb/] Visiting Professor, Institute for the Study of Languages and Cultures of Asia and Africa, Tokyo University of Foreign Studies, Japan +81 3 5974 3880 [$B%8%`!&%V%j!<%s(B@$BEl5~30Bg(B]
- Follow-Ups:
- Re: XIM, kinput2 & Tk
- From: Christopher SEKIYA <wileyc@example.com>
- XIM, kinput2 & Tk
- From: "Stephen J. Turnbull" <turnbull@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: MySQL
- Next by Date: Re: XIM, kinput2 & Tk
- Prev by thread: Re: funny bug
- Next by thread: Re: XIM, kinput2 & Tk
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links