Received: from mail-fx0-f61.google.com ([209.85.161.61])
	by chain.digitalkingdom.org with esmtp (Exim 4.72)
	(envelope-from <bpfk-list+bncCJ2UzZHuDRCt_83lBBoEth8Amw@googlegroups.com>)
	id 1P5Pnm-0005Is-3W; Mon, 11 Oct 2010 14:21:05 -0700
Received: by fxm16 with SMTP id 16sf273850fxm.16
        for <multiple recipients>; Mon, 11 Oct 2010 14:20:51 -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=Tx4JnWU8mWbLmO6vBS7c2InNcLB6nMqDC8bfIMVny8k=;
        b=PDkFzX650uFg9hRrFjS8BXL8dOtZv/wXbX7x44BGT5zqXhN7Yp1brp+BUSDVD1Hhj7
         KaZ0yNjIdKOwAtNCmu3TS1vFIQBHf8Bmwqkev9g2ibo6zn2DZ5uYV2uuKwJc+8jNW7Gp
         sDPJyMERy47Xjt7EgoSrJPxQRgrey0+TF1c1Y=
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=LGl4CZXKX/TignijbhjgTMTrbGnWD2BjV1F40lSm6LElfE4tPBKjrBvL9mxX6tkq/n
         PUQqWA7PFbdkK6xnCMjhq4L68BG0CPf8sZdjRrOfm8JrFQiLd6720nhpMBowXnlL8CGe
         M40VRFNApJkJBFVBPQM3GDtrAw4XOM7fVTZCQ=
Received: by 10.223.94.130 with SMTP id z2mr95763fam.27.1286832045463;
        Mon, 11 Oct 2010 14:20:45 -0700 (PDT)
X-BeenThere: bpfk-list@googlegroups.com
Received: by 10.223.59.212 with SMTP id m20ls1025810fah.3.p; Mon, 11 Oct 2010
 14:20:44 -0700 (PDT)
Received: by 10.223.114.10 with SMTP id c10mr382050faq.8.1286832044810;
        Mon, 11 Oct 2010 14:20:44 -0700 (PDT)
Received: by 10.223.114.10 with SMTP id c10mr382049faq.8.1286832044773;
        Mon, 11 Oct 2010 14:20:44 -0700 (PDT)
Received: from mail-fx0-f51.google.com (mail-fx0-f51.google.com [209.85.161.51])
        by gmr-mx.google.com with ESMTP id b13si2013765fab.13.2010.10.11.14.20.43;
        Mon, 11 Oct 2010 14:20:43 -0700 (PDT)
Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 209.85.161.51 as permitted sender) client-ip=209.85.161.51;
Received: by fxm14 with SMTP id 14so675634fxm.24
        for <bpfk-list@googlegroups.com>; Mon, 11 Oct 2010 14:20:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.239.132.15 with SMTP id 15mr463696hbp.2.1286832043467; Mon, 11
 Oct 2010 14:20:43 -0700 (PDT)
Received: by 10.239.162.66 with HTTP; Mon, 11 Oct 2010 14:20:43 -0700 (PDT)
In-Reply-To: <4CB3493A.7010406@lojban.org>
References: <AANLkTi=2R1tYqwGzuL1oLN448q-aB3BHEcB4Z9h+5FBs@mail.gmail.com>
	<AANLkTimsi5eFPPfbLFg7jgDnA-3rNXX+6UkMw852CBMk@mail.gmail.com>
	<AANLkTinaNdo3eTkWBwdKgUYHobmOUPMKNd1zHkAC_KzG@mail.gmail.com>
	<AANLkTikROXvZ0J_KtzpkqxjMhXYVGY2WkBoWbidHJUoG@mail.gmail.com>
	<4CB0B239.50107@lojban.org>
	<AANLkTimzz=Exgf-94tnkebibZs8ZhtmO_Z9meeorSLKj@mail.gmail.com>
	<4CB1F3EA.5000608@lojban.org>
	<AANLkTi=-z=KfdA3EQYF-g2Ab9v=PXCHZGr0g=17RBF3j@mail.gmail.com>
	<4CB20ADF.6050500@lojban.org>
	<AANLkTikJQAkx145XeQBC=f5KBq0wyLz_yd4wgkCH8Bbk@mail.gmail.com>
	<AANLkTinFLROKSf7WLn3r82hHVLGUjTUx6VLG=MereADY@mail.gmail.com>
	<AANLkTimU6eie6HXqfVYWCKEYxBEn=uvyRk+oRbsCSyGv@mail.gmail.com>
	<AANLkTi=5rsT0HCwd+aO+Pyt-2r6Q06jxss0zk2e+B+LE@mail.gmail.com>
	<AANLkTimVM9COtdvBy6oH66imQOmMWXbumv3GQjYw8JhG@mail.gmail.com>
	<4CB2335F.7000606@lojban.org>
	<AANLkTi=eC0yrzcPj8DLqRVK+dnzQgt+-diwO0aM7rrj-@mail.gmail.com>
	<4CB253D0.1020806@lojban.org>
	<AANLkTikDa_qf9vK0wEeu-LsGmby0dVg5Mc7aAsMOPCEy@mail.gmail.com>
	<4CB3493A.7010406@lojban.org>
