Received: from mail-lb0-f191.google.com ([209.85.217.191]:32990) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.80.1) (envelope-from ) id 1Yl46C-00038u-41; Wed, 22 Apr 2015 16:30:35 -0700 Received: by lbio15 with SMTP id o15sf596006lbi.0; Wed, 22 Apr 2015 16:30:24 -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=ctXH0rAx2+4CCxiLysvxp+ZKJtSGeZkx+938yWhVenY=; b=DTd0McHj9GpiuyTEnr7jtVmEd2UPKCVN0sQIMzZrCRp77igV/4mKp5tz88BCRp0yVA bUIqEVHNCTHuf/HFv1Ag0mSDbzFJMxPXGBHdgG1E0IxeI9MA+25AUpzKqdRMj4OCDaf/ HoD1Ln8HVXXW8Q5RxB4xvewkjJXg6bubrQ7owty1s36DCro6gmnPqCEce1mPqtMW2d23 30dtdMIRxOCS7tw+zJTZ3Rl7d4eo4sAVmFZ/FQXAhgd05QOidOhtosRN+Z1Jez8HUsBg 3npNn6ErAIRkaXd9P0gcR18lxvVmdhQc2ERk19h6PVVfYAoT+LPeZPaW2xw0YnPRDdUL gUgQ== X-Received: by 10.152.228.170 with SMTP id sj10mr324lac.20.1429745424876; Wed, 22 Apr 2015 16:30:24 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.152.116.38 with SMTP id jt6ls292976lab.101.gmail; Wed, 22 Apr 2015 16:30:24 -0700 (PDT) X-Received: by 10.112.29.39 with SMTP id g7mr13175lbh.1.1429745424161; Wed, 22 Apr 2015 16:30:24 -0700 (PDT) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com. [2a00:1450:400c:c05::22a]) by gmr-mx.google.com with ESMTPS id gt9si428130wib.2.2015.04.22.16.30.24 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Apr 2015 16:30:24 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::22a as permitted sender) client-ip=2a00:1450:400c:c05::22a; Received: by mail-wi0-x22a.google.com with SMTP id n10so74315804wiu.1 for ; Wed, 22 Apr 2015 16:30:24 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.63.80 with SMTP id e16mr68104wjs.56.1429745424084; Wed, 22 Apr 2015 16:30:24 -0700 (PDT) Received: by 10.27.56.18 with HTTP; Wed, 22 Apr 2015 16:30:24 -0700 (PDT) In-Reply-To: References: Date: Wed, 22 Apr 2015 20:30:24 -0300 Message-ID: Subject: Re: [bpfk] tagged termsets From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= To: bpfk-list@googlegroups.com Content-Type: multipart/alternative; boundary=047d7b86dae21f33150514588cbf 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::22a 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: -2.3 (--) X-Spam_score: -2.3 X-Spam_score_int: -22 X-Spam_bar: -- Content-Length: 4856 --047d7b86dae21f33150514588cbf Content-Type: text/plain; charset=UTF-8 On Wed, Apr 22, 2015 at 8:17 PM, Alex Burka wrote: > I apologize if I'm bringing up a sore subject that's been discussed > before. > I don't remember this being discussed before. > But I found a parsing difference between jbofi'e and camxes: > > Text in question: {bai nu'i ge da gi de}, i.e. a forethought termset > inside (or so I thought) a modal tag > > jbofi'e output: (0[{bai } VAU])0 > camxes output: ([{bai KU} {nu'i ge da NUhU gi de NUhU}] VAU) > Clearly a bug in jbofi'e. A termset is a set (sequence) of terms, and terms are already tagged, they cannot be tagged a second time. > Apparently, jbofi'e regards the termset as inside the modal, while camxes > doesn't. This seems quite significant, since if I added a selbri {bai nu'i > ge da gi de broda}, the x1 of broda is either {zo'e} or {da}+{de}, > depending on whether the termset is encapsulated by the modal or not. > YACC/EBNF grammar agrees with camxes. Is this a known parsing difference? Is it related to gek-termsets? Do I > simply still not understand termsets? > I don't think it's related to gek-termsets, no. 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. --047d7b86dae21f33150514588cbf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Wed, Apr 22, 2015 at 8:17 PM, Alex Burka <durka42@gmail.com>= wrote:
I apologize if I'm bringing up a sore subject that's been= discussed before.

I don't remem= ber this being discussed before.
=C2=A0
But I found a parsing differ= ence between jbofi'e and camxes:

Text in question: {= bai nu'i ge da gi de}, i.e. a forethought termset inside (or so I thoug= ht) a modal tag

jbofi'e output:=C2=A0(0[{bai &= lt;nu'i (1[ge da gi de] NU'U)1>} VAU])0
camxes output:= =C2=A0([{bai KU} {nu'i ge da NUhU gi de NUhU}] VAU)

Clearly a bug in jbofi'e. A termset is a set (= sequence) of terms, and terms are already tagged, they cannot be tagged a s= econd time.=C2=A0
=C2=A0
Apparently, jbofi'e regards the te= rmset as inside the modal, while camxes doesn't. This seems quite signi= ficant, since if I added a selbri {bai nu'i ge da gi de broda}, the x1 = of broda is either {zo'e} or {da}+{de}, depending on whether the termse= t is encapsulated by the modal or not.

YACC/EBNF grammar agrees with camxes.=C2=A0

Is thi= s a known parsing difference? Is it related to gek-termsets? Do I simply st= ill not understand termsets?

I = don't think it's related to gek-termsets, no.

<= div>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.
--047d7b86dae21f33150514588cbf--