Received: from mail-wi0-f191.google.com ([209.85.212.191]:33060) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.80.1) (envelope-from ) id 1Ybcq3-0005Yd-Fh; Fri, 27 Mar 2015 15:34:56 -0700 Received: by wiwh11 with SMTP id h11sf12896969wiw.0; Fri, 27 Mar 2015 15:34:44 -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=IfLjxrVrVwt29k64eSvd5g+iQ6Wiu3buZ4ArvMKECvc=; b=Psuec+bKVcQoZGXYktS2QpMGwpRBSW3WEj+4Iie+YAr7eT3AQYDNbA8Cj0vyO5VTPR stVbceMh1yBf5Kg0cA9Xh91EvVXD7UjokKmdf2BzZhTlmXURU9zkyKjpQYSR+hwqUHlo eM2AnJeQ0qRjz6yY/4/oAt/1FPwS+OQCV2glmhztdu/IX6jP3ICuXO7Q0AcV9NX9xizD FbbHX4SIQ7yQoTt1Zv2Smx9kbqba3Xb2HTNvwkOpX4UQ/VJS5w4+VbPhyJL/ME1gChXM BC3A2ubaZpoSCmyeeZPlx13+HtM5lqWzb8yWWNQLKVdQDhBedH80zZoND42cGscBiA7Q omsQ== X-Received: by 10.180.211.208 with SMTP id ne16mr10522wic.4.1427495684387; Fri, 27 Mar 2015 15:34:44 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.180.91.72 with SMTP id cc8ls260313wib.6.canary; Fri, 27 Mar 2015 15:34:44 -0700 (PDT) X-Received: by 10.180.90.169 with SMTP id bx9mr250952wib.6.1427495684157; Fri, 27 Mar 2015 15:34:44 -0700 (PDT) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com. [2a00:1450:400c:c05::236]) by gmr-mx.google.com with ESMTPS id o3si215656wib.2.2015.03.27.15.34.44 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Mar 2015 15:34:44 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::236 as permitted sender) client-ip=2a00:1450:400c:c05::236; Received: by mail-wi0-x236.google.com with SMTP id g7so41719865wib.1 for ; Fri, 27 Mar 2015 15:34:44 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.94.164 with SMTP id dd4mr42502447wjb.56.1427495684083; Fri, 27 Mar 2015 15:34:44 -0700 (PDT) Received: by 10.27.86.219 with HTTP; Fri, 27 Mar 2015 15:34:44 -0700 (PDT) In-Reply-To: <5515264B.1030009@gmx.de> References: <5515264B.1030009@gmx.de> Date: Fri, 27 Mar 2015 19:34:44 -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=047d7bb041022b158f05124cbd24 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::236 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: 5175 --047d7bb041022b158f05124cbd24 Content-Type: text/plain; charset=UTF-8 On Fri, Mar 27, 2015 at 6:43 AM, selpa'i wrote: > > I'm actually a big fan of fragments; I use {to be} and {to noi} a lot, Yes, I forgot about fragments within to-toi, I have used many of those too. They still make me uncomfortable though. Something like fu'e-fu'o would seem to make more sense for that kind of thing. > and it's also nice when you want to add onto someone else's sentence, e.g. > > A: mi viska lo pendo > B: be ma > A: la .djan. > Could B say "be ma" if A had said "mi viska lo pendo ku"? or "mi viska lo pendo vau"? Even fragment {na} is sort of semi-common as a slang thing; in the > experimental grammar it was extended to allow multiple NA in a row as a > fragment as well. > If it was tanru-unit that was elidable, as gleki is suggesting, this would be just a case of "na [COhE]". I actually frequently miss a method to use a fragmental ?{to JOI SUMTI > toi}, but sadly it would clash with {.i joi}, so I'm stuck with {to ri JOI > SUMTI toi), which doesn't always work. > It would work with a fu'e-fu'o type parenthetical, instead of a to-toi type. > I find fragments very useful for spontaneous human speech. > I don't doubt that human speech is full of "broken sentences". I just don't like much the way "fragment" is implemented in Lojban's grammar. 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. --047d7bb041022b158f05124cbd24 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Fri, Mar 27, 2015 at 6:43 AM, selpa'i <seladwa@gmx.de> = wrote:

I'm actually a big fan of fragments; I use {to be} and {to noi} a lot, =

Yes, I forgot about fragments within to-to= i, I have used many of those too. They still make me uncomfortable though. = Something like fu'e-fu'o would seem to make more sense for that kin= d of thing.
=C2=A0
and it&#= 39;s also nice when you want to add onto someone else's sentence, e.g.<= br>
A: mi viska lo pendo
B: be ma
A: la .djan.

Could B say "be ma&qu= ot; if A had said "mi viska lo pendo ku"? or "mi viska lo pe= ndo vau"?

Even fragment {na} is sort of semi-common as a slang thing; in the experime= ntal grammar it was extended to allow multiple NA in a row as a fragment as= well.

If it was tanru-unit that was el= idable, as gleki is suggesting, this would be just a case of "na [COhE= ]".=C2=A0

I actually frequently miss a method to use a fragmental ?{to JOI SUMTI toi}= , but sadly it would clash with {.i joi}, so I'm stuck with {to ri JOI = SUMTI toi), which doesn't always work.

<= div>It would work with a fu'e-fu'o type parenthetical, instead of a= to-toi type.
=C2=A0
I find fragments very useful for spontaneous human speech.
=

I don't doubt that human speech is full of "br= oken sentences". I just don't like much the way "fragment&quo= t; is implemented in Lojban's grammar.=C2=A0

m= u'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.
--047d7bb041022b158f05124cbd24--