From fracture@cs6668125-184.austin.rr.com Wed Jul 30 15:07:17 2003
Received: with ECARTIS (v1.0.0; list lojban-list); Wed, 30 Jul 2003 15:07:17 -0700 (PDT)
Received: from cs24349-133.austin.rr.com
	([24.243.49.133] helo=cs6668125-184.austin.rr.com ident=root)
	by digitalkingdom.org with esmtp (Exim 4.12)
	id 19hz67-000779-00
	for lojban-list@lojban.org; Wed, 30 Jul 2003 15:07:08 -0700
Received: from cs6668125-184.austin.rr.com (asdf@localhost [127.0.0.1])
	by cs6668125-184.austin.rr.com (8.12.8p1/8.12.8) with ESMTP id h6UMHEtG043801
	for <lojban-list@lojban.org>; Wed, 30 Jul 2003 17:17:14 -0500 (CDT)
	(envelope-from fracture@cs6668125-184.austin.rr.com)
Received: (from fracture@localhost)
	by cs6668125-184.austin.rr.com (8.12.8p1/8.12.8/Submit) id h6UMHEOX043800
	for lojban-list@lojban.org; Wed, 30 Jul 2003 17:17:14 -0500 (CDT)
Date: Wed, 30 Jul 2003 17:17:13 -0500
From: Jordan DeLong <fracture@allusion.net>
To: lojban-list@lojban.org
Subject: [lojban] Re: le du
Message-ID: <20030730221713.GA43767@allusion.net>
References: <20030730123834.80685.qmail@web41902.mail.yahoo.com> <00d501c356e5$4c6e4360$3f3d0751@oemcomputer>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q"
Content-Disposition: inline
In-Reply-To: <00d501c356e5$4c6e4360$3f3d0751@oemcomputer>
User-Agent: Mutt/1.4.1i
X-archive-position: 6007
X-ecartis-version: Ecartis v1.0.0
Sender: lojban-list-bounce@lojban.org
Errors-to: lojban-list-bounce@lojban.org
X-original-sender: fracture@allusion.net
Precedence: bulk
Reply-to: lojban-list@lojban.org
X-list: lojban-list


--ikeVEW9yuYc//A+q
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 30, 2003 at 07:41:30PM +0100, And Rosta wrote:
> xorxes:
> > --- Jordan DeLong <fracture@allusion.net> wrote:
> > > On Tue, Jul 29, 2003 at 11:11:25AM -0700, Jorge Llambmas wrote:
> > > > Is there any brivla with even less content that will do instead?
> > > [...]
> > >=20
> > > Yes.  {co'e}.
> >=20
> > But {co'e} is heavily context dependant. {ro da du de} is always
> > true. {ro da co'e de} may be true or false, depending on context:
> > before we can evaluate it we need to work out what co'e stands for=20
> > in this case and then see whether it holds for everything.=20
>=20
> The original question can be reposed as: What fills the gap in the
> following pattern?
>=20
> go'a-series  : ra-series
> broda-series : ke'a-series
> bu'a-series  : da-series
> co'e         : ???????

=2E...  zo'e, of course ...

> > Another possibility we have not yet considered is {le bu'a}.
>=20
> We have not considered the more general question of what bu'a
> means when not quantified in the prenex. Personally, I would
> see it as the brivla equivalent of ce'u, in which case it wouldn't
> be equivalent to {le du}.

Seems to me that it should probably default to su'obu'a, like da
defaults to su'oda.

--=20
Jordan DeLong - fracture@allusion.net
lu zo'o loi censa bakni cu terzba le zaltapla poi xagrai li'u
                                     sei la mark. tuen. cusku

--ikeVEW9yuYc//A+q
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE/KEPpDrrilS51AZ8RAlr/AJ4o/bAFIPY79Ua/h9Ngj+DKc1IfEgCcCJOf
9kaJGtY0B802Jeht1EYS7pE=
=Zcny
-----END PGP SIGNATURE-----

--ikeVEW9yuYc//A+q--