Received: from mail-ww0-f61.google.com ([74.125.82.61])
	by chain.digitalkingdom.org with esmtp (Exim 4.72)
	(envelope-from <bpfk-list+bncCJ2UzZHuDRCen8nlBBoEmyJEoA@googlegroups.com>)
	id 1P55YJ-0004ZA-7X; Sun, 10 Oct 2010 16:43:42 -0700
Received: by wwe15 with SMTP id 15sf675391wwe.16
        for <multiple recipients>; Sun, 10 Oct 2010 16:43:32 -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
         :in-reply-to:references: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
         :content-transfer-encoding;
        bh=ul33ahlOD83QV8owexXe61g3vEmYNZmnvQ0bE0XAdv4=;
        b=AhHL/uiWkoN+1X2OQUe3mA31gNRsn38InizQ9DbgtRLjkLA+Tx4QWL3oug4xh8L6Nf
         B/tawaEJGU2HAq+J5Y3mZ+Pp1+uL2OpgpMMnCOaugwBJDXBXLush7erBts1xlMVl6k06
         Au8lVF1n3JzwYbekj4X+k7wbqAe4AjzIM5A6c=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlegroups.com; s=beta;
        h=x-beenthere:received-spf:mime-version:in-reply-to:references: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:content-transfer-encoding;
        b=jk5cao+saRmcSC3yD2j9oaMhrKP7+Wb0/MqeAyaNChatWN3B5qNbs+lBeXb3tYtFgL
         tluxtr8OR11k+Smj3pIh/ur1V7U7y51q3j6xnfsuotLFJ4+5hVzU3HPz5VqRFVH9XWK9
         4cR4vkbRZ0VPO2A/nA601k48fHv9anuOPb5pk=
Received: by 10.216.237.9 with SMTP id x9mr571552weq.11.1286754206507;
        Sun, 10 Oct 2010 16:43:26 -0700 (PDT)
X-BeenThere: bpfk-list@googlegroups.com
Received: by 10.227.3.19 with SMTP id 19ls936573wbl.3.p; Sun, 10 Oct 2010
 16:43:25 -0700 (PDT)
Received: by 10.227.136.8 with SMTP id p8mr232437wbt.28.1286754205677;
        Sun, 10 Oct 2010 16:43:25 -0700 (PDT)
Received: by 10.227.136.8 with SMTP id p8mr232436wbt.28.1286754205651;
        Sun, 10 Oct 2010 16:43:25 -0700 (PDT)
Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50])
        by gmr-mx.google.com with ESMTP id x33si2692611wbs.5.2010.10.10.16.43.24;
        Sun, 10 Oct 2010 16:43:24 -0700 (PDT)
Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 74.125.82.50 as permitted sender) client-ip=74.125.82.50;
Received: by mail-ww0-f50.google.com with SMTP id 13so211945wwb.31
        for <bpfk-list@googlegroups.com>; Sun, 10 Oct 2010 16:43:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.135.211 with SMTP id o19mr5042985wbt.73.1286754204326;
 Sun, 10 Oct 2010 16:43:24 -0700 (PDT)
Received: by 10.227.145.130 with HTTP; Sun, 10 Oct 2010 16:43:24 -0700 (PDT)
In-Reply-To: <AANLkTinWgwkpvWTogj8k3xjS_NW1ETJSe9x0PdeCejcn@mail.gmail.com>
References: <AANLkTimubXTKdRJveiZb_ddpEMnWg4GvGSQQtbbWcRg=@mail.gmail.com>
	<AANLkTim3O60hBwnHHVaN=S1VMa4FeERiV6dRMs+=fnJr@mail.gmail.com>
	<AANLkTi=6Hh3-UeOWZa7cCTek4ojhpLcSvZyFprd+Bk-4@mail.gmail.com>
	<AANLkTi=rFOh1rF2tDgDoQ=q79YCO2PvKFejfAQo0Xfv3@mail.gmail.com>
	<AANLkTinWgwkpvWTogj8k3xjS_NW1ETJSe9x0PdeCejcn@mail.gmail.com>
Date: Sun, 10 Oct 2010 20:43:24 -0300
Message-ID: <AANLkTikja4sTOBSJS-QMGrfHAiLAQNk=SKH_PpuAj0fW@mail.gmail.com>
Subject: Re: [bpfk] Re: {.i} and {ni'o}, continuation or new jufra
From: =?ISO-8859-1?Q?Jorge_Llamb=EDas?= <jjllambias@gmail.com>
To: bpfk-list@googlegroups.com
X-Original-Sender: jjllambias@gmail.com
X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com:
 domain of jjllambias@gmail.com designates 74.125.82.50 as permitted sender)
 smtp.mail=jjllambias@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: <bpfk-list.googlegroups.com>
