Received: from mail-gg0-f189.google.com ([209.85.161.189]:59893) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1TKjw4-00077W-QO; Sat, 06 Oct 2012 23:02:03 -0700 Received: by mail-gg0-f189.google.com with SMTP id o6sf1915164ggm.16 for ; Sat, 06 Oct 2012 23:01:50 -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=N2HpoM+Y54PnhJz1bYvlzQ7GieYO1KEsZ/6ryiUvCPc=; b=YtNe4PIyU1nAvWi8Z8WetVQf3ASr+nV5Iycnzko2dX59vTRQZiELPI+r7XuPUq0b5u QTv6iRTHLU2MXtAnAp88aAUaNPVgGK7fxL11s08ArLYFGeejhkpVyaHtz4JNgdywSyD1 2YWpIkQ8i/Fik6/AepL/Yh216NWUIWpYvdAu630WBsgik6S0cKboCZFfl/xz03xxrNSs 0kwnuCHk1lX7bgIkANZZTaVTxjoF8AppYBL1atTp5wTSEBFLCeu0P+EfL+UCcRQxMMhA CxHrKicm6b4UQV4wqLPFezCklT0Cs3Fj7xZFMBsI9fGV58OxhKVSocEu5udeW6j4FnTC rfMg== Received: by 10.236.115.33 with SMTP id d21mr1507449yhh.12.1349589710067; Sat, 06 Oct 2012 23:01:50 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.236.92.236 with SMTP id j72ls5678582yhf.1.gmail; Sat, 06 Oct 2012 23:01:49 -0700 (PDT) Received: by 10.236.118.82 with SMTP id k58mr1509024yhh.1.1349589709457; Sat, 06 Oct 2012 23:01:49 -0700 (PDT) Date: Sat, 6 Oct 2012 23:01:47 -0700 (PDT) From: la gleki To: lojban@googlegroups.com Message-Id: In-Reply-To: References: <20121001200454.GV1589@nvg.org> <5069F9D3.804@gmx.de> <58680262-ade6-45c0-bd7b-875fcc55a353@googlegroups.com> <6468a0a7-357d-4f07-9f02-1da61a75374c@googlegroups.com> <506C65FF.2040907@gmx.de> <506D82E4.3080604@gmx.de> <506DE7BF.7040609@gmx.de> <02211ac3-9a31-433e-ba19-8df4c623128e@googlegroups.com> <506EFE60.6060005@gmx.de> <66a49230-9801-41db-91bc-868b24124349@googlegroups.com> <0e843db9-9aec-479a-9178-02ea5d2e0f57@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_105_31082697.1349589707439" X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / ------=_Part_105_31082697.1349589707439 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sunday, October 7, 2012 6:45:40 AM UTC+4, tsani wrote: > > On 6 October 2012 09:33, la gleki >wr= ote: > >> >> >> On Saturday, October 6, 2012 8:21:14 PM UTC+4, tsani wrote: >>> >>> Why is having a {ce'u} in djica *so* important? We've gotten along *jus= t=20 >>> fine* using {zo'e} there, even though it refers to djica1 in a lot of= =20 >>> cases.=20 >> >> >> zo'e doesn't refer to first places of nesting bridi.=20 >> It's equally unnatural to say {mi djica lo nu mi sipna} by repeating {mi= }=20 >> two times. If onlu we had some analogue to {ce'u} or {ri} referring to t= he=20 >> previous sumti even if it's {mi}. >> >> > Indeed, {zo'e} can refer to *anything* (with some exceptions). If it's=20 > clear that it's {mi}, then it's {mi}. Remember, *this has never been a=20 > problem before*. To really solve this problem, we could redefine djica to= =20 > use only ka+ce'u, but that would violently break usage, and leaving us wi= th=20 > {pacna} for old-djica. > I don't want to redefine anything and to limit djica to ka+ce'u structures. mi djica lo nu ro remna ku citka mi djica lo nu/ka ce'u citka ^ ^ that is my proposal. However, {ce'u} or {ka+ce'u} in the second=20 sentence might be replaced with something else (I don't care with what but= =20 it must be a variable, not a constant like {mi}). > > .i mi'e la tsani mu'o > =20 > >> >>> There are some selbri, say kakne, where {zo'e} in the abstraction kakne= 2=20 >>> breaks the meaning in some way, such as {mi kakne lo nu do citka lo pli= se}.=20 >>> IMO selbri that get *weird* when there's no ce'u should have {ka}.=20 >>> >>> Furthermore, nu+ce'u is strange to me, because {ce'u} marks an argument= =20 >>> slot in a function, but {nu}, et al., abstractions are never=20 >>> function-abstractions. As I detail in my analysis of abstractors, there= 're=20 >>> two classes of abstractors, namely function-abstractors and=20 >>> non-function-abstractors. It gets a bit fuzzy eventually, because some= =20 >>> abstractors are function when they contain {ce'u}, but can equally not= =20 >>> contain {ce'u}. {ni} is an example of such an abstractor: >>> >>> {.i mi zmadu do lo ni xendo} vs {.i lo ni mi prami do cu zmadu lo ni do= =20 >>> nelci lo mlatu kei du bu} (du bu is the identity function). >>> >>> The advantage of not allow {ce'u} inside {nu} is that {nu} are as a=20 >>> result completely self-contained entities. {lo nu mi do cinba} forms on= e=20 >>> single object that doesn't depend on the containing bridi.=20 >>> >>> As for {su'u}, it turns out that it's simply a vague abstractor, and=20 >>> that's it. It's a stand-in for any regular abstractor, and its type is= =20 >>> completely context-dependent. Although this has never really happened a= s=20 >>> far as I know, it would, however, be possible to create new types of=20 >>> abstractors by means of su'u2. >>> >>> .i mi'e la tsani mu'o >>> >>> On 5 October 2012 21:47, la gleki wrote: >>> >>>> >>>> >>>> On Friday, October 5, 2012 7:36:18 PM UTC+4, selpa'i wrote: >>>>> >>>>> Am 05.10.2012 16:41, schrieb la gleki:=20 >>>>> >=20 >>>>> >=20 >>>>> > On Thursday, October 4, 2012 11:47:16 PM UTC+4, selpa'i wrote:=20 >>>>> >=20 >>>>> > Am 04.10.2012 17:02, schrieb la gleki:>=20 >>>>> > >=20 >>>>> > >> 1."I want to eat an apple".=20 >>>>> > >>=20 >>>>> > >> The normal way uses an infinitive compound:=20 >>>>> > >>=20 >>>>> > >> ^:i \ji /daw crw \xo plyw=20 >>>>> > >>=20 >>>>> > >> But you can also use an explicit infinitive:=20 >>>>> > >>=20 >>>>> > >> ^:i \ji /daw \vo crw \xo plyw=20 >>>>> > >>=20 >>>>> > >> 2."I want you to eat an apple".=20 >>>>> > >>=20 >>>>> > >> ^:i \ji /gu pli \ju ^vo crw \xo plyw=20 >>>>> > >>=20 >>>>> > >> or=20 >>>>> > >>=20 >>>>> > >> ^:i \ji ^ju /gu pli \crw \xo plyw=20 >>>>> > >>=20 >>>>> > >=20 >>>>> > > But I have a clear feeling that in both sentences the same= =20 >>>>> semantic=20 >>>>> > > prime can be used. And this prime describes "desire".=20 >>>>> > > Lojban can replace {ce'u} with anything. Natlangs can do th= e=20 >>>>> same.=20 >>>>> > > gua\spi can't. {to zoi gy. I don't want to criticize gua\sp= i=20 >>>>> > anymore.=20 >>>>> > > gy. toi}=20 >>>>> >=20 >>>>> > You cannot replace ce'u at all or else it's gone and it's not a= =20 >>>>> > ka-abstraction anymore (or not a well-formed one).=20 >>>>> >=20 >>>>> >=20 >>>>> > True. Still the same brivla can be used. Unlike gua\spi.=20 >>>>> >>>>> >>>>> No, it can not. If you "ce'u-ize" the gimste, for instance by saying= =20 >>>>> that djica2 ba a ka (which is a bad example, but it illustrates the= =20 >>>>> point), then you will not be able to use it for "I want you to broda"= ,=20 >>>>> because that's a different predicate that doesn't involve yourself in= =20 >>>>> the abstraction. >>>> >>>> >>>> Well, I'm not sure if we should ce'u-ize gismu with {nu} abstractions= . >>>> But if do this for {djica} then it would be >>>> 1.{mi djica lo nu ce'u citka} >>>> 2.{mi djica lo nu do citka} >>>> >>>> That's all I want. But gua\spi's /daw/ can't do that. >>>> >>>> We could also say {mi djica lo nu ce'u citka i do na go'i} =3D "I want= to=20 >>>> eat but you don't" (if {go'i} is able to update the value of {ce'u} in= the=20 >>>> previous sentence, of course) >>>> >>>> This is a *strenght* of gua\spi; its predicates are=20 >>>>> semantically much clearer.=20 >>>>> >>>> >>>> Well, well, I don't want someone to stop learning gua\spi because=20 >>>> "gua\spi is a crap. I know, la gleki told me". :) >>>> >>>> >>>>> >>>>> >=20 >>>>> > What natlangs can and=20 >>>>> > can't do has little relevance when discussing Lojbanic topics= =20 >>>>> such as=20 >>>>> > ka-abstractions.=20 >>>>> >=20 >>>>> >=20 >>>>> > Then gua\spi has little relevance too.=20 >>>>> >>>>> What? Gua\spi is not a natlang, and you brought up Gua\spi in the=20 >>>>> first=20 >>>>> place. Gua\spi's entire gimste is ce'u-ized, that's what it looks=20 >>>>> like.=20 >>>>> >>>>> >=20 >>>>> >=20 >>>>> >=20 >>>>> > In Lojban, djica2 is a nu, not a ka. You could say that djica= =20 >>>>> should be=20 >>>>> > polymorphic and allow both nu and ka, but I don't think that's= =20 >>>>> what=20 >>>>> > you're saying, is it? (I don't know *what* you are saying).=20 >>>>> >=20 >>>>> >=20 >>>>> > My only complaint that we have a nice shortcut of saying {du'u=20 >>>>> ce'u}=20 >>>>> > but we don't have one for {nu ce'u}.=20 >>>>> >>>>> But ka is not a shortcut for du'u ce'u... ka is what you get if you= =20 >>>>> have=20 >>>>> a du'u abstraction and add a ce'u to it.=20 >>>>> >>>>> >=20 >>>>> > Why is it a nu? Because you can djica things that don't involve= =20 >>>>> > yourself. (Gua\spi's _daw_ is restricted to desiring to do or b= e=20 >>>>> > something, hence it's always like a Lojban ka. And that's why= =20 >>>>> the=20 >>>>> > second=20 >>>>> > example uses a different predicate.)=20 >>>>> >=20 >>>>> > Again, what is the difference between the Lojban and the gua\sp= i=20 >>>>> > sentence?=20 >>>>> >=20 >>>>> >=20 >>>>> > Hopefully no semantic difference. Looks like Lojban just gives more= =20 >>>>> > freedom in recombining the same words without drawing in extra=20 >>>>> predicates.=20 >>>>> >>>>> Okay, but that wasn't even your original point. And as I tried to=20 >>>>> explain above, you get seperate predicates if you ce'u-ize the gimste= .=20 >>>>> One will be=20 >>>>> >>>>> x1 wants to be/do x2 (ka)=20 >>>>> >>>>> the other will be=20 >>>>> >>>>> x1 wants/wishes/desires that x2 (nu) happen=20 >>>>> >>>>> Is that what you want or not?=20 >>>>> >>>>> >=20 >>>>> >=20 >>>>> > Let's stop arguing and let's ce'u-ize gimste :).=20 >>>>> >=20 >>>>> > How the new ce'u-ized definitions of gismu should look like in ur= =20 >>>>> opinion?=20 >>>>> >>>>> Just look at gua\spi's gimste. It did everything right in that regard= ,=20 >>>>> but you have to remember that gua\spi is not Lojban, and not=20 >>>>> everything=20 >>>>> can be copied 1:1.=20 >>>>> >>>>> mu'o mi'e la selpa'i=20 >>>>> >>>>> --=20 >>>>> pilno zo le xu .i lo dei bangu cu se cmene zo lojbo .e nai zo lejbo= =20 >>>>> >>>>> do=E1=BB=8B m=C3=A8lbi mlen=C3=AC'u=20 >>>>> .i do c=C3=A0tlu ki'u=20 >>>>> ma fe la x=C3=A0mpre =C5=ADu=20 >>>>> .i do t=C3=ACnsa c=C3=A0rmi=20 >>>>> gi'e s=C3=ACrji se t=C3=A0rmi=20 >>>>> .i ta=E1=BB=8B bo pu c=C3=ACtka lo gr=C3=A0na ku=20 >>>>> >>>> --=20 >>>> You received this message because you are subscribed to the Google=20 >>>> Groups "lojban" group. >>>> To view this discussion on the web visit https://groups.google.com/d/*= * >>>> msg/lojban/-/WyFuvnW2QSEJ >>>> . >>>> >>>> To post to this group, send email to loj...@googlegroups.com. >>>> To unsubscribe from this group, send email to lojban+un...@** >>>> googlegroups.com. >>>> >>>> For more options, visit this group at http://groups.google.com/** >>>> group/lojban?hl=3Den . >>>> >>> >>> --=20 >> You received this message because you are subscribed to the Google Group= s=20 >> "lojban" group. >> To view this discussion on the web visit=20 >> https://groups.google.com/d/msg/lojban/-/JzUcrDw0IJAJ. >> >> To post to this group, send email to loj...@googlegroups.com >> . >> To unsubscribe from this group, send email to=20 >> lojban+un...@googlegroups.com . >> For more options, visit this group at=20 >> http://groups.google.com/group/lojban?hl=3Den. >> > > --=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/-/nbErKbv7oj0J. 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_105_31082697.1349589707439 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Sunday, October 7, 2012 6:45:40 AM UTC+4, tsani wrote:On 6 October 2012 09:33, la gleki <gleki.is...@gmail.com> wrote:


