Received: from mail-la0-f64.google.com ([209.85.215.64]:33773) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.80.1) (envelope-from ) id 1YfzEg-0007Yj-Bf; Wed, 08 Apr 2015 16:18:19 -0700 Received: by labgd6 with SMTP id gd6sf34967774lab.0; Wed, 08 Apr 2015 16:18:10 -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=kkJit5ciwksW4GDbz6DtOmyPOsIhEfiz5wcJ0ZihZMo=; b=Ni/tPPYtQXXeRsyQ15dm6vdgFEQMlSF8FXoRaiEn/UYmZXdvogSlRtuRrlRi3vKMlb s4LNexu/Qa78kGIQkJ3hQ2+2+8/a3uBTdG3Hi8WGAI87UWwd+DEbILPte12Xni55S0SV gtqJWXaMG/X/AtuYWaaqcm69DHPsvkCt1Ntzlz+6ijv8pdIFTb4RyD1oLOyK1mN/ZTBA F2UDQKOKuWdCcHfnbPfy3KmTLiyu+y0l8Pgf4hthHwTwPnYPYGPhMG5ijkKlbY3v+MRJ GOEf5S1XIawKMCqFqR4C+HY6kY3BrsthcW8+yXTjyL68KHO2DFmLdzE3bVuAbMHtgXdC Knbw== X-Received: by 10.152.36.34 with SMTP id n2mr42258laj.30.1428535090873; Wed, 08 Apr 2015 16:18:10 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.152.43.82 with SMTP id u18ls273522lal.79.gmail; Wed, 08 Apr 2015 16:18:10 -0700 (PDT) X-Received: by 10.112.46.172 with SMTP id w12mr3635723lbm.18.1428535090282; Wed, 08 Apr 2015 16:18:10 -0700 (PDT) Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com. [2a00:1450:400c:c00::233]) by gmr-mx.google.com with ESMTPS id sf8si706408wic.2.2015.04.08.16.18.10 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Apr 2015 16:18:10 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c00::233 as permitted sender) client-ip=2a00:1450:400c:c00::233; Received: by mail-wg0-x233.google.com with SMTP id k9so80856173wgs.3 for ; Wed, 08 Apr 2015 16:18:10 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.63.16 with SMTP id c16mr55300754wjs.117.1428535090181; Wed, 08 Apr 2015 16:18:10 -0700 (PDT) Received: by 10.27.56.18 with HTTP; Wed, 8 Apr 2015 16:18:10 -0700 (PDT) In-Reply-To: <55258F43.5060402@gmail.com> References: <5523DFCA.40002@gmail.com> <55258F43.5060402@gmail.com> Date: Wed, 8 Apr 2015 20:18:10 -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=047d7b86da3a997b4605133ebe2c 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:c00::233 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.6 (-) X-Spam_score: -1.6 X-Spam_score_int: -15 X-Spam_bar: - Content-Length: 5295 --047d7b86da3a997b4605133ebe2c Content-Type: text/plain; charset=UTF-8 On Wed, Apr 8, 2015 at 5:27 PM, Ilmen wrote: Standard Camxes.js: ([mi CU] [{ba brode} VAU] [gi'e { VAU} VAU]) > Neither this: http://www.lojban.org/camxes/ nor this: http://users.digitalkingdom.org/~rlpowell/hobbies/lojban/grammar/lojban.peg.txt seem to agree with that, so I suppose those are older versions of standard camxes. But I'm glad the new standard has "tag !selbri KU?". (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?). > > Yeah, I've noticed this flaw a few days ago. I'm not sure whether this can > be fixed. > I guess it's because "ca gi" wants to be a gek, so "ge ca gi" is like "ge ge". In order to "fix" it (if we grant it needs to be fixed, which I'm not sure we should) we may need to change the "stag gik" rule in "gek" to something like "stag gik &gek_tail", with gek_tail = subsentence gik subsentence / sumti gik sumti_4 / ... with all the possible uses of a "true gek". But I don't think we want to do that. 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. --047d7b86da3a997b4605133ebe2c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Wed, Apr 8, 2015 at 5:27 PM, Ilmen <ilmen.pokebip@gmail.com> wrote:

=20 =20 =20
Standard Camxes.js: ([mi CU] [{= ba brode} VAU] [gi'e {<pu brodo> VAU} VAU])

seem to agree with that, so I suppose th= ose are older versions of standard camxes.

But= I'm glad the new standard has "tag !selbri KU?".
<= br>
<= blockquote type=3D"cite">
(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&= quot; not elidible in those three special contexts (are there more?).
Yeah, I've noticed this flaw a few days ago. I'm not sure wheth= er this can be fixed.

=C2=A0I guess = it's because "ca gi" wants to be a gek, so "ge ca gi&quo= t; is like "ge ge".=C2=A0

In order to &q= uot;fix" it (if we grant it needs to be fixed, which I'm not sure = we should) we may need to change the "stag gik" rule in "gek= " to something like "stag gik &gek_tail", with

gek_tail =3D subsentence gik subsentence / sumti gik sumti_= 4 / ...

with all the possible uses of a "true= gek". But I don't think we want to do that.

<= 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.
--047d7b86da3a997b4605133ebe2c--