Received: from mail-ve0-f187.google.com ([209.85.128.187]:63438) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1U5lGJ-0005Dx-Ds; Wed, 13 Feb 2013 14:57:16 -0800 Received: by mail-ve0-f187.google.com with SMTP id oz10sf604677veb.24 for ; Wed, 13 Feb 2013 14:57:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received:x-received:received-spf :mime-version:x-received:in-reply-to:references:date:message-id :subject:from: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:content-transfer-encoding; bh=jzrjrKn8C17DooXTx0ce21hGh7BwebmrQdnuRx1lboo=; b=uELAQzZ5wWAHljk4z8j+rr8utyDZYUtKjqXz4sPUk0HRlkTrx+qBa67OWlDfDrZZ5O 5hnLrCiIyoPgxeEmxTStPvkzzJh6Ta+9bNRsDMSeS1RJtXPfE9ml776vl41y4D2vHHpa XTUlEbFKz4qjpnvq+8la6Fr3QYqjRHU3VAM3mMNLmla1Y8EptqHsSbCibo3iwpvQYxTp HvnSHMFWMgeYYiJh9dQulS1WO8ZFdW5ULNw1PpjEELtjSFGdIbffJQtZtGmVsdXJaQuc FYVdyJaSln92Sm6cjVC8qnR5Ymr7dgwL9UvbFzNK4NTAnQUWR/5KSbUDXQGpoXBZS/t4 UcBQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:x-beenthere:x-received:x-received:received-spf :mime-version:x-received:in-reply-to:references:date:message-id :subject:from: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:content-transfer-encoding; bh=jzrjrKn8C17DooXTx0ce21hGh7BwebmrQdnuRx1lboo=; b=N6xr6/cOU6n9lyx4Y3jqqOKyj77eMVbUlsmLxsK16csgkPpMaRT1ws2dFMuR4yvJUd erUBbOSiFVAZFgoun+8PkjzBPf6ey5uZ4tT871GRtPHhjJ+3bvlT8L1Tn2qHgqc5XeF2 R6hY4Gtw/Zwb8uTmKWmCo9AYmbgNTnDFxXZECX98O3CZ5ZGLduA9FIhCLbtxDfVHQ9xF 1I05+WdswMhK103H99Y+8RbedUwEBvZHonbxeJEqbhAW5uSbZUFWYli3JjWgnHHHBKmo QJ0gDD98nRLJNpCeW5Rai3CRRjnErPqRXlMt0jWvpJdqeKDHRzS+WbtrFmXlSpEp+L9g /RYQ== X-Received: by 10.182.123.12 with SMTP id lw12mr20069obb.10.1360796224558; Wed, 13 Feb 2013 14:57:04 -0800 (PST) X-BeenThere: lojban-beginners@googlegroups.com Received: by 10.182.31.113 with SMTP id z17ls119570obh.41.gmail; Wed, 13 Feb 2013 14:56:53 -0800 (PST) X-Received: by 10.182.172.65 with SMTP id ba1mr3779492obc.17.1360796213437; Wed, 13 Feb 2013 14:56:53 -0800 (PST) X-Received: by 10.182.172.65 with SMTP id ba1mr3779490obc.17.1360796213391; Wed, 13 Feb 2013 14:56:53 -0800 (PST) Received: from mail-ia0-x229.google.com (mail-ia0-x229.google.com [2607:f8b0:4001:c02::229]) by gmr-mx.google.com with ESMTPS id cf5si707328igb.2.2013.02.13.14.56.53 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Feb 2013 14:56:53 -0800 (PST) Received-SPF: pass (google.com: domain of felipeg.assis@gmail.com designates 2607:f8b0:4001:c02::229 as permitted sender) client-ip=2607:f8b0:4001:c02::229; Received: by mail-ia0-x229.google.com with SMTP id j5so1725558iaf.14 for ; Wed, 13 Feb 2013 14:56:53 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.50.88.136 with SMTP id bg8mr14525033igb.96.1360794538140; Wed, 13 Feb 2013 14:28:58 -0800 (PST) Received: by 10.231.177.1 with HTTP; Wed, 13 Feb 2013 14:28:57 -0800 (PST) In-Reply-To: References: <63dcdf07-3c53-4967-b50e-e3c684b4db0b@googlegroups.com> <20130210031456.GF6270@samsa.fritz.box> <20130210130730.GG6270@samsa.fritz.box> Date: Wed, 13 Feb 2013 19:28:57 -0300 Message-ID: Subject: Re: [lojban-beginners] search for happiness. {sisku lo selgleki} or {sisku lo ka selgleki}? From: =?ISO-8859-1?Q?Felipe_Gon=E7alves_Assis?= To: lojban-beginners@googlegroups.com X-Original-Sender: felipeg.assis@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of felipeg.assis@gmail.com designates 2607:f8b0:4001:c02::229 as permitted sender) smtp.mail=felipeg.assis@gmail.com; dkim=pass header.i=@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: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / On 12 February 2013 02:00, Jacob Errington 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 > that the zo'e inside it are magically changing. In Lojban, every event is > unique, but as humans we roll them together. > In reality, what's happening when you quantify over an event like that, y= ou > want to make a whole bunch of slightly different events: the event of goi= ng > home on Monday, and the one of Tuesday, and the one on Wednesday, etc. Ea= ch > of these events in unique. > It seems like a predicate logic sentence would be best to describe this, = and > ultimately moves the quantifier scope higher: {.i so'i da zo'u mi gleki l= o > ka klama lo zdani ca da} "For many X, I am happy to go home at X." This > ultimately creates many properties of going home, for each of which it is > asserted that the speaker is happy about that. > Then you should agree that quantifying over red things is equally problematic, because each red thing is unique, so that instead of {mi citka so'i da poi xunre} we would have something like {so'i de zo'u mi citka lo xunre be sela'u de} or, using your idea of space-time, {so'i de zo'u mi citka lo xunre be bu'u de} We are used to talking about different sunsets as well as about different red things. We understand that each sunset is slightly different from the other, as we understand that each red thing is slightly different from the other, but that does not stops us from describing them with a common predicate, as well as counting them. I see nothing illogical in that. Anyway, you've made your point that limitedness of expression is not a problem, but see last paragraph. >> >> 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 >> short >> is his/her body, not his/her friendliness. > > > As I explained, the general benefit of making places infinitive-places wi= th > {ka} is to make jvajvo more commonplace. As it stands, we frequently drop > "repeated" places that it would be nice to still have. Reconsider my > examples of {ctidji}. Using current nu-based djica, there is no way to ge= t > both 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 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 ju= st > have to throw in -fri- to get the other meaning: > ctidji =3D x1 djica lo ka ce'u citka x2 ... > 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 > 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} and {lo ka}: {.i m= i > djica co li'i do broda}. This has the unfortunate disadvantage 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). > {djica} is a different discussion. I too disagree that a {nu}-clause makes sense in djica2. Your {ko'a djica ko'e} is just my {ko'a djica lo du'u ko'a ckaji ko'e}, and my {ko'a djica ko'e} is your {ko'a djica lo ka lifri su'o fasnu be ko'e}. I just think that, if you accept that wanting people to live in peace in the next century can be paraphrased as wanting to lifri that, you have made the definition of {lifri} almost vacuous. > (The choice of li'i and lifri in general for more flexibility in the rigi= d > infinitive system requires that the actual association between the lifri1 > and lifri2 possibly be extremely vague, which isn't exactly a problem.) > Yeah, you appear to agree. Don't you find it ugly? Besides, you don't have to ka-ify djica2 to get jvajvo for the infinitive interpretations. Dependent places in lujvo is a common issue that has to be dealt with anyhow, and other more general and less invasive solutions exist. If you want {rodydji} to be strictly reserved to {ko'a djica lo du'u ko'e broda} under the {du'u} definition of {djica}, we could have {rodydjisi'u} for {ko'a simxu lo ka ce'u djica lo du'u ce'u broda}. Another option is to be liberal about djica2, allowing both properties and propositions, and then making the distinction via {kambrodykezdji} vs {dumbrodykezdji}, which would be even more regular lujvo. > As for your comparison between {gleki lo ka se li'i broda} 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 syllables (short > syllables with no consonant clusters) longer. (At most four, if you inclu= de > the extra kei.) Also, I find it much easier to understand a compound > abstractor like this than complex linked arguments. Speech cost is the least. The complexity of the object is the problem. It is only easy to handle when it is part of a set phrase, such as {ko'a gleki lo ka se li'i broda}. I made the argument because I thought you wanted to emphasize the experience as the source of happyness. Now I see that the experience is for you just a way of getting an extra place to fit the {ce'u} of an uncalled for property. > Also, stuzi1 and stuzi2 are arguably *the same thing*, which can be > troubling... > Now, if stuzi1 and stuzi2 are argubly the same thing, then {mi klama lo > stuzi be ko'a} and {mi klama ko'a} are also arguably the same thing. > However, under my infinitives system, events are not interchangeable with > ka-abstractions, and there is no way to define an equivalency as I have i= n > the case of stuzi. > I agree, and hold my point. Besides the counting, I believe events can also be pointed to, and may fill places for both time and space (although, like objects that have more clear limits in space than in time, events usually are more clearly delimited in time rather than in space). Here your {ko'a gleki ko'e} is my {ko'a gleki lo nu ko'a ckaji ko'e}, and my {ko'a gleki ko'e} is your {ko'a gleki lo ka lifri ko'e}. The problem is that you have unnecessarily put an essentially concrete object (the event) under an intensional scope (the property). Nothing stops us from doing that as much as we can. For example, we could define {citka} to mean "x1 eats something with property x2", rendering {mi citka lo ka plise} instead of {mi citka lo plise}. This would make the lujvo {plisycti} represent the same structure as {volka'e}, but that is, I repeat, ugly, and complicates things, not on the syllable-count level, but on the grammatical one. mu'o mi'e .asiz. --=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.