On Saturday, October 6, 2012 8:21:14 PM UTC+4, tsani wrote:Why is having a {ce'u} in djica *so* i= mportant? We've gotten along *just fine* using {zo'e} there, even though it= refers to djica1 in a lot of cases. 

zo'e doesn't refer to first places of nesting bri= di. 
It's equally unnatural to say {mi djica lo nu mi sipna}= by repeating {mi} two times. If onlu we had some analogue to {ce'u} or {ri= } referring to the previous sumti even if it's {mi}.


Indeed, {zo'e} can refer to= *anything* (with some exceptions). If it's clear that it's {mi}, then it's= {mi}. Remember, *this has never been a problem before*. To really solve th= is problem, we could redefine djica to use only ka+ce'u, but that would vio= lently break usage, and leaving us with {pacna} for old-djica.
<= /blockquote>

I don't want to redefine anything and to li= mit djica to ka+ce'u structures.
mi djica lo nu ro remna ku citka=
mi djica lo nu/ka ce'u citka

^ ^ that i= s my proposal. However, {ce'u} or {ka+ce'u} in the second sentence might be= replaced with something else (I don't care with what but it must be a vari= able, not a constant like {mi}).

.i mi'e la tsani mu'o
 

There are some selbri, say kakne, where {zo'e} in = the abstraction kakne2 breaks the meaning in some way, such as {mi kakne lo= nu do citka lo plise}. IMO selbri that get *weird* when there's no ce'u sh= ould have {ka}. 

Furthermore, nu+ce'u is strange to me, because {ce'u} m= arks an argument slot in a function, but {nu}, et al., abstractions are nev= er function-abstractions. As I detail in my analysis of abstractors, there'= re two classes of abstractors, namely function-abstractors and non-function= -abstractors. It gets a bit fuzzy eventually, because some abstractors are = function when they contain {ce'u}, but can equally not contain {ce'u}. {ni}= is an example of such an abstractor:

{.i mi zmadu do lo ni xendo} vs {.i lo ni mi prami do c= u zmadu lo ni do nelci lo mlatu kei du bu} (du bu is the identity function)= .

The advantage of not allow {ce'u} inside {nu} is= that {nu} are as a result completely self-contained entities. {lo nu mi do= cinba} forms one single object that doesn't depend on the containing bridi= . 

As for {su'u}, it turns out that it's simply a vague ab= stractor, and that's it. It's a stand-in for any regular abstractor, and it= s type is completely context-dependent. Although this has never really happ= ened as far as I know, it would, however, be possible to create new types o= f abstractors by means of su'u2.

.i mi'e la tsani mu'o

On 5 October 2012 21:47, la gleki <gleki.is...@gmail.com> wrote:


On F= riday, October 5, 2012 7:36:18 PM UTC+4, selpa'i wrote:
Am 05.10.2012 16:41, schrieb la gleki:
>
>
> On Thursday, October 4, 2012 11:47:16 PM UTC+4, selpa'i wrote:
>
>     Am 04.10.2012 17:02, schrieb la gleki:>
>       >
>       >>     1."I want to eat an ap= ple".
>       >>
>       >>     The normal way uses an= infinitive compound:
>       >>
>       >>     ^:i \ji /daw crw \xo p= lyw
>       >>
>       >>     But you can also use a= n explicit infinitive:
>       >>
>       >>     ^:i \ji /daw \vo crw \= xo plyw
>       >>
>       >>     2."I want you to eat a= n apple".
>       >>
>       >>     ^:i \ji /gu pli \ju ^v= o crw \xo plyw
>       >>
>       >>     or
>       >>
>       >>     ^:i \ji ^ju /gu pli \c= rw \xo plyw
>       >>
>       >
>       > But I have a clear feeling that in both = sentences the same semantic
>       > prime can be used. And this prime descri= bes "desire".
>       > Lojban can replace {ce'u} with anything.= Natlangs can do the same.
>       > gua\spi can't. {to zoi gy. I don't want = to criticize gua\spi
>     anymore.
>       > gy. toi}
>
>     You cannot replace ce'u at all or else it's gone and= it's not a
>     ka-abstraction anymore (or not a well-formed one).
>
>
> True. Still the same brivla can be used. Unlike gua\spi.


No, it can not. If you "ce'u-ize" the gimste, for instance by saying=20
that djica2 ba a ka (which is a bad example, but it illustrates the=20
point), then you will not be able to use it for "I want you to broda",= =20
because that's a different predicate that doesn't involve yourself in= =20
the abstraction.

Well, I'm = not sure if we should ce'u-ize gismu with {nu}  abstractions.
But if do this for {djica} then it would be
1.{mi djica lo nu c= e'u citka}
2.{mi djica lo nu do citka}

That's all I want= . But gua\spi's /daw/ can't do that.

We could also= say {mi djica lo nu ce'u citka i do na go'i} =3D "I want to eat but you do= n't" (if {go'i} is able to update the value of {ce'u} in the previous sente= nce, of course)

This is a *str= enght* of gua\spi; its predicates are=20
semantically much clearer.

Well, well, I don't want someone= to stop learning gua\spi  because "gua\spi is a crap. I know, la glek= i told me". :)



>
>     What natlangs can and
>     can't do has little relevance when discussing Lojban= ic topics such as
>     ka-abstractions.
>
>
> Then gua\spi has little relevance too.

What? Gua\spi is not a natlang, and you brought up Gua\spi in the first= =20
place. Gua\spi's entire gimste is ce'u-ized, that's what it looks like.

>
>
>
>     In Lojban, djica2 is a nu, not a ka. You could say t= hat djica should be
>     polymorphic and allow both nu and ka, but I don't th= ink that's what
>     you're saying, is it? (I don't know *what* you are s= aying).
>
>
> My only complaint  that we have a nice shortcut of saying {du= 'u ce'u}
> but we don't have one for {nu ce'u}.

But ka is not a shortcut for du'u ce'u... ka is what you get if you hav= e=20
a du'u abstraction and add a ce'u to it.

>
>     Why is it a nu? Because you can djica things that do= n't involve
>     yourself. (Gua\spi's _daw_ is restricted to desiring= to do or be
>     something, hence it's always like a Lojban ka. And t= hat's why the
>     second
>     example uses a different predicate.)
>
>     Again, what is the difference between the Lojban and= the gua\spi
>     sentence?
>
>
> Hopefully no semantic difference. Looks like Lojban just gives mor= e
> freedom in recombining the same words without drawing in extra pre= dicates.

Okay, but that wasn't even your original point. And as I tried to=20
explain above, you get seperate predicates if you ce'u-ize the gimste.= =20
One will be

x1 wants to be/do x2 (ka)

the other will be

x1 wants/wishes/desires that x2 (nu) happen

Is that what you want or not?

>
>
> Let's stop arguing and let's ce'u-ize gimste :).
>
> How the new ce'u-ized definitions of gismu should look like in ur = opinion?

Just look at gua\spi's gimste. It did everything right in that regard,= =20
but you have to remember that gua\spi is not Lojban, and not everything= =20
can be copied 1:1.

mu'o mi'e la selpa'i

--=20
pilno zo le xu .i lo dei bangu cu se cmene zo lojbo .e nai zo lejbo

do=E1=BB=8B m=C3=A8lbi mlen=C3=AC'u
    .i do c=C3=A0tlu ki'u
ma fe la x=C3=A0mpre =C5=ADu
    .i do t=C3=ACnsa c=C3=A0rmi
gi'e s=C3=ACrji se t=C3=A0rmi
    .i ta=E1=BB=8B bo pu c=C3=ACtka lo gr=C3=A0na ku

--
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/-/WyFuvnW2QSEJ.

=20 To post to this group, send email to loj...@googlegroups.com.
To unsubscribe from this group, send email to lojban+un...@google= groups.com.

For more options, visit this group at http://groups.google.com/grou= p/lojban?hl=3Den.

--
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/-/JzUcrDw0IJAJ.

=20 To post to this group, send email to loj...@googlegroups.com.
To unsubscribe from this group, send email to lojban+un...@googl= egroups.com.
For more options, visit this group at http://groups.google.com/group/= lojban?hl=3Den.

--
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/-/nb= ErKbv7oj0J.
=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_105_31082697.1349589707439--