From lojban-out@lojban.org Mon Apr 28 13:37:28 2003
Return-Path: <lojban-out@lojban.org>
X-Sender: lojban-out@lojban.org
X-Apparently-To: lojban@yahoogroups.com
Received: (EGP: mail-8_2_6_6); 28 Apr 2003 20:37:27 -0000
Received: (qmail 77809 invoked from network); 28 Apr 2003 20:26:43 -0000
Received: from unknown (66.218.66.216)
  by m9.grp.scd.yahoo.com with QMQP; 28 Apr 2003 20:26:43 -0000
Received: from unknown (HELO digitalkingdom.org) (204.152.186.175)
  by mta1.grp.scd.yahoo.com with SMTP; 28 Apr 2003 20:26:45 -0000
Received: from lojban-out by digitalkingdom.org with local (Exim 4.12)
  id 19AFD2-00010N-00
  for lojban@yahoogroups.com; Mon, 28 Apr 2003 13:26:44 -0700
Received: from digitalkingdom.org ([204.152.186.175] helo=chain)
  by digitalkingdom.org with esmtp (Exim 4.12)
  id 19AFCq-0000ze-00; Mon, 28 Apr 2003 13:26:32 -0700
Received: with ECARTIS (v1.0.0; list lojban-list); Mon, 28 Apr 2003 13:26:30 -0700 (PDT)
Received: from cs6668125-184.austin.rr.com ([66.68.125.184] ident=root)
  by digitalkingdom.org with esmtp (Exim 4.12)
  id 19AFCX-0000z5-00
  for lojban-list@lojban.org; Mon, 28 Apr 2003 13:26:14 -0700
Received: from cs6668125-184.austin.rr.com (asdf@localhost [127.0.0.1])
  by cs6668125-184.austin.rr.com (8.12.6p2/8.12.3) with ESMTP id h3SKbxsr099975
  for <lojban-list@lojban.org>; Mon, 28 Apr 2003 15:37:59 -0500 (CDT)
  (envelope-from fracture@cs6668125-184.austin.rr.com)
Received: (from fracture@localhost)
  by cs6668125-184.austin.rr.com (8.12.6p2/8.12.3/Submit) id h3SKbxAX099974
  for lojban-list@lojban.org; Mon, 28 Apr 2003 15:37:59 -0500 (CDT)
Date: Mon, 28 Apr 2003 15:37:59 -0500
To: lojban-list@lojban.org
Subject: [lojban] Re: BPFK phpbb
Message-ID: <20030428203758.GA99775@allusion.net>
References: <20030428190602.GZ22216@digitalkingdom.org> <20030428194858.18292.qmail@web20506.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl"
Content-Disposition: inline
In-Reply-To: <20030428194858.18292.qmail@web20506.mail.yahoo.com>
User-Agent: Mutt/1.5.1i
X-archive-position: 4986
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
X-list: lojban-list
X-eGroups-From: Jordan DeLong <fracture@allusion.net>
From: Jordan DeLong <lojban-out@lojban.org>
Reply-To: fracture@allusion.net
X-Yahoo-Group-Post: member; u=116389790
X-Yahoo-Profile: lojban_out

--BXVAT5kNtrzKuDFl
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 28, 2003 at 12:48:58PM -0700, Jorge Llamb=EDas wrote:
>=20
> la camgusmis cusku di'e
>=20
> > My new example of how insane this is is=20
> >=20
> > nai nai nai mi nai nelci nai nai nai
> >=20
> > which would be legal if this change was made.
>=20
> nai nai nai na'e bo mi na'e na'e na'e nelci
>=20
> is currently grammatical (and equally bad style).

But
broda .i nai nai nai na'e bo mi na'e na'e na'e nelci .i broda
is not.

And neither is "mi nai" for that matter. Or how about strange
things like "leka klama keinai cu xamgu".

Anyway, I dunno why the text rule allows a nai at the start, but
you're ignoring camgusmis' point by focusing on that---namely that
if nai is in UI, it can be used *anywhere*, and thus it should be
a word which makes sense to be used anywhere (like "ui").

Other than the problem with making too many sentences legal, I would
complain that it complicates the parse tree of things like {mi
na.enai do klama}. The first "na" is handled at the same level as
the .e and as part of the structure there. But the second "nai"
(if in UI) is handled at a lower level of the parser (where it
allows UIs after any word).

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

--BXVAT5kNtrzKuDFl
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQE+rZEmDrrilS51AZ8RAg8UAJ9kpxxUY2RMpnOppwd1jKzjlN0LDQCgjpGZ
YrbfemNHKowuDM45qROQ9cM=
=Cea2
-----END PGP SIGNATURE-----

--BXVAT5kNtrzKuDFl--

