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 VAA00618 for ; Tue, 28 Nov 1995 21:49:36 -0500 Message-Id: <199511290249.VAA00618@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 5C6F1FF9 ; Tue, 28 Nov 1995 21:38:47 -0500 Date: Tue, 28 Nov 1995 19:33:50 -0700 Reply-To: Chris Bogart Sender: Lojban list From: Chris Bogart Subject: Special meaning of V-initial X-To: lojban@cuvmb.bitnet To: John Cowan Status: OR X-From-Space-Date: Tue Nov 28 21:49:45 1995 X-From-Space-Address: LOJBAN%CUVMB.BITNET@UBVM.CC.BUFFALO.EDU >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. For example, now we say {le nanmu poi prami mi} and the x1 of {prami} is elided, and we can assume it's {ke'a}, which here equals {le nanmu}. Without this special treatment of V-initial, we'd have to say {le nanmu poi prami ke'a mi} or {le nanmu poi ke'a prami mi} or {le nanmu poi ke'a mi prami}. So: it saves 2 syllables in what's arguably the most common way of using {poi}. May or may not be worth it, depending on how you value word order flexibility vs. brevity. BTW should I stick this along with the historical explanation in the FAQ? I do think I've heard the question before. ____ Chris Bogart \ / http://www.quetzal.com Boulder, CO \/ cbogart@quetzal.com