Received: from mail-yh0-f61.google.com ([209.85.213.61]:38700) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1U5Gcu-0001fc-Ib; Tue, 12 Feb 2013 06:14:39 -0800 Received: by mail-yh0-f61.google.com with SMTP id q3sf31695yhf.6 for ; Tue, 12 Feb 2013 06:14:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received: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=ecsYNJaXDnO5B4ig+y8Dx3onWCGMaviwuaP6q8yKux4=; b=p3UQZ58Mx46fiGD77KcZXzBbDpGpWrvvWEdZm/Vt3BvYRpDSKzVo7bemqBNb8m3KjQ ovCMCzYpTjgmueElMbPDqHHqnwA2DGBGGaoN1mB0K+MpaAySghCJbNGYZ0nN2LJiS6vf QjzWQolHxt7Ut4i4p3ln59dnjopqhuK1cEjVcPMSmKQI+miZBZPgH+s9LlqBy9pWbhP2 Qsz3SH2ThZg4eGSpS2UoTMo16lD8LFo1ptZwd7qHsjJcr1JgmJtFx9zMgtub+pMRvPs0 7ZmAfggz5zUMlZriQQ+NNnBDDfHH+EfZny/MT2OpehI2N/9F/+Rl3UhtOLZ2nqOZLI1y joTg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:x-beenthere:x-received: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=ecsYNJaXDnO5B4ig+y8Dx3onWCGMaviwuaP6q8yKux4=; b=v0Zk8TAqCriRYIgbePU9oUAmv6j5nBcTSpZQ9DhCKmVPVmAYH6mz3uojOC6kw74B/X nxc3HDQcgzLdO4kFZ+jEPFqvN9EnaO27/KEuNHdoY9KFhDNOJZztjX/9jAJw+z43it1a VYUHG8zNo+JCg8xr0/ROp+EGuDj1PxlMLLMZ+mGzM65rt0aAY7F7Fcyh++pkIfVgEKqB K3V0E5HaFSb7paWmJwcOr2cppX9r1mh8yMtaO6fGoEwK6pWCBSk3GYqGcy34NqTkz8OJ bZxmRhCOkCfcpdTL5O7X/B0Mfagr9JlsRq7Bj0Imk8Oi7b4+QF7NyDlNmCKLmN3inL1d u+rA== X-Received: by 10.49.116.1 with SMTP id js1mr1248464qeb.19.1360678461780; Tue, 12 Feb 2013 06:14:21 -0800 (PST) X-BeenThere: lojban-beginners@googlegroups.com Received: by 10.49.60.163 with SMTP id i3ls73870qer.29.gmail; Tue, 12 Feb 2013 06:14:21 -0800 (PST) X-Received: by 10.49.116.115 with SMTP id jv19mr1233809qeb.21.1360678460861; Tue, 12 Feb 2013 06:14:20 -0800 (PST) Date: Tue, 12 Feb 2013 06:14:20 -0800 (PST) From: la gleki To: lojban-beginners@googlegroups.com Message-Id: In-Reply-To: References: <63dcdf07-3c53-4967-b50e-e3c684b4db0b@googlegroups.com> <20130210031456.GF6270@samsa.fritz.box> <20130210130730.GG6270@samsa.fritz.box> Subject: Re: [lojban-beginners] search for happiness. {sisku lo selgleki} or {sisku lo ka selgleki}? MIME-Version: 1.0 X-Original-Sender: gleki.is.my.name@gmail.com Reply-To: lojban-beginners@googlegroups.com Precedence: list Mailing-list: list lojban-beginners@googlegroups.com; contact lojban-beginners+owners@googlegroups.com List-ID: X-Google-Group-Id: 300742228892 List-Post: , List-Help: , List-Archive: Sender: lojban-beginners@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary="----=_Part_225_25415463.1360678460618" X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / ------=_Part_225_25415463.1360678460618 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tuesday, February 12, 2013 9:00:11 AM UTC+4, tsani wrote: > > On 10 February 2013 14:43, Felipe Gon=E7alves Assis > > wrote: > >> doi tsani >> >> I see things a bit different. I believe that kakne2 and djica2 should >> be abstracts >> ({ka} and {du'u}), but for their intensionality. gleki2, on the other >> hand, is as >> concrete an event as it can be, not an abstract property or >> proposition. Consider >> {mi gleki so'i lo nu mi klama lo zdani be mi} >> >> > Actually, quantifying over events like that has various problems, namely= =20 > that the zo'e inside it are magically changing. In Lojban, every event is= =20 > unique, but as humans we roll them together.=20 > In reality, what's happening when you quantify over an event like that,= =20 > you want to make a whole bunch of slightly different events: the event of= =20 > going home on Monday, and the one of Tuesday, and the one on Wednesday,= =20 > etc. Each of these events in unique. > It seems like a predicate logic sentence would be best to describe this,= =20 > and ultimately moves the quantifier scope higher: {.i so'i da zo'u mi gle= ki=20 > lo ka klama lo zdani ca da} "For many X, I am happy to go home at X." Thi= s=20 > ultimately creates many properties of going home, for each of which it is= =20 > asserted that the speaker is happy about that. > =20 > >> Also, your >> {mi gleki lo ka se li'i do citka lo plise} instead of >> {mi gleki lo nu do citka lo plise} >> is like >> {mi klama lo stuzi be lo zdani be mi} instead of >> {mi klama lo zdani be mi} >> or >> "I saw an image of the sun setting" instead of >> "I saw the sun setting", >> >> This extreme typing of sumti places just creates hindrances in >> expression without >> adding anything to the speaker's or listener's understanding of the >> world. I already >> know that it is my experience of an event that can bring me happiness=20 >> about it, >> not somebody else's, and that what determines whether someone is tall or= =20 >> short >> is his/her body, not his/her friendliness. >> > > As I explained, the general benefit of making places infinitive-places=20 > with {ka} is to make jvajvo more commonplace. As it stands, we frequently= =20 > drop "repeated" places that it would be nice to still have. Reconsider my= =20 > examples of {ctidji}. Using current nu-based djica, there is no way to ge= t=20 > both meanings in separate lujvo. Making the lujvo always drops the other= =20 > one. If we define ctidji with a place merger, we can't recover ctidji=20 > without that merger. > ctidji =3D x1 djica lo nu x1 citka x2 ... > or > ctidji =3D x1 djica lo nu x2 citka x3 ... ? > Defining one makes the other undefinable, whereas with infinitives, we=20 > just have to throw in -fri- to get the other meaning: > ctidji =3D x1 djica lo ka ce'u citka x2 ...=20 > and > ctifridji =3D x1 djica lo ka ce'u lifri lo li'i x2 citka x3 ... > > I agree, it creates some boilerplate if you want to say something like "I= =20 > want you to eat an apple," but there're ways to circumvent this. In fact,= I=20 > frequently use this tanru trick to avoid using {lo nu} and {lo ka}: {.i m= i=20 > djica co li'i do broda}. This has the unfortunate disadvantage of making = it=20 > impossible to assign djica3 (or explicitly assign djica2, although tanru= =20 > inference tells us that {lo ka se li'i do broda} is djica 2). > > Another way to "cheat the system" would be to use sei, assuming sei=20 > functions as a bridi relative clause (which I believe is the most sane=20 > interpretation of sei and as I see it, breaks no usage whatsoever): {.i s= ei=20 > mi djica do broda [da'i]}. We might need to include {da'i} in some cases,= =20 > where subjunctives happen implicitly in the nested bridi. In the case of= =20 > djica2, we usually assume that the djica2 is subjunctive, i.e. is true=20 > hypothetically, but not in reality. My example with sei, however, moves t= he=20 > nested bridi onto the top level, pushing the djica-bridi into a relative= =20 > clause. Strictly speaking, the nested bridi becomes claimed, which is=20 > undesirable in the case of djica. > This really looks like trying to patch flaws. djica2 always implies {da'i}.= =20 Several other brivla imply it too. =20 > > (The choice of li'i and lifri in general for more flexibility in the rigi= d=20 > infinitive system requires that the actual association between the lifri1= =20 > and lifri2 possibly be extremely vague, which isn't exactly a problem.) > > As for your comparison between {gleki lo ka se li'i broda} and {klama lo= =20 > stuzi be ko'a} isn't entirely rational. The "speech cost" of {ka se li'i}= =20 > versus the introduction of a whole other selbri and linked arguments is= =20 > completely different. {ka se li'i} versus {nu} is only 3 syllables (short= =20 > syllables with no consonant clusters) longer. (At most four, if you inclu= de=20 > the extra kei.) Also, I find it much easier to understand a compound=20 > abstractor like this than complex linked arguments.=20 > Also, stuzi1 and stuzi2 are arguably *the same thing*, which can be=20 > troubling. Let's take a look at another selbri for comparison. Although= =20 > it's experimental, {ditcu} is the best example of this: "x1 is the=20 > time-duration of x2." It turns out that both the x1 and x2 are events,=20 > because in Lojban, there isn't actually a system for representing=20 > quantities, so we use objects (or events) as proxies for their relevant= =20 > properties. That being said, ditcu simply states an equivalency in the=20 > event-bridis' ze'a-tag: {ko'a ko'e go ditcu gi dunli lo ka makau jai ze'a= =20 > fasnu fai ce'u}. Now to get back to stuzi, does stuzi simply state an=20 > equivalency in the objects' bu'u-tag ? {ko'a ko'e go stuzi gi dunli lo ka= =20 > makau jai bu'u me ko'a} ? I'm not entirely sure. It doesn't really look= =20 > like it, because that means I get to say things like {.i lo zdani be mi c= a=20 > stuzi mi}, which shouldn't really make sense. However, that being said,= =20 > *what* kinds of things can we even *put* in stuzi1 ? > Now, if stuzi1 and stuzi2 are argubly the same thing, then {mi klama lo= =20 > stuzi be ko'a} and {mi klama ko'a} are also arguably the same thing.=20 > However, under my infinitives system, events are not interchangeable with= =20 > ka-abstractions, and there is no way to define an equivalency as I have i= n=20 > the case of stuzi. > > .i mi'e la tsani mu'o > > --=20 You received this message because you are subscribed to the Google Groups "= Lojban Beginners" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban-beginners+unsubscribe@googlegroups.com. To post to this group, send email to lojban-beginners@googlegroups.com. Visit this group at http://groups.google.com/group/lojban-beginners?hl=3Den= . For more options, visit https://groups.google.com/groups/opt_out. ------=_Part_225_25415463.1360678460618 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tuesday, February 12, 2013 9:00:11 AM UTC+4, tsani wrote:On 10 February 2013 14:43, Felipe Gon= =E7alves Assis <felipe...@gmail.com> wrote:
doi tsani

I see things a bit different. I believe that kakne2 and djica2 should
be abstracts
({ka} and {du'u}), but for their intensionality. gleki2, on the other
hand, is as
concrete an event as it can be, not an abstract property or
proposition. Consider
  {mi gleki so'i lo nu mi klama lo zdani be mi}


Actually, quantifying over events like= that has various problems, namely that the zo'e inside it are magically ch= anging. In Lojban, every event is unique, but as humans we roll them togeth= er. 
In reality, what's happening when you quantify over an event like that= , you want to make a whole bunch of slightly different events: the event of= going home on Monday, and the one of Tuesday, and the one on Wednesday, et= c. Each of these events in unique.
It seems like a predicate logic sentence would be best to describe thi= s, and ultimately moves the quantifier scope higher: {.i so'i da zo'u mi gl= eki lo ka klama lo zdani ca da} "For many X, I am happy to go home at X." T= his ultimately creates many properties of going home, for each of which it = is asserted that the speaker is happy about that.
 
Also, your
  {mi gleki lo ka se li'i do citka lo plise} instead of
  {mi gleki lo nu do citka lo plise}
is like
  {mi klama lo stuzi be lo zdani be mi} instead of
  {mi klama lo zdani be mi}
or
 "I saw an image of the sun setting" instead of
 "I saw the sun setting",

This extreme typing of sumti places just creates hindrances in
expression without
adding anything to the speaker's or listener's understanding of the
world. I already
know that it is my experience of an event that can bring me happiness about= it,
not somebody else's, and that what determines whether someone is tall or sh= ort
is his/her body, not his/her friendliness.

<= div>As I explained, the general benefit of making places infinitive-places = with {ka} is to make jvajvo more commonplace. As it stands, we frequently d= rop "repeated" places that it would be nice to still have. Reconsider my ex= amples of {ctidji}. Using current nu-based djica, there is no way to get bo= th meanings in separate lujvo. Making the lujvo always drops the other one.= If we define ctidji with a place merger, we can't recover ctidji without t= hat merger.
ctidji =3D x1 djica lo nu x1 citka x2 ...
or
ctidj= i =3D x1 djica lo nu x2 citka x3 ... ?
Defining one makes the oth= er undefinable, whereas with infinitives, we just have to throw in -fri- to= get the other meaning:
ctidji =3D x1 djica lo ka ce'u citka x2 ... 
and
<= div>ctifridji =3D x1 djica lo ka ce'u lifri lo li'i x2 citka x3 ...
I agree, it creates some boilerplate if you want to say s= omething like "I want you to eat an apple," but there're ways to circumvent= this. In fact, I frequently use this tanru trick to avoid using {lo nu} an= d {lo ka}: {.i mi djica co li'i do broda}. This has the unfortunate disadva= ntage of making it impossible to assign djica3 (or explicitly assign djica2= , although tanru inference tells us that {lo ka se li'i do broda} is djica = 2).

Another way to "cheat the system" would be to use sei, = assuming sei functions as a bridi relative clause (which I believe is the m= ost sane interpretation of sei and as I see it, breaks no usage whatsoever)= : {.i sei mi djica do broda [da'i]}. We might need to include {da'i} in som= e cases, where subjunctives happen implicitly in the nested bridi. In the c= ase of djica2, we usually assume that the djica2 is subjunctive, i.e. is tr= ue hypothetically, but not in reality. My example with sei, however, moves = the nested bridi onto the top level, pushing the djica-bridi into a relativ= e clause. Strictly speaking, the nested bridi becomes claimed, which is und= esirable in the case of djica.

= This really looks like trying to patch flaws. djica2 always implies {da'i}.= Several other brivla imply it too.

 

(The choice of li'i and lifri in general for more flexi= bility in the rigid infinitive system requires that the actual association = between the lifri1 and lifri2 possibly be extremely vague, which isn't exac= tly a problem.)

As for your comparison between {gleki lo ka se li'i bro= da} and {klama lo stuzi be ko'a} isn't entirely rational. The "speech cost"= of {ka se li'i} versus the introduction of a whole other selbri and linked= arguments is completely different. {ka se li'i} versus {nu} is only 3 syll= ables (short syllables with no consonant clusters) longer. (At most four, i= f you include the extra kei.)  Also, I find it much easier to understa= nd a compound abstractor like this than complex linked arguments. 
Also, stuzi1 and stuzi2 are arguably *the same thing*, which can be tr= oubling. Let's take a look at another selbri for comparison. Although it's = experimental, {ditcu} is the best example of this: "x1 is the time-duration= of x2." It turns out that both the x1 and x2 are events, because in Lojban= , there isn't actually a system for representing quantities, so we use obje= cts (or events) as proxies for their relevant properties. That being said, = ditcu simply states an equivalency in the event-bridis' ze'a-tag: {ko'a ko'= e go ditcu gi dunli lo ka makau jai ze'a fasnu fai ce'u}. Now to get back t= o stuzi, does stuzi simply state an equivalency in the objects' bu'u-tag ? = {ko'a ko'e go stuzi gi dunli lo ka makau jai bu'u me ko'a} ? I'm not entire= ly sure. It doesn't really look like it, because that means I get to say th= ings like {.i lo zdani be mi ca stuzi mi}, which shouldn't really make sens= e. However, that being said, *what* kinds of things can we even *put* in st= uzi1 ?
Now, if stuzi1 and stuzi2 are argubly the same thing, then {mi klama l= o stuzi be ko'a} and {mi klama ko'a} are also arguably the same thing. Howe= ver, under my infinitives system, events are not interchangeable with ka-ab= stractions, and there is no way to define an equivalency as I have in the c= ase of stuzi.

.i mi'e la tsani mu'o

--
You received this message because you are subscribed to the Google Groups &= quot;Lojban Beginners" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban-beginners+unsubscribe@googlegroups.com.
To post to this group, send email to lojban-beginners@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban-beginners?hl=3Den. For more options, visit https://groups.google.com/groups/opt_out.
 
 
------=_Part_225_25415463.1360678460618--