From lojban+bncCOjSjrXVGBCPjojgBBoEkjIdBA@googlegroups.com Sat May 29 23:35:12 2010 Received: from mail-vw0-f61.google.com ([209.85.212.61]) by chain.digitalkingdom.org with esmtp (Exim 4.71) (envelope-from ) id 1OIc71-0000Qn-Q1; Sat, 29 May 2010 23:35:11 -0700 Received: by vws15 with SMTP id 15sf68335vws.16 for ; Sat, 29 May 2010 23:35:01 -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=ZY7odyJMYWSF9/JwG3u5iSVtrYlCTWE8JnAGMrmDkNw=; b=EknEO0mEOwujojxfBffC8AchcDW87J+9yv88ALxPBeO/CLXDDIvJwdSf0Hy4N+k+Ir w7zqEKfB6Q8q3e4oEr2a9u+zwdQ3TV2Yy/7RYsx7+JaLc/gDuc4Jpua3WVwZG+gWxlaV LgaFK1tb1EkHR6sd3k45wk5yejYUVi5DvVxdQ= 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=C11aSSwTg/Q+IPquWtyBsfTDzcmU/G3hFRDd+R6+8nX6e3Tt1zJwrQUXq78eFlM5fx KcvvIA15v6ZPT5n+uuQW0fGCA4BRGSiGBZfMLTs5ACDdITShRszBW/dDxA7YbRHfSvDu v/IpVhHf7YBett0tgaMPOcHBn5xhocAMcCv8c= Received: by 10.220.126.222 with SMTP id d30mr145168vcs.19.1275201295828; Sat, 29 May 2010 23:34:55 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.220.47.17 with SMTP id l17ls1562977vcf.5.p; Sat, 29 May 2010 23:34:55 -0700 (PDT) Received: by 10.220.185.9 with SMTP id cm9mr671870vcb.22.1275201295075; Sat, 29 May 2010 23:34:55 -0700 (PDT) Received: by 10.220.185.9 with SMTP id cm9mr671869vcb.22.1275201295036; Sat, 29 May 2010 23:34:55 -0700 (PDT) Received: from mail-vw0-f52.google.com (mail-vw0-f52.google.com [209.85.212.52]) by gmr-mx.google.com with ESMTP id b14si3071019vcx.1.2010.05.29.23.34.54; Sat, 29 May 2010 23:34:54 -0700 (PDT) Received-SPF: pass (google.com: domain of lukeabergen@gmail.com designates 209.85.212.52 as permitted sender) client-ip=209.85.212.52; Received: by vws18 with SMTP id 18so2034687vws.11 for ; Sat, 29 May 2010 23:34:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.60.142 with SMTP id p14mr2053927vch.176.1275201293747; Sat, 29 May 2010 23:34:53 -0700 (PDT) Received: by 10.220.94.77 with HTTP; Sat, 29 May 2010 23:34:53 -0700 (PDT) In-Reply-To: References: <3414c7b0-2a75-4cb2-99a4-0afa6458f6ba@t34g2000prd.googlegroups.com> <7ac5ef76-747a-4077-ac8d-bd45e0c68005@y6g2000pra.googlegroups.com> <556832.6378.qm@web81302.mail.mud.yahoo.com> <959500ee-ea4d-4acf-9353-f2c990ba25a7@t34g2000prd.googlegroups.com> Date: Sun, 30 May 2010 02:34:53 -0400 Message-ID: Subject: Re: [lojban] Re: Named multiples From: Luke Bergen To: lojban@googlegroups.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of lukeabergen@gmail.com designates 209.85.212.52 as permitted sender) smtp.mail=lukeabergen@gmail.com; dkim=pass (test mode) header.i=@gmail.com X-Original-Sender: lukeabergen@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=e0cb4e8876e52187910487c9f0e3 --e0cb4e8876e52187910487c9f0e3 Content-Type: text/plain; charset=ISO-8859-1 >>> Is {me} being removed from the grammar due to it not being necessary >>> after this change? >> >> No, definitely not. > Then under what condition would it still be used? The example from the CLL for {me} is something like: {la djan me li ci nolraitru} or something. On Sun, May 30, 2010 at 2:22 AM, Lindar wrote: > > Same as between {lo broca} and {la broca}. > > Ah... Makes sense. So la .lindar. is "Lindar." (a meaningless string > of characters) and lo .lindar. is "Thing(s) named Lindar." ? That's > nifty. > > > > Can cmevla have multiple places? > > > > I don't see why not? > > .spagetis. = x1 is spaghetti with sauce x2 > ?? > > > > Is {me} being removed from the grammar due to it not being necessary > > > after this change? > > > > No, definitely not. > > Then under what condition would it still be used? > > > > Could this possibly be used as a system for creating "slang" words? > > > > Sure, why not? That's a good thing about cmevla: they're easy to make. > > Then I shall coin the first rude Anglo slang, ".kul.". > > Well, I'm convinced. It seems like a decent idea as long as it doesn't > get abused. Do we just start using it now, is there some kind of > ceremony we have to have first, or... what now? Does everybody agree > on exactly how it'll work? > > -- > 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. > > -- 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. --e0cb4e8876e52187910487c9f0e3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
>>> Is {me} being removed from the gr= ammar due to it not being necessary
>>> after this change?
>>
>> No, definitely not.=

> Then = under what condition would it still be used?

The example from the CLL for {me} is something like: {la djan me li ci nolr= aitru} or something. =A0

On Sun, May 30, = 2010 at 2:22 AM, Lindar <lindarthebard@yahoo.com> wrote:
> Same as between {lo = broca} and {la broca}.

Ah... Makes sense. So la .lindar. is "Lindar." (a meaningle= ss string
of characters) and lo .lindar. is "Thing(s) named Lindar." ? That= 's
nifty.

> > Can cmevla have multiple places?
>
> I don't see why not?

.spagetis. =3D x1 is spaghetti with sauce x2
??

> > Is {me} being removed from the grammar due to it not being necess= ary
> > after this change?
>
> No, definitely not.

Then under what condition would it still be used?

> > Could this possibly be used as a system for creating "slang&= quot; words?
>
> Sure, why not? =A0That's a good thing about cmevla: they're ea= sy to make.

Then I shall coin the first rude Anglo slang, ".kul.".

Well, I'm convinced. It seems like a decent idea as long as it doesn= 9;t
get abused. Do we just start using it now, is there some kind of
ceremony we have to have first, or... what now? Does everybody agree
on exactly how it'll work?

--
You received this message because you are subscribed to the Google Groups &= quot;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/lojba= n?hl=3Den.


--
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.
--e0cb4e8876e52187910487c9f0e3--