Received: from mail-gy0-f189.google.com ([209.85.160.189]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1P5prA-0002ji-Id; Tue, 12 Oct 2010 18:10:16 -0700 Received: by gyh3 with SMTP id 3sf1928675gyh.16 for ; Tue, 12 Oct 2010 18:10:06 -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; bh=UqH0ctH4dqq5GsDqGcU0IazTNP0Cye1d+XjJzfbPQFU=; b=0fKnudLymS1sXKZHPnf8oslkERAna1xg/1GoA+GavMhtesp71UaunwcIellYGb+eCH PdGcBulhiGODk59xITP9PtYPy6HaHgmcU7azzo98v9RB1s4Bd1BaQjNY8phS+uQtklDm 1IXNHjS/fFUiME5GWjmAus8w5R5UIs7bCPun0= 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; b=ayq0n7imjBHKGQy4qQ5jLqLewWsqwzmN981ojWwAbUrsnAyxY1ROYsIX3Z1Ye4ayVu FwfADIWNGOyERKsLDVjcJjWKAHHLeoVRdwLKnxunOWONtsUOod2Z7O/ubrYxEGraVPqX DDwQPLlz/b11EFxIX8hQxwOt9xO02symXRzTc= Received: by 10.90.53.2 with SMTP id b2mr58959aga.30.1286932200411; Tue, 12 Oct 2010 18:10:00 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.231.112.41 with SMTP id u41ls354910ibp.1.p; Tue, 12 Oct 2010 18:10:00 -0700 (PDT) Received: by 10.231.183.71 with SMTP id cf7mr2337376ibb.17.1286932200206; Tue, 12 Oct 2010 18:10:00 -0700 (PDT) Received: by 10.231.183.71 with SMTP id cf7mr2337375ibb.17.1286932200148; Tue, 12 Oct 2010 18:10:00 -0700 (PDT) Received: from mail-iw0-f173.google.com (mail-iw0-f173.google.com [209.85.214.173]) by gmr-mx.google.com with ESMTP id bm7si5439880ibb.2.2010.10.12.18.09.59; Tue, 12 Oct 2010 18:09:59 -0700 (PDT) Received-SPF: pass (google.com: domain of eyeonus@gmail.com designates 209.85.214.173 as permitted sender) client-ip=209.85.214.173; Received: by mail-iw0-f173.google.com with SMTP id 34so5588016iwn.18 for ; Tue, 12 Oct 2010 18:09:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.191.136 with SMTP id dm8mr6408071ibb.75.1286932198867; Tue, 12 Oct 2010 18:09:58 -0700 (PDT) Received: by 10.231.206.68 with HTTP; Tue, 12 Oct 2010 18:09:58 -0700 (PDT) In-Reply-To: References: <4CB2335F.7000606@lojban.org> <4CB253D0.1020806@lojban.org> <4CB3576C.2000009@lojban.org> <4CB48045.9050503@lojban.org> <4CB4A74F.9040003@lojban.org> Date: Tue, 12 Oct 2010 19:09:58 -0600 Message-ID: Subject: Re: [bpfk] BPFK work 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.173 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=0016367d6c4a90451c0492754094 Content-Length: 11751 --0016367d6c4a90451c0492754094 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 2010/10/12 Jorge Llamb=EDas > On Tue, Oct 12, 2010 at 9:37 PM, Jonathan Jones wrote= : > > > > I have an easy fix for that specific example. I believe I've mentioned = it > > before. > > > > Preface your speech with {.i}. > > But that's my point, if you make ".i" obligatory before every > utterance, you are changing the language. (And the formal grammar will > still not be able to identify where one speaker ends and another > begins, so it still cannot generate a conversation from the input.) > So? Why does the grammar need to know who the speaker is? It doesn't know now, and it doesn't seem important to me in the slightest. What matters is that the separate jufra are unambiguously separate jufra. And I don't see making {.i} "obligatory" is changing the language - in my mind, it already is, but due to the intuitiveness and laziness of humans, we are able to omi= t it, knowing that the audience's mental parser will insert it where needed - something a machine can't now do. On Sun, Oct 10, 2010 at 11:12 AM, Robert LeChevalier wro= te: > "Back in the day"..., we thought that each exchange in formal Lojban > conversation would generally involve starting with .i or ni'o.... > > lojbab Apparently my opinion on the matter dates back some time, as well. If all you are saying is that using ".i" makes for a certain kind of > exchanges to be mushable into one long text and the result is most > often still grammatical and (somewhat) similar to what was intended by > the speakers, then sure, that's true. Okay. Enough about text. Screw the whole concept of text. I am talking abou= t individual jufra. SENTENCES. Specifically, how to unambiguously determine, without resorting to "pragmatics", whether or not {lo zarci}, to use your oft-repeated example, is a part of the jufra {do klama ma}, or if it is a new jufra. But that has nothing to do with > the formal grammar, it's just one style that you prefer, because you > happen to like conversations that can be mushed into a single text. > The style I proposed, starting every utterance with "ni'o mi'e of speaker>" is even more precise if you want that kind of precision. > Yes. It is. And it will most likely be used on those occasions that warrant it, such as when the referent of {mi} is not obvious. Although I think that it should only be {ni'o mi'e ...} when the speaker is beginning a new subject. > > Then it becomes > > > > A: .i do klama ma > > B: .i lo zarci > > > > Amazingly, this rule tells you how to separate the single input ".i do > klama > > ma .i lo zarci" into the two strings produced by A and B, > > No, there is no way for the formal grammar to tell it came from two > different speakers, unless you also make it a rule that a speaker can > only produce one bridi at a time. > Why does it matter how many speakers were involved? It's obviously {do klam= a ma} and {lo zarci}, not {do klama ma lo zarci}, which is what is important, is it not? > > isn't based on any > > heuristics or voice recognition, and is already part of the formal > grammar! > > Huzzah! > > > > Which is yet another reason why I frown on the practice of /not/ > beginning > > one's speech with one of {.i}, {ni'o}, or {no'i}, and .lojbab. apparent= ly > is > > in agreement with me. > > But why don't you also frown on the practice of not beginning with ".i > mi'e ". You are not consistent in your frowning. > > mu'o mi'e xorxes > I'm just going to quote myself, as we've already been over this before. On Sun, Oct 10, 2010 at 2:24 PM, Jonathan Jones wrote: > No, I don't do that, and considering that {mi} means "the speaker(s)", it= 's > always obvious that {mi} is referring to me when I'm speaking. Whether or > not others are also being referred to with {mi}, that's something I leave= up > to context. If I wish to explicitly indicate that my use of {mi} includes > others besides myself, I probably would, in that case, begin with {.i mi'= e > [the referents of mi]}, and refer to myself in the third person when I am > referring to only myself during that conversation. --=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. --0016367d6c4a90451c0492754094 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

2010/10/12 Jorge Llamb=EDas <jjllamb= ias@gmail.com>
On Tue, Oct 12, 2010 at 9:37 PM, Jonathan Jones <eyeonus@gmail.com> wrote:
>
> I have an easy fix for that specific example. I believe I've menti= oned it
> before.
>
> Preface your speech with {.i}.

But that's my point, if you make ".i" obligatory before= every
utterance, you are changing the language. (And the formal grammar will
still not be able to identify where one speaker ends and another
begins, so it still cannot generate a conversation from the input.)

So? Why does the grammar need to know who the speaker is?= It doesn't know now, and it doesn't seem important to me in the sl= ightest. What matters is that the separate jufra are unambiguously separate= jufra. And I don't see making {.i} "obligatory" is changing = the language - in my mind, it already is, but due to the intuitiveness and = laziness of humans, we are able to omit it, knowing that the audience's= mental parser will insert it where needed - something a machine can't = now do.

On Sun, Oct 10, 2010 at 11:12 AM, Robert LeC= hevalier <lojbab@= lojban.org> wrote:
"Back in the day"..., we thought that each exchange in formal Lo= jban=20 conversation would generally involve starting with .i or ni'o....

lojbab

Apparently my opinion on the matter dates back = some time, as well.

If all you are saying is that using ".i" makes for a certain kind= of
exchanges to be mushable into one long text and the result is most
often still grammatical and (somewhat) similar to what was intended by
the speakers, then sure, that's true.

Okay. Enough= about text. Screw the whole concept of text. I am talking about individual= jufra. SENTENCES. Specifically, how to unambiguously determine, without re= sorting to "pragmatics", whether or not {lo zarci}, to use your o= ft-repeated example, is a part of the jufra {do klama ma}, or if it is a ne= w jufra.

But tha= t has nothing to do with
the formal grammar, it's just one style that you prefer, because you happen to like conversations that can be mushed into a single text.
The style I proposed, starting every utterance with "ni'o mi'e= <name
of speaker>" is even more precise if you want that kind of precisio= n.

Yes. It is. And it will most likely = be used on those occasions that warrant it, such as when the referent of {m= i} is not obvious. Although I think that it should only be {ni'o mi'= ;e ...} when the speaker is beginning a new subject.
=A0
> Then it becomes
>
> A: .i do klama ma
> B: .i lo zarci
>
> Amazingly, this rule tells you how to separate the single input "= .i do klama
> ma .i lo zarci" into the two strings produced by A and B,

No, there is no way for the formal grammar to tell it came from two different speakers, unless you also make it a rule that a speaker can
only produce one bridi at a time.

Why does it matt= er how many speakers were involved? It's obviously {do klama ma} and {l= o zarci}, not {do klama ma lo zarci}, which is what is important, is it not= ?
=A0
> isn't based on any
> heuristics or voice recognition, and is already part of the formal gra= mmar!
> Huzzah!
>
> Which is yet another reason why I frown on the practice of /not/ begin= ning
> one's speech with one of {.i}, {ni'o}, or {no'i}, and .loj= bab. apparently is
> in agreement with me.

But why don't you also frown on the practice of not beginning wit= h ".i
mi'e <name>". You are not consistent in your frowning.

mu'o mi'e xorxes

I'm just going= to quote myself, as we've already been over this before.

On Sun, Oct 10, 2010 at 2:24 PM, Jonathan Jones <eyeonus@gmail.com&= gt; wrote:
No, I don't do that, and considering that {mi} means "the speaker(s)&= quot;, it's always obvious that {mi} is referring to me when I'm speaking. Whether= =20 or not others are also being referred to with {mi}, that's something I= =20 leave up to context. If I wish to explicitly indicate that my use of=20 {mi} includes others besides myself, I probably would, in that case,=20 begin with {.i mi'e [the referents of mi]}, and refer to myself in the= =20 third person when I am referring to only myself during that=20 conversation.

--
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 )

--
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.
--0016367d6c4a90451c0492754094--