Received: from mail-la0-f61.google.com ([209.85.215.61]:33684) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.80.1) (envelope-from ) id 1YfHfY-000594-9p; Mon, 06 Apr 2015 17:47:09 -0700 Received: by labgd6 with SMTP id gd6sf13479213lab.0; Mon, 06 Apr 2015 17:47:01 -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=pMUbxOFVcaRf28mOEMTYuMTjXuMgqv46bYbAUZiLGKw=; b=jzTat4iUB5TQy+OAsdJTjMeCqzTQE55bOQ7UgkrMFGKVhq53H8OeHUEIbfMokRorqc xxskDofN1S4FBBnIJPaYxTZ1+feFDnPIEcAQ2NIXvPjHUngeQlvicUG7QYyeY2w5dxkw yiayZw8uHE68G7AtkT/VY+zpg9PhcRTk5RxkaeJa/WBx1i/idSRpZjq8cE02RbP1dJ8L 90x85WLeI/QTPIePw+CUA/SNuT8f2bqE1HUdc0xFrK1/Bt2UIji6G0r7+lGUW6Upfajp T7aQBJKjwKVwizIoRpfcaXXqZRXyfJ55hqP9i9hEruXAZuiV2EaQksGaBKUjtajyXoOM JS2w== X-Received: by 10.180.75.105 with SMTP id b9mr12605wiw.17.1428367620959; Mon, 06 Apr 2015 17:47:00 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.180.83.65 with SMTP id o1ls599494wiy.47.canary; Mon, 06 Apr 2015 17:47:00 -0700 (PDT) X-Received: by 10.180.91.76 with SMTP id cc12mr166753wib.7.1428367620658; Mon, 06 Apr 2015 17:47:00 -0700 (PDT) Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com. [2a00:1450:400c:c05::230]) by gmr-mx.google.com with ESMTPS id ec7si323898wib.3.2015.04.06.17.47.00 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Apr 2015 17:47:00 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::230 as permitted sender) client-ip=2a00:1450:400c:c05::230; Received: by mail-wi0-x230.google.com with SMTP id di4so3026164wid.0 for ; Mon, 06 Apr 2015 17:47:00 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.192.167 with SMTP id hh7mr35367204wjc.151.1428367620585; Mon, 06 Apr 2015 17:47:00 -0700 (PDT) Received: by 10.27.56.18 with HTTP; Mon, 6 Apr 2015 17:47:00 -0700 (PDT) In-Reply-To: <55231E87.1040600@gmx.de> References: <55231E87.1040600@gmx.de> Date: Mon, 6 Apr 2015 21:47:00 -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=047d7b8743f8a240dd051317c0ad 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::230 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: 5622 --047d7b8743f8a240dd051317c0ad Content-Type: text/plain; charset=UTF-8 On Mon, Apr 6, 2015 at 9:02 PM, selpa'i wrote: > la .xorxes. cu cusku di'e > >> What does the SOI term mean? Is there a new proposed meaning for "soi"? >> Is it something like "lo poi'i"? >> > > See: http://mw.lojban.org/index.php?title=new_soi ua je'e .i'e .i simlu lo ka xamgu .i simsa lo'u se kai lo ka le'u BTW, are there any plans to get rid of SA, or are people still in love >> with it? It makes the grammar so much harder to read. >> > > Almost all uses of {sa} are in {sa .i}, so maybe we could simplify {sa} by > making it just remove the current sentence entirely. > Even that would have its complications, but it would be better than the pehe_sa's and cehe-sa's I'm seeing now. Another option would be to make SA+sentence or SA+term or maybe SA+word a > free modifier (I'm not sure how exactly that would play out though). > That wouldn't work to "fix" broken sentences, which seems to be one of its main uses. In any case, I agree that SA adds a lot of annoying complexity to the > grammar (even though it's kind of a nice mechanism to have). The original SA-"any selma'o" was unwieldly because of the huge number of selma'o that Lojban has, but at least in some sense was not arbitrary. The current version requires knowing which constructs are SA-erasable and which are not, which seems like a fairly arbitrary collection. Maybe I'm just too prejudiced against it, but I really don't like it. 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. --047d7b8743f8a240dd051317c0ad Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Mon, Apr 6, 2015 at 9:02 PM, selpa'i <seladwa@gmx.de> wrote:
la .xorxes. cu cusku di'e
What does the SOI term mean? Is there a new proposed meaning for "soi&= quot;?
Is it something like "lo poi'i"?

See: http://mw.lojban.org/index.php?title=3Dnew_soi

ua je'e .i'e .i simlu lo ka xamgu .i simsa lo= 'u se kai lo ka le'u=C2=A0

BTW, are there any plans to get rid of SA, or are people still in love
with it? It makes the grammar so much harder to read.

Almost all uses of {sa} are in {sa .i}, so maybe we could simplify {sa} by = making it just remove the current sentence entirely.
<= br>
Even that would have its complications, but it would be bette= r than the pehe_sa's and cehe-sa's I'm seeing now.=C2=A0
<= div>
Another option would be to make SA+sentence or SA+term or maybe SA+word a f= ree modifier (I'm not sure how exactly that would play out though).
=

That wouldn't work to "fix" = broken sentences, which seems to be one of its main uses.

In any case, I agree that SA adds a lot of annoying complexity to the gramm= ar (even though it's kind of a nice mechanism to have).

The original SA-"any selma'o" was unwieldly = because of the huge number of selma'o that Lojban has, but at least in = some sense was not arbitrary. The current version requires knowing which co= nstructs are SA-erasable and which are not, which seems like a fairly arbit= rary collection. Maybe I'm just too prejudiced against it, but I really= don't like it.

mu'o mi'e xorxes=C2=A0=

--
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.
--047d7b8743f8a240dd051317c0ad--