From lojban+bncCIycn8S8DhCjurDfBBoEt9UQhA@googlegroups.com Thu May 13 08:39:36 2010 Received: from mail-yw0-f141.google.com ([209.85.211.141]) by chain.digitalkingdom.org with esmtp (Exim 4.71) (envelope-from ) id 1OCaVY-0007Ib-Fw; Thu, 13 May 2010 08:39:35 -0700 Received: by ywh5 with SMTP id 5sf1124403ywh.25 for ; Thu, 13 May 2010 08:39:26 -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-authentication-results:x-original-sender:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe:content-type; bh=kwjw4iDuEADmdEsSfQK0n1IreQSyrqYS40kCD8itUN4=; b=6YTtSrVErc5WDVvSmjcQskQ0rmE2einROCPyK3loSSAw7IQSgCsVFNbFl96J4I5GP+ BdF77brxD8ZRTGjwuAM5CBcdRYaQr3i9Kp6sI4qu5eGNu15ajJoLLHIq+XipUWY3aGCm EfzqvjxL0Z8yWnCJqseApVkKVjVtsqYTKAJYo= 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-authentication-results :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; b=wNshjFtO8stSr1nij8Kv3ps6qWp54tJNoOaveVo42X031OpROKgzsPv+fdW4Mu2z+t PFjFgWABlINn+KCTKjn2uUfLAMXBXZnnzjKht9+uylOEVDEGUqFnfyzxkjB2JbT/+xDq eKkQ4+w40YhUhSPsXMD7yOh1Jp5ITH2/s6VMs= Received: by 10.150.127.28 with SMTP id z28mr42907ybc.58.1273765156097; Thu, 13 May 2010 08:39:16 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.101.139.8 with SMTP id r8ls6149727ann.7.p; Thu, 13 May 2010 08:39:15 -0700 (PDT) Received: by 10.100.55.35 with SMTP id d35mr1602032ana.57.1273765155077; Thu, 13 May 2010 08:39:15 -0700 (PDT) Received: by 10.100.55.35 with SMTP id d35mr1602031ana.57.1273765155036; Thu, 13 May 2010 08:39:15 -0700 (PDT) Received: from mail-qy0-f193.google.com (mail-qy0-f193.google.com [209.85.221.193]) by gmr-mx.google.com with ESMTP id 24si82217yxe.9.2010.05.13.08.39.13; Thu, 13 May 2010 08:39:14 -0700 (PDT) Received-SPF: pass (google.com: domain of mturniansky@gmail.com designates 209.85.221.193 as permitted sender) client-ip=209.85.221.193; Received: by qyk31 with SMTP id 31so2021241qyk.25 for ; Thu, 13 May 2010 08:39:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.17.217 with SMTP id t25mr6268692qaa.86.1273765150600; Thu, 13 May 2010 08:39:10 -0700 (PDT) Received: by 10.229.225.66 with HTTP; Thu, 13 May 2010 08:39:10 -0700 (PDT) In-Reply-To: References: Date: Thu, 13 May 2010 11:39:10 -0400 Message-ID: Subject: Re: [lojban] Attitudinal scales and the meaning of {cu'i} From: Michael Turniansky To: lojban@googlegroups.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of mturniansky@gmail.com designates 209.85.221.193 as permitted sender) smtp.mail=mturniansky@gmail.com; dkim=pass (test mode) header.i=@gmail.com X-Original-Sender: mturniansky@gmail.com Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=00c09f9c97a25487b204867b8f48 --00c09f9c97a25487b204867b8f48 Content-Type: text/plain; charset=ISO-8859-1 On Wed, May 12, 2010 at 11:39 AM, Daniel Brockman wrote: > What we could do about {ba'a cu'i} is turn it into a separate cmavo. > Then we get to define another variant of it as well (its opposite): > > ba'u'i = I experience > ba'u'i nai = I imagine/fantasize about > > .i ba'u'i nai mabla zgike = I have this awful song stuck in my head > > > We have the same issues with the event contour, bu'ocu'i, don't we? I'm quite willing to say that [na]cu'i/ru'e/sai/cai are context dependent, in the same way that "jai" or "bo" do different things in different contexts. There is no reason why lojban can't have cmavo"idioms" that aren't necessarily necessarily parseable in meaning by their components. Lujvo, for example, already and explicitly are this. Some things are already in common use, for example za'u roi This is probably heresy, though... --gejyspa -- 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. --00c09f9c97a25487b204867b8f48 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Wed, May 12, 2010 at 11:39 AM, Daniel= Brockman <danie= l@brockman.se> wrote:
What we could do about {ba'a cu'i} is turn it into a separate cmavo= .
Then we get to define another variant of it as well (its opposite):

ba'u'i =3D I experience
ba'u'i nai =3D I imagine/fantasize about

.i ba'u'i nai mabla zgike =3D I have this awful song stuck in my he= ad


=A0= We have the same issues with the event contour, bu'ocu'i, don'= t we?=A0=A0=A0=A0 I'm quite willing to say that [na]cu'i/ru'e/s= ai/cai are context dependent, in the same way that "jai" or "= ;bo" do different things in different contexts.=A0 There is no reason = why lojban can't have cmavo"idioms" that aren't necessari= ly necessarily parseable in meaning by their components.=A0 Lujvo, for exam= ple, already and explicitly are this.=A0 Some things are already in common = use, for example za'u roi

=A0 This is probably heresy, though...

=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0 --gejyspa


--
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.
--00c09f9c97a25487b204867b8f48--