From fracture@cs6668125-184.austin.rr.com Tue Apr 29 20:18:45 2003
Received: with ECARTIS (v1.0.0; list lojban-list); Tue, 29 Apr 2003 20:18:45 -0700 (PDT)
Received: from cs6668125-184.austin.rr.com ([66.68.125.184] ident=root)
	by digitalkingdom.org with esmtp (Exim 4.12)
	id 19Ai73-0008Jp-00
	for lojban-list@lojban.org; Tue, 29 Apr 2003 20:18:29 -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 h3U3UMsr010848
	for <lojban-list@lojban.org>; Tue, 29 Apr 2003 22:30:22 -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 h3U3UMF9010847
	for lojban-list@lojban.org; Tue, 29 Apr 2003 22:30:22 -0500 (CDT)
Date: Tue, 29 Apr 2003 22:30:22 -0500
From: Jordan DeLong <fracture@allusion.net>
To: lojban-list@lojban.org
Subject: [lojban] Re: BPFK phpbb
Message-ID: <20030430033022.GB10708@allusion.net>
References: <20030429162224.GG20953@digitalkingdom.org> <20030429122726.H59548-100000@granite.thestonecutters.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="eAbsdosE1cNLO4uF"
Content-Disposition: inline
In-Reply-To: <20030429122726.H59548-100000@granite.thestonecutters.net>
User-Agent: Mutt/1.5.1i
X-archive-position: 5039
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


--eAbsdosE1cNLO4uF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 29, 2003 at 12:28:53PM -0400, Invent Yourself wrote:
> On Tue, 29 Apr 2003, Robin Lee Powell wrote:
>=20
> > On Tue, Apr 29, 2003 at 12:14:04PM -0400, Invent Yourself wrote:
> > > On Tue, 29 Apr 2003, Jordan DeLong wrote:
> > > > I think it's been pretty well demonstrated that nai is not a
> > > > word that makes sense to be used anywhere, so I'm done.
> > >
> > > You're dropping the context. Is this a case of the principle that
> > > everything in UI must be able to make sense anywhere?
> >
> > Ummm, duh?
> >
> > That's the whole *point* of UI.
>=20
> But we've already ascertained that at least one UI, namely kau, has
> problems in certain places. Go ahead and stick kau all the places that
> Jorge stuck nai, and see if you can get the same level of meaning he did.

Right; kau shouldn't be in UI.

If someone writes up a proposal allowing kau after KOhA and *only*
after KOhA I will support it.

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

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

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

iD8DBQE+r0NNDrrilS51AZ8RAgiEAJ9f6oKGWp968K6jxKTiua6vJQBa1QCeOUNK
5gRf+H+iSMeZhEOBoX7J0KM=
=Oa+Y
-----END PGP SIGNATURE-----

--eAbsdosE1cNLO4uF--