Received: from mail-wi0-f185.google.com ([209.85.212.185]:44392) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XeVmp-0003Ta-Ew for lojban-list-archive@lojban.org; Wed, 15 Oct 2014 14:07:17 -0700 Received: by mail-wi0-f185.google.com with SMTP id n3sf213675wiv.22 for ; Wed, 15 Oct 2014 14:07:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:date:message-id:subject:from: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=EyAJFiukihk/cqk8wp3+CBirS78LHNt/SpzwbrNOA7g=; b=oW4mXIdY4uxC042FpxzNQQ13gkyBlIPC/mcOddnv5kqz4PRJb76YEFoX/efCGijnIn QKi2JKXjGmu5vLIoeEfL42HeRYEDOimYwx3gFsGKYUKOzfisAJl25vqo0dV4U6ZtL/jW TUpOmmF60uok0681KfgCpb2/tmDfiU414bsPwRjH88HhDNHIwO0syvj8vh4AgL8PB20/ 6fenaJvtmh2Y/kf3D+/BX6Gllx6XAX4Lx7+FOSew8EY9ZMA6utqZwR/z3gISglvlrZYM s3g0tip+5ziC8SQp3/ouF3bKKD2ShmR9574jIKadgwEIcWjuEYRbhKXxTlUXpX2bnIn1 JeTg== X-Received: by 10.180.100.106 with SMTP id ex10mr3168wib.0.1413407224570; Wed, 15 Oct 2014 14:07:04 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.180.78.2 with SMTP id x2ls184104wiw.1.gmail; Wed, 15 Oct 2014 14:07:04 -0700 (PDT) X-Received: by 10.180.72.141 with SMTP id d13mr2532355wiv.6.1413407224096; Wed, 15 Oct 2014 14:07:04 -0700 (PDT) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com. [2a00:1450:400c:c05::231]) by gmr-mx.google.com with ESMTPS id o2si541389wib.2.2014.10.15.14.07.04 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 15 Oct 2014 14:07:04 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::231 as permitted sender) client-ip=2a00:1450:400c:c05::231; Received: by mail-wi0-x231.google.com with SMTP id fb4so3042227wid.16 for ; Wed, 15 Oct 2014 14:07:04 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.73.244 with SMTP id o20mr15333702wiv.12.1413407224021; Wed, 15 Oct 2014 14:07:04 -0700 (PDT) Received: by 10.217.105.201 with HTTP; Wed, 15 Oct 2014 14:07:03 -0700 (PDT) In-Reply-To: <20141015005542.GC3713@gonzales> References: <20141011021201.GH22868@gonzales> <20141011143749.GD23876@gonzales> <20141012012427.GF23876@gonzales> <20141012173533.GG23876@gonzales> <20141014010742.GF19061@gonzales> <20141015005542.GC3713@gonzales> Date: Wed, 15 Oct 2014 18:07:03 -0300 Message-ID: Subject: Re: [lojban] Re: tersmu 0.2 From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= To: lojban@googlegroups.com X-Original-Sender: jjllambias@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::231 as permitted sender) smtp.mail=jjllambias@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=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: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=f46d0435c06a82c80b05057c832a X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --f46d0435c06a82c80b05057c832a Content-Type: text/plain; charset=UTF-8 On Tue, Oct 14, 2014 at 9:55 PM, Martin Bays wrote: > > > But the rule for logically connected sumti at top level is the same rule > as for logical connectives in various other places, e.g. bridi tails, > abstractions, tags, operators, operands. Roughly, that rule is: you > substitute in each of the connected possibilities, yielding two > propositions, then logically connect those propositions. > Yes, but that rule doesn't automatically apply to all constructs. You can't for example apply it directly to "lo broda be ko'a .e ko'e cu brode". Therefore it is effectively a separate rule for each construct it applies to. For sumti-tail there's an obvious choice: {lo [quantifier] [sumti]} > could be equivalent to {lo [quantifier] me [sumti]} for complex sumti as > well as for simple sumti. > LE [quantifier] [sumti] is interesting. I think I never actually gave much thought to "lo re lo mlatu .e ci lo gerku" having such a very unintuitive parse. In any case, I wouldn't introduce an additional rule to interpret "lo ci ko'a .a ko'e": lo ci ko'a .a ko'e =lo poi'i ci mei gi'e me ko'a .a ko'e =lo poi'i ci mei gi'e ga me ko'a gi me ko'e I assume you are not interpreting it in that way, but rather as "lo ci ko'a ku .a lo ci ko'e"? For {me}, I'm not sure... is there something {ko'a me ko'e .e ko'i} > could mean other than {ko'a me ko'e .i je ko'a me ko'i}? > For "me [sumti]", the predicate "menre" was proposed, such that "me [sumti]" = "menre (be) [sumti]". "me ko'a .e ko'e" doesn't require a new rule since: me ko'a .e ko'e = menre ko'a .e ko'e = ge menre ko'a gi menre ko'e = ge me ko'a gi me ko'e As for {mo'e}, I suppose we could use a relation "is the value > corresponding to"? But it really does seem to me much simpler to just > have {mo'e ko'a .e ko'e} be equivalent to {mo'e ko'a .e mo'e ko'e}. > I have no idea what the rules for mekso are in detail, so I don't know whether for example "li na'u sinso mo'e ko'a .e ko'e" is supposed to be equivalent to "lo sinso be ko'a .e ko'e" or to "li na'u sinso mo'e ko'a lo'o .e li na'u sinso mo'e ko'e". I would like to say (not too adamantly) that it's the first, which doesn't require an additional rule for ".e", but you are probably interpreting as the second. > Do we even know what "na ku zo'u broda .i bo brode" means? > > I believe it's the same as "na ku ge broda gi brode". > I suppose that's one choice, although it's not a necessity that juxtaposition be equated with conjunction, or that the negation of two separate propositions has to be the negation of their conjunction. mu'o mi'e xorxes -- You received this message because you are subscribed to the Google Groups "lojban" group. To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban. For more options, visit https://groups.google.com/d/optout. --f46d0435c06a82c80b05057c832a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Tue, Oct 14, 2014 at 9:55 PM, Martin Bays <mbays@sdf.org> wr= ote:

But the rule for logically connected sumti at top level is the same = rule
as for logical connectives in various other places, e.g. bridi tails,
abstractions, tags, operators, operands. Roughly, that rule is: you
substitute in each of the connected possibilities, yielding two
propositions, then logically connect those propositions.

Yes, but that rule doesn't automatically apply to all= constructs. You can't for example apply it directly to "lo broda = be ko'a .e ko'e cu brode". Therefore it is effectively a separ= ate rule for each construct it applies to.

For sumti-tail there's an obvious choice: {lo [quantifier] [sumti]}
could be equivalent to {lo [quantifier] me [sumti]} for complex sumti as well as for simple sumti.

LE [quantifie= r] [sumti] is interesting. I think I never actually gave much thought to &q= uot;lo re lo mlatu .e ci lo gerku" having such a very unintuitive pars= e.

In any case, I wouldn't introduce an additi= onal rule to interpret "lo ci ko'a .a ko'e":
lo ci ko'a .a ko'e
=3Dlo poi'i ci mei gi= 'e me ko'a .a ko'e
=3Dlo poi'i ci mei gi'e ga= me ko'a gi me ko'e

I assume you are not i= nterpreting it in that way, but rather as "lo ci ko'a ku .a lo ci = ko'e"?=C2=A0

For {me}, I'm not sure... is there something {ko'a me ko'e .e k= o'i}
could mean other than {ko'a me ko'e .i je ko'a me ko'i}?

