From fracture@cs6668125-184.austin.rr.com Tue Jul 22 19:43:05 2003
Received: with ECARTIS (v1.0.0; list lojban-list); Tue, 22 Jul 2003 19:43:05 -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 19f9ad-00076a-00
	for lojban-list@lojban.org; Tue, 22 Jul 2003 19:42:51 -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 h6N2rCxN070252
	for <lojban-list@lojban.org>; Tue, 22 Jul 2003 21:53:17 -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 h6N2rCMQ070251
	for lojban-list@lojban.org; Tue, 22 Jul 2003 21:53:12 -0500 (CDT)
Date: Tue, 22 Jul 2003 21:53:12 -0500
From: Jordan DeLong <fracture@allusion.net>
To: lojban-list@lojban.org
Subject: [lojban] Re: le du
Message-ID: <20030723025312.GA70208@allusion.net>
References: <20030721180838.U72693-100000@granite.thestonecutters.net> <00df01c34fd9$2cf11340$55350751@oemcomputer> <20030722005320.GA61835@allusion.net> <3F1CE8E8.5050000@bilkent.edu.tr> <002a01c35053$0845b6c0$c2e1fea9@oemcomputer>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK"
Content-Disposition: inline
In-Reply-To: <002a01c35053$0845b6c0$c2e1fea9@oemcomputer>
User-Agent: Mutt/1.4.1i
X-archive-position: 5958
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


--CE+1k2dSO48ffgeK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 22, 2003 at 02:12:26PM +0100, And Rosta wrote:
> Robin.tr:
> > Jordan DeLong wrote:
> > > Of course, in *real* usage, in a case where the referent wasn't
> > > recently mentioned, you'd probably say "zo'e". =20
> > >=20
> > I can't see the point in using zo'e in the first place - if it's=20
> > obvious, leave it blank.
>=20
> A couple of possible reasons:
>=20
> 1) To avoid leaving a blank that might incorrectly be filled by
> implicit ke'a or ce'u (since by default the first blank place gets=20
> filled by ke'a/ce'u).
>=20
> 2) To indicate that the place is not to be filled by implicit zi'o.
>=20
> However, if one goes to the trouble of using explicit zo'e, one
> could equally well go the trouble of choosing a more precise
> sumti.

Only if that other sumti is <=3D 2 syllables.

Otherwise (and more probably) it is more trouble.

--=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

--CE+1k2dSO48ffgeK
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQE/HfiYDrrilS51AZ8RAvZKAJ9F3eSJqgZtmma53+w2aFXX8myUQwCeKWNa
kYADQNnhABOxpfCdA1RJbtk=
=uaOT
-----END PGP SIGNATURE-----

--CE+1k2dSO48ffgeK--