From LOJBAN%CUVMB.BITNET@UBVM.CC.BUFFALO.EDU Thu Nov 30 15:28:16 1995 Received: from VMS.DC.LSOFT.COM (vms.dc.lsoft.com [205.186.43.2]) by locke.ccil.org (8.6.9/8.6.10) with ESMTP id PAA08097 for ; Thu, 30 Nov 1995 15:28:13 -0500 Message-Id: <199511302028.PAA08097@locke.ccil.org> Received: from PEACH.EASE.LSOFT.COM (205.186.43.4) by VMS.DC.LSOFT.COM (LSMTP for OpenVMS v1.0a) with SMTP id 722FE18D ; Thu, 30 Nov 1995 15:17:38 -0500 Date: Thu, 30 Nov 1995 19:14:09 +0000 Reply-To: ucleaar Sender: Lojban list From: ucleaar Subject: Re: Special meaning of V-initial X-To: lojban@cuvmb.cc.columbia.edu To: John Cowan Status: OR Chris: > >And: > >> > I agree. I would also prefer that V-initial not be singled out like > >> > that. > >> Do we know why it is? A relic of some ancient Brownian predilection? > Jorge: > >Something to do with the Loglan imperative, I think. > I also remember seeing an argument related to relative phrases something > like this: in a {poi broda} phrase it's likely that you'll want x1 to be > {ke'a} and to explicitly state x2. If V-initial weren't special, and if > syntax within a poi were consistent with sentence-level syntax, then you'd > have to explicitly use {fe} or {zo'e} or {ke'a} to get to the x2. Missing out {kea} is not something I'd wish to encourage, but be that as it may, this rationale extends beyond relative phrases, since in general it is possible to elide x1 but not have to mark by {fe} the x2, so long as x2 remains post selbri. > BTW should I stick this along with the historical explanation in the FAQ? > I do think I've heard the question before. Yes. --- And