Return-Path: <@FINHUTC.HUT.FI:LOJBAN@CUVMB.BITNET> Received: from FINHUTC.hut.fi by xiron.pc.helsinki.fi with smtp (Linux Smail3.1.28.1 #1) id m0qaoDw-00004xC; Wed, 17 Aug 94 19:52 EET DST Message-Id: Received: from FINHUTC.HUT.FI by FINHUTC.hut.fi (IBM VM SMTP V2R2) with BSMTP id 7068; Wed, 17 Aug 94 19:51:00 EET Received: from SEARN.SUNET.SE (NJE origin MAILER@SEARN) by FINHUTC.HUT.FI (LMail V1.1d/1.7f) with BSMTP id 7065; Wed, 17 Aug 1994 19:50:59 +0200 Received: from SEARN.SUNET.SE (NJE origin LISTSERV@SEARN) by SEARN.SUNET.SE (LMail V1.2a/1.8a) with BSMTP id 2161; Wed, 17 Aug 1994 18:50:00 +0200 Date: Wed, 17 Aug 1994 12:53:29 EDT Reply-To: jorge@PHYAST.PITT.EDU Sender: Lojban list From: Jorge Llambias Subject: Re: xruti X-To: lojban@cuvmb.cc.columbia.edu To: Veijo Vilva Content-Length: 1221 Lines: 37 la lojbab cusku di'e > I would suspect that if "-gau" is causing problems with x2, you may need a new > convention that does not cause x2 patient. I guess you meant that you want a convention that _does_ make x2 the patient. I think this may cause more confusion than anything else. Since the problem is solved using {jai}, I wouldn't make an exception for just a few cases. > Either that, or change "jai" to something that can get a useful rafsi, which > will in turn probably cause some other rafsi changes. It can get a useful rafsi as it is: "jaz" (or "jax"). Of course, something like jal, jar, jam or jan would be even better, but you'd have to take it away from something else. Then we'd have: jazga'i (jai galfi) x1 changes x2 into x3 with event x4 As opposed to: gafygau (galfi gasnu) x1 changes, with event x2, x3 into x4 > Remmebering that -gau and -zu'e (which I presume also has the same problem) > are unique among gismu in being designed to cause raising, I guess one could define: gafygau: gas1 (gas2=gal1) gal2 gal3 x1 is the agent in an event that changes x2 into x3 but this would deviate from the usual way -gau works, and doesn't really offer anything better than jai. Jorge