From lojban+bncCIywt_XDCRCc0fvtBBoEOUKDYQ@googlegroups.com Mon May 02 10:25:26 2011 Received: from mail-gy0-f189.google.com ([209.85.160.189]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1QGwqc-000244-Aa; Mon, 02 May 2011 10:25:25 -0700 Received: by gyf1 with SMTP id 1sf10734079gyf.16 for ; Mon, 02 May 2011 10:23:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:x-beenthere:received-spf :x-yahoo-newman-property:x-yahoo-newman-id:message-id:x-ymail-osg :x-mailer:references:date:from:subject:to:in-reply-to:mime-version :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=GD0fVuxxyhsP9v6m3lN3CXNjXQoDRWo/EUCU43YIwFc=; b=K7IKa6DyIsCO9CC962kRfjB452qTawbjUFuZ5Lder5VIHRqFU6JDV+H/ZhhAhMOINz CiUr02InfHK/QbwGFQkBzKYrQtEgDTD5kHD0AgqKTUfLqKhKAKhoftJz+naOrpEiSH/v hweAMW6esiRNxxVb8EGbbx/7roayFtOxMyous= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:x-yahoo-newman-property:x-yahoo-newman-id :message-id:x-ymail-osg:x-mailer:references:date:from:subject:to :in-reply-to:mime-version: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; b=PJ6uYpXE5os9Cp9ojD3YYTKx0UnWkmdjLaftvhAczIZwvwK8NhzzWsrUwAwWATuq0H 4CPPCpSkaVXDoGugHFesBNoGU6xdFu842X9iSJWZMhL1/IYsbdHqbQixc6r4PQJOAeTe V+3BAFLtrbVM/Qgl8ghPLxVyLcYbkZEsSReCY= Received: by 10.101.24.3 with SMTP id b3mr842321anj.30.1304357020400; Mon, 02 May 2011 10:23:40 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.100.30.35 with SMTP id d35ls692500and.6.gmail; Mon, 02 May 2011 10:23:40 -0700 (PDT) Received: by 10.101.138.18 with SMTP id q18mr3115108ann.0.1304357019993; Mon, 02 May 2011 10:23:39 -0700 (PDT) Received: by 10.150.73.31 with SMTP id v31msyba; Mon, 2 May 2011 09:46:39 -0700 (PDT) Received: by 10.101.218.17 with SMTP id v17mr543286anq.5.1304354798868; Mon, 02 May 2011 09:46:38 -0700 (PDT) Received: by 10.101.218.17 with SMTP id v17mr543283anq.5.1304354798831; Mon, 02 May 2011 09:46:38 -0700 (PDT) Received: from nm26-vm1.access.bullet.mail.mud.yahoo.com (nm26-vm1.access.bullet.mail.mud.yahoo.com [66.94.236.226]) by gmr-mx.google.com with SMTP id x34si2086622anx.9.2011.05.02.09.46.37; Mon, 02 May 2011 09:46:37 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 66.94.236.226 as permitted sender) client-ip=66.94.236.226; Received: from [66.94.237.126] by nm26.access.bullet.mail.mud.yahoo.com with NNFMP; 02 May 2011 16:46:37 -0000 Received: from [66.94.237.115] by tm1.access.bullet.mail.mud.yahoo.com with NNFMP; 02 May 2011 16:46:37 -0000 Received: from [127.0.0.1] by omp1020.access.mail.mud.yahoo.com with NNFMP; 02 May 2011 16:46:37 -0000 X-Yahoo-Newman-Property: ymail-5 X-Yahoo-Newman-Id: 436781.76169.bm@omp1020.access.mail.mud.yahoo.com Received: (qmail 91470 invoked by uid 60001); 2 May 2011 16:46:37 -0000 Message-ID: <169940.81010.qm@web81303.mail.mud.yahoo.com> X-YMail-OSG: 5vZ2V7IVM1m4zZKR2VrF_7pXItt_Ls7e7OEwzcMh9Tjp.M_ KQjY9jJNuF7irJYATL1NtTVAhyrBRoh6z21mx1ppmHvlVhO__dw9O1rqMVOY vRuYUOZpDqgElWXrb1vzqSsToEhf84SB4seMoplNkG4Sg9Yo8W4wFufeS53u kP5TumJOOIZUNHd32wkpA1SixQ7NSJkvxrBnmbOgSp9xtT0tJXJ5fnr8P5hr eojAQjClGta5N6Nd4Wk_VPFQAPnYZyuvhMN8UT72xTXsR87HIrIogv9td895 IX8vAmaITBDZXRnXBb1c0iJTRFeIlM3jr3scQrYoQG0aiK6flpiGOTp7ecIL PNSeii2MDPwnN4UAcksSiSAt_.04ShVa542OgbTrh5bWlc8LeEOS_IhYLFn7 usZFntFa_GAiF9yU- Received: from [99.92.108.41] by web81303.mail.mud.yahoo.com via HTTP; Mon, 02 May 2011 09:46:36 PDT X-Mailer: YahooMailRC/559 YahooMailWebService/0.8.110.299900 References: <412353.33616.qm@web81303.mail.mud.yahoo.com> Date: Mon, 2 May 2011 09:46:36 -0700 (PDT) From: John E Clifford Subject: Re: [lojban] xorlo and default quantifiers To: lojban@googlegroups.com In-Reply-To: MIME-Version: 1.0 X-Original-Sender: kali9putra@yahoo.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 66.94.236.226 as permitted sender) smtp.mail=kali9putra@yahoo.com; dkim=pass (test mode) header.i=@yahoo.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="0-588106004-1304354796=:81010" --0-588106004-1304354796=:81010 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Are you a teacher? Your ability to confuse a simple situation is=20 profession-worthy. The short answer is "No". The two sentences do not=20 necessarily point to the same object -- a truth value, I suppose, or a=20 proposition or a state of affairs -- in either way. In the real world, nev= er=20 mind alternate ones, they mean different things and so may have different t= ruth=20 values and so on down the line (or up it, depending on your ontologies). I am not sure what z is here, but it does not much matter; I suppose the po= int=20 is that x and y have been assigned the same value but could, in the course = of=20 the run,.come to have different ones, whereas whatever value is assigned x = is=20 automatically assigned to z as well. The problem is that you two sentences= are=20 not even as alike as x and y, let alone x and z (which I would suppose is= =20 something like na-shifting, for example -- however that is working this yea= r). Let's begin by assuming that 'lo gerku' has the same referent(s) in both=20 sentences. So, the first sentence says that none of those referents is whi= le. =20 The second says that those referents collectively are not white. Except wh= en=20 there is only one referent, it is not perfectly clear what the referents be= ing=20 (or not being) collectively white means. On one notion of participation, t= his=20 would simply make no sense, or, at least, would be categorically false, and= so=20 the second sentence would be true, whether or not the first was. On anothe= r,=20 the truth of the first would compel the truth of the second, but not conver= sely=20 (this version amount to taking 'lo gerku cu blabi' as 'ro lo gerku cu blabi= ') =20 On a third reading, the two would be strictly equivalent, by na-shifting,= =20 essentially. And there are other readings that fall in between. =20 Being a logical language doesn't mean all problem are solved; it merely mea= ns=20 the confusions are at a higher level (or deeper structure). ________________________________ From: Luke Bergen To: lojban@googlegroups.com Sent: Mon, May 2, 2011 11:04:59 AM Subject: Re: [lojban] xorlo and default quantifiers So, in programming terms: x =3D "hello" y =3D "hello" z =3D x; Now, x and y are "equal" in the sense that they have the same "meaning". B= ut x=20 and z are "equal" in a much more fundamental way. They are 2 different poi= nters=20 but they are pointing at the same object. In that sense, I am asking if {no lo gerku cu blabi} and {lo gerku cu na bl= abi}=20 are "equivalent" in the sense that "x" and "y" are. OR are they "equal" in= the=20 sense that "x" and "z" are? The difference being, it is possible that in some universe "x" and "y" coul= d=20 potentially be different (as in, maybe I just haven't thought of a way yet = which=20 they are different). While "x" and "z" are the exact same thing. =20 Another way to think of it is: I understand "equivalence" to mean "they amo= unt=20 to the same thing" while "equality" is "one can be derived from the other i= n a=20 direct way so that it is logically impossible for the 2 things to differ" i= .e.=20 they share the same identity, they are just different expressions of the sa= me=20 thing. Just because 2 things always MEAN the same thing, does that mean that they = ARE=20 the same thing? broda cei lo gerku ku na blabi .i brode cei no lo gerku ku blabi .i xu lo d= u'u=20 broda cu mintu lo du'u brode .ixu lo du'u broda cu simsa lo du'u brode kei = roda=20 .ixu lo du'u broda cu me lo du'u brode On Mon, May 2, 2011 at 11:23 AM, John E Clifford wro= te: If you do assume thatt lo nanmu cu bevri lo pipno has an implicit ro in fro= nt,=20 you will misunderstand what it says. >no is not a number like the others, being defined by a negation, though i= t does=20 >represent a digit. used on an argument, it affects the whole proposition (= as=20 >does every quantifier), in this case by putting a negation somewhere in it= . >Incidentally, whether you take noun phrases as referring to objects or L-s= ets,=20 >no is not a permissible internal quantifier. >The apple eating examples are not equivalent, since 'lo plise' in one need= not=20 >have the same referent as 'plise' in the second. In the second 'plise' re= fers=20 >to all apples (in the domain), in the first 'lo plise' refers to apples wh= ich=20 >may be contextually specified (less than all). So the second imples the = first=20 >but not conversely. (What do you mean by "are teh statements the same?" o= ther=20 >than "do they mean the same thing" -- clearly they are different sentences= .) > > > > ________________________________ From: Luke Bergen >To: lojban@googlegroups.com >Sent: Sun, May 1, 2011 11:04:56 PM > >Subject: Re: [lojban] xorlo and default quantifiers > > >mmm, good points. I guess what I was getting at is, just because there ar= e no=20 >default quantifiers doesn't mean that people are going to use context to a= ssume=20 >them. (for example, you assume that {ro lo nanmu cu bevri lo pipno}) > > >And also that seems weird. {no} is a number just like {pa}, {re}, {su'o},= or=20 >{so'i}. It seems weird that using it as a quantifier of a sumti can direc= tly=20 >effect the selbri in ways that other numbers can't. > > >I understand intuitively why that is the case. But it still feels strange= . I=20 >kind of have to wonder if {mi na citka lo plise} and {mi citka no plise} r= eally=20 >are identical (I know that the meanings of the statements are the same, bu= t are=20 >the statements themselves the same as each other) > > >2011/5/1 Jorge Llamb=EDas > >On Sun, May 1, 2011 at 5:08 PM, Luke Bergen wrote: >>> So I was thinking about this earlier today and came to a realization. = If >>> xorlo says that there are no default quantifiers for {lo} then wouldn't= {no} >>> be a reasonable possibility for the assumed quantifier? >> >>No, there isn't an assumed quantifier either. >> >> >>> e.g. {mi citka lo plise}. {lo plise} has no outer quantifier (implicit= or >>> explicit), but I suspect that most people will pick up from context tha= t I >>> in fact {citka pa lo su'opa plise} or something like it. >> >>It will depend on the context, but as an isolated sentence I would >>translate it as "I eat apples". It doesn't even have to be about any >>specific occasion. I suspect that "I eat exactly one of the at least >>one apples" is not one of the most common interpretations. >> >> >>> Furthermore, if I >>> said {mi nelci lo nu tcidu .i mi ponse lo cukta} I would think that peo= ple >>> would read that as something like {mi ponse so'o lo so'i cukta} or some= thing >>> like it. >> >>I would read it as "I like reading. I own books." I don't think I >>would read it as "I own several of many books". >> >> >>> So if context can change the assumptions that the tecusku makes about t= he >>> secusku, then couldn't one of those assumptions be {no lo cukta} since = there >>> is no proscribed default? >> >>No, because "no" contains a negation. If you say "mi citka" you can't >>expect people to understand that you mean "mi na citka". Similarly, if >>you say "mi citka lo plise" you can't expect anyone to understand that >>you mean "mi citka no lo plise". >> >> >>> Either the default quantifiers of {lo} should be {su'o} or it should be >>> reasonable to assume that {mi xebni lo nu tcidu .ija'ebo mi ponse lo cu= kta} >>> could be understood as {mi xebni lo nu tcidu .ija'ebo mi ponse no lo cu= kta}. >> >>But "lo" has no quantifiers, default or otherwise. Why do you want to >>force one on it? >> >> >>> In my mind the latter is an unsafe assumption and I suspect that most >>> tecusku would respond with something like {.ue do cusku lo du'u brodado= na >>> nelci lo nu tcidu .iku'i do ji'a cusku lo nu do ponse lo cukta .i va'o = lo nu >>> broda kei mi sruma lo nu na brode}. Therefore, I argue that even if th= e >>> grammar claims that {lo} has no default quantifiers, people read lojban= with >>> the assumption that {lo}'s implicit quantifiers are {su'o}. >>> Thoughts? >> >>I at least don't. >> >>Here is an example where "su'o" fails: >> >>lo ci nanmu ca'o bevri lo pipno. >>"Three men are carrying a piano." >> >>It would not occur to me to conclude that at least one of the three >>men is carrying a piano, my assumption would be that they are all >>three doing it together. >> >>mu'o mi'e xorxes >> >>-- >>You received this message because you are subscribed to the Google Groups= =20 >>"lojban" group. >>To post to this group, send email to lojban@googlegroups.com. >>To unsubscribe from this group, send email to=20 >>lojban+unsubscribe@googlegroups.com. >>For more options, visit this group at=20 >>http://groups.google.com/group/lojban?hl=3Den. >> >> > --=20 > >You received this message because you are subscribed to the Google Groups= =20 >"lojban" group. >To post to this group, send email to lojban@googlegroups.com. >To unsubscribe from this group, send email to=20 >lojban+unsubscribe@googlegroups.com. >For more options, visit this group at=20 >http://groups.google.com/group/lojban?hl=3Den. > --=20 > >You received this message because you are subscribed to the Google Groups= =20 >"lojban" group. >To post to this group, send email to lojban@googlegroups.com. >To unsubscribe from this group, send email to=20 >lojban+unsubscribe@googlegroups.com. >For more options, visit this group at=20 >http://groups.google.com/group/lojban?hl=3Den. > --=20 You received this message because you are subscribed to the Google Groups= =20 "lojban" group. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to=20 lojban+unsubscribe@googlegroups.com. For more options, visit this group at=20 http://groups.google.com/group/lojban?hl=3Den. --=20 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. --0-588106004-1304354796=:81010 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Are you a teacher?  Your ability to confuse a simple situ= ation is profession-worthy.  The short answer is "No".  The two s= entences do not necessarily point to the same object -- a truth value, I su= ppose, or a proposition or a state of affairs -- in either way.  In th= e real world, never mind alternate ones, they mean different things and so = may have different truth values and so on down the line (or up it, dependin= g on your ontologies).
I am not sure what z is here, but it does not muc= h matter; I suppose the point is that x and y have been assigned the same v= alue but could, in the course of the run,.come to have different ones, wher= eas whatever value is assigned x is automatically assigned to z as well.&nb= sp; The problem is that you two sentences are not even as alike as x and y, let alone x and z (which I would suppose is something like na-shifting,= for example -- however that is working this year).
Let's begin by assum= ing that 'lo gerku' has the same referent(s) in both sentences.  So, t= he first sentence says that none of those referents is while.  The sec= ond says that those referents collectively are not white.  Except when= there is only one referent, it is not perfectly clear what the referents b= eing (or not being) collectively white means.  On one notion of partic= ipation, this would simply make no sense, or, at least, would be categorica= lly false, and so the second sentence would be true, whether or not the fir= st was.  On another, the truth of the first would compel the truth of = the second, but not conversely (this version amount to taking 'lo gerku cu = blabi' as 'ro lo gerku cu blabi')  On a third reading, the two would b= e strictly equivalent, by na-shifting, essentially.  And there are other readings that fall in between. 
Being a logical languag= e doesn't mean all problem are solved; it merely means the confusions are a= t a higher level (or deeper structure).



