Received: from mail-la0-f55.google.com ([209.85.215.55]:34578) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.80.1) (envelope-from ) id 1YfcjI-0004A1-0Y; Tue, 07 Apr 2015 16:16:25 -0700 Received: by lamq1 with SMTP id q1sf24243171lam.1; Tue, 07 Apr 2015 16:16:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type: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; bh=4YyMVrWrRoINsPz8GicmJZepc0OkQlhLdOnE6hdA9mc=; b=bQNI9BRKfOOdMZwwwsynov/5bA7NMgaCclNeTBTD8ia7Cbk1HgYX97wz64TaP6rovS yLLI8n97wBeuEup9+vMt/BMe2y2xlIpzfRoWO8rloUodat8UiyLBvnheXAwT4NzyqNlC S918J836OB7rKvKZdKrHNGUtQA1vVo4BgYxZG8vN6mDFt9rgar7/7jl1OvsSut+xn0h8 e+Spm3dOkhPfm2xjijUeN63Ms8jiy4Ez51vyC6oa7uTfFCCg9ehNuf+GsBZ1yIj1/b5W u+ql18eKfG5k+3eRSUB96Z0OkgvpH1Tcs1I4jjD1js2ht+uuTl2wlsTzU/wDGaP0IxlQ +dLw== X-Received: by 10.180.91.6 with SMTP id ca6mr51327wib.18.1428448576412; Tue, 07 Apr 2015 16:16:16 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.180.77.199 with SMTP id u7ls106691wiw.44.canary; Tue, 07 Apr 2015 16:16:16 -0700 (PDT) X-Received: by 10.180.23.40 with SMTP id j8mr852488wif.2.1428448576084; Tue, 07 Apr 2015 16:16:16 -0700 (PDT) Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com. [2a00:1450:400c:c05::22f]) by gmr-mx.google.com with ESMTPS id g5si535668wix.1.2015.04.07.16.16.16 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Apr 2015 16:16:16 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::22f as permitted sender) client-ip=2a00:1450:400c:c05::22f; Received: by mail-wi0-x22f.google.com with SMTP id k4so35079001wiz.1 for ; Tue, 07 Apr 2015 16:16:16 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.192.167 with SMTP id hh7mr45093638wjc.151.1428448576012; Tue, 07 Apr 2015 16:16:16 -0700 (PDT) Received: by 10.27.56.18 with HTTP; Tue, 7 Apr 2015 16:16:15 -0700 (PDT) In-Reply-To: <5523DFCA.40002@gmail.com> References: <5523DFCA.40002@gmail.com> Date: Tue, 7 Apr 2015 20:16:15 -0300 Message-ID: Subject: Re: [bpfk] Proposal: sumti must always be tagged with "tag" even if it's elidible. From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= To: bpfk-list@googlegroups.com Content-Type: multipart/alternative; boundary=047d7b8743f8f406f505132a990b X-Original-Sender: jjllambias@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::22f as permitted sender) smtp.mail=jjllambias@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Reply-To: bpfk-list@googlegroups.com Precedence: list Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com List-ID: X-Google-Group-Id: 972099695765 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -1.7 (-) X-Spam_score: -1.7 X-Spam_score_int: -16 X-Spam_bar: - Content-Length: 6127 --047d7b8743f8f406f505132a990b Content-Type: text/plain; charset=UTF-8 On Tue, Apr 7, 2015 at 10:46 AM, Ilmen wrote: > abs_term = "absorbable term", "term that becomes a selbritcita when > followed by a selbri". > > I implemented this absorbable/non-absorbable term grammar split in order > to implement the standard behavior of selbritcita as per Jbofihe; that is, > {lo nu brodo ba brode} parses as {lo nu brodo ba CU brode} in the standard > version of Camxes; however, {mi ba brode gi'e pu brodo} parses as {mi CU ba > brode gi'e pu brodo}, so the behavior of "ba" varies depending on its > environment: if "ba" is within a bridi-tail, it is non-absorbable (it > cannot become a selbritcita), but if it is in a bridi-head, it is > absorbable as a selbritcita. > Does "mi ba brode gi'e pu brodo" parse as "mi CU ba brode gi'e pu brodo" and not as "mi ba (ku) CU brode gi'e pu brodo" in standard camxes? I think it's the latter. "tag selbri" _should_ have priority over "tag (ku) selbri", but I don't think it does in current camxes. Does Jbofihe use camxes? I thought it didn't, but this page doesn't say: http://mw.lojban.org/papri/jbofi%27e I know this tag grammar split is rather ugly, but at this time I hadn't > been able to find a better solution. Any alternative implementation is > welcomed. > Which sentence currently uses "term" but couldn't use "abs_term" instead? Hmm, I just looked, and it seems that gek_termset, LAhE term, and BE term could have a (slight) problem, in the sense that KU would not be elidible in "ge ca (ku) gi ba (ku) broda", "la'e ba (ku) broda", "broda be ba (ku) brode". (BTW, "ge ca (ku) gi ba (ku) klama" seems to be failing if we elide the first "ku".) Maybe it's better to just make the KU of "tag KU" not elidible in those three special contexts (are there more?). mu'o mi'e xorxes -- You received this message because you are subscribed to the Google Groups "BPFK" group. To unsubscribe from this group and stop receiving emails from it, send an email to bpfk-list+unsubscribe@googlegroups.com. To post to this group, send email to bpfk-list@googlegroups.com. Visit this group at http://groups.google.com/group/bpfk-list. For more options, visit https://groups.google.com/d/optout. --047d7b8743f8f406f505132a990b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Tue, Apr 7, 2015 at 10:46 AM, Ilmen <ilmen.pokebip@gmail.com&= gt; wrote:
=20 =20 =20
abs_term =3D "absorbable t= erm", "term that becomes a selbritcita when followed by a selbri".

I implemented this absorbable/non-absorbable term grammar split in order to implement the standard behavior of selbritcita as per Jbofihe; that is, {lo nu brodo ba brode} parses as {lo nu brodo ba CU brode} in the standard version of Camxes; however, {mi ba brode gi'e pu brodo} parses as {mi CU ba brode gi'e pu brodo}, so the behavior of "ba" varies depending on its environment: if &quo= t;ba" is within a bridi-tail, it is non-absorbable (it cannot become a selbritcita), but if it is in a bridi-head, it is absorbable as a selbritcita.

Does "mi ba= brode gi'e pu brodo" parse as "mi CU ba brode gi'e pu br= odo" and not as "mi ba (ku) CU brode gi'e pu brodo" in s= tandard camxes?=C2=A0 I think it's the latter. "tag selbri" _= should_ have priority over "tag (ku) selbri", but I don't thi= nk it does in current camxes.

Does Jbofihe use cam= xes? I thought it didn't, but this page doesn't say: http://mw.lojban.org/papri/jbofi%27e=

I know this tag grammar split is rather ugly, but at this time I hadn't been able to find a better solution. Any alternative implementation is welcomed.

Which= sentence currently uses "term" but couldn't use "abs_te= rm" instead? Hmm, I just looked, and it seems that gek_termset, LAhE t= erm, and BE term could have a (slight) problem, in the sense that KU would = not be elidible in "ge ca (ku) gi ba (ku) broda", "la'e = ba (ku) broda", "broda be ba (ku) brode".

(BTW, "ge ca (ku) gi ba (ku) klama" seems to be failing if= we elide the first "ku".)

Maybe it&= #39;s better to just make the KU of "tag KU" not elidible in thos= e three special contexts (are there more?).

mu'= ;o mi'e xorxes

--
You received this message because you are subscribed to the Google Groups &= quot;BPFK" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bpfk-list= +unsubscribe@googlegroups.com.
To post to this group, send email to bpfk-list@googlegroups.com.
Visit this group at ht= tp://groups.google.com/group/bpfk-list.
For more options, visit http= s://groups.google.com/d/optout.
--047d7b8743f8f406f505132a990b--