Received: from mail-la0-f64.google.com ([209.85.215.64]:44667) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XnV8a-0006A6-TR for lojban-list-archive@lojban.org; Sun, 09 Nov 2014 08:15:00 -0800 Received: by mail-la0-f64.google.com with SMTP id pn19sf667786lab.19 for ; Sun, 09 Nov 2014 08:14:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe:content-type; bh=QKya1NgP1yB3OCuUXRo8y7G1tb8+XrmFyC9Bcnauy/4=; b=Sgaz9sph3E1/8UtomFSxH0QTGqDlwqROuJ94KCTwscYVf3a2jSnJH0b7McbL5StPbp kOmS2GL/IqLUI9VDdLn/AEOHl6uqpUNCCB0SDupZuXtv1Id+oy95Aw9gsC0oGr+5BKRq SWKY+jxpkze0jRhiXqLZzLILCdjw8P/n9KMc49caLt41ZBSEaaIuwa88Rub+iCW30r03 gj3n5RyEwR+n9FcM0D3s0PRQgHbgxN5yHgVTizohyf7fwuNNZkK4VBDzGSR8GHyP88Z0 7FkID6HTPDS0DHffpPIh2/amXtNfKiNiA/yD1Vd5EY/xuukmqH46dUTpNKcJEvC9GZah ytIw== X-Received: by 10.152.7.143 with SMTP id j15mr340465laa.0.1415549682016; Sun, 09 Nov 2014 08:14:42 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.152.37.1 with SMTP id u1ls387797laj.29.gmail; Sun, 09 Nov 2014 08:14:40 -0800 (PST) X-Received: by 10.112.151.38 with SMTP id un6mr271693lbb.0.1415549680301; Sun, 09 Nov 2014 08:14:40 -0800 (PST) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com. [2a00:1450:400c:c05::231]) by gmr-mx.google.com with ESMTPS id o2si432828wib.2.2014.11.09.08.14.40 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 09 Nov 2014 08:14:40 -0800 (PST) Received-SPF: pass (google.com: domain of gleki.is.my.name@gmail.com designates 2a00:1450:400c:c05::231 as permitted sender) client-ip=2a00:1450:400c:c05::231; Received: by mail-wi0-x231.google.com with SMTP id ex7so8394565wid.10 for ; Sun, 09 Nov 2014 08:14:40 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.186.207 with SMTP id fm15mr36049368wjc.1.1415549680197; Sun, 09 Nov 2014 08:14:40 -0800 (PST) Received: by 10.194.103.65 with HTTP; Sun, 9 Nov 2014 08:14:39 -0800 (PST) In-Reply-To: References: <20141028022945.GA6097@gonzales> <20141030013306.GO4023@gonzales> <20141104010958.GA27496@gonzales> <20141105035457.GA7768@gonzales> <20141108171532.GB10866@gonzales> Date: Sun, 9 Nov 2014 19:14:39 +0300 Message-ID: Subject: Re: [lojban] Re: tersmu 0.2 From: Gleki Arxokuna To: "lojban@googlegroups.com" X-Original-Sender: gleki.is.my.name@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of gleki.is.my.name@gmail.com designates 2a00:1450:400c:c05::231 as permitted sender) smtp.mail=gleki.is.my.name@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=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: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=047d7beb9102d9a64705076f571a X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --047d7beb9102d9a64705076f571a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2014-11-09 0:07 GMT+03:00 Jorge Llamb=C3=ADas : > > > On Sat, Nov 8, 2014 at 2:15 PM, Martin Bays wrote: > >> * Saturday, 2014-11-08 at 11:40 -0300 - Jorge Llamb=C3=ADas < >> jjllambias@gmail.com>: >> >> > On Sat, Nov 8, 2014 at 7:34 AM, Gleki Arxokuna < >> gleki.is.my.name@gmail.com> >> > wrote: >> > >> > > In {mi nelci ko'a ne semau ko'e} isn't {ne semau} always expanded in= to >> > > {noi ke'a no'a semau ko'e}? >> > >> > It's more like: "noi ke'a zmadu ko'e lo ka no'a xi pa". >> >> Such rules involving {no'a} don't work for most BAI, though, so either >> this is part of the definition of {mau} or (I think preferably) it's >> just an obvious devaguing of {noi ke'a co'e se mau ko'e}. >> > > I agree, yes. I'd say the latter. We can concoct contrived examples where > "ko'a" is the property zmadu3 rather than the zmadu1 that ko'e is being > compared with. > For me it's the only formalisation of {ne semau} that depends on the semantics of {semau} of course. There are rules for each BAI just like e.g. {ca} refers to the clause, {semau} in the main clause refers with its implied zmadu1 to {lo nei} and wth zmadu3 to {lo nu nei}. I don't agree that in {mi nelci ko'a ne semau ko'e} {ko'a} can ever refer to zmadu3. For me its always zmadu1. If we say that it can be anything then BAI become useless because of ambiguity. Why not then say that {mi nelci la betis semau la mark} can mean "I like Betty more than Mark" where it in fact should have only one meaning "I like Betty more than Mark does." ? I dont want introduce any ambiguity to the language since even English doesnt allow for that and since it would lead users to stop using BAI and resorting to bulkier constructs that are not necessarily the same since {la betis cu zmadu la mark lo ka se nelci mi} changes focus compared to the original sentence which is not always desirable and you would say that {fi'o} is just as ambiguous as BAI. I'm also surprised that BPFK didnt formalize it despite discussions in tiki= . --=20 You received this message because you are subscribed to the Google Groups "= lojban" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban. For more options, visit https://groups.google.com/d/optout. --047d7beb9102d9a64705076f571a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


