Received: from mail-vc0-f189.google.com ([209.85.220.189]:34958) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1Svp3v-00043r-IJ; Mon, 30 Jul 2012 05:27:11 -0700 Received: by vcbfl10 with SMTP id fl10sf6416488vcb.16 for ; Mon, 30 Jul 2012 05:26:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:from:date:message-id:subject :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=2slJLbfu39vfyxkywytXzybqKfuNPEQXuKqx2ZSF4rk=; b=m1g9CEMBBCHkn2Q5fkP3xUdGJoHaXGft+a9+dFvbE2u1CMfeqxT9B0FEO4X+G4FCwF Jp6/ygyNd1MJ0Hfidp7uqE4zEPAW+fkHOdv0kdrRNIPxcq+6jGgUpcnh1m/VOFy2QI4b N6BVun1aIXwRYjBL0tt/U//Lv1IkcB/x5pv/Y= Received: by 10.52.66.137 with SMTP id f9mr783746vdt.14.1343651216808; Mon, 30 Jul 2012 05:26:56 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.52.100.135 with SMTP id ey7ls3464761vdb.6.gmail; Mon, 30 Jul 2012 05:26:56 -0700 (PDT) Received: by 10.52.33.1 with SMTP id n1mr15201328vdi.4.1343651216120; Mon, 30 Jul 2012 05:26:56 -0700 (PDT) Received: by 10.52.33.1 with SMTP id n1mr15201327vdi.4.1343651216108; Mon, 30 Jul 2012 05:26:56 -0700 (PDT) Received: from mail-vc0-f177.google.com (mail-vc0-f177.google.com [209.85.220.177]) by gmr-mx.google.com with ESMTPS id y4si1367136vds.2.2012.07.30.05.26.56 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 30 Jul 2012 05:26:56 -0700 (PDT) Received-SPF: pass (google.com: domain of nictytan@gmail.com designates 209.85.220.177 as permitted sender) client-ip=209.85.220.177; Received: by mail-vc0-f177.google.com with SMTP id fl13so5172668vcb.8 for ; Mon, 30 Jul 2012 05:26:56 -0700 (PDT) Received: by 10.52.71.137 with SMTP id v9mr9584013vdu.63.1343651215981; Mon, 30 Jul 2012 05:26:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.24.193 with HTTP; Mon, 30 Jul 2012 05:26:35 -0700 (PDT) From: Jacob Errington Date: Mon, 30 Jul 2012 08:26:35 -0400 Message-ID: Subject: [lojban] Afterthought TAG Termset Connectives To: lojban@googlegroups.com X-Original-Sender: nictytan@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of nictytan@gmail.com designates 209.85.220.177 as permitted sender) smtp.mail=nictytan@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=20cf307d03746e3cb204c60b2d41 X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / --20cf307d03746e3cb204c60b2d41 Content-Type: text/plain; charset=ISO-8859-1 Do these exist? The forethought version is grammatical: {.i nu'i ca gi zo .u'i ny nu'u gi zo .i'i cy selsku} Considering that afterthought TAG connectives take the form of <[connective] TAG bo> where [connective] is the connective of the appropriate connective selma'o, e.g. {mi .e ca bo do}, I would presume that the afterthought termset connective form would be <[sumti] pe'e je TAG bo [sumti]> where [sumti] is >=1 sumti. Unfortunately, of course, this does not parse in jbofi'e. Additionally, it would appear as though TAG connectives such as {.e ca bo} are not valid utterances by themselves, whereas bare connectives such as {.e} are. I'm not sure that this is desirable, but it does make it impossible to answer {ji}-questions and such with tag connectives. I can think of an example usage inspired by the CLL example of {ji}: {.i do djica tu'a lo tcati ji lo ckafi} "Would you like tea or coffee?" {.e ba bo} (English sucks for the answer:) "The former, then the latter." (This example is incidentally unaffected by the connective problem that usually arises when using connectives in non-top-level contexts like {tu'a ko'a .e ko'a}. The problem itself is that it's arguable as to whether {tu'a ko'a .e ko'e broda} is equivalent to {tu'a ko'a broda .ije tu'a ko'e broda} -> {lo su'u ko'a co'e cu broda .ije lo su'u ko'e co'e cu broda} or rather {lo su'u ko'a .e ko'e co'e cu broda}. A similar, more drastic case occurs in {lo pendo be mi .e do}, which we'd naturally assume is "the friend of both me and you" but it's arguable as to whether {lo pendo be mi .e do cu broda} is equivalent to {lo pendo be mi cu broda .ije lo pendo be do cu broda} or {zo'e noi pendo mi .e do cu broda}. My rationale behind supporting the latter interpretation is that using one descriptor should only create one description, whereas the former interpretation creates two descriptions behind the scenes, namely {lo pendo be mi} and {lo pendo be do} which could be referring to entirely different things. Additionally although less importantly, the latter interpretation seems far more natural, not to mention that to achieve the meaning of the former interpretation using the latter, one must necessarily employ the {zo'e noi} construction, which is unnecessarily cumbersome, whereas with the latter interpretation, one must simply repeat {lo pendo} such that {lo pendo be mi ku .e lo pendo be do}. The only apparent downside to the latter interpretation is that when using afterthought, in order to repeat the main description, a lot of terminators might be required, not to mention that if the description is fairly complex (a four-part tanru) it can become very annoying to repeat it.) Returning to the main point of this post, considering that termsets is a part of the language that everybody loves to hate, it's unlikely that afterthought tag termset connectives will ever see the light of day, but I don't think that the cmavo required for termsets are going to disappear any time soon (at least not before mekso, for which there remains proponents.) Therefore, I see no reason why this discrepancy between forethought and afterthought should exist. (Not to mention the impossible non-logical bridi-tail afterthought connective, which I wanted to use just today...) Could it be that afterthought tag termset connection was impossible due to a parser limitation? What with the PEG being capable of all sorts of things that the older grammars weren't, could this be implemented in the current grammar? As far as I can tell, making {pe'e JA TAG bo} grammatical breaks no usage at all. mu'o mi'e la tsani -- 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. --20cf307d03746e3cb204c60b2d41 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Do these exist?
The forethought version is grammatical:

