From lojban-out@lojban.org Mon Dec 02 08:18:28 2002 Return-Path: X-Sender: lojban-out@lojban.org X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_2_3_0); 2 Dec 2002 16:18:28 -0000 Received: (qmail 82126 invoked from network); 2 Dec 2002 16:18:28 -0000 Received: from unknown (66.218.66.216) by m10.grp.scd.yahoo.com with QMQP; 2 Dec 2002 16:18:28 -0000 Received: from unknown (HELO digitalkingdom.org) (204.152.186.175) by mta1.grp.scd.yahoo.com with SMTP; 2 Dec 2002 16:18:28 -0000 Received: from lojban-out by digitalkingdom.org with local (Exim 4.05) id 18ItH9-0008C7-00 for lojban@yahoogroups.com; Mon, 02 Dec 2002 08:18:27 -0800 Received: from digitalkingdom.org ([204.152.186.175] helo=chain) by digitalkingdom.org with esmtp (Exim 4.05) id 18ItH4-0008Bq-00; Mon, 02 Dec 2002 08:18:22 -0800 Received: with ECARTIS (v1.0.0; list lojban-list); Mon, 02 Dec 2002 08:18:21 -0800 (PST) Received: from cs6668125-184.austin.rr.com ([66.68.125.184] ident=root) by digitalkingdom.org with esmtp (Exim 4.05) id 18ItGz-0008Bh-00 for lojban-list@lojban.org; Mon, 02 Dec 2002 08:18:17 -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 gB2GO8G9037382 for ; Mon, 2 Dec 2002 10:24:08 -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 gB2GO7qI037381 for lojban-list@lojban.org; Mon, 2 Dec 2002 10:24:07 -0600 (CST) Date: Mon, 2 Dec 2002 10:24:07 -0600 To: lojban-list@lojban.org Subject: [lojban] Re: Why we should cancel the vote or all vote NO (was RE: Official Statement- LLG Board approves new baseline policy Message-ID: <20021202162407.GA37047@allusion.net> References: <5.1.0.14.0.20021201175116.031410b0@pop.east.cox.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="x+6KMIRAuhnl3hBn" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i X-archive-position: 2879 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+6KMIRAuhnl3hBn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 02, 2002 at 11:04:47AM -0000, And Rosta wrote: > Lojbab: [...] > > > > At the very most, if noone has ever ever ever used lau, I might acc= ept > > > > turning lau into say xu'e, and releasing lau. But for a one syllabl= e > > > > cmavo to be necessary for something Zipfeanly, it has to be somethi= ng > > > > so urgent and obvious, I'd have thought the heavens would be clamor= ing > > > > for it by now. In my book, xa'o and mu'ei are the only ones even cl= ose > > > > to this (with mu'ei endangered by sumtcita ka'e); and they're not t= hat > > > > close > > > > > >You will see from what I say above that I favour deassigning monosylla= bics > > >that are not heavily used, and reassigning them only after a LOT of > > >skilled usage > > > > The whole area of alphabets and lerfu is tied up with Mex. We cannot s= ay > > how useful Mex will be, but it certainly will not be useful if we make = it > > more difficult to use >=20 > Avoiding making mex harder to use is not a good reason for not making the > rest of the language easier to use. I am proposing (and I think Jordan is > too) that mex and other stuff that has never seen substantial usage be > made more longwinded so that future generations of fluent lojbanists can > decide where shortwindedness can most efficaciously be applied. I don't support touching any of mex (unless lau/tei is considered mex). I support And's *idea* here, but not the exact method by which he wants to implement it. I think it is sufficent to add new assignments for one or two 0-usage monosyllabic cmavo without revoking their own assignemnts, and to refrain from using monosyllabic xVV space. [...] > > >and instead > > >simply say that the mini-dictionary fixes the meaning of the cmavo it > > >lists. A proper syntactic parser should not have the mahoste built > > >in to it, but should instead take input from a community-maintained > > >mahoste that can be updated with cmavo not listed in the mini-dictiona= ry > > > > Then write one >=20 > I have (collaboratively) written one for cmavo that are not in the > official mahoste. It is on the wiki. It is easily adaptable (with > about 1 minute's work) by anyone writing a parser to take input from > a mahoste. Erm. Lojbab was suggesting you write that parser. ;P --=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 --x+6KMIRAuhnl3hBn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE964knDrrilS51AZ8RAr0sAJ9iCbuGCoqAdl7dGYZAsCfuLfI1mQCgpb9F 65iKhz/aEjpJNdbvbVzp4U8= =frQs -----END PGP SIGNATURE----- --x+6KMIRAuhnl3hBn--