Received: from mail-yx0-f189.google.com ([209.85.213.189]:58393) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1S4ex2-0007r7-Ce; Mon, 05 Mar 2012 12:56:14 -0800 Received: by yenm3 with SMTP id m3sf4635314yen.16 for ; Mon, 05 Mar 2012 12:56:06 -0800 (PST) Received-SPF: pass (google.com: domain of lojban+bncCP--_J2JAxDi0NT6BBoEBogrkw@googlegroups.com designates 10.224.222.148 as permitted sender) client-ip=10.224.222.148; Authentication-Results: mr.google.com; spf=pass (google.com: domain of lojban+bncCP--_J2JAxDi0NT6BBoEBogrkw@googlegroups.com designates 10.224.222.148 as permitted sender) smtp.mail=lojban+bncCP--_J2JAxDi0NT6BBoEBogrkw@googlegroups.com; dkim=pass header.i=lojban+bncCP--_J2JAxDi0NT6BBoEBogrkw@googlegroups.com Received: from mr.google.com ([10.224.222.148]) by 10.224.222.148 with SMTP id ig20mr13847864qab.17.1330980966056 (num_hops = 1); Mon, 05 Mar 2012 12:56:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:date:from:to:message-id:in-reply-to:references:subject :mime-version: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=PNq9jRlqfEgbU3LzkWcZgEP4G3v5SQMi1bYwtlBZHUU=; b=zsf+cjkF+GEzBVol23p0daPWTfB72mIq5aP4STBDUZpEoOO6b/OEG1GIgz1Y7Np1av o1YaXb/TyTaUzP5WnCCkbyaIz3Lu+gCdgcMRs6p3Rj/6vV4vzqztQl/qGvTCs6k3yKm/ 8g7R3mWPOLyp0Oq2ClsEYptIi0wSH0UyfPMVM= Received: by 10.224.222.148 with SMTP id ig20mr4123271qab.17.1330980962273; Mon, 05 Mar 2012 12:56:02 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.229.117.204 with SMTP id s12ls6609689qcq.7.gmail; Mon, 05 Mar 2012 12:56:00 -0800 (PST) Received: by 10.236.77.165 with SMTP id d25mr2285876yhe.1.1330980960737; Mon, 05 Mar 2012 12:56:00 -0800 (PST) Date: Mon, 5 Mar 2012 12:56:00 -0800 (PST) From: vruxir To: lojban@googlegroups.com Message-ID: <22733730.2112.1330980960085.JavaMail.geo-discussion-forums@ynlt17> In-Reply-To: References: <201203050232.47562.phma@phma.optus.nu> <7853015.1110.1330974066635.JavaMail.geo-discussion-forums@vbze11> Subject: Re: [lojban] What's the deal with me'ispe and bunspe? MIME-Version: 1.0 X-Original-Sender: kextrii@gmail.com X-Original-Authentication-Results: ls.google.com; spf=pass (google.com: domain of kextrii@gmail.com designates internal as permitted sender) smtp.mail=kextrii@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="----=_Part_2111_11127600.1330980960083" X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / ------=_Part_2111_11127600.1330980960083 Content-Type: text/plain; charset=ISO-8859-1 On Monday, March 5, 2012 3:09:52 PM UTC-5, aionys wrote: > > On Mon, Mar 5, 2012 at 12:01 PM, vruxir wrote: > >> ...I would assume, by my understanding of tanru where the first element >> modifies the second, that the most basic definitions of me'ispe and bunspe >> are: >> > > lujvo are not tanru. lujvo are defined words, said definition determined > by the creator, and do not necessarily have anything to do with the meaning > of any tanru. > That's correct. However, a lujvo is a compact way to express a useful relationship, and there's only room for one (or very few) lujvo combining a particular set of terms. So it makes sense that if the lujvo is created suboptimally without forethought, it can be changed by consensus, as you proposed. Except we disagree on what modification should be made. > lo me'ispe: sister kind-of spouse -> sister's spouse (gender not >> specified, so not necessarily brother- or sister-in-law) >> (shorthand for lo speni be lo mensi) >> > > a "sister kind-of spouse" is a spouse who is a sister, not a sister of a > spouse. > I concede that, as a basic definition of "sister kind-of spouse", incestuous marriage is just as conceivable as spouse-associated-with-a-sister. Which meaning would be more frequently referred to in typical conversation, I wonder. > By my definition, {zo me'ispe smuni lu ko'a mensi ko'e lonu speni lu} = > "x1 is the sister of x2 by the bond of marriage; x1 is x2's sister-in-law" > > But it still looks to me like a lujvo relatable to a reversed tanru, where the second element, "speni", is modifying the first element, "mensi"; i.e. mensi co speni "sister of-type spouse" Like you said, the lujvo doesn't have to resemble any particular tanru, but it would be easier to understand and remember if the ordering didn't seem backwards. 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/-/fpwSUCWvhVwJ. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en. ------=_Part_2111_11127600.1330980960083 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Monday, March 5, 2012 3:09:52 PM UTC-5, aionys wrote:
On Mon, Mar 5, 2012 = at 12:01 PM, vruxir wrote:
...I would assume, by my understanding of tanru where the first elemen= t modifies the second, that the most basic definitions of me'ispe and bunsp= e are:

lujvo are not tanru. lujvo are defined wo= rds, said definition determined by the creator, and do not necessarily have= anything to do with the meaning of any tanru.
 
That's correct. However, a l= ujvo is a compact way to express a useful relationship, and there's only ro= om for one (or very few) lujvo combining a particular set of terms. So it m= akes sense that if the lujvo is created suboptimally without forethought, i= t can be changed by consensus, as you proposed. Except we disagree on what = modification should be made.
 
lo me'ispe: sister kind-of spouse -&= gt; sister's spouse (gender not specified, so not necessarily brother- or s= ister-in-law)
(shorthand for lo speni be lo mensi)

a "sis= ter kind-of spouse" is a spouse who is a sister, not a sister of a spouse.<= br>

I concede that, as a b= asic definition of "sister kind-of spouse", incestuous marriage is jus= t as conceivable as spouse-associated-with-a-sister. Which meaning wou= ld be more frequently referred to in typical conversation, I wonder.
<= div> 
By my definition, {zo me'ispe smuni lu ko'a mensi ko'e lo= nu speni lu} =3D "x1 is the sister of x2 by the bond of marriage; x1 is x2'= s sister-in-law"


But it= still looks to me like a lujvo relatable to a reversed tanru, where the se= cond element, "speni", is modifying the first element, "mensi"; i.e. mensi = co speni "sister of-type spouse"

Like you said= , the lujvo doesn't have to resemble any particular tanru, but it would be = easier to understand and remember if the ordering didn't seem backwards.


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/-/fp= wSUCWvhVwJ.
=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_2111_11127600.1330980960083--