2014-11-09 0:07 GMT+03:00 Jorge Llamb=C3=ADas <jjllambias@gmail.com= >:


On Sat, Nov= 8, 2014 at 2:15 PM, Martin Bays <mbays@sdf.org> wrote:
* Saturday, 2014-11-08 at 11:40 -0300 - Jorge Llamb=C3=ADas <= ;jjllambias@gmail= .com>:

> On Sat, Nov 8, 2014 at 7:34 AM, Gleki Arxokuna <gleki.is.my.name@gmail.com= >
> wrote:
>
> > In {mi nelci ko'a ne semau ko'e} isn't {ne semau} alw= ays expanded into
> > {noi ke'a no'a semau ko'e}?
>
> It's more like: "noi ke'a zmadu ko'e lo ka no'a x= i pa".

Such rules involving {no'a} don't work for most BAI, though,= so either
this is part of the definition of {mau} or (I think preferably) it's just an obvious devaguing of {noi ke'a co'e se mau ko'e}.

I agree= , yes. I'd say the latter. We can concoct contrived examples where &quo= t;ko'a" is the property zmadu3 rather than the zmadu1 that ko'= e is being compared with.

For m= e it's the only formalisation of {ne semau} that depends on the semanti= cs of {semau} of course.

There are rules for each = BAI just like e.g. {ca} refers to the clause, {semau} in the main clause re= fers with its implied zmadu1 to {lo nei} and wth zmadu3 to {lo nu nei}.

I don't agree that in=C2=A0{mi nelci ko'a ne = semau ko'e}
{ko'a} can ever refer to zmadu3. For me its a= lways zmadu1.
If we say that it can be anything then BAI become u= seless because of ambiguity.

Why not then say that=
{mi nelci la betis semau la mark} can mean "I like Betty mo= re than Mark" where it in fact should have only one meaning "I li= ke Betty more than Mark does." ?


I dont want introduce any ambiguity to the language since even English d= oesnt allow for that and since it would lead users to stop using BAI and re= sorting to bulkier constructs that are not necessarily the same since {la b= etis cu zmadu la mark lo ka se nelci mi} changes focus compared to the orig= inal sentence which is not always desirable and you would say that {fi'= o} is just as ambiguous as BAI.

I'm also surpr= ised that BPFK didnt formalize it despite discussions in tiki.

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsub= scribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http:= //groups.google.com/group/lojban.
For more options, visit http= s://groups.google.com/d/optout.
--047d7beb9102d9a64705076f571a--