List-Post: <http://groups.google.com/group/bpfk-list/post?hl=en_US>, <mailto:bpfk-list@googlegroups.com>
List-Help: <http://groups.google.com/support/?hl=en_US>, <mailto:bpfk-list+help@googlegroups.com>
List-Archive: <http://groups.google.com/group/bpfk-list?hl=en_US>
Sender: bpfk-list@googlegroups.com
List-Subscribe: <http://groups.google.com/group/bpfk-list/subscribe?hl=en_US>, <mailto:bpfk-list+subscribe@googlegroups.com>
List-Unsubscribe: <http://groups.google.com/group/bpfk-list/subscribe?hl=en_US>,
 <mailto:bpfk-list+unsubscribe@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Length: 3856

On Sun, Oct 10, 2010 at 8:03 PM, Jonathan Jones <eyeonus@gmail.com> wrote:
> 2010/10/10 Jorge Llamb=EDas <jjllambias@gmail.com>
>>
>> A: .i ie pei xamgu
>> B: nai .i na xamgu
>
> Okay, two questions.
>
> 1) What does nai by itself even mean? and

It's the answer to the "pei" question.

> 2) Has anyone, ever, used nai in that way in conversation, as opposed to =
as
> an example of "something that causes this to break"?

I have no idea. What I'm asking is if you are aware that you are
proposing a change to the currently official language, or whether you
think you are describing the official language. If the latter, you are
wrong. If the former, I'm not convinced by the arguments you have
given.

>> > {.i lo broda cu brode lu .i broda lo brodi li'u .i li'o} is a sinlge
>> > jufra
>> > followed by one or more omitted jufra, as indicated by {li'o}.
>>
>> Syntactically, "li'o" is not a jufra, it just attaches to ".i", but
>> I'm not sure how this has to do with anything anyway.
>
> Hence my use of the word "indicated", which is a synonym for "symbolized"=
.

Well, syntactically there is nothing omitted. I'm not trying to be
difficult here, but we seem to be mixing up semantic and syntactic
issues. We are discussing a syntactic issue, right? We are talking
about the syntactic construct "text", not about what we may or may not
choose to loosely call a "text" in a more general sense. We are
discussing the kind of thing we feed to the parser in the hopes that
it is accepted as a valid "text".

>> > {la.alis.} is a single text. It is composed of a large multitude of
>> > jufra.
>>
>> Yes course, with a single speaker/author, Lewis Carrol.
>>
>> (Strictly speaking, it won't completely parse with the current
>> grammar, but the breaking points are very few. In principle it could
>> have been a single text, yes. It is not a conversation where texts are
>> exchanged between two or more peoiple.)
>
> Neither of those points seem to have any relevance to this discussion. I =
was
> merely providing an example of what I consider the difference between a
> jufra =3D sentence and a text to be.

OK. Yes, of course a text can consist of several sentences. That has
never been in dispute. So we agree about that.

> Unlike you, I consider an entire conversation to be a single "text", in t=
he
> same way that I consider a thread on these groups to be a single text.

The second part is irrelevant to the Lojban syntactic construct called
"text". The first part does not work in general. Some valid
conversations cannot be reduced to a single "text" construct.

> Also
> apparently unlike you, I don't think that {mi}, {do}, etc. must remain th=
e
> same throughout a single text, but can - and do - change referents with e=
ach
> new sentence.

Normally they (especially "mi") only change referents with each new
speaker, not each new sentence. But right, if you parse a whole
conversation as one text, such text will not have a fixed speaker.
That was my point, wasn't it? You lose that property for texts, of
having a fixed speaker.

> A: "(.i) [bridi] .i [bridi]" two jufra, one text.
>
> A: "(.i) [bridi]"
> B: "(.i) [bridi]" two jufra, one text.
>
> A: "(.i) ma klama"
> B: "(.i) lo zarci (go'i)" two jufra, one text.

We are obviously talking about different things, since ".i" cannot be
omitted by B in the last two cases for them to be a single text, so
what's the parenthesis for? The parser will not insert the ".i" for
you the way it will insert an elidable terminator,

mu'o mi'e xorxes

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