From lojban-out@lojban.org Sun Dec 01 15:47:43 2002 Return-Path: X-Sender: lojban-out@lojban.org X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_2_3_0); 1 Dec 2002 23:47:43 -0000 Received: (qmail 98076 invoked from network); 1 Dec 2002 23:47:43 -0000 Received: from unknown (66.218.66.217) by m8.grp.scd.yahoo.com with QMQP; 1 Dec 2002 23:47:43 -0000 Received: from unknown (HELO digitalkingdom.org) (204.152.186.175) by mta2.grp.scd.yahoo.com with SMTP; 1 Dec 2002 23:47:43 -0000 Received: from lojban-out by digitalkingdom.org with local (Exim 4.05) id 18IdoN-0000Dn-00 for lojban@yahoogroups.com; Sun, 01 Dec 2002 15:47:43 -0800 Received: from digitalkingdom.org ([204.152.186.175] helo=chain) by digitalkingdom.org with esmtp (Exim 4.05) id 18IdoG-0000DW-00; Sun, 01 Dec 2002 15:47:36 -0800 Received: with ECARTIS (v1.0.0; list lojban-list); Sun, 01 Dec 2002 15:47:35 -0800 (PST) Received: from cs6668125-184.austin.rr.com ([66.68.125.184] ident=root) by digitalkingdom.org with esmtp (Exim 4.05) id 18Ido9-0000DN-00 for lojban-list@lojban.org; Sun, 01 Dec 2002 15:47:29 -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 gB1NrFG9030017 for ; Sun, 1 Dec 2002 17:53:15 -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 gB1NrF7p030016 for lojban-list@lojban.org; Sun, 1 Dec 2002 17:53:15 -0600 (CST) Date: Sun, 1 Dec 2002 17:53:15 -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: <20021201235315.GA29685@allusion.net> References: <6182E3BC-04E0-11D7-B360-003065D4EC72@optushome.com.au> <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="ZGiS0Q5IWpPtfppv" Content-Disposition: inline In-Reply-To: <5.1.0.14.0.20021201175116.031410b0@pop.east.cox.net> User-Agent: Mutt/1.5.1i X-archive-position: 2838 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: 17329 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 01, 2002 at 06:19:26PM -0500, Robert LeChevalier wrote: > At 07:08 PM 12/1/02 +0000, And Rosta wrote: [...] > >These freed up monosyllabic cmavo, along with all other unassigned > >monosyllabic should not be assigned. After enough text has been written > >after this point -- a million words of good-quality writing, say -- the > >corpus should be examined and monosyllabic cmavo assigned to the highest > >frequency forms. (In hindsight, I think no monosyllabic cmavo should > >have been assigned before a million words of quality usage, but it's > >too late now for this.) > >(2) As described on the wiki at "Exploiting the preparser". The idea is > >that once there is enough text to generate high quality statistics, > >new cmavo could be introduced that rewrite as high-frequency cmavo > >sequences. If this were to happen, it would be many years hence, and > >I simply think we should not at this stage constitutionally prohibit > >it from ever occurring. >=20 > The bottom line is that if there is any significant possibility of this=20 > happening in the future, then large numbers of people will refuse to lear= n=20 > Lojban, and we will never GET the usage needed to make Zipfean=20 > decisions. You have NO idea how painful the revisions to TLI Loglan were= ,=20 > over the years, to the TLI community. EVERY change, no matter how minor,= =20 > lost people, and the major changes lost lots of people even when it made= =20 > the language much better. Even today, 15 years after we last used TLI=20 > Loglan in any significant way, Nora more than I (but both of us) still=20 > occasionally pull up a TLI gismu rather than a Lojban gismu for a=20 > concept. Every change you guys make to the CLL baseline with your jboske= =20 > debates (and I won't pretend any longer that your debates haven't=20 > effectively changed the baseline, which is one reason why the new policy)= =20 > makes it that much more likely that I never will speak Lojban as much as = I=20 > did in 1997. If the byfy result is planned to be modified, by any criter= ia=20 > set down like planned Zipfean adjustments, then I won't bother to learn t= he=20 > language. And if I won't, I'm sure a lot of others won't. I'm for a much more moderate approach to allowing Zipfean adjustability, in which no more than the 5 mono-syllabic xVV and perhaps lau (and maybe one or two of its siblings which have exactly 0 usage) are reserved for future shortenings. WRT to (theoretically) assigned cmavo like lau, the existing forms should be left in-tact with new assignments in CVVV space. Done this way, the plan for potential shortenings would neither invalidate existing usage nor invaldiate future usage, and would also not 'render CLL useless'. For example, if "xai" gets assigned to "se kai le ka" in the year 2015, it's not going to damage the ability to use "se kai le ka" (and doubtless many would continue to do so primarily). I strongly do not support the more radical plan for this which And is suggesting (and as he himself says, chances are no one else does). [...] > >As for disyllabics that currently clamour for monosyllabics, I personall= y > >crave them for {du'u} above all, and also {lo'e}, {le'e} and perhaps > >{ke'a} and {ce'u}. >=20 > I don't crave ANY change to any cmavo that I already know and use. I wan= t=20 > the bloody language to stop changing long enough for me and others to=20 > really learn it and BECOME skilled speakers. .iecai Shortings of ke'a and ce'u and du'u etc (and not groups of cmavo containing them) are nothing less than tinkering, as far as I'm concerned. It would never happen without significant deliberate prescription in the future, which is something hopefully to be a unneeded as possible. > >Certainly I find myself using {lo'edu'u} constantly > >and find it extremely irritating -- infuriating, even (given that the > >language design could have reduced it to two, one or even zero syllables= ). >=20 > Whereas "la'edi'u" was a common phrase from the earliest versions of=20 > Lojban, and no one ever suggested that it deserved a shorter form. Nor d= o=20 > I want one now. Actually I believe And has in fact proposed a two syllable cmavo to mean "la'edi'u". I have no idea why that would be useful. [...] > >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-dictionary= . >=20 > Then write one. Well said! > Meanwhile, in how many natural languages are the set of structure words=20 > really an open set? Furthermore, who controls this 'community maintained list'? The answer, of course, is AndR does: about 90% of stuff on the experimental cmavo page on the wiki are forms which no one has or will ever use, that he puts up there whenever he thinks of something. (I believe it was xod who described him as a "cizra cmavo minji"). These types of changes are purely frivolous and mabla, and LLG has a mandate (as far as I can tell) to do all in its power to discourage 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 --ZGiS0Q5IWpPtfppv Content-Type: application/pgp-signature Content-Disposition: inline [Attachment content not displayed.] --ZGiS0Q5IWpPtfppv--