<= /div>
{.i nu'i ca gi zo .u'i ny nu'u gi zo .i'i cy sels= ku}

Considering that afterthought TAG connectives = take the form of <[connective] TAG bo> where [connective] is the conn= ective of the appropriate connective selma'o, e.g. {mi .e ca bo do}, I = would presume that the afterthought termset connective form would be <[s= umti] pe'e je TAG bo [sumti]> where [sumti] is >=3D1 sumti. Unfor= tunately, of course, this does not parse in jbofi'e.

Additionally, it would appear as though TAG connectives= such as {.e ca bo} are not valid utterances by themselves, whereas bare co= nnectives such as {.e} are. I'm not sure that this is desirable, but it= does make it impossible to answer {ji}-questions and such with tag connect= ives. I can think of an example usage inspired by the CLL example of {ji}:= =A0
{.i do djica tu'a lo tcati ji lo ckafi} "Would you like tea o= r coffee?"
{.e ba bo} (English sucks for the answer:) "= The former, then the latter."

(This example i= s incidentally unaffected by the connective problem that usually arises whe= n using connectives in non-top-level contexts like {tu'a ko'a .e ko= 'a}. The problem itself is that it's arguable as to whether {tu'= ;a ko'a .e ko'e broda} is equivalent to {tu'a ko'a broda .i= je tu'a ko'e broda} -> {lo su'u ko'a co'e cu broda .= ije lo su'u ko'e co'e cu broda} or rather {lo su'u ko'a= .e ko'e co'e cu broda}.=A0

A similar, more drastic case occurs in {lo pendo be mi = .e do}, which we'd naturally assume is "the friend of both me and = you" but it's arguable as to whether {lo pendo be mi .e do cu brod= a} is equivalent to {lo pendo be mi cu broda .ije lo pendo be do cu broda} = or {zo'e noi pendo mi .e do cu broda}. My rationale behind supporting t= he latter interpretation is that using one descriptor should only create on= e description, whereas the former interpretation creates two descriptions b= ehind the scenes, namely {lo pendo be mi} and {lo pendo be do} which could = be referring to entirely different things.=A0Additionally although less imp= ortantly, the latter interpretation seems far more natural, not to mention = that to achieve the meaning of the former interpretation using the latter, = one must necessarily employ the {zo'e noi} construction, which is unnec= essarily cumbersome, whereas with the latter interpretation, one must simpl= y repeat {lo pendo} such that {lo pendo be mi ku .e lo pendo be do}. The on= ly apparent downside to the latter interpretation is that when using aftert= hought, in order to repeat the main description, a lot of terminators might= be required, not to mention that if the description is fairly complex (a f= our-part tanru) it can become very annoying to repeat it.)

Returning to the main point of this post, considering t= hat termsets is a part of the language that everybody loves to hate, it'= ;s unlikely that afterthought tag termset connectives will ever see the lig= ht of day, but I don't think that the cmavo required for termsets are g= oing to disappear any time soon (at least not before mekso, for which there= remains proponents.) Therefore, I see no reason why this discrepancy betwe= en forethought and afterthought should exist. (Not to mention the impossibl= e non-logical bridi-tail afterthought connective, which I wanted to use jus= t today...) Could it be that afterthought tag termset connection was imposs= ible due to a parser limitation? What with the PEG being capable of all sor= ts of things that the older grammars weren't, could this be implemented= in the current grammar? As far as I can tell, making {pe'e JA TAG bo} = grammatical breaks no usage at all.

mu'o mi'e la tsani

--
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.
--20cf307d03746e3cb204c60b2d41--