From bpfk-list+bncCJXwn4e6DRCz2dflBBoEGkjEfg@googlegroups.com Wed Oct 13 10:30:48 2010 Received: from mail-fx0-f61.google.com ([209.85.161.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1P65A2-0001H5-9A; Wed, 13 Oct 2010 10:30:48 -0700 Received: by fxm16 with SMTP id 16sf645800fxm.16 for ; Wed, 13 Oct 2010 10:30: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:received:mime-version:received :in-reply-to:references:from:date:message-id:subject: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=hiH+H3p1we5fdUnvT908MANcYEF9tF/gd5lkiLOob48=; b=YTtkWEtFWygnp2dxyRa09bgQEYSaza4RrlsOUygL1nWvGeCRGOb3cX8JsmKpOxXaPg 8bSneG3L/2EB6L2iEXdFVN5wrIedf/Ltg2ZHpAeoJlVgQQId9F8kGVrK3aOIkFsRxBdl UlhtsWpdN9zmdJF9dYgYYWTmtkvxzRmMeofp0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:in-reply-to:references:from :date:message-id:subject: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=TfpbZvGwO2euCII10a3RIpkMmCdR2cWUB7bA+SCWB/qJOqOAezBVCX4y9SXSOBBMyN RglPkHu3TDwGdhY180misfUq13JpDOZvRWQbokZqnco9wiXpqUVFr4/bioV2mmBbM0zc treERvGT/H62Q+M2CBcRqOLgk3TYsPH6cV0P0= Received: by 10.223.91.65 with SMTP id l1mr214216fam.18.1286991027348; Wed, 13 Oct 2010 10:30:27 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.204.48.209 with SMTP id s17ls609576bkf.2.p; Wed, 13 Oct 2010 10:30:26 -0700 (PDT) Received: by 10.204.32.3 with SMTP id a3mr464514bkd.18.1286991025963; Wed, 13 Oct 2010 10:30:25 -0700 (PDT) Received: by 10.204.32.3 with SMTP id a3mr464512bkd.18.1286991025911; Wed, 13 Oct 2010 10:30:25 -0700 (PDT) Received: from mail-fx0-f53.google.com (mail-fx0-f53.google.com [209.85.161.53]) by gmr-mx.google.com with ESMTP id u2si5292350bkd.2.2010.10.13.10.30.24; Wed, 13 Oct 2010 10:30:24 -0700 (PDT) Received-SPF: pass (google.com: domain of adamlopresto@gmail.com designates 209.85.161.53 as permitted sender) client-ip=209.85.161.53; Received: by fxm8 with SMTP id 8so1480264fxm.26 for ; Wed, 13 Oct 2010 10:30:24 -0700 (PDT) Received: by 10.239.142.83 with SMTP id f19mr595839hba.82.1286991024326; Wed, 13 Oct 2010 10:30:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.239.170.139 with HTTP; Wed, 13 Oct 2010 10:30:04 -0700 (PDT) In-Reply-To: References: From: Adam Lopresto Date: Wed, 13 Oct 2010 12:30:04 -0500 Message-ID: Subject: Re: [bpfk] Re: {.i} and {ni'o}, continuation or new jufra To: bpfk-list@googlegroups.com X-Original-Sender: adamlopresto@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of adamlopresto@gmail.com designates 209.85.161.53 as permitted sender) smtp.mail=adamlopresto@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=001485f03662d588e4049282f2ec --001485f03662d588e4049282f2ec Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 2010/10/12 Jorge Llamb=EDas > So the conversation generator gets a sequence of "text"s as input and > outputs one "conversation", right? All it does is surround each text > with fa'ai/fa'o (when they are not already present, I suppose) and > then outputs their concatenation. That seems simple enough. > That is one possible conversationer, yes. > The problem I see is that we must already have the string of texts to > feed the conversationer. You can't feed it the string of phonemes "do > klama ma lo zarci" and expect it to split it into two texts, you must > feed it first chunk "do klama ma", second chunk "lo zarci". In other > words, the hard work will be done somewhere else, not by the > conversationer. > Right. If *all* you have is a stream of phonemes without knowledge of who spoke which, then the situation is hopeless (unless everyone is very cooperative). Fortunately, situations where that actually happens are exceedingly rare. At least, I can't think of any. In speech, we recognize who is saying what as easily (and often with much more accuracy) than the individual phonemes. In IRC, every PRIVMSG comes in separately, with its ow= n source. In an email conversation, we have lots of headers on each mail (so starting the actual message with {fa'ai} and ending with {fa'o} might be a good practice; an entire mbox file could be fed to a de-conversationer). Th= e idea is not that the information can be recovered from nowhere, but that there is a format in which it *can* be preserved, if we need to. --=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. --001485f03662d588e4049282f2ec Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

2010/10/12 Jorge Llamb=EDas <jjllambias@gmail.com&= gt;
So the conversation generator gets a sequence of "te= xt"s as input and
outputs one "conversation", right? All it does is surround each t= ext
with fa'ai/fa'o (when they are not already present, I suppose) and<= br> then outputs their concatenation. That seems simple enough.

That is one possible conversationer, yes.
= =A0
The problem I see is that we must already have the string of texts to
feed the conversationer. You can't feed it the string of phonemes "= ;do
klama ma lo zarci" and expect it to split it into two texts, you must<= br> feed it first chunk "do klama ma", second chunk "lo zarci&qu= ot;. In other
words, the hard work will be done somewhere else, not by the
conversationer.

Right. If *all* you hav= e is a stream of phonemes without knowledge of who spoke which, then the si= tuation is hopeless (unless everyone is very cooperative). Fortunately, sit= uations where that actually happens are exceedingly rare. At least, I can&#= 39;t think of any. In speech, we recognize who is saying what as easily (an= d often with much more accuracy) than the individual phonemes. In IRC, ever= y PRIVMSG comes in separately, with its own source. In an email conversatio= n, we have lots of headers on each mail (so starting the actual message wit= h {fa'ai} and ending with {fa'o} might be a good practice; an entir= e mbox file could be fed to a de-conversationer). The idea is not that the = information can be recovered from nowhere, but that there is a format in wh= ich it *can* be preserved, if we need to.

--
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.
--001485f03662d588e4049282f2ec--