From lojban+bncCK7Yk5CUCxCLn5zzBBoEYjJ3xA@googlegroups.com Tue Sep 06 23:30:47 2011 Received: from mail-fx0-f61.google.com ([209.85.161.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1R1Bem-0001na-6M; Tue, 06 Sep 2011 23:30:47 -0700 Received: by fxd2 with SMTP id 2sf303166fxd.16 for ; Tue, 06 Sep 2011 23:30:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:in-reply-to:message-id:date :subject:from:to:x-original-sender:x-original-authentication-results :reply-to:precedence:mailing-list:list-id:x-google-group-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; bh=sdWPyQ7WvqEl6y/U1mfJ5ZPT72D2WOInlBF4qSGqwVU=; b=Pb5Hyg/hMkESPfIA7A6OTw3uoIC1U2KfOThftKbUccQoEVWpKlYm2VTgllB8Cy61gi LWIYGP9TQHWra0xDGkxsfo7AiQONLvo5JOswE7OO3fCfs9CPOdgaQwPnrUXhzVIsq9ds WAHI9TEFFNr44+yCmtTr8wCDHmgF4e4gi67To= Received: by 10.223.28.91 with SMTP id l27mr969573fac.35.1315377035756; Tue, 06 Sep 2011 23:30:35 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.204.131.67 with SMTP id w3ls1391419bks.2.gmail; Tue, 06 Sep 2011 23:30:34 -0700 (PDT) Received: by 10.204.5.83 with SMTP id 19mr1234776bku.9.1315377034523; Tue, 06 Sep 2011 23:30:34 -0700 (PDT) Received: by 10.204.5.83 with SMTP id 19mr1234775bku.9.1315377034503; Tue, 06 Sep 2011 23:30:34 -0700 (PDT) Received: from mail-fx0-f71.google.com (mail-fx0-f71.google.com [209.85.161.71]) by gmr-mx.google.com with ESMTPS id p10si642831fak.1.2011.09.06.23.30.34 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 06 Sep 2011 23:30:34 -0700 (PDT) Received-SPF: pass (google.com: domain of rdentato@gmail.com designates 209.85.161.71 as permitted sender) client-ip=209.85.161.71; Received: by fxe22 with SMTP id 22so79064fxe.6 for ; Tue, 06 Sep 2011 23:30:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.221.8 with SMTP id q8mr500191wep.4.1315377034256; Tue, 06 Sep 2011 23:30:34 -0700 (PDT) In-Reply-To: Message-ID: <0016e651fec0df660a04ac541439@google.com> Date: Wed, 07 Sep 2011 06:30:34 +0000 Subject: Re: Re: [lojban] tosmabru test From: rdentato@gmail.com To: lojban@googlegroups.com X-Original-Sender: rdentato@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of rdentato@gmail.com designates 209.85.161.71 as permitted sender) smtp.mail=rdentato@gmail.com Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=0016e651fec0df65f004ac541436 --0016e651fec0df65f004ac541436 Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes On , Ross Ogilvie wrote: > The issue is that there is no whitespace in speech. I would have a very hard time trying not to "pronounce" a whitespace as short pause. I would read {pa plise} and {paplise} differently putting a short interruption between {pa} and {plise} in the first case. The fact that they are the same just put more strain on the listener that has to break up words in his mind without the help of that short interruption. After all, we do have {.} so if I really meant two words, why didn't I say {pa.plise}? But, I'm not complaining, just wanted to understand the benefits. So far it seems to me that this would help the speaker making him free to pronounce words as a single flow with a price for the listener that has to break things up without counting on the short pauses that the whitespaces imply (at least to me). remod -- You received this message because you are subscribed to the Google Groups "lojban" group. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en. --0016e651fec0df65f004ac541436 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On , Ross Ogilvie <oges007@gmail.com> wrote:
> The issue is t= hat there is no whitespace in speech.

I would have a very hard t= ime trying not to "pronounce" a whitespace as short pause.
I= would read {pa plise} and {paplise} differently putting a short interrupti= on between {pa} and {plise} in the first case.
The fact that they are = the same just put more strain on the listener that has to break up words in= his mind without the help of that short interruption.

After al= l, we do have {.} so if I really meant two words, why didn't I say {pa.= plise}?

But, I'm not complaining, just wanted to understand = the benefits. So far it seems to me that this would help the speaker making= him free to pronounce words as a single flow with a price for the listener= that has to break things up without counting on the short pauses that the = whitespaces imply (at least to me).

remod

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com.
For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.
--0016e651fec0df65f004ac541436--