Received: from mail-pd0-f186.google.com ([209.85.192.186]:38422) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XnaWO-0000hm-GP for lojban-list-archive@lojban.org; Sun, 09 Nov 2014 13:59:52 -0800 Received: by mail-pd0-f186.google.com with SMTP id r10sf977262pdi.13 for ; Sun, 09 Nov 2014 13:59:38 -0800 (PST) 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=LJ51Q+RE6yIv4G5LMKUu/EvxVhYBBf+FhNk4oMDCB+c=; b=ULrysMj/Yudi0GCDLrTCqoWECDjDCjk0MMD39L5UMs2EAc1DQzbbqW21yQhrl5iqrg 5gkKg6w8JDSsIb3D1NS8gDA9EQYmOXrzDDm8+uLMjju1GheTMPdbDkiOqvzlw99mPubc 8wEffEyEbUWxG7YxovTfXRWzVP6jEQZCg8HT/fHEUu2y4d4096xopbqy/MUZ4syWUIMz AzEFOrq/aQZdHUlf95kDlxb3iJaDcHZY0q7zA3SVy4HTEojmxUm5Zo90aL+xTr4Dq1c4 FJNfjlR4wxDUrBBtQRweuu6iExsfyIr3/96IcOxZ3pGOhDx1PAK/C/i0YCcVG6chR2tf ET4A== X-Received: by 10.50.124.8 with SMTP id me8mr190400igb.3.1415570378076; Sun, 09 Nov 2014 13:59:38 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.51.17.97 with SMTP id gd1ls2770767igd.22.canary; Sun, 09 Nov 2014 13:59:37 -0800 (PST) X-Received: by 10.66.66.234 with SMTP id i10mr20017013pat.31.1415570377671; Sun, 09 Nov 2014 13:59:37 -0800 (PST) Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.24]) by gmr-mx.google.com with ESMTPS id jq13si974447pbb.1.2014.11.09.13.59.37 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 09 Nov 2014 13:59:37 -0800 (PST) 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 sA9LxXlE006096 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO) for ; Sun, 9 Nov 2014 21:59:35 GMT Received: from martin by thegonz.net with local (Exim 4.80.1) (envelope-from ) id 1XnaVC-0000hN-Q8 for lojban@googlegroups.com; Sun, 09 Nov 2014 16:58:30 -0500 Date: Sun, 9 Nov 2014 16:58:30 -0500 From: Martin Bays To: lojban@googlegroups.com Subject: Re: [lojban] Re: tersmu 0.2 Message-ID: <20141109215830.GB30874@gonzales> References: <20141108232204.GB31242@gonzales> <20141109145940.GA8588@gonzales> <20141109154145.GC8588@gonzales> <20141109161417.GE8588@gonzales> <20141109192217.GH8588@gonzales> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kORqDWCi7qDJ0mEj" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://mbays.freeshell.org/pubkey.asc X-PGP-KeyId: B5FB2CD6 X-cunselcu'a-valsi: carmi 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: - --kORqDWCi7qDJ0mEj Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Sunday, 2014-11-09 at 17:46 -0300 - Jorge Llamb=EDas : > On Sun, Nov 9, 2014 at 4:22 PM, Martin Bays wrote: >=20 > > What's the advantage of adding this layer of indirection? >=20 > I don't think I'm adding any layers. All I'm saying is that a bridi refers > to one thing rather than to a whole family of things. I see. Persuing this would lead to the "which is primary - the instance or the kind?" debate, which is probably best avoided! > One thing which seems like a clear disadvantage to me: > > e.g. in this example > > ca ro nu mi xagji kei mi klama lo zarci .e ba bo lo zdani > > -> ca ro nu mi xagji kei ko'a fasnu .i ko'a nu ge ko'e fasnu gi ko'i > > fasnu > > .i ko'i nu ko'o balvi ko'e .i ko'e nu mi klama lo zarci > > .i ko'o nu mi klama lo zdani > > , there's still no specific indication that the instance of ko'e > > witnessing {ko'e fasnu} is the same as the instance of {ko'e} witnessing > > {ko'o balvi ko'e}. The only connection is that they're both meant to > > happen at around the same time. >=20 > You introduced instances of ko'e in your indirect metalinguistic > interpretation, but no instances of ko'e are required to interpret the > sentence. In the direct interpretation there's just ko'e. You check wheth= er > ko'o and ko'e satisfy balvi( , ) at the right time, not that any new enti= ty > called intance of ko'e satisfies it. OK, fine. But however you want to describe it, there's an element of co-ordination between the {ko'e fasnu} and the {ko'o balvi ko'e} which I believe is a crucial part of the semantics of the original sentence, but which seems to get lost in your kind-based rewriting. Depending on how things work, maybe it could be a matter of making the translation be: ca ro nu mi xagji kei lo nu mi klama lo zarci kei fasnu je se balvi be lo nu mi klama lo zdani (where again we need to add, and can't seem to in lojban, that the {lo nu}s are getting kinds)? I'm thinking that using {je} there be different from using {gi'e} - if ko'a is the kind of broda(x), then {ko'a brodi je brodu} ~~ {su'o da poi broda cu brodi je brodu} {ko'a brodi gi'e brodu} ~~ {su'o da poi broda cu brodi .i je su'o da poi broda cu brodu} (where I don't know exactly what the relation between left and right is, but probably at least right implies left). > Or how do you interpret "ca ro nu mi xagji kei mi mi ctigau"? Is there > any indication that the time-slice of "mi" witnessing the first "mi" > is the same time-slice of "mi" witnessing the second "mi" of "mi mi > ctigau"? I'm not sure what you're getting at. The times are (roughly) the same, by the semantics of {ca}, so yes they're (roughly) the same time-slices. But no extra indication of that is required. I suppose one has to use that future-me can't be hungry now. Martin --kORqDWCi7qDJ0mEj Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlRf44YACgkQULC7OLX7LNawwACePHhNz5O3OyVDAYxEmgoJr4Zs rQsAnjCavoPliDjpu8vXZ4WGdF5UDGyz =D25Z -----END PGP SIGNATURE----- --kORqDWCi7qDJ0mEj--