From @YaleVM.YCC.YALE.EDU:LOJBAN@CUVMB.BITNET  Sat Feb 12 09:59:07 1994
Received: from ELI.CS.YALE.EDU by NEBULA.SYSTEMSZ.CS.YALE.EDU via SMTP; Sat, 12 Feb 1994 15:00:35 -0500
Received: from YALEVM.YCC.YALE.EDU by eli.CS.YALE.EDU via SMTP; Sat, 12 Feb 1994 15:00:30 -0500
Message-Id: <199402122000.AA02787@eli.CS.YALE.EDU>
Received: from CUVMB.CC.COLUMBIA.EDU by YaleVM.YCC.Yale.Edu (IBM VM SMTP V2R2)    with BSMTP id 6751; Sat, 12 Feb 94 14:58:41 EST
Received: from CUVMB.COLUMBIA.EDU by CUVMB.CC.COLUMBIA.EDU (Mailer R2.07) with  BSMTP id 8938; Sat, 12 Feb 94 14:59:30 EDT
Date:         Sat, 12 Feb 1994 14:59:07 EST
Reply-To: Jorge Llambias <jorge@PHYAST.PITT.EDU>
Sender: Lojban list <LOJBAN%CUVMB.bitnet@YaleVM.YCC.YALE.EDU>
From: Jorge Llambias <jorge@PHYAST.PITT.EDU>
Subject:      Re: [Re] Place structures with co
To:         lojban@cuvmb.cc.columbia.edu
Status: RO
X-Status: 

ui coi fi'i doi veion
i mutce temci le nu do vi zasti pu
i a'u do ma puca'o gasnu

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

> It has been noted before that we mustn't take the parses too literally :-)

Touche'  :)

[good explanation of the status quo deleted]

> i.e. the purpose of co is to make the sumti places of the modifier more
> easily accessible.

These places are also easily accesible using {be}:

brode co broda be da

But the trailing places of brode are lost once the {co} appears.

My point is that it's not correct to say that {co} gives the possibility
to use modificand-modifier word order. It seems more logical to me that
the places of a tanru should always be those of the tertanru, without
this exception.

Jorge