Received: from mail-ob0-f189.google.com ([209.85.214.189]:49204) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1UbZZP-0005ga-1H for lojban-list-archive@lojban.org; Sun, 12 May 2013 09:56:34 -0700 Received: by mail-ob0-f189.google.com with SMTP id un3sf290499obb.6 for ; Sun, 12 May 2013 09:56:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received:received-spf:x-ct-class :x-ct-score:x-ct-refid:x-ct-spam:x-authority-analysis:x-cm-score :message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-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; bh=Lf71Qw9JpvGwU6PuCqWIdih9BlIyrmQKhBgHDzkcx+Y=; b=MNLEX3Q/CwyCqH71wrXHrDD4t7clwQ+dfcrO3liHqJYNybmdiIFkT0JA4Lz2MSwQI+ YhQwRl5DEpRhqDz7Gov2U+2ol9tzl8X3dnyfz2OsNV/FlPg336iwXAfUONWJtV6Dv0Ra LhGLuAH2mC+XOX7GTjBXx6KbSZK5c7NpPbHC6+4I2T5omBvOnF6T8RHRx+NZ5FW35/Ce Ol0Gfqi++QcR2mj7pY9vDz9axY6tT1XgbPm8bQM51YnA/wxzyNu6tnV/az0kiItX+20j tmVajgT6QX4t/AowDXut4Lv+gyypbxG1CLW+47+bGZxtBymmrHmrMPjdm+I8K6AiUMUa dDCw== X-Received: by 10.49.104.209 with SMTP id gg17mr1820429qeb.7.1368377776554; Sun, 12 May 2013 09:56:16 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.49.14.103 with SMTP id o7ls2652047qec.9.gmail; Sun, 12 May 2013 09:56:15 -0700 (PDT) X-Received: by 10.224.59.205 with SMTP id m13mr16919195qah.7.1368377775587; Sun, 12 May 2013 09:56:15 -0700 (PDT) Received: from eastrmfepo202.cox.net (eastrmfepo202.cox.net. [68.230.241.217]) by gmr-mx.google.com with ESMTP id f2si801575qcv.1.2013.05.12.09.56.15 for ; Sun, 12 May 2013 09:56:15 -0700 (PDT) Received-SPF: neutral (google.com: 68.230.241.217 is neither permitted nor denied by best guess record for domain of lojbab@lojban.org) client-ip=68.230.241.217; Received: from eastrmimpo306 ([68.230.241.238]) by eastrmfepo202.cox.net (InterMail vM.8.01.05.09 201-2260-151-124-20120717) with ESMTP id <20130512165615.DTGI14810.eastrmfepo202.cox.net@eastrmimpo306> for ; Sun, 12 May 2013 12:56:15 -0400 Received: from [192.168.0.100] ([72.209.255.54]) by eastrmimpo306 with cox id b4wE1l00M1BBvFL014wEU6; Sun, 12 May 2013 12:56:14 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A02020A.518FC9AE.00D7,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=FMjFMZUs c=1 sm=1 a=DJcW3uYjUF7QOSDKTYkEUA==:17 a=YsUzL_8ObRgA:10 a=_bwt1_8owo4A:10 a=xmHE3fpoGJwA:10 a=8nJEP1OIZ-IA:10 a=8YJikuA2AAAA:8 a=G_z1siSQsB4A:10 a=-XF6XVQFaoMmKrqtvIUA:9 a=wPNLvfGTeEIA:10 a=dxBpO5_FDU0A:10 a=s1ZwAcS5I-bMi3ZE:21 a=xWvUwbA3xyLxw5lu:21 a=DJcW3uYjUF7QOSDKTYkEUA==:117 X-CM-Score: 0.00 Message-ID: <518FC9B5.1090805@lojban.org> Date: Sun, 12 May 2013 12:56:21 -0400 From: "Bob LeChevalier, President and Founder - LLG" Organization: The Logical Language Group, Inc. User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: lojban@googlegroups.com Subject: Re: [lojban] Higher-precedence Grouping with {bo} Is Impossible for TAG Sentence Connectives References: In-Reply-To: X-Original-Sender: lojbab@lojban.org X-Original-Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 68.230.241.217 is neither permitted nor denied by best guess record for domain of lojbab@lojban.org) smtp.mail=lojbab@lojban.org 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: text/plain; charset=ISO-8859-1; format=flowed X-Spam-Score: 0.0 (/) X-Spam_score: 0.0 X-Spam_score_int: 0 X-Spam_bar: / Jacob Errington wrote: > The title says it all; the following won't parse: > > {.i broda .ija'ebo brode .iseri'abobo brodi} > > Semantically, it should parse meaning that {.i brode .iseri'abo brodi} > is the right-hand operand of {.ija'ebo}. > > On a related note, even-higher-precedence grouping with bo is not > possible for ijeks; the following won't parse: > > .i (broda .ijebo (brode .ijebo ((brodi .ijebobo brodo) .ijebo brodu))) > > Parentheses show intended parse. > > Furthermore, multiple {bo} are not allowed in tanru groupings: > > {.i (broda bo ((brode bo bo brodi) bo brodo))} > > It just seems like multiple {bo} is illegal across the board. Bug or > feature? Could this even be implemented? If it can, should we? > > .i mi'e la tsani mu'o The first problem is that the parser does not allow multiple "bo"s. That is why it won't parse. Additional bos would have no meaning, grammatical or otherwise. If you use only one bo in each .i compound, then all of them will group pairwise STRICTLY from the right. So .i broda .ija'e brode .iseri'abo brodi groups .i broda .i(ja'e brode .iseri'abo brodi) Note that you don't need a bo at all before the brode. For your second example, this results: .i broda .ije( brode .ijebo( brodi .ijebo( brodo .ijebo brodu))) There is no provision using bo to make something other than the rightmost group first. If you want to mix left and right grouping, you need tu'e/tu'u forethought to mark the left groupings. See CLL chapter 14 section 8 example 8.3 through 8.6, which has good discussion of the whys and wherefores. The notes after 8.6 specificall say that afterthought connectives with bo are primarily for simple expression of the special case of right grouping. Anything really complex needs the bracketing that is possible with forethought connection (and I observe that human beings don't generally formulate complex groupings in afterthought). i broda .ije brode .ijetu'e brodi .ije brodo tu'u .ijebo brodu gives the bracketing you showed, with the brodi/brodo pair grouping left, marked by tu'e/tu'u. If you only used bo then you would parenthesize sentences from the right (and again you don't need a bo before the brode). Sentence logical connection is a difficult problem, especially when you try to account for logical scope, so it is designed to be less flexible. More broadly, really complex constructs are more easily expressed using gi'ebo/gi'eke for right and left grouping in afterthought, and ga/gi for forethought. Since these constructs connect multiple "bridi-tails" (selbri plus trailing sumti) within one .i sentence, for maximal flexibility, you have to but all the sumti including x1 after the selbri. These are also described in that same chapter of CLL. lojbab -- Bob LeChevalier lojbab@lojban.org www.lojban.org President and Founder, The Logical Language Group, Inc. -- You received this message because you are subscribed to the Google Groups "lojban" group. To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban?hl=en. For more options, visit https://groups.google.com/groups/opt_out.