From lojban+bncCIywt_XDCRDJ8t7oBBoEG8x_QA@googlegroups.com Sun Dec 26 13:53:29 2010 Received: from mail-yi0-f61.google.com ([209.85.218.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1PWyWp-0002az-C5; Sun, 26 Dec 2010 13:53:29 -0800 Received: by yia27 with SMTP id 27sf3651902yia.16 for ; Sun, 26 Dec 2010 13:53:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:received:x-beenthere:received:received:received :received:received-spf:received:message-id:x-ymail-osg:received :x-mailer:references:date:from:subject:to:in-reply-to:mime-version :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe:content-type; bh=3kEfdxOtUitDJ4Cwx76b43iblpyuzUKcQbG15i+DJ+g=; b=1D9YFVKrSuZaKJ2tiPjfO+oTyyC8Zfp3le3BrvW1drdEhqfy7DyJ2tT1zExsXiAgkJ hQmK7nZRxkZRYLvHgCP7KOO2fG5xb8JIpWAEeVsuR2ri7bSGby+Gjl8rhdurZG5oUQKR WmserRSMqei3N1mBUtC4dGx25J6Od/7AqYsMo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:message-id:x-ymail-osg:x-mailer:references :date:from:subject:to:in-reply-to:mime-version:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; b=0522JcK4pie1mv0bVrnQodzLbk2hCFtyqjNUSN8AFFPTcTc0rtsSIxMnk17Wb+fonD 6TJn+4gYC3GDa6N+WudG/GFuReqDeZlVDk62GA/hZphrHf0TICkT8aRUIfo7wa7IGZ5d bVRsV1iRLoBSg4H8pDwqJSnaj++EhtrzxcfO8= Received: by 10.151.63.9 with SMTP id q9mr1051187ybk.52.1293400393092; Sun, 26 Dec 2010 13:53:13 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.100.56.38 with SMTP id e38ls1923353ana.3.p; Sun, 26 Dec 2010 13:53:12 -0800 (PST) Received: by 10.100.109.4 with SMTP id h4mr1284252anc.31.1293400392477; Sun, 26 Dec 2010 13:53:12 -0800 (PST) Received: by 10.100.109.4 with SMTP id h4mr1284251anc.31.1293400392448; Sun, 26 Dec 2010 13:53:12 -0800 (PST) Received: from web81302.mail.mud.yahoo.com (web81302.mail.mud.yahoo.com [68.142.199.118]) by gmr-mx.google.com with SMTP id i35si4905897anh.10.2010.12.26.13.53.11; Sun, 26 Dec 2010 13:53:11 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 68.142.199.118 as permitted sender) client-ip=68.142.199.118; Received: (qmail 22171 invoked by uid 60001); 26 Dec 2010 21:53:10 -0000 Message-ID: <782268.21580.qm@web81302.mail.mud.yahoo.com> X-YMail-OSG: CB9dbrAVM1n8lZMd.mRpplcpm4duqV0Eh20ScF1t30UaotC 37xQy97cieI4RoTB0PUytOUbCuCV8CQ_WUFYZtehDK_Pf.K6VNzDw6t4sEvN kyHfwwVc7U72LIBm.PeMm0rrqYM6qMs6tnLus7IErQmxo_q6lFI5Q_b9CuRe I8BQxOtzJ4CIi.aCsgMcv.ddvIp8jzJDvzmS0VN3iBvJDsIS895IaMILG9hv .4FvHb5fT034CH02FhsPox4Z7nGJrm0S6tGV5Yb3.coFABnR2XMbkRV4teMz hyJfejIQhd1kjHfkxYN91qVlQhOqiAgN7x3eVqNcc6CNTGhaEHnB5B6Vigzd 0J4Ft1NwQwdbIUbbRp5bAcHTAkRB9p.9M4JTAKdLoidJ2NjycWSIdb6QaRWE kve_UWHxqWwt7 Received: from [99.92.110.13] by web81302.mail.mud.yahoo.com via HTTP; Sun, 26 Dec 2010 13:53:10 PST X-Mailer: YahooMailRC/553 YahooMailWebService/0.8.107.285259 References: Date: Sun, 26 Dec 2010 13:53:10 -0800 (PST) From: John E Clifford Subject: Re: [lojban] Tanru automatically forming To: lojban@googlegroups.com In-Reply-To: MIME-Version: 1.0 X-Original-Sender: kali9putra@yahoo.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 68.142.199.118 as permitted sender) smtp.mail=kali9putra@yahoo.com; dkim=pass (test mode) header.i=@yahoo.com Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary="0-622327631-1293400390=:21580" --0-622327631-1293400390=:21580 Content-Type: text/plain; charset=ISO-8859-1 Whoa! Is this really a proposal to have *one* cmavo for all tanru? A sort of weak 'zei'? I was expecting the old "the relation between the modifier and the modified is ambiguous" screed. Is there any real reason to do this? They already have the shortest cmavo of all, ' ', joining them. To be sure, it is used for other things as well, but each use is contextually defined and that has to be at least one such joining (maybe just concatenation, but that makes for hard reading) for a language to work at all -- we can't mark everything (because of infinite regress). So, any other tanru marker is going to make Lojban sentences (which already suffer from a lot of cmavo snow) longer, often a lot longer. And to what gain? Are there tanru that aren't recognizable as such? I suppose that there can be for us poor non-computers, as we go down some tree of subordinate arguments or whatever. But surely these are very rare and and best be handled a "WTF" -- for which there is a handy cmavo -- rather than marking all the non-problematic ones. As long as we are not going to go to some version of full parentheses, nothing is better than what we have (which almost translates into full parentheses when used correctlly). From: Ian Johnson To: lojban@googlegroups.com Sent: Sun, December 26, 2010 1:24:46 PM Subject: Re: [lojban] Tanru automatically forming At the quoted response in particular: what? The simplest bridi would have no tanru; all the sumti would be LE GISMU, and the selbri would also be GISMU. Under this system a typical sentence would look like {lo broda brode lo brodi lo brodo}. More generally: From the logical perspective, this argument makes a degree of sense; saying "sumti ends here" or "predicate starts here" does make more sense than saying "tanru begins here". However, from a cmavo count perspective, this isn't really the case; you could write an entire paragraph without ever forming a tanru, quite easily, and in the meantime the majority of the sentences would have a {cu}. The main disadvantage (and I thought about this after I sent my original email, actually) is that some select sentences wind up having a LOT of cmavo, and in fact a lot of repeated cmavo. For default grouping in particular, there's a pretty easy fix for this that I didn't think about: have the {ja'ei} go out in front. Then you only need one {ja'ei} to group a bunch of selbri into a tanru with the default grouping. I think this would probably be necessary even when using {ke} and friends (so you'd see {ja'ei broda ke brode brodi} and so on) but maybe not. The problem with {ja'ei} out in front is with situations that are currently treated by saying {lo broda brode cu brodi}. Then you really would be adding cmavo, because you'd have to say {lo ja'ei broda brode cu brodi}. But only in that case would you be adding cmavo; I'm fairly sure that the net number of cmavo would still be lower. mu'o mi'e .latros. On Sun, Dec 26, 2010 at 12:57 PM, Oleksii Melnyk wrote: > > >2010/12/26 Ian Johnson > > >{lo gerku cu klama} is more common than {lo gerku klama cu bajra}. >> >Even simplest bridi have only one place for "cu", but 2..6 for a tanru. So, >exchanging [0..1] cu with [2..6] "ja'ei"(or whatever) is a waste of brevity. > >-- >mu'o mi'e lex > > -- >You received this message because you are subscribed to the Google Groups >"lojban" group. >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. > -- You received this message because you are subscribed to the Google Groups "lojban" group. 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. -- You received this message because you are subscribed to the Google Groups "lojban" group. 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. --0-622327631-1293400390=:21580 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Whoa!  Is this really a proposal to have *one* cmavo= for all tanru?  A sort of weak 'zei'?  I was expecting the old "= the relation between the modifier and the modified is ambiguous" screed.&nb= sp; Is there any real reason to do this?  They already have the shorte= st cmavo of all, ' ', joining them.  To be sure, it is used for other = things as well, but each use is contextually defined and that has to be at = least one such joining (maybe just concatenation, but that makes for hard r= eading) for a language to work at all  -- we can't mark everything (be= cause of infinite regress).  So, any other tanru marker is going to ma= ke Lojban sentences (which already suffer from a lot of cmavo snow) longer,= often a lot longer.  And to what gain?  Are there tanru that aren't recognizable as such?  I suppose that there can be for us poor= non-computers, as we go down some tree of subordinate arguments or whateve= r.  But surely these are very rare and and best be handled a "WTF" -- = for which there is a handy cmavo -- rather than marking all the non-problem= atic ones.
As long as we are not going to go to some versi= on of full parentheses, nothing is better than what we have (which almost t= ranslates into full parentheses when used correctlly).

