From lojban-out@lojban.org Thu May 13 16:20:11 2004 Return-Path: X-Sender: lojban-out@lojban.org X-Apparently-To: lojban@yahoogroups.com Received: (qmail 63545 invoked from network); 13 May 2004 23:20:10 -0000 Received: from unknown (66.218.66.172) by m22.grp.scd.yahoo.com with QMQP; 13 May 2004 23:20:10 -0000 Received: from unknown (HELO chain.digitalkingdom.org) (64.81.49.134) by mta4.grp.scd.yahoo.com with SMTP; 13 May 2004 23:20:10 -0000 Received: from lojban-out by chain.digitalkingdom.org with local (Exim 4.32) id 1BOPUm-0000JJ-Oi for lojban@yahoogroups.com; Thu, 13 May 2004 16:20:08 -0700 Received: from dsl081-049-134.sfo1.dsl.speakeasy.net ([64.81.49.134] helo=chain.digitalkingdom.org) by chain.digitalkingdom.org with esmtp (Exim 4.32) id 1BOPU8-0000IV-Ju; Thu, 13 May 2004 16:19:28 -0700 Received: with ECARTIS (v1.0.0; list lojban-list); Thu, 13 May 2004 16:19:25 -0700 (PDT) Received: from [195.167.170.152] (helo=bowl.fysh.org ident=mail) by chain.digitalkingdom.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.32) id 1BOPTx-0000IE-VQ for lojban-list@lojban.org; Thu, 13 May 2004 16:19:19 -0700 Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian)) id 1BOPTp-0007LG-00; Fri, 14 May 2004 00:19:09 +0100 Date: Fri, 14 May 2004 00:19:08 +0100 Message-ID: <20040513231908.GL16333@fysh.org> References: <20040513213804.GG16333@fysh.org> <20040513214744.GA4461@digitalkingdom.org> <20040513222637.GI16333@fysh.org> <20040513224341.GF4461@digitalkingdom.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040513224341.GF4461@digitalkingdom.org> User-Agent: Mutt/1.3.28i X-archive-position: 7821 X-ecartis-version: Ecartis v1.0.0 Sender: lojban-list-bounce@lojban.org Errors-to: lojban-list-bounce@lojban.org X-original-sender: zefram@fysh.org X-list: lojban-list To: lojban@yahoogroups.com X-eGroups-Remote-IP: 64.81.49.134 X-eGroups-From: Zefram From: Zefram Reply-To: zefram@fysh.org Subject: [lojban] Re: erasure words X-Yahoo-Group-Post: member; u=116389790 X-Yahoo-Profile: lojban_out X-Yahoo-Message-Num: 22284 Robin Lee Powell wrote: >I completely understand that. There is no valid way to handle something >when all I know is that it erases *something*. Yes. That's half of my point. The other half is that there *are* valid ways to handle something when all you know is that it *doesn't* erase anything. I'm not sure quite how much one can do in this case; it's not a lot, but you can at least, in theory, allow the erroneous word to be erased. In the example "le broda cei'au si brode", if one knows for certain that "cei'au" is not an eraser then one can confidently preprocess to "le broda brode". > Despite all of this discussion, the language is *not* actually >open for change. My understanding is that the language may be added to in the future, albeit at a slow pace, and that this is what the extended cmavo space is for. Am I right here? I, too, wish to preserve the stability of Lojban. For clarity: I mentally divide language discussions here into a handful of categories: * working out what the current language definition really means (e.g., the "zo fu bu" debate) * artifacts of the current implementations that we might want to define differently (e.g., "zei" at the beginning of text) * possible future additions to the language (any proposed new cmavo) * tricky parts of the language that we could have done differently ("zoi si") The borders between these categories are fuzzy in some cases, and some conversations have aspects of more than one category. My understanding is that only the last of these four categories is really problematic, because it is only in that category that the language definition is being contradicted so as to invalidate existing usages. Anything in the third category can't become official in the near future, but doesn't actually cause a problem. Is this a good view of things? I'm personally very clear on the distinction between what a particular parser implements and the official language. These parsers are, among other uses, testbeds for experimental variations of the language. Something I might have missed so far: is there a taboo here against discussing possible language changes due to fear of rehashing the (extensive) language design work? Perhaps I have been insufficiently conservative, for which I apologise. >1. I'm already doing it, so I'm not sure what the point is, although I >would *love* someone to look over my PEG grammar. I'd like to. I've never seen PEG before. >2. I honestly don't think that you understand how hard a problem Lojban >grammar is to implement. Fair enough. It's certainly going to be a challenge. We'll see how it turns out. -zefram