Return-Path: Received: from fiport.funet.fi by xiron.pc.helsinki.fi with smtp (Linux Smail3.1.28.1 #1) id m0rcNOC-00001oC; Thu, 9 Feb 95 03:09 EET Received: from SEARN.SUNET.SE (MAILER@SEARN) by FIPORT.FUNET.FI (PMDF V4.3-13 #2494) id <01HMTSEUVL2O002TNO@FIPORT.FUNET.FI>; Thu, 09 Feb 1995 01:05:21 +0200 (EET) Received: from SEARN.SUNET.SE (NJE origin LISTSERV@SEARN) by SEARN.SUNET.SE (LMail V1.2a/1.8a) with BSMTP id 6439; Thu, 9 Feb 1995 02:05:59 +0100 Date: Thu, 09 Feb 1995 00:25:56 +0000 From: ucleaar Subject: Re: ago24 & replies In-reply-to: (Your message of Tue, 07 Feb 95 12:30:09 PST.) Sender: Lojban list To: Veijo Vilva Reply-to: ucleaar Message-id: <01HMTSEWCP06002TNO@FIPORT.FUNET.FI> X-Envelope-to: veion@XIRON.PC.HELSINKI.FI Content-transfer-encoding: 7BIT X-To: lojban@cuvmb.cc.columbia.edu Content-Length: 2710 Lines: 62 pc: > (I assume that Griecan pragmatics is not the Freudian psychology of lin- > guistics, but that that some possible turns of phrase cannot be > explained to carry some meanings). Could you have another go at saying that? I didn't understand. > Finally, some of the shifts seem just pointless, if not counter- > productive. Some of the above may be of that sort, but the shift > of _lo_broda_ from "all broda" to "some broda," both of which are > redundant for Qda poi constructions and much less efficient in > that role, strikes me as an especially clear case of change for > change sake and without regard to further consequences. What used {lo broda} to mean, or what should it mean if it were not redundant with Q da poi? > Some Notes on Related Threads > 1. I see _xo'u_ is still alive. It is barely alive, being savaged by Jorge's incisive assaults and supported only by my feeble advocacy. > Good! The move to the heqad of the highest prenex is simply the > simplest rule and the one that seems to be involved most often > in natural languages What the **** is a heqad? It looks Arabic, & hasn't made it into the OED (1st ed). > Some of the comments on _xo'u_ seem to be > more appropriate to whatever it is that marks terms in opaque > contexts that can shine through the opacity and be taken to have > external reference. Why shouldn't {xohu} fulfil this function? > 3. The thing And wants for this sibling problem, one from column > A and one from column J is a Cartesian product, for which we once > had a cmavo in JOI, though I cannot now lex it. Can anyone elaborate on this for my benefit? The problem is how to say "mothers of fathers of Jorge and And" (such that J & A are not siblings) without expanding to {lo mamta be lo patfu be J beho beho e lo mamta be lo patfu be A}. > 5. If we are to have lambda variable, we need a slough of them, > since the whole point of lambdacism is that different ones can be > replaced differently. In particular, _lo ka kea mamta kea_ is > not the mother relation but the self-mother relation (one that > rarely holds except for the odd goddess), since _kea_ must be > replaced by the same term in all its occurrences on each applica- > tion. To the severely limited extent that I understand this, it seems to me that (a) you could solve the need for a slough (a slew?) by subscripting, and (b) something other than {keha} should be used, since in relative clauses {keha} appears to behave very differently (though I daren't venture to attempt to say how). --- And