From: Ian Johnson <blindbravado@gmail.com>
To:= lojban@googlegroups.com
Sent: Sun, December 26, 2010 1:24:46 PM
Subject: Re: [lojban] Tanru automatically forming
At the quoted response in particular: what? The simplest bridi would have n= o tanru; all the sumti would be LE GISMU, and the selbri would also be GISM= U. Under this system a typical sentence would look like {lo broda brode lo = brodi lo brodo}.

More generally:
From the logical perspective, this argument makes a = degree of sense; saying "sumti ends here" or "predicate starts here" does m= ake more sense than saying "tanru begins here".

However, from a cmavo count perspective, this isn't really the case; yo= u could write an entire paragraph without ever forming a tanru, quite easil= y, and in the meantime the majority of the sentences would have a {cu}. The= main disadvantage (and I thought about this after I sent my original email= , actually) is that some select sentences wind up having a LOT of cmavo, an= d in fact a lot of repeated cmavo.

For default grouping in particular, there's a pretty easy fix for this = that I didn't think about: have the {ja'ei} go out in front. Then you only = need one {ja'ei} to group a bunch of selbri into a tanru with the default g= rouping. I think this would probably be necessary even when using {ke} and = friends (so you'd see {ja'ei broda ke brode brodi} and so on) but maybe not= .

The problem with {ja'ei} out in front is with situations that are curre= ntly treated by saying {lo broda brode cu brodi}. Then you really would be = adding cmavo, because you'd have to say {lo ja'ei broda brode cu brodi}. Bu= t only in that case would you be adding cmavo; I'm fairly sure that the net= number of cmavo would still be lower.

mu'o mi'e .latros.


--
You received this message because you are subscribed to the Google Groups "= lojban" group.
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/lojba= n?hl=3Den.

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
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.
--0-622327631-1293400390=:21580--