From: Luke Bergen <lukeabergen@gmail.com>
<= b>To: lojban@googlegroups.com=
Sent: Mon, May 2, 2011= 11:04:59 AM
Subject: R= e: [lojban] xorlo and default quantifiers

So, in programming terms:
x =3D "hello"
y =3D "hello"
z =3D x;

Now, x and y are "equal" in the sense = that they have the same "meaning".  But x and z are "equal" in a much = more fundamental way.  They are 2 different pointers but they are poin= ting at the same object.

In that sense, I am asking if {no lo gerku cu blabi} an= d {lo gerku cu na blabi} are "equivalent" in the sense that "x" and "y" are= .  OR are they "equal" in the sense that "x" and "z" are?

The difference being, it is possible that in some unive= rse "x" and "y" could potentially be different (as in, maybe I just haven't= thought of a way yet which they are different).  While "x" and "z" ar= e the exact same thing.  

Another way to think of it is: I understand "equivalenc= e" to mean "they amount to the same thing" while "equality" is "one can be = derived from the other in a direct way so that it is logically impossible f= or the 2 things to differ" i.e. they share the same identity, they are just= different expressions of the same thing.

Just because 2 things always MEAN the same thing, does = that mean that they ARE the same thing?

broda cei = lo gerku ku na blabi .i brode cei no lo gerku ku blabi .i xu lo du'u broda = cu mintu lo du'u brode .ixu lo du'u broda cu simsa lo du'u brode kei roda .= ixu lo du'u broda cu me lo du'u brode

On Mon, May 2, 2011 at 11:23 AM, J= ohn E Clifford <kali9putra@yahoo.com> wrote:
If you do assume thatt lo nanmu cu bevri lo pipno has an = implicit ro in front, you will misunderstand what it says.
no is not a n= umber  like the others, being defined by a negation, though it does re= present a digit. used on an argument, it affects the whole proposition (as = does every quantifier), in this case by putting a negation somewhere in it.=
Incidentally, whether you take noun phrases as referring to objects or L-se= ts, no is not a permissible internal quantifier.
The apple eating exampl= es are not equivalent, since 'lo plise' in one need not have the same refer= ent as 'plise' in the second.  In the second 'plise' refers to all app= les (in the domain), in the first 'lo plise' refers to apples which may be = contextually specified (less than all).  So the second imples the first but not conversely.  (What do you mean by "are teh statemen= ts the same?" other than "do they mean the same thing" -- clearly they are = different sentences.)


From: Luke Bergen <lukeabergen@gmail.com>
To: lojban@googlegroups.com
Sent: Sun, May 1, 2011 11:04:56 PM

Subject: Re: [lojban] x= orlo and default quantifiers

mmm, good points.  I guess what I was getting at is, just because ther= e are no default quantifiers doesn't mean that people are going to use cont= ext to assume them.  (for example, you assume that {ro lo nanmu cu bev= ri lo pipno})

And also that seems weird.  {no} is a number just like = {pa}, {re}, {su'o}, or {so'i}.  It seems weird that using it as a quan= tifier of a sumti can directly effect the selbri in ways that other numbers= can't.

I understand intuitively why that is the case.  Bu= t it still feels strange.  I kind of have to wonder if {mi na citka lo= plise} and {mi citka no plise} really are identical (I know that the meani= ngs of the statements are the same, but are the statements themselves the s= ame as each other)

2011/5/1 Jorge Llamb=EDas = <jjllambias@gmail.com>
On Sun, May 1, 2011 at 5:08 PM, Luke Bergen <lukeabergen@gmail.com> wrote:
> So I was thinking about this earlier today and came to a realization. =  If
> xorlo says that there are no default quantifiers for {lo} then wouldn'= t {no}
> be a reasonable possibility for the assumed quantifier?

No, there isn't an assumed quantifier either.

> e.g. {mi citka lo plise}.  {lo plise} has no outer quantifier (im= plicit or
> explicit), but I suspect that most people will pick up from context th= at I
> in fact {citka pa lo su'opa plise} or something like it.

It will depend on the context, but as an isolated sentence I would translate it as "I eat apples". It doesn't even have to be about any
specific occasion. I suspect that "I eat exactly one of the at least
one apples" is not one of the most common interpretations.

> Furthermore, if I
> said {mi nelci lo nu tcidu .i mi ponse lo cukta} I would think that pe= ople
> would read that as something like {mi ponse so'o lo so'i cukta} or som= ething
> like it.

I would read it as "I like reading. I own books." I don't think I
would read it as "I own several of many books".

> So if context can change the assumptions that the tecusku makes about = the
> secusku, then couldn't one of those assumptions be {no lo cukta} since= there
> is no proscribed default?

No, because "no" contains a negation. If you say "mi citka" you can't=
expect people to understand that you mean "mi na citka". Similarly, if
you say "mi citka lo plise" you can't expect anyone to understand that
you mean "mi citka no lo plise".

> Either the default quantifiers of {lo} should be {su'o} or it should b= e
> reasonable to assume that {mi xebni lo nu tcidu .ija'ebo mi ponse lo c= ukta}
> could be understood as {mi xebni lo nu tcidu .ija'ebo mi ponse no lo c= ukta}.

But "lo" has no quantifiers, default or otherwise. Why do you want to=
force one on it?

>  In my mind the latter is an unsafe assumption and I suspect that= most
> tecusku would respond with something like {.ue do cusku lo du'u brodad= o na
> nelci lo nu tcidu .iku'i do ji'a cusku lo nu do ponse lo cukta .i va'o= lo nu
> broda kei mi sruma lo nu na brode}.  Therefore, I argue that even= if the
> grammar claims that {lo} has no default quantifiers, people read lojba= n with
> the assumption that {lo}'s implicit quantifiers are {su'o}.
> Thoughts?

I at least don't.

Here is an example where "su'o" fails:

lo ci nanmu ca'o bevri lo pipno.
"Three men are carrying a piano."

It would not occur to me to conclude that at least one of the three
men is carrying a piano, my assumption would be that they are all
three doing it together.

mu'o mi'e xorxes

--
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@googlegro= ups.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@googlegro= ups.com.
For more options, visit this group at http://groups.googl= e.com/group/lojban?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@googlegro= ups.com.
For more options, visit this group at http://groups.googl= e.com/group/lojban?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/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.
--0-588106004-1304354796=:81010--