Received: from mail-yx0-f189.google.com ([209.85.213.189]:38839) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1TJ0bp-00042N-GV; Tue, 02 Oct 2012 04:26:03 -0700 Received: by yenq10 with SMTP id q10sf6262873yen.16 for ; Tue, 02 Oct 2012 04:25:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-beenthere:received-spf:mime-version:in-reply-to:references:from :date:message-id:subject: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=rmSAOzBqTJQO89JnIdZJPXflHSE5kedVvclLXEhepzs=; b=sBqOQBvVsgJdyZTvpPE6pEkekADmCxrHGpRgNllEEls+6PuVLo1WeSmfALxXjYexA/ 7UjiScOYh3XhlMJLqaueZGxhHjh+lrbbZw12hqPrRM8tnjHQk8Hr2+5DRkMvlTqoiv5S qDJC5x2LJXolaHgXrdgMt+J66DOjNETAh1DQJ7rLkFv15kdm9Oi5mvMXpe3YKeXpokPn CiyQTguBFo2m7JgxfDt9h94MP45FB/bxc8CyY5lfOZrxSEMxBeWi+OI7wdXAhXtRiOel x3NKtD9x6fiS+UiJ9VarNf5SbeVYeAWX36wSg0mvKOsi2SdLUkUEiYItYNcgcV6ADLMW KkDg== Received: by 10.52.90.129 with SMTP id bw1mr3247805vdb.13.1349177146956; Tue, 02 Oct 2012 04:25:46 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.52.88.174 with SMTP id bh14ls152476vdb.4.gmail; Tue, 02 Oct 2012 04:25:46 -0700 (PDT) Received: by 10.58.58.100 with SMTP id p4mr5304998veq.38.1349177146490; Tue, 02 Oct 2012 04:25:46 -0700 (PDT) Received: by 10.58.58.100 with SMTP id p4mr5304997veq.38.1349177146463; Tue, 02 Oct 2012 04:25:46 -0700 (PDT) Received: from mail-vb0-f49.google.com (mail-vb0-f49.google.com [209.85.212.49]) by gmr-mx.google.com with ESMTPS id r14si38010vdu.1.2012.10.02.04.25.46 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 02 Oct 2012 04:25:46 -0700 (PDT) Received-SPF: pass (google.com: domain of nictytan@gmail.com designates 209.85.212.49 as permitted sender) client-ip=209.85.212.49; Received: by mail-vb0-f49.google.com with SMTP id fo1so7795729vbb.8 for ; Tue, 02 Oct 2012 04:25:46 -0700 (PDT) Received: by 10.52.95.237 with SMTP id dn13mr8151947vdb.83.1349177146304; Tue, 02 Oct 2012 04:25:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.92.48 with HTTP; Tue, 2 Oct 2012 04:25:26 -0700 (PDT) In-Reply-To: <58680262-ade6-45c0-bd7b-875fcc55a353@googlegroups.com> References: <20121001200454.GV1589@nvg.org> <5069F9D3.804@gmx.de> <58680262-ade6-45c0-bd7b-875fcc55a353@googlegroups.com> From: Jacob Errington Date: Tue, 2 Oct 2012 04:25:26 -0700 Message-ID: Subject: Re: [lojban] What place of nesting bridi {ce'u} refers to? To: lojban@googlegroups.com X-Original-Sender: nictytan@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of nictytan@gmail.com designates 209.85.212.49 as permitted sender) smtp.mail=nictytan@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=20cf307d04c08b687a04cb11c8c7 X-Spam-Score: 0.0 (/) X-Spam_score: 0.0 X-Spam_score_int: 0 X-Spam_bar: / --20cf307d04c08b687a04cb11c8c7 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable It's funny that you're thinking about this now. It's reminding me of myself when I "discovered" this phenomenon some months ago. On 2 October 2012 01:26, la gleki wrote: > > > On Tuesday, October 2, 2012 12:15:29 AM UTC+4, selpa'i wrote: >> >> Am 01.10.2012 22:04, schrieb Arnt Richard Johansen: >> > On Sun, Sep 30, 2012 at 12:56:59AM -0700, la gleki wrote: >> > >> >> These examples are pretty clear. No ambiguity. Now let's open Chapter >> 11.4 >> >> http://dag.github.com/cll/11/**4/ >> >> >> >> 4.9) la djan. cu zmadu la djordj. le ka mi prami ce'u >> >> John exceeds George in-the property-of (I love X). >> >> >> >> This is something very strange. >> >> Let's imagine that I'm a boy and I meet a girl. I tell her >> >> >> >> {do melbi mi lo ka ce'u clani} >> >> >> >> Does {ce'u} refer to {do} or {mi}? >> > Neither. {ce'u} does not refer to anything, and that's sort of the >> whole point. The clause refers to a =93property=94 of being tall *in the >> abstract*, not that of someone in particular being tall. >> >> Yes, but the ce'u place gets filled later by one of the sumti in the >> parent bridi, and that is what the question was about. >> >> > * lo ka mi clani >> > my height >> > >> > * lo ka do clani >> > your height >> > >> > * lo ka lo penbi cu clani >> > a pen being long >> >> These are very non-standard, and probably many would call them >> incorrect. The only way I can see to make these work is to say that "lo >> ka mi clani" is to be interpreted as "lo ka mi no'u ce'u clani", or else >> the "ce'u" would end up in a different sumti place and the meaning would >> change drastically. >> >> >> I believe that {ce'u no'u ko'a} is wrong. The bridi in which the property-abstraction appears provides the value for the ce'u-place. Personally filling a ce'u-place changes the abstraction type from ka to du'u. > > * lo ka clani >> > being long (OR being a dimension of length OR being a standard of >> length) >> >> Right, but much more than with "ke'a", where this is handled much more >> loosely, the convention is that "ce'u" fills the first empty slot. >> > > So if there are no {ce'u} specified we must understand it as the first > and only the first slot is filled with omitted {ce'u}. If two or more of > the slots of the nested brivla are filled we must specify all of them > (like in {mi e do simxu lo ka ce'u ce'u prami}), right? > > That would make sense however this is something that must be included int= o > CLL 2.0. > IMO {ce'u}-izing gimste is also a must. > > btw, dont you think that we can use {ce'u} in {mi djica lo ka/nu **ce'u** > citka lo plise} instead of {vo'a/mi}? > > > Sure, but what of wanting things that don't involve djica1 at all? I've thought long and hard about this, as evidenced by the abstractions paper that I wrote on the wiki. In general, when an abstraction place doesn't make sense if you exclude the broda1 from it, then it requires ka. *{.i mi kakne lo nu do citka lo plise} (example from an old mriste thread of mine) is nonsense, which prompts me to believe that kakne2 is a ka or equivalent. However {.i mi djica lo nu do klama lo zarci} makes perfect sense, even though the djica1 is not inside the djica2. The gimste being more prescriptive about abstraction types would be great, but good luck finding enough people who support the cause of more rigid types. (AFAIK there are at most two or three, myself and probably you included.) .i mi'e la tsani mu'o --=20 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. --20cf307d04c08b687a04cb11c8c7 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable It's funny that you're thinking about this now. It's reminding = me of myself when I "discovered" this phenomenon some months ago.=

On 2 October 2012 01:26, la gleki <gleki.is.my.name@gmail.com> wrote:

=
On Tuesday, October 2, 2012 12:15:29 AM UTC+4, selpa'i wrote: Am 01.10.2012 22:04, schrieb Arnt Richard Johansen:
> On Sun, Sep 30, 2012 at 12:56:59AM -0700, la gleki wrote:
>
>> These examples are pretty clear. No ambiguity. Now let's o= pen Chapter 11.4
>> = http://dag.github.com/cll/11/4/
>>
>> 4.9) =A0 la djan. cu zmadu la djordj. le ka mi prami ce'u
>> =A0 =A0 =A0 =A0 John exceeds George in-the property-of (I love= X).
>>
>> This is something very strange.
>> Let's imagine that I'm a boy and I meet a girl. I tell= her
>>
>> {do melbi mi lo ka ce'u clani}
>>
>> Does {ce'u} refer to {do} or {mi}?
> Neither. {ce'u} does not refer to anything, and that's sor= t of the whole point. The clause refers to a =93property=94 of being tall *= in the abstract*, not that of someone in particular being tall.

Yes, but the ce'u place gets filled later by one of the sumti in th= e=20
parent bridi, and that is what the question was about.

> * lo ka mi clani
> =A0 =A0my height
>
> * lo ka do clani
> =A0 =A0your height
>
> * lo ka lo penbi cu clani
> =A0 =A0a pen being long

These are very non-standard, and probably many would call them=20
incorrect. The only way I can see to make these work is to say that &qu= ot;lo=20
ka mi clani" is to be interpreted as "lo ka mi no'u ce= 9;u clani", or else=20
the "ce'u" would end up in a different sumti place and th= e meaning would=20
change drastically.



I believe tha= t {ce'u no'u ko'a} is wrong. The bridi in which the property-ab= straction appears provides the value for the ce'u-place. Personally fil= ling a ce'u-place changes the abstraction type from ka to du'u.
=A0
> * lo ka clani
> =A0 =A0being long (OR being a dimension of length OR being a stand= ard of length)

Right, but much more than with "ke'a", where this is hand= led much more=20
loosely, the convention is that "ce'u" fills the first em= pty slot.

So if there are no {ce'= ;u} =A0specified we must understand it as the first and only the first slot= is filled with omitted {ce'u}. If two or more of the slots of the =A0n= ested brivla are filled we must specify all of them (like in {mi e do simxu= lo ka ce'u ce'u prami}), right?

That would make sense however this is something that mu= st be included into CLL 2.0.
IMO=A0{ce'u}-izing gimste is als= o a must.=A0

btw, dont you think that we can use {= ce'u} in {mi djica lo ka/nu *ce'u* citka lo plise} instead o= f {vo'a/mi}?


Sure, but what of wanting things that don't involve djica1 = at all?
I've thought long and hard about this, as evidenced b= y the abstractions paper that I wrote on the wiki. In general, when an abst= raction place doesn't make sense if you exclude the broda1 from it, the= n it requires ka.=A0

*{.i mi kakne lo nu do citka lo plise} (example from an= old mriste thread of mine)
is nonsense, which prompts me to beli= eve that kakne2 is a ka or equivalent.

However {.i= mi djica lo nu do klama lo zarci} makes perfect sense, even though the dji= ca1 is not inside the djica2.

The gimste being more prescriptive about abstraction ty= pes would be great, but good luck finding enough people who support the cau= se of more rigid types. (AFAIK there are at most two or three, myself and p= robably you included.)

.i mi'e la tsani mu'o

--
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.
--20cf307d04c08b687a04cb11c8c7--