Received: from mail-wg0-f55.google.com ([74.125.82.55]:33974) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.80.1) (envelope-from ) id 1YbHjK-000549-C1; Thu, 26 Mar 2015 17:02:34 -0700 Received: by wghl2 with SMTP id l2sf27048278wgh.1; Thu, 26 Mar 2015 17:02:23 -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=iZ8ruiGCCZwiRfjgrWt/pxr7VDlqHvHnmjjtK+ke41k=; b=MJd1eMK3X0UmvPCeHIhAx3HSKTKFnnMl+3KawPi4SwBcqomlCo0LxdV5fUtfAiigOc Myi0aUkCxEtjoEB57rPX37kQ7lAV32MT5jFrwaTx3uSHnpdqAQgeSmv6MEJWxY+QaFQu YzMcShNpBRp0er/6DtTGM/+mOwyQ8ey75e+MvCtMZTPUDsxIQyX/uvW5Gd29aSF43v21 hp/R0NoemLu3fX5rtCVMV91HzKqM4Da+zlbHZojZYgFxBlbr07o5qxNs7whihKkqVELx 181Ppa0FkI1hVq3K/+jC+9nLjvcMOR8oker4NiFj0crnCTxGyGgzDHAbWF5b8JsmbjBf F0Qg== X-Received: by 10.152.219.36 with SMTP id pl4mr61217lac.20.1427414543523; Thu, 26 Mar 2015 17:02:23 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.152.5.104 with SMTP id r8ls287703lar.48.gmail; Thu, 26 Mar 2015 17:02:23 -0700 (PDT) X-Received: by 10.112.181.166 with SMTP id dx6mr3896045lbc.17.1427414543007; Thu, 26 Mar 2015 17:02:23 -0700 (PDT) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com. [2a00:1450:400c:c05::22e]) by gmr-mx.google.com with ESMTPS id o3si38865wib.2.2015.03.26.17.02.22 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Mar 2015 17:02:22 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::22e as permitted sender) client-ip=2a00:1450:400c:c05::22e; Received: by mail-wi0-x22e.google.com with SMTP id g7so27957273wib.1 for ; Thu, 26 Mar 2015 17:02:22 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.108.203 with SMTP id hm11mr50682469wib.49.1427414542900; Thu, 26 Mar 2015 17:02:22 -0700 (PDT) Received: by 10.27.86.219 with HTTP; Thu, 26 Mar 2015 17:02:22 -0700 (PDT) In-Reply-To: References: Date: Thu, 26 Mar 2015 21:02:22 -0300 Message-ID: Subject: Re: [bpfk] Improvements to fragments in ilmentufa parser From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= To: bpfk-list@googlegroups.com Content-Type: multipart/alternative; boundary=e89a8f3ba93dc6e70b051239d891 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::22e 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: 7449 --e89a8f3ba93dc6e70b051239d891 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Mar 26, 2015 at 4:30 AM, Gleki Arxokuna wrote: > > 2015-03-26 1:04 GMT+03:00 Jorge Llamb=C3=ADas : >> >> On Wed, Mar 25, 2015 at 6:35 AM, Gleki Arxokuna < >> gleki.is.my.name@gmail.com> wrote: >>> >>> >>> E.g. I suppose COhE_elidible should be inserted to more constructs. but >>> I haven't looked at where it can be done. What else apart from what has >>> been done can be autocorrected to bridi status? >>> >> >> Every fragment can. For example instead of fragment "ek" you could have >> "KOhA_elidable ek KOhA_elidable COhE.elidable", where KOhA_elidable coul= d >> return "ZOhE". >> > > Not sure I would use that. How would this work for joik? {joi} fragment > could be understood both as {zo'e joi zo'e co'e} and as {co'e joi co'e} > "joi" can't be a fragment though. The reason is that it would clash with the sentence connective ".i joi". Fragment is a weird rule, I would happily remove relative clauses, links and linkargs from it. I don't think fragment "na" is used much either. > Okay, then I'll add > fragment =3D COhE_fragment / ek free* / gihek free* / quantifier / > (NA_clause !JA_clause free*)+ / relative_clauses / links / linkargs > > COhE_fragment =3D prenex (terms GOhA_elidible VAU_elidible free*)* / term= s > GOhA_elidible VAU_elidible free* > > sentence =3D terms? bridi_tail_t1 (joik_jek bridi_tail / joik_jek stag? > KE_clause free* bridi_tail KEhE_elidible free*)* / COhE_fragment > > Thus only COhE_fragment can be a sentence, and the structure of > COhE_fragment is limited only to {mi zo'u ca ma}, {mi ije ma} and {mi dji= ca > lo nu lo plise}. > I wonder whether it wouldn't be more elegant to eliminate COhE_fragment and make the "selbri" of a bridi-tail elidable instead. Something like: bridi-tail-3 <- selbri? tail-terms / gek-sentence At some point there was talk of making the selbri of a sumti-tail elidable as well, so that "lo ku" would be a valid sumti. mu'o mi'e xorxes --=20 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 e= mail 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. --e89a8f3ba93dc6e70b051239d891 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Thu, Mar 26, 2015 at 4:30 AM, Gleki Arxokuna <<= a href=3D"mailto:gleki.is.my.name@gmail.com" target=3D"_blank">gleki.is.my.= name@gmail.com> wrote:
2015-03-2= 6 1:04 GMT+03:00 Jorge Llamb=C3=ADas <jjllambias@gmail.com>:
On Wed, Mar 25, 2015 at 6:35 AM, Gleki Arxokuna <gleki.is.my.name@gmail.com> wrote:

E.g.=C2=A0I suppose COhE_elidible should = be inserted to more constructs. but I haven't looked at where it can be= done. What else apart from what has been done can be autocorrected to brid= i status?

Every fragment= can. For example instead of fragment "ek" you could have "K= OhA_elidable ek KOhA_elidable COhE.elidable", where KOhA_elidable coul= d return "ZOhE".=C2=A0
<= br>
Not sure I would use that. How would this work for joi= k? {joi} fragment could be understood both as {zo'e joi zo'e co'= ;e} and as {co'e joi co'e}

"joi" can't be a fragment though. The reason = is that it would clash with the sentence connective ".i joi". Fra= gment is a weird rule, I would happily remove relative clauses, links and l= inkargs from it. I don't think fragment "na" is used much eit= her.
=C2=A0=C2=A0
Okay, then I'll add<= /div>
fragment =3D COhE_fragment / ek free* / gihek free* / quanti= fier / (NA_clause !JA_clause free*)+ / relative_clauses / links / linkargs<= /div>

COhE_fragment =3D prenex (terms GOhA_elidible VAU_elidi= ble free*)* / terms GOhA_elidible VAU_elidible free*
sentence =3D terms? bridi_tail_t1 (joik_jek bridi_tail / joik_j= ek stag? KE_clause free* bridi_tail KEhE_elidible free*)* / COhE_fragment

Thus only COhE_fragment can be a sentence, an= d the structure of COhE_fragment is limited only to {mi zo'u ca ma}, {m= i ije ma} and {mi djica lo nu lo plise}.

I wonder whether it wouldn't be more elegant to e= liminate COhE_fragment and make the "selbri" of a bridi-tail elid= able instead. Something like:

=C2=A0bridi-tail-3 <- selbri? tail-ter= ms / gek-sentence

At some point there was talk of making the selbri of a sumti= -tail elidable as well, so that "lo ku" would be a valid sumti.

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.
--e89a8f3ba93dc6e70b051239d891--