From fracture@cs6668125-184.austin.rr.com Wed Feb 26 15:46:10 2003 Received: with ECARTIS (v1.0.0; list lojban-list); Wed, 26 Feb 2003 15:46:10 -0800 (PST) Received: from cs6668125-184.austin.rr.com ([66.68.125.184] ident=root) by digitalkingdom.org with esmtp (Exim 4.12) id 18oBFV-0004O7-00 for lojban-list@lojban.org; Wed, 26 Feb 2003 15:46:05 -0800 Received: from cs6668125-184.austin.rr.com (asdf@localhost [127.0.0.1]) by cs6668125-184.austin.rr.com (8.12.3/8.12.3) with ESMTP id h1QNqiZB022585 for ; Wed, 26 Feb 2003 17:52:44 -0600 (CST) (envelope-from fracture@cs6668125-184.austin.rr.com) Received: (from fracture@localhost) by cs6668125-184.austin.rr.com (8.12.3/8.12.3/Submit) id h1QNqiwL022584 for lojban-list@lojban.org; Wed, 26 Feb 2003 17:52:44 -0600 (CST) Date: Wed, 26 Feb 2003 17:52:44 -0600 From: Jordan DeLong To: lojban-list@lojban.org Subject: [lojban] Re: Nick will be with you shortly Message-ID: <20030226235244.GA22288@allusion.net> References: <20030226030837.GA18158@allusion.net> <20030226194836.GJ17377@digitalkingdom.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mYCpIKhGyMATD0i+" Content-Disposition: inline In-Reply-To: <20030226194836.GJ17377@digitalkingdom.org> User-Agent: Mutt/1.5.1i X-archive-position: 4175 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 --mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 26, 2003 at 11:48:36AM -0800, Robin Lee Powell wrote: > On Tue, Feb 25, 2003 at 09:08:38PM -0600, Jordan DeLong wrote: > > On Tue, Feb 25, 2003 at 09:49:30PM -0500, Craig wrote: > > > >is too baroque to be acceptable (or that there is no problem with > > > >{loi} to be solved), but I'll just have to lump it. > > >=20 > > > I don't know what the problem with {loi} is, and when the BPFK > > > appears and we all get a veto I will veto any change to {loi} that > > > doesn't demonstrate that there is one. In fact, I plan to veto any > > > change to the language that doesn't solve a problem which is either > > > obvious or explained in the proposal; the BPFK should not act > > > lightly. But, if the jposkepre have been able to put much effort > > > into {loi}, then I'm sure there is a problem and that their proposal > > > will explain it to us. > >=20 > > There is no problem with loi. >=20 > Since more than one competent lojbanist disagrees with you, you are > prima facia wrong, even if all your points are correct. Huh? This is a fallacy (argumentum ad populum). Statements have a particular truth value regardless of what we believe about them. But anyway. If there is a problem with loi (rather, with lojbanmasses), it certainly hasn't been demonstrated yet. --=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 --mYCpIKhGyMATD0i+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE+XVNLDrrilS51AZ8RAo10AJ4oH3Y6Ex5yHdS+LrGvFO3YTNWHzACfe7La CqbwoOkYcE/+MfPO0GaK4ps= =7CVQ -----END PGP SIGNATURE----- --mYCpIKhGyMATD0i+--