For "me [sumti]", the predicate= "menre" was proposed, such that "me [sumti]" =3D "= ;menre (be) [sumti]". "me ko'a .e ko'e" doesn't = require a new rule since:=C2=A0

me ko'a .e ko&= #39;e
=3D menre ko'a .e ko'e
=3D ge menre ko= 9;a gi menre ko'e
=3D ge me ko'a gi me ko'e


As for {mo'e}, I suppose we could use a relation "is the value
corresponding to"? But it really does seem to me much simpler to just<= br> have {mo'e ko'a .e ko'e} be equivalent to {mo'e ko'a .e= mo'e ko'e}.

I have no ide= a what the rules for mekso are in detail, so I don't know whether for e= xample "li na'u sinso mo'e ko'a .e ko'e" is suppo= sed to be equivalent to "lo sinso be ko'a .e ko'e" or to = "li na'u sinso mo'e ko'a lo'o .e li na'u sinso mo&= #39;e ko'e". I would like to say (not too adamantly) that it's= the first, which doesn't require an additional rule for ".e"= , but you are probably interpreting as the second.=C2=A0

=C2=A0> Do we even know what "na ku zo'u broda .i = bo brode" means?

I believe it's the same as "na ku ge broda gi brode".<= br>

I suppose that's one choice, althou= gh it's not a necessity that juxtaposition be equated with conjunction,= or that the negation of two separate propositions has to be the negation o= f their conjunction.
=C2=A0
mu'o mi'e xorxes

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsub= scribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http:= //groups.google.com/group/lojban.
For more options, visit http= s://groups.google.com/d/optout.
--f46d0435c06a82c80b05057c832a--