From lojban+bncCML0xpmUARDEi4ftBBoEkJoSVw@googlegroups.com Sun Apr 10 07:59:39 2011 Received: from mail-ww0-f61.google.com ([74.125.82.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1Q8w6s-0007Nv-Dx; Sun, 10 Apr 2011 07:59:38 -0700 Received: by wwb13 with SMTP id 13sf5265425wwb.16 for ; Sun, 10 Apr 2011 07:59:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:x-beenthere:received-spf:mime-version:date :message-id:subject:from:to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type; bh=DWRD0w/hh6lwRtrIrn3BE/4jAqm2/yqcA/MgwJ65H4k=; b=xUfjc/2MKMXtgD8lNJR4NwP+pVb6ZV5Kiey2P+2q8CSZMzgxwaYfai8/534XGrx18i 7H154DkQkwulkOBp5jCgqDCoWc3U+Fc+lpyoMFaGQOOXl+Z31rZq7m5BW1GFK7nqcxkR PE7J43kUcyuokFcdP/izXrCzJRWCy5ktSkqUg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:date:message-id:subject:from :to:x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:x-google-group-id:list-post :list-help:list-archive:sender:list-subscribe:list-unsubscribe :content-type; b=WhWyQOMKoPs9ropwPhuWSe8azd+M7x/W0pcgOYhhMy4aQoffJy1i3iujjApnUnvZji pio8aCNv1cA7i5u7ZWACgF5KZQO1FA+GjuFlpe/cAwJ3YOLJcvZMOE05D75U8N+HcrEb DlOfjA69q49ARaPuVdMDtJLDarJmyQ5NJA8sM= Received: by 10.216.239.135 with SMTP id c7mr524576wer.1.1302447556701; Sun, 10 Apr 2011 07:59:16 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.216.85.204 with SMTP id u54ls916247wee.0.p; Sun, 10 Apr 2011 07:59:15 -0700 (PDT) Received: by 10.216.65.201 with SMTP id f51mr106851wed.14.1302447555682; Sun, 10 Apr 2011 07:59:15 -0700 (PDT) Received: by 10.216.65.201 with SMTP id f51mr106850wed.14.1302447555658; Sun, 10 Apr 2011 07:59:15 -0700 (PDT) Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by gmr-mx.google.com with ESMTPS id h6si609397wes.11.2011.04.10.07.59.15 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 10 Apr 2011 07:59:15 -0700 (PDT) Received-SPF: pass (google.com: domain of blindbravado@gmail.com designates 74.125.82.42 as permitted sender) client-ip=74.125.82.42; Received: by mail-ww0-f42.google.com with SMTP id 4so2112020wwk.5 for ; Sun, 10 Apr 2011 07:59:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.48.197 with SMTP id v47mr1671045web.82.1302447555522; Sun, 10 Apr 2011 07:59:15 -0700 (PDT) Received: by 10.216.244.10 with HTTP; Sun, 10 Apr 2011 07:59:15 -0700 (PDT) Date: Sun, 10 Apr 2011 10:59:15 -0400 Message-ID: Subject: [lojban] Regularization From: Ian Johnson To: lojban@googlegroups.com X-Original-Sender: blindbravado@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of blindbravado@gmail.com designates 74.125.82.42 as permitted sender) smtp.mail=blindbravado@gmail.com; dkim=pass (test mode) header.i=@gmail.com Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=001485f6d9bae2b0b504a091b3f6 --001485f6d9bae2b0b504a091b3f6 Content-Type: text/plain; charset=ISO-8859-1 On IRC we were observing that common usage of {va'o} is not really consistent with its definition as a BAI associated with {vanbi}. Instead, it winds up being used like a nonlogical "if", that is one with causation implied in some way. We then went into some ideas about how one might correct this to make things regular again--redefine va'o, use another gismu to tie to va'o, bring in a new cmavo to mean what va'o is supposed to mean, etc. And then I realized that this is "regularization"--taking a regular language that has evolved with usage slightly, but not a whole lot, and attempting to take the new, evolved language and make it regular again. Is there a policy or something on this subject? That is, is it official that Lojban is free to go as it pleases? mu'o mi'e .latros. -- You received this message because you are subscribed to the Google Groups "lojban" group. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en. --001485f6d9bae2b0b504a091b3f6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On IRC we were observing that common usage of {va'o} is not really cons= istent with its definition as a BAI associated with {vanbi}. Instead, it wi= nds up being used like a nonlogical "if", that is one with causat= ion implied in some way. We then went into some ideas about how one might c= orrect this to make things regular again--redefine va'o, use another gi= smu to tie to va'o, bring in a new cmavo to mean what va'o is suppo= sed to mean, etc.

And then I realized that this is "regularization"--taking a r= egular language that has evolved with usage slightly, but not a whole lot, = and attempting to take the new, evolved language and make it regular again.= Is there a policy or something on this subject? That is, is it official th= at Lojban is free to go as it pleases?

mu'o mi'e .latros.

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com.
For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.
--001485f6d9bae2b0b504a091b3f6--