From fracture@cs6668125-184.austin.rr.com Fri Apr 18 15:51:10 2003 Received: with ECARTIS (v1.0.0; list lojban-list); Fri, 18 Apr 2003 15:51:10 -0700 (PDT) Received: from cs6668125-184.austin.rr.com ([66.68.125.184] ident=root) by digitalkingdom.org with esmtp (Exim 4.12) id 196ehE-00026N-00 for lojban-list@lojban.org; Fri, 18 Apr 2003 15:51:04 -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 h3IN1psr007225 for ; Fri, 18 Apr 2003 18:01:56 -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 h3IN1pel007224 for lojban-list@lojban.org; Fri, 18 Apr 2003 18:01:51 -0500 (CDT) Date: Fri, 18 Apr 2003 18:01:51 -0500 From: Jordan DeLong To: lojban-list@lojban.org Subject: [lojban] Re: ynai Message-ID: <20030418230151.GB6836@allusion.net> References: <200304181839.17563.phma@webjockey.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3uo+9/B/ebqu+fSQ" Content-Disposition: inline In-Reply-To: <200304181839.17563.phma@webjockey.net> User-Agent: Mutt/1.5.1i X-archive-position: 4847 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 --3uo+9/B/ebqu+fSQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 18, 2003 at 06:39:16PM -0400, Pierre Abbat wrote: > On Friday 18 April 2003 18:30, Craig wrote: > > >".y" is in selma'o Y, not UI - can it really be negated? > > > > Y shouldn't be negatable. Y is not negatable in actual usage. The Book = does > > not mention Y being negatable. Jbofi'e thinks Y is negatable. Jordan te= lls > > me that the BNF disagrees. Hrm, looks like Y is not negatable. >=20 > What about {mi viska le bloti .ui .y. nai}? The way the bnf is defined that would not parse, unfortunately. The rules for that stuff are informal though; they shouldn't be taken too literally. "Y" really ought to be dealt with at the same level as si/sa/su, as someone mentioned. --=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 --3uo+9/B/ebqu+fSQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE+oIPfDrrilS51AZ8RAokPAJ0VIMg3hdivOk7N4A073kAAzWJgDACgs6Sd BLkHrYEbEZ933LMOs8TBcmM= =t91v -----END PGP SIGNATURE----- --3uo+9/B/ebqu+fSQ--