Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: Kinput2 and Wnn6
- To: tlug@example.com
- Subject: Re: tlug: Kinput2 and Wnn6
- From: Frank Bennett <bennett@example.com>
- Date: 12 Oct 1998 11:20:45 +0900
- Content-Type: text/plain; charset=US-ASCII
- In-Reply-To: "Stephen J. Turnbull"'s message of "Mon, 12 Oct 1998 10:58:17 +0900 (JST)"
- References: <Pine.LNX.3.96LJ1.1b7.981009160844.2090E-100000@example.com><19981009171557O.hhasebe@example.com><m3btnm848p.fsf@example.com><13854.43829.460163.613583@example.com><m3ww696p0p.fsf@example.com><13857.25145.577289.552713@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
"Stephen J. Turnbull" <turnbull@example.com> writes: > >>>>> "Frank" == Frank Bennett <bennett@example.com> writes: > > Frank> Sorry, I should have stated the point more explicitly: why > Frank> should the _server_ behave differently when it is accessed > Frank> via different > > Because the client/server interfaces are different, is what I meant. > The way that kinput2 interacts with Wnn is different from the way that > Emacs does. They use the same API, but their usages differ. Agreed. With any sort of luck, I'll hear something back from Ishisone-san about whether he plans to fix it in the next patchlevel. > Another possibility is that the database is poorly implemented and (a) > the running process's data doesn't get informed about updates from > another process running concurrently or (b - hard to believe it would > be this bad) locking is badly implemented so that one process's > updates get wiped out by the other's update. (b) is not the problem; updates always fail to happen from Kinput2, even when there is only one running process using it, and no Emacs in memory. The data doesn't turn up later, either, so (a) (if I understand the point correctly) isn't the problem either. It looks very much like there are just buttons that Emacs/egg pushes in the API that Kinput2 doesn't (yet) know how to use. Wnn6 works fine with Emacs; there doesn't seem to be cause for raising suspicions about its internal design yet (whatever one might think about the terms under which it is distributed). I'm pretty confident that the problem will get fixed reasonably soon; the Applixware and Wnn6 people could both do quite well out of the university market, but that market will not open to them unless something is done about this limitation in Kinput2 --- as an earlier correspondent indicated in this thread, Applixware-J is frustrating to Japanese users, so Japanese labs (including mine) will hold off purchasing and installing it until the FEP improves, or someone comes along with another package that works better. It's just a matter of time. Cheers, -- -x80 Frank G Bennett, Jr @@ Faculty of Law, Nagoya Univ () email: bennett@example.com Tel: +81[(0)52]789-2239 () WWW: http://rumple.soas.ac.uk/~bennett/ --------------------------------------------------------------- Next Nomikai: 20 November, 19:30 Tengu TokyoEkiMae 03-3275-3691 Next Meeting: 12 December, 12:30 Tokyo Station Yaesu central gate --------------------------------------------------------------- Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp
- References:
- Re: tlug: Kinput2 and Wnn6
- From: Scott Stone <sstone@example.com>
- Re: tlug: Kinput2 and Wnn6
- From: Hiroshi Hasebe <hhasebe@example.com>
- Re: tlug: Kinput2 and Wnn6
- From: Frank Bennett <bennett@example.com>
- Re: tlug: Kinput2 and Wnn6
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Re: tlug: Kinput2 and Wnn6
- From: Frank Bennett <bennett@example.com>
- Re: tlug: Kinput2 and Wnn6
- From: "Stephen J. Turnbull" <turnbull@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: My *beepin* 486 (was Re: tlug: The meeting...)
- Next by Date: Re: tlug: parallel-port IDE
- Prev by thread: Re: tlug: Kinput2 and Wnn6
- Next by thread: Re: tlug: Kinput2 and Wnn6
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links