From lojban-out@lojban.org Tue Apr 29 20:19:01 2003 Return-Path: X-Sender: lojban-out@lojban.org X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_2_6_6); 30 Apr 2003 03:19:00 -0000 Received: (qmail 22748 invoked from network); 30 Apr 2003 03:18:58 -0000 Received: from unknown (66.218.66.218) by m8.grp.scd.yahoo.com with QMQP; 30 Apr 2003 03:18:58 -0000 Received: from unknown (HELO digitalkingdom.org) (204.152.186.175) by mta3.grp.scd.yahoo.com with SMTP; 30 Apr 2003 03:18:58 -0000 Received: from lojban-out by digitalkingdom.org with local (Exim 4.12) id 19Ai7V-0008Kk-00 for lojban@yahoogroups.com; Tue, 29 Apr 2003 20:18:57 -0700 Received: from digitalkingdom.org ([204.152.186.175] helo=chain) by digitalkingdom.org with esmtp (Exim 4.12) id 19Ai7M-0008KG-00; Tue, 29 Apr 2003 20:18:48 -0700 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 ; 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 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 X-list: lojban-list X-eGroups-From: Jordan DeLong From: Jordan DeLong Reply-To: fracture@allusion.net X-Yahoo-Group-Post: member; u=116389790 X-Yahoo-Profile: lojban_out X-Yahoo-Message-Num: 19515 --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 [Attachment content not displayed.] --eAbsdosE1cNLO4uF--