From @YaleVM.YCC.YALE.EDU:LOJBAN@CUVMB.BITNET  Fri Feb 11 11:42:27 1994
Received: from ELI.CS.YALE.EDU by NEBULA.SYSTEMSZ.CS.YALE.EDU via SMTP; Fri, 11 Feb 1994 16:48:36 -0500
Received: from YALEVM.YCC.YALE.EDU by eli.CS.YALE.EDU via SMTP; Fri, 11 Feb 1994 16:48:03 -0500
Message-Id: <199402112148.AA29978@eli.CS.YALE.EDU>
Received: from CUVMB.CC.COLUMBIA.EDU by YaleVM.YCC.Yale.Edu (IBM VM SMTP V2R2)    with BSMTP id 6462; Fri, 11 Feb 94 16:45:08 EST
Received: from CUVMB.COLUMBIA.EDU by CUVMB.CC.COLUMBIA.EDU (Mailer R2.07) with  BSMTP id 3129; Fri, 11 Feb 94 16:46:46 EDT
Date:         Fri, 11 Feb 1994 16:42:27 EST
Reply-To: jorge@PHYAST.PITT.EDU
Sender: Lojban list <LOJBAN%CUVMB.bitnet@YaleVM.YCC.YALE.EDU>
From: Jorge Llambias <jorge@PHYAST.PITT.EDU>
Subject:      Place structures with {co}
To:         lojban@cuvmb.cc.columbia.edu
Status: RO
X-Status: 

la kolin cusku lu

> ckire do doi xorxes le kecti pinka

li'u
i ue u'i ma kecti pinka
i mi pu cusku le ckire pinka
i mi na'e sanji le nu mi kecti te pinka

> I cannot think of a way of inverting
> broda brode da
> as you are trying to do.
>
> brode co broda da
> expressly means
> broda be da co brode

I guess you mean
broda be da brode

This is not the idea that I get from looking at the BNF,
which has the trailing sumti attaching to the whole bridi,

        brode co broda da

parses as:

        ({brode co broda} {da VAU})

Which suggests to me something different from:

        ({brode co <broda [be da BE'O]>} VAU)

If {brode co broda da} doesn't mean {broda brode da}, then
the claim that {co} is there to permit the modifier to come
after the modificand (is this the right word?), as in some
languages (like Spanish :) is not quite true, because using
it restricts what we can say with that tanru. (A lot of places
become inaccessible, unless used before the selbri.)

So {broda brode} has a different place structure
than {brode co broda}. (If a tanru can be said to have a
place structure.)

I'm not saying it's wrong, just that it's a bit strange.

Jorge