Received: from mail-yx0-f191.google.com ([209.85.213.191]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1P52yg-0005MR-GK; Sun, 10 Oct 2010 13:58:47 -0700 Received: by yxh35 with SMTP id 35sf2471545yxh.28 for ; Sun, 10 Oct 2010 13:58:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:received:x-beenthere:received:received:received :received:received-spf:received:mime-version:received:received:date :message-id:subject:from:to: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:content-type; bh=+DNvAZVXRhyCLpV+fRecT/JGBJSOn2NrYgGbU1W5ibk=; b=dWQ99sH6WwgGxOMMqraPdgLy2RAkCsoIjPrXuYPR92F7qv+/ZTkyPDJshZeaoK+4Ta 3Ngcr/IGBpRc8TQpK13NJfeD8XIer6rIXR3OVgPCHMEB/wv3IBfXBoUzwufgnUAv1CUU X3LqO+ycJACOvJT5zPxSO+k3khywD2q2wvnt8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:date:message-id:subject:from :to: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:content-type; b=PFIeEnV9YcJFZE3pOY97J2DMyWZPyXtY6o6PKmCGM3WdM49iZI2Si35bOVhSHM3AFK yes7LO6wpT2DlKYh0AwIZIsSoelUNutnxJ/wVhqJD62OL4GmcbdJ8xZfcbYGWz+5tAie 08FNb0wDD6fYOKUR6/pGMYjBqiCc/N/xH0LLo= Received: by 10.91.34.32 with SMTP id m32mr191111agj.49.1286744310757; Sun, 10 Oct 2010 13:58:30 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.231.123.203 with SMTP id q11ls1405354ibr.2.p; Sun, 10 Oct 2010 13:58:30 -0700 (PDT) Received: by 10.231.183.11 with SMTP id ce11mr1395597ibb.5.1286744310544; Sun, 10 Oct 2010 13:58:30 -0700 (PDT) Received: by 10.231.183.11 with SMTP id ce11mr1395596ibb.5.1286744310509; Sun, 10 Oct 2010 13:58:30 -0700 (PDT) Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by gmr-mx.google.com with ESMTP id cm31si3888088ibb.3.2010.10.10.13.58.29; Sun, 10 Oct 2010 13:58:29 -0700 (PDT) Received-SPF: pass (google.com: domain of eyeonus@gmail.com designates 209.85.214.172 as permitted sender) client-ip=209.85.214.172; Received: by mail-iw0-f172.google.com with SMTP id 10so5025091iwn.17 for ; Sun, 10 Oct 2010 13:58:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.35.131 with SMTP id p3mr488221ibd.177.1286744309313; Sun, 10 Oct 2010 13:58:29 -0700 (PDT) Received: by 10.231.206.68 with HTTP; Sun, 10 Oct 2010 13:58:29 -0700 (PDT) Date: Sun, 10 Oct 2010 14:58:29 -0600 Message-ID: Subject: [bpfk] {.i} and {ni'o}, continuation or new jufra From: Jonathan Jones To: bpfk-list@googlegroups.com X-Original-Sender: eyeonus@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of eyeonus@gmail.com designates 209.85.214.172 as permitted sender) smtp.mail=eyeonus@gmail.com; dkim=pass (test mode) header.i=@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: List-Post: , List-Help: , List-Archive: Sender: bpfk-list@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=00032557a2ba7930cc0492498152 Content-Length: 6036 --00032557a2ba7930cc0492498152 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable This thread is so completely unrelated to BPFK work that I feel we really ought to move it to a new thread by now. On Sun, Oct 10, 2010 at 2:54 PM, Jonathan Jones wrote: > 2010/10/10 Jorge Llamb=EDas > >> On Sun, Oct 10, 2010 at 5:37 PM, Robert LeChevalier >> wrote: >> >> > >> > The problem I thought was being discussed was how to identify somethin= g >> as >> > syntactically part of someone else's text. >> >> You seemed to be arguing that that was the case by default, and you >> needed a FAhO to break that default, which is contrary to everything I >> have ever learned about Lojban. >> >> Let me put it this way: >> >> A: (something that parses correctly on its own) >> B: (something that parses correctly on its own) >> >> My default assumption is that what A said is one text, and what B said >> is another text. In some special cases, B may be adding something to >> A's text, but normally they are just responding to A's text with their >> own new text. >> >> That's the Lojban I have learned starting from your lessons. Is that >> not your current understanding too? >> >> mu'o mi'e xorxes >> > > If what B says is parsable, but would cause jbofi'e to say "selbri may be > missing on line x column x", then I would probably assume that it is a > continuation. That's the first thing I look for to determine if the new > speaker's utterance is a case of continuation or of an elided {.i}. Howev= er, > that assumption really depends on context more than anything else. > > > -- > mu'o mi'e .aionys. > > .i.a'o.e'e ko cmima le bende pe lo pilno be denpa bu .i doi luk. mi patfu > do zo'o > (Come to the Dot Side! Luke, I am your father. :D ) > > In the case of: A: [bridi] B: [bridi] I would likely assume B was not continuing A's jufra, as if they had said: A: .i [bridi] B: .i [bridi] --=20 mu'o mi'e .aionys. .i.a'o.e'e ko cmima le bende pe lo pilno be denpa bu .i doi luk. mi patfu d= o zo'o (Come to the Dot Side! Luke, I am your father. :D ) --=20 You received this message because you are subscribed to the Google Groups "= BPFK" group. To post to this group, send email to bpfk-list@googlegroups.com. To unsubscribe from this group, send email to bpfk-list+unsubscribe@googleg= roups.com. For more options, visit this group at http://groups.google.com/group/bpfk-l= ist?hl=3Den. --00032557a2ba7930cc0492498152 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable This thread is so completely unrelated to BPFK work that I feel we really o= ught to move it to a new thread by now.

O= n Sun, Oct 10, 2010 at 2:54 PM, Jonathan Jones <eyeonus@gmail.com> wrote:
2010/10/10 Jorge Llamb=EDas &= lt;jjllambias@gma= il.com>
On Sun, Oct 10, 2010 at 5:37 PM, Robert LeChevalier <lojbab@lojban.org> wrote:
>
> The problem I thought was being discussed was how to identify somethin= g as
> syntactically part of someone else's text.

You seemed to be arguing that that was the ca= se by default, and you
needed a FAhO to break that default, which is contrary to everything I
have ever learned about Lojban.

Let me put it this way:

A: =A0(something that parses correctly on its own)
B: =A0(something that parses correctly on its own)

My default assumption is that what A said is one text, and what B said
is another text. In some special cases, B may be adding something to
A's text, but normally they are just responding to A's text with th= eir
own new text.

That's the Lojban I have learned starting from your lessons. Is that not your current understanding too?

mu'o mi'e xorxes

If what B says i= s parsable, but would cause jbofi'e to say "selbri may be missing = on line x column x", then I would probably assume that it is a continu= ation. That's the first thing I look for to determine if the new speake= r's utterance is a case of continuation or of an elided {.i}. However, = that assumption really depends on context more than anything else.


--
mu'o mi'e .aionys.

.i.a'o.e'e ko cmima le= bende pe lo pilno be denpa bu .i doi luk. mi patfu do zo'o
(Come to= the Dot Side! Luke, I am your father. :D )


In the case of:

A: [bridi]
B: = [bridi]

I would likely assume B was not continuing A&#= 39;s jufra, as if they had said:

A: .i [bridi]
B: .i [bridi]
--
mu'o mi'e .aionys.

.i.a'o.e'e ko cmima le ben= de pe lo pilno be denpa bu .i doi luk. mi patfu do zo'o
(Come to the= Dot Side! Luke, I am your father. :D )

--
You received this message because you are subscribed to the Google Groups "= BPFK" group.
To post to this group, send email to bpfk-list@googlegroups.com.
To unsubscribe from this group, send email to bpfk-list+unsubscribe@googleg= roups.com.
For more options, visit this group at http://groups.google.com/group/bpfk-l= ist?hl=3Den.
--00032557a2ba7930cc0492498152--