Received: from mail-gg0-f189.google.com ([209.85.161.189]:37797) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1T7UOa-0004Tx-Bk; Fri, 31 Aug 2012 09:48:40 -0700 Received: by ggcs5 with SMTP id s5sf2770992ggc.16 for ; Fri, 31 Aug 2012 09:48:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-beenthere:date:from:to:message-id:in-reply-to:references:subject :mime-version: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=AR4GalVYCRGiCev6vW6J2jVSA0WE/AvlzQqvw02U8sY=; b=qJofT29tpjqUKbQZ0QLXQyPTVSzQKzHY1/gyvFDwNbPHdiF5/J7nc+AoayflqQmoqb bBSgD2M1efLWMYD75Mvmm1LHRuOJkBsb2oSVzTTN0jj+mtQBfiIM5cO/lkgo2q+5jaHH g+VKdsgSJDWVv8P4oc5jMB33x0W+SIzL/mqgbI9ZvI8ZYzZWH80ek7Tsza5E0rEbfxSH MH8jym/0JQws9gwbAtNfs0zjVxY1opjmQjZHrtTxWw0C0HqXunquexLtY0UZVKJx+Avv brgW51KcBqCXRZi9OuVOJYUllDUD33At5TeowytvEqRS/F8+cGvJDILSab5K/+kNOj48 x8sg== Received: by 10.52.37.74 with SMTP id w10mr1602314vdj.8.1346431709551; Fri, 31 Aug 2012 09:48:29 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.220.147.138 with SMTP id l10ls3376224vcv.7.gmail; Fri, 31 Aug 2012 09:48:29 -0700 (PDT) Received: by 10.52.23.145 with SMTP id m17mr1601831vdf.0.1346431709066; Fri, 31 Aug 2012 09:48:29 -0700 (PDT) Date: Fri, 31 Aug 2012 09:48:28 -0700 (PDT) From: la gleki To: lojban@googlegroups.com Message-Id: <55e70b7d-e835-423b-8557-8ae88b88a4e2@googlegroups.com> In-Reply-To: <502A9A2C.20606@gmail.com> References: <502A81EB.2000005@gmail.com> <502A9A2C.20606@gmail.com> Subject: Re: [lojban] Revising mu'ei and CAhA once again. Possible worlds. MIME-Version: 1.0 X-Original-Sender: gleki.is.my.name@gmail.com X-Original-Authentication-Results: ls.google.com; spf=pass (google.com: domain of gleki.is.my.name@gmail.com designates internal as permitted sender) smtp.mail=gleki.is.my.name@gmail.com; dkim=pass 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="----=_Part_1254_18808761.1346431708448" X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / ------=_Part_1254_18808761.1346431708448 Content-Type: text/plain; charset=ISO-8859-1 On Tuesday, August 14, 2012 10:34:20 PM UTC+4, And Rosta wrote: > > Gleki Arxokuna, On 14/08/2012 18:23: > > I wish Robin started using {mu'ei} again but > > it's really when usage decides. May be human brain just doesn't want > > to deal with A-level at such level of precision. May be {ka'e/na > > ka'e/ka'ei/bia'i} or even {bi'ai} is enough. > > The evidence of natural language is to the contrary. The > could/probably/would contrast is the some/most/all contrast. > > > The use of {da'i} is interesting. For a logical language it's > > completely deplorable, because there's a complete mismatch between > > the lexicosyntactic form and the logical form, and no explicit rule > > about how to get from one to the other -- it works by mere stipulated > > magic. But it caught on among those impatient to be actively using > > the language, and nicely illustrated the fundamental incompatibility > > between a loglang and a language governed by the principle of "let > > usage decide". > > > > May be we can determine the most common usage of {da'i} and redefine > > it from the point of view of A/M/F-level scheme? May be we should > > perform analysis of Lojban corpus and tatoeba sentences? > > {da'i} is in UI, isn't it? So it doesn't have the right grammatical > properties. > It is in UI. If I "discovered" A and F levels why not bind {da'i} to A-level i.e. make it a synonym of {ka'e} but without changing the grammar and selmaho and {da'inai} would be "equal" to {ca'a}. > The purest ways to proceed would be either (1) to define things so that > they're logical and regular, regardless of usage, i.e. basically just > implement all xorxes's proposals, or (2) to treat the language as an > inchoate natlang, a la Lojbab, and abduce grammar out of usage as > linguistics of natlangs does. > > --And. > -- You received this message because you are subscribed to the Google Groups "lojban" group. To view this discussion on the web visit https://groups.google.com/d/msg/lojban/-/OETsc6alUy8J. 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. ------=_Part_1254_18808761.1346431708448 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tuesday, August 14, 2012 10:34:20 PM UTC+4, And Rosta wrote:Gleki Arxokuna, On 14/08/2012 18:2= 3:
> I wish Robin started using {mu'ei} again but
> it's really when usage decides. May be human brain just doesn't wa= nt
> to deal with A-level at such level of precision. May be {ka'e/na
> ka'e/ka'ei/bia'i} or even {bi'ai} is enough.

The evidence of natural language is to the contrary. The could/probably= /would contrast is the some/most/all contrast.

> The use of {da'i} is interesting. For a logical language it's
> completely deplorable, because there's a complete mismatch between
> the lexicosyntactic form and the logical form, and no explicit rul= e
> about how to get from one to the other -- it works by mere stipula= ted
> magic. But it caught on among those impatient to be actively using
> the language, and nicely illustrated the fundamental incompatibili= ty
> between a loglang and a language governed by the principle of "let
> usage decide".
>
> May be we can determine the most common usage of {da'i} and redefi= ne
> it from the point of view of A/M/F-level scheme? May be we should
> perform analysis of Lojban corpus and tatoeba sentences?

{da'i} is in UI, isn't it? So it doesn't have the right grammatical pro= perties.
It is in UI. If I "discovered" A and F levels why not= bind {da'i} to A-level i.e. make it a synonym of {ka'e} but without changi= ng the grammar and selmaho
and {da'inai} would be "equal" to {ca'= a}.


The purest ways to proceed would be either (1) to define things so that= they're logical and regular, regardless of usage, i.e. basically just impl= ement all xorxes's proposals, or (2) to treat the language as an inchoate n= atlang, a la Lojbab, and abduce grammar out of usage as linguistics of natl= angs does.

--And.

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To view this discussion on the web visit https://groups.google.com/d/msg/lojban/-/OE= Tsc6alUy8J.
=20 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.
------=_Part_1254_18808761.1346431708448--