Return-Path: <@FINHUTC.HUT.FI:LOJBAN@CUVMB.BITNET>
Received: from FINHUTC.hut.fi by xiron.pc.helsinki.fi  with smtp
	(Linux Smail3.1.28.1 #14) id m0pVQW2-0000PdC; Sat, 12 Feb 94 22:00 EET
Message-Id: <m0pVQW2-0000PdC@xiron.pc.helsinki.fi>
Received: from FINHUTC.HUT.FI by FINHUTC.hut.fi (IBM VM SMTP V2R2)
   with BSMTP id 5431; Sat, 12 Feb 94 22:00:22 EET
Received: from SEARN.SUNET.SE (NJE origin MAILER@SEARN) by FINHUTC.HUT.FI (LMail V1.1d/1.7f) with BSMTP id 5429; Sat, 12 Feb 1994 22:00:22 +0200
Received: from SEARN.SUNET.SE (NJE origin LISTSERV@SEARN) by SEARN.SUNET.SE
 (LMail V1.2a/1.8a) with BSMTP id 2146; Sat, 12 Feb 1994 20:59:33 +0100
Date:         Sat, 12 Feb 1994 14:59:07 EST
Reply-To:     Jorge Llambias <jorge@PHYAST.PITT.EDU>
Sender:       Lojban list <LOJBAN%CUVMB.bitnet@FINHUTC.hut.fi>
From:         Jorge Llambias <jorge@PHYAST.PITT.EDU>
Subject:      Re: Place structures with {co}
X-To:         lojban@cuvmb.cc.columbia.edu
To:           Veijo Vilva <veion@XIRON.PC.HELSINKI.FI>
Content-Length: 848
Lines: 31

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