Received: from mail-pa0-f61.google.com ([209.85.220.61]:33631) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1TJRHB-0002Lv-DV; Wed, 03 Oct 2012 08:54:27 -0700 Received: by padfa11 with SMTP id fa11sf5690429pad.16 for ; Wed, 03 Oct 2012 08:54:15 -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: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=GbNZ74451cHwxiDS+yaoFUSphRpw8zyX3eiO8nQB9TM=; b=gI9sEEwLjeGdLt1/ADMe6qz07dzYwikXgF2oSg0cKDMj6D1c32iWsgsyM4aFJJPErS fiPtgYioeapRwwSNg2N6F8LhvuDBuTr0ixEF6ihPjXCRdzpkjXJzsGMaXYdzXOxqNZQu ynIshiYGOMJA9HWLqYaSnrCPEjy53aXtQ+pbA+IXQmxmyxLIoIN/CuwrNrA/WZAX6CWg 4arIyb1J7pkgPWNhdhgoK5qH+5NM9a8wn3ftMt1w60hJwQP3edyJJvpTmxzu/NzF/eO6 zkylRipwYuiT3b9x6lkvz/ef3PRNsHw36ql5ti0GubCeinpmxfHWHimqO+M5wA3gYW3F m27A== Received: by 10.52.92.207 with SMTP id co15mr384683vdb.9.1349279654662; Wed, 03 Oct 2012 08:54:14 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.52.73.72 with SMTP id j8ls1391691vdv.7.gmail; Wed, 03 Oct 2012 08:54:14 -0700 (PDT) Received: by 10.52.72.197 with SMTP id f5mr372180vdv.17.1349279654071; Wed, 03 Oct 2012 08:54:14 -0700 (PDT) Date: Wed, 3 Oct 2012 08:54:13 -0700 (PDT) From: la gleki To: lojban@googlegroups.com Message-Id: <6468a0a7-357d-4f07-9f02-1da61a75374c@googlegroups.com> In-Reply-To: References: <20121001200454.GV1589@nvg.org> <5069F9D3.804@gmx.de> <58680262-ade6-45c0-bd7b-875fcc55a353@googlegroups.com> Subject: Re: [lojban] What place of nesting bridi {ce'u} refers to? MIME-Version: 1.0 X-Original-Sender: gleki.is.my.name@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_1742_11730283.1349279653489" X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / ------=_Part_1742_11730283.1349279653489 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On Tuesday, October 2, 2012 3:25:47 PM UTC+4, tsani wrote: > > It's funny that you're thinking about this now. xajmi la'a ije ku'i nalgleki ju'o And I only got convinced that {ka=3Dsu'u ce'u} Such understanding would give us a nice abbreviation, though. By {ce'u}-izing gimste I mean that currently each gismu is described in jvs= =20 in 1. glossword 2. keywords 3. definition 4. notes I propose that we add the fifth item 5. ce'u formula. For *zmadu *it will be *3 (1,2)* which means that the abstraction of the first place has the first slot=20 (i.e. ce'u) referring equally to the first and the second slots of the=20 nesting brivla. For *kakne* we have 2(1) i.e. lo se kakne has ce'u inside that refers to lo kakne. If {ka=3Dsu'u ce'u} then we'll have very nice and compact way of expressing= =20 such an important and *useful* concept of natlangs as *infinitives*. I don't like how gua\spi works here cuz as i can see it demands using=20 another gismu every time you change the value of {ce'u}. However, many European Indoeuropean languages allow very intuitive ways of= =20 expressing {ce'u} and {vo'a}. I want to eat an apple =3D I want that I eat an apple [a really awkward= =20 lojban-style sentence] {mi djica lo ka citka??) =3D mi djica lo nu mi/vo'a citka lo plise So {ka=3Dsu'u ce'u} can be of great use after we ce'u-ize gimste. It's reminding me of myself when I "discovered" this phenomenon some months= =20 > ago. > > On 2 October 2012 01:26, la gleki >wr= ote: > >> >> >> On Tuesday, October 2, 2012 12:15:29 AM UTC+4, selpa'i wrote: >>> >>> Am 01.10.2012 22:04, schrieb Arnt Richard Johansen:=20 >>> > On Sun, Sep 30, 2012 at 12:56:59AM -0700, la gleki wrote:=20 >>> >=20 >>> >> These examples are pretty clear. No ambiguity. Now let's open Chapte= r=20 >>> 11.4=20 >>> >> http://dag.github.com/cll/11/**4/ = =20 >>> >>=20 >>> >> 4.9) la djan. cu zmadu la djordj. le ka mi prami ce'u=20 >>> >> John exceeds George in-the property-of (I love X).=20 >>> >>=20 >>> >> This is something very strange.=20 >>> >> Let's imagine that I'm a boy and I meet a girl. I tell her=20 >>> >>=20 >>> >> {do melbi mi lo ka ce'u clani}=20 >>> >>=20 >>> >> Does {ce'u} refer to {do} or {mi}?=20 >>> > Neither. {ce'u} does not refer to anything, and that's sort of the=20 >>> whole point. The clause refers to a =93property=94 of being tall *in th= e=20 >>> abstract*, not that of someone in particular being tall.=20 >>> >>> Yes, but the ce'u place gets filled later by one of the sumti in the=20 >>> parent bridi, and that is what the question was about.=20 >>> >>> > * lo ka mi clani=20 >>> > my height=20 >>> >=20 >>> > * lo ka do clani=20 >>> > your height=20 >>> >=20 >>> > * lo ka lo penbi cu clani=20 >>> > a pen being long=20 >>> >>> 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 "lo= =20 >>> ka mi clani" is to be interpreted as "lo ka mi no'u ce'u clani", or els= e=20 >>> the "ce'u" would end up in a different sumti place and the meaning woul= d=20 >>> change drastically.=20 >>> >>> >>> > I believe that {ce'u no'u ko'a} is wrong. The bridi in which the=20 > property-abstraction appears provides the value for the ce'u-place.=20 > Personally filling a ce'u-place changes the abstraction type from ka to= =20 > du'u. > =20 > >> > * lo ka clani=20 >>> > being long (OR being a dimension of length OR being a standard of= =20 >>> length)=20 >>> >>> Right, but much more than with "ke'a", where this is handled much more= =20 >>> loosely, the convention is that "ce'u" fills the first empty slot.=20 >>> >> >> So if there are no {ce'u} specified we must understand it as the first= =20 >> and only the first slot is filled with omitted {ce'u}. If two or more of= =20 >> the slots of the nested brivla are filled we must specify all of them= =20 >> (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=20 >> into CLL 2.0. >> IMO {ce'u}-izing gimste is also a must.=20 >> >> btw, dont you think that we can use {ce'u} in {mi djica lo ka/nu **ce'u*= *=20 >> 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= =20 > paper that I wrote on the wiki. In general, when an abstraction place=20 > doesn't make sense if you exclude the broda1 from it, then it requires ka= .=20 > > *{.i mi kakne lo nu do citka lo plise} (example from an old mriste thread= =20 > of mine) > is nonsense, which prompts me to believe that kakne2 is a ka or equivalen= t. > > However {.i mi djica lo nu do klama lo zarci} makes perfect sense, even= =20 > though the djica1 is not inside the djica2. > > The gimste being more prescriptive about abstraction types would be great= ,=20 > but good luck finding enough people who support the cause of more rigid= =20 > types. (AFAIK there are at most two or three, myself and probably you=20 > included.) > > .i mi'e la tsani mu'o > --=20 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/lo= jban/-/zeHkZeE6vsUJ. 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_1742_11730283.1349279653489 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable

On Tuesday, October 2, 2012 3:25:47 PM UTC+4, tsani wrote:It's funny that you're thinking about t= his now.

xajmi la'a ije ku'i nalgleki ju'o<= /div>


And I only got convinced that
=

{ka=3Dsu'u ce'u}

Such understa= nding would give us a nice abbreviation, though.

B= y {ce'u}-izing gimste I mean that currently each gismu is described in jvs = in
1. glossword
2. keywords
3. definition
4. notes

I propose that we add the fifth it= em
5. ce'u formula.


For <= i>zmadu it will be
3 (1,2)
which means that = the abstraction of the first place has the first slot (i.e. ce'u) referring= equally to the first and the second slots of the nesting brivla.

For kakne we have
2(1)
i.e. lo s= e kakne has ce'u inside that refers to lo kakne.

<= br>
If {ka=3Dsu'u ce'u} then we'll have very nice and compac= t way of expressing such an important and useful concept of nat= langs as infinitives.
I don't like how gua\spi works here = cuz as i can see it demands using another gismu every time you change the v= alue of {ce'u}.

However, many European Indoeuropea= n languages allow very intuitive ways of expressing {ce'u} and {vo'a}.

I want to eat an apple    =3D I want that I = eat an apple [a really awkward lojban-style sentence]
{mi djica l= o ka citka??)  =3D mi djica lo nu mi/vo'a citka lo plise

So {ka=3Dsu'u ce'u} can be of great use after we= ce'u-ize gimste.


It's reminding me of myself when I "discovered" this= phenomenon some months ago.

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


On Tuesday, October 2, 201= 2 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 propert= y-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 a= bstract*, not that of someone in particular being tall.

Yes, but the ce'u place gets filled later by one of the sumti in the=20
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=20
incorrect. The only way I can see to make these work is to say that "lo= =20
ka mi clani" is to be interpreted as "lo ka mi no'u ce'u clani", or els= e=20
the "ce'u" would end up in a different sumti place and the meaning woul= d=20
change drastically.



I believe tha= t {ce'u no'u ko'a} is wrong. The bridi in which the property-abstraction ap= pears provides the value for the ce'u-place. Personally filling a ce'u-plac= e 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= =20
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  nes= ted brivla are filled we must specify all of them (like in {mi e do simxu l= o 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 {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}?



S= ure, 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 pa= per 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 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 view this discussion on the web visit https://groups.google.com/d/msg/lojban/-/ze= HkZeE6vsUJ.
=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_1742_11730283.1349279653489--