Received: from mail-ie0-f183.google.com ([209.85.223.183]:43171) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XaQ6t-0005BD-Jv for lojban-list-archive@lojban.org; Sat, 04 Oct 2014 07:15:11 -0700 Received: by mail-ie0-f183.google.com with SMTP id rp18sf226796iec.20 for ; Sat, 04 Oct 2014 07:14:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent :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; bh=a22MpoyAaPIQL0KGCObwR/OoM1IJ9sVj7p+MwRPLZ84=; b=e7gQ5Xt9BGtuwv02xXUPkSArNrckf7cHDTIoZ+xX6REmhmDPcRZiwBYJVGp6HKZyBv EZeIZhvzbpGYeKqYjLaFxhG9sbkunqUF8oo91oYWCrR1ziUkWJzmFTG5hxf04FRGU/6i vwEMJkO8Gp12iM1gYKhoc1pUIqEiRHHRrv59IyLNJk1bDumkUTuH5Ljgqu6usCFLs2rb qyqyhJWSF7P8ngxw0DJdqzHAGAz9C+C5HqUnETXFseTSMq3zYxn78R/kyIhHjkU4I40A ZwnxxgjpSNPO0f1krpi8ko2VelkcsvnHdm2nD4WKuaUB7wBnlF4LPdBsn/xX+1OzDjRi qUKQ== X-Received: by 10.50.164.137 with SMTP id yq9mr42519igb.16.1412432093013; Sat, 04 Oct 2014 07:14:53 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.50.128.42 with SMTP id nl10ls1593034igb.25.gmail; Sat, 04 Oct 2014 07:14:52 -0700 (PDT) X-Received: by 10.42.13.146 with SMTP id d18mr13499917ica.19.1412432092610; Sat, 04 Oct 2014 07:14:52 -0700 (PDT) Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.24]) by gmr-mx.google.com with ESMTPS id pz1si1336074pbb.0.2014.10.04.07.14.52 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 04 Oct 2014 07:14:52 -0700 (PDT) Received-SPF: none (google.com: mbays@sdf.org does not designate permitted sender hosts) client-ip=192.94.73.24; Received: from thegonz.net (d24-141-9-29.home.cgocable.net [24.141.9.29]) (authenticated (0 bits)) by sdf.lonestar.org (8.14.8/8.14.5) with ESMTP id s94EEY8K025355 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO) for ; Sat, 4 Oct 2014 14:14:35 GMT Received: from martin by thegonz.net with local (Exim 4.80.1) (envelope-from ) id 1XaQ64-00082u-2Z for lojban@googlegroups.com; Sat, 04 Oct 2014 10:14:08 -0400 Date: Sat, 4 Oct 2014 10:14:07 -0400 From: Martin Bays To: lojban@googlegroups.com Subject: Re: [lojban] Re: tersmu 0.2 Message-ID: <20141004141407.GG32481@gonzales> References: <3c3b1c5e-cac2-42df-9d67-553a849789d3@googlegroups.com> <20140927192952.GS28734@gonzales> <20140927195841.GT28734@gonzales> <5349359c-f884-4976-a3e1-b0610eabeff6@googlegroups.com> <20140928013358.GB28734@gonzales> <20140928152915.GB7320@gonzales> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LSp5EJdfMPwZcMS1" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://mbays.freeshell.org/pubkey.asc X-PGP-KeyId: B5FB2CD6 X-cunselcu'a-valsi: gunka User-Agent: Mutt/1.5.22 (2013-10-16) X-Original-Sender: mbays@sdf.org X-Original-Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: mbays@sdf.org does not designate permitted sender hosts) smtp.mail=mbays@sdf.org 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: , X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --LSp5EJdfMPwZcMS1 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Sunday, 2014-09-28 at 22:00 -0300 - Jorge Llamb=EDas : > On Sun, Sep 28, 2014 at 12:29 PM, Martin Bays wrote: >=20 > > In particular, passing this lojbanic form back through tersmu would > > yield something involving {srana} whose equivalence to the original form > > involving f(x) is far from immediate. Worse, there wouldn't even be > > a fixed point for the lojban form - since {pe} without a quantifier is > > taken as effectively introducing a {noi} clause, {ro da zo'u fy pe da > > broda da} would become {ro da zo'u ge fyno pe da ge'u srana da gi fyno > > pe da ge'u me fy me'u .i ro da zo'u fyno pe da ge'u broda da}, which on > > another pass through would blow up those {pe} clauses even further... >=20 > Yes, I see what you mean. I take it then that the parser doesn't touch > li-expressions, or at least some of them? It handles matching operands with operators and so on, but quickly arrives at a fixed point. > > Hmm. I've been adopting {lo broda} =3D=3D {zo'e noi broda} as absolute > > dogma, so it's really making a side-claim that the referent(s) broda(s). > > You think a more accurate dogma would be > > {lo broda} =3D=3D {zo'e noi ca'e broda}? >=20 > No, I was thinking of "ca'e" as defining the new auxiliary variables > introduced by the parsing. I wouldn't say it's a definition exactly. That it brodas need not be enough to pick the referent out uniquely, so I don't see that we can take it as a definition. > But I do think that noi-clauses in general, and > the noi-clause used in the espansion of "lo" in particular, have an > illocutionary force different from assertions. I'm now thinking "zo'e noi > sa'a broda" could be it. Hmm. Could you spell out a bit more what this means? I'd interpret that as "zo'e brodas, but this isn't the main point of my text", just making explicit what's already implicit in relegating the assertion to a noi-clause. I would take that kind of subtlety to be extralogical. Martin --LSp5EJdfMPwZcMS1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlQwAK8ACgkQULC7OLX7LNZvogCgz5TWlvkyy/Y1mRbz0cb55v3L Kq4AoKzxjUb8K/8UJR5ss4aQv3/AMQ44 =1kYD -----END PGP SIGNATURE----- --LSp5EJdfMPwZcMS1--