Date: Mon, 11 Oct 2010 18:20:43 -0300
Message-ID: <AANLkTinF1Kuvpe2O_Cuy7iCGtTGBYGVLc4q7ViE-kBWM@mail.gmail.com>
Subject: Re: [bpfk] BPFK work
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 209.85.161.51 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=windows-1252
Content-Transfer-Encoding: quoted-printable
Content-Length: 4037

On Mon, Oct 11, 2010 at 2:28 PM, Robert LeChevalier <lojbab@lojban.org> wro=
te:
> 3. The formalization of the machine grammar has not to my knowledge ever
> been fully implemented,

It has for several years now. It hasn't yet been made official, but it
has been formalized, the whole thing, from the morphology up,
including all the tricky magic words.

There are some issues still to decide, but not because they haven't
been formalized, only because we have to make choices as to which
formal version of a rule is preferrable. (I'm thinking of the various
possibilities for SA here, and different options for the details of
long consonant or vowel clusters in the phonotactics of cmevla and
fu'ivla.)

> and the fact that we are having this discussion
> indicates that the concept of "text" was never formally defined in terms
> necessary to account for multiple speakers.

That's a pragmatic matter, external to the formal grammar, right.

>=A0In the formal grammar, "text"
> is everything up until a fa'o (which almost no one uses - except apparent=
ly
> in Twitter),

It is also often used as a sort of "The End" for stories, for example
at the end of "Alice in Wonderland".

> and thus it is arbitrary to say that change of speaker ends a
> text.

It is arbitrary, yes, and it has always been the usual practice, both
in teaching materials and in actual use for example in IRC. It's easy
to finds loads of examples.

>=A0By the formal language, no fa'o: no end of text.

That's not quite right.

 In PEG, FAhO is optional, otherwise the end of input is enough to
signal the end of text.

In BNF the rule for FAhO is only given informally, it is not a part of
the formalization:
"FAhO is a universal terminator and signals the end of parsable input."

In YACC it is also only given as part of the pre-parsing shenanigans,
and it is only optional. In the YACC document it is mentioned three
times:
"If the text contains a FAhO, treat that as the end-of-text and ignore
everything that follows it."
%token FAhO_529         /* normally elided =92done pause=92 to indicate end
                                   of utterance string */
  /* An empty text is legal; formerly this was handled by the explicit
   appearance of FAhO_529, but this is now absorbed by the preparser. */


> By the formal grammar, if there is no fa'o, there is no new text. Indeed,=
 by
> the formal grammar, there is no concept of more than one text and after a
> fa'o, everything else until the end of time is non-Lojban. %^)

That's absurd. By the formal grammar, each input that parses correctly
is a valid Lojban text. There's no reason to think that only one valid
Lojban text exists in all the universe.

>> Why? Why wouldn't the computer just parse each speaker's text on its
>> own?
>
> The computer doesn't know what a "speaker" is.

Computers nowadays are pretty good at voice recognition.

>=A0It knows what a text-stream
> is, and that such a text-stream ends with a fa'o and only with a fa'o.

You can program a computer to recognize different speakers and feed
the contribution from each speaker to the parser as a separate input.
That of course has nothing to do with the formal grammar.

> =A0Actual implementation is thus erroneous in that it can end other than =
with
> a fa'o (i.e with whatever the computer system recognizes as "end-of-text"=
.

"fa'o" has never been an obligatory end of text indicator, as far as I can =
tell.

>> A: do klama ma
>> B: lo zarci
>
> "Formally", to the Lojbanic computer, that is "do klama ma lo zarci". It
> doesn't know what "A:" and "B:" are. =A0"Formally", to the Lojbanic compu=
ter
> there is no possibility of more than one text.

Absurd.

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.