Received: from mail-da0-f56.google.com ([209.85.210.56]:34364) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1UeyUE-000051-SG for lojban-list-archive@lojban.org; Tue, 21 May 2013 19:09:18 -0700 Received: by mail-da0-f56.google.com with SMTP id i30sf402940dad.1 for ; Tue, 21 May 2013 19:09:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-beenthere: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:x-google-group-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; bh=x7GrE7s74yFd6lqitoh2zUT/3qF9j2wfy2o7gKAMU6U=; b=TFRpXIL3+eNLDvDoKp8nf8NJxr78lbXDd8VsuNLC3sXK1TU3Wp7TjurbqeTBTGTdnf qgFe+Og76z7/cox/sHNuf7UGBNcxfZMBhtpl2uVkgz8eeTekGuG3Wzs6OA23CUhddNtE 1f7R1xwtTijNBYpQt+Fimip0nlhEEpKwb1YQ5qQzWpZRqQJDBW7GB86OO+yeMPfvI2ft 73hXYXKcwE7HIkVwuB4AnUWIcu1UhTUYiwScBMOk2uxj3v64HTNRsKXUVOn2zUGa7XGb A3yK7sozQjO7N5zfqrHXLMLA07dtBnYLRQXeLua8Sy9jfB+tHavuCKUp6def6Wd9CopE qYnA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-beenthere: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:x-google-group-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; bh=x7GrE7s74yFd6lqitoh2zUT/3qF9j2wfy2o7gKAMU6U=; b=y3bsTGGGSFXnDY1FgTX7/4ea+IgHSKObUGLej5ivcWeHo2gpqKZNwuSHfhh8U3igCr qLYruinE+IMJ2F+ZSjFFJNSA+CAhXxonUj5wCuJQ3SmXm/TfBuEv8EuhPSWj2rC31WkN K59b6iPRba9xMcxq8AGpavhQ4XwgrtC4DpD2+Xn9ie7grLKeu0Tp1atEnV4LtHzTHuEg 2EgklhHHD4lkYmRRiyl7r/CBgCwrFh6tMiZYqOvxTq4r6sooGTI0SYQWOojmToNM06u4 UvzUy2qD5GPuRGW4dfpd+cPpcpL46BCZIWTy0D4/UsGbNYUtZuwzeiltxiRJPdu8m1bc nwng== X-Received: by 10.49.12.43 with SMTP id v11mr490326qeb.38.1369188539762; Tue, 21 May 2013 19:08:59 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.49.51.69 with SMTP id i5ls602757qeo.89.gmail; Tue, 21 May 2013 19:08:59 -0700 (PDT) X-Received: by 10.52.244.1 with SMTP id xc1mr1142614vdc.7.1369188539351; Tue, 21 May 2013 19:08:59 -0700 (PDT) Received: from mail-vb0-x22a.google.com (mail-vb0-x22a.google.com [2607:f8b0:400c:c02::22a]) by gmr-mx.google.com with ESMTPS id xu10si319055vdb.0.2013.05.21.19.08.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 May 2013 19:08:59 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2607:f8b0:400c:c02::22a as permitted sender) client-ip=2607:f8b0:400c:c02::22a; Received: by mail-vb0-f42.google.com with SMTP id w15so549609vbf.1 for ; Tue, 21 May 2013 19:08:59 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.220.174.75 with SMTP id s11mr1989223vcz.61.1369188539199; Tue, 21 May 2013 19:08:59 -0700 (PDT) Received: by 10.220.13.3 with HTTP; Tue, 21 May 2013 19:08:59 -0700 (PDT) In-Reply-To: <519C13CF.1090406@gmx.de> References: <519C13CF.1090406@gmx.de> Date: Tue, 21 May 2013 23:08:59 -0300 Message-ID: Subject: Re: [lojban] Tags and bridi operators From: =?ISO-8859-1?Q?Jorge_Llamb=EDas?= 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 2607:f8b0:400c:c02::22a as permitted sender) smtp.mail=jjllambias@gmail.com; dkim=pass header.i=@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: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=047d7b3a90b282758204dd450c61 X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / --047d7b3a90b282758204dd450c61 Content-Type: text/plain; charset=ISO-8859-1 On Tue, May 21, 2013 at 9:39 PM, selpa'i wrote: > We know that na(ku), quantifiers, connectives and tenses are bridi > operators, but what about non-tense tags? Some clearly are bridi operators, > for instance the causals: > In general, tags for which the rest of the bridi is an argument of the tag's underlying selbri would be bridi operators. Those are also the easiest tags to come up with a clean definition for. Maybe all tags have to be defined that way. > Either we make every tag, no matter what selma'o it belongs to, a bridi > operator, or we pick some that are operators and some that aren't depending > on what is the most useful / easiest to use. The problem with the second > option is that it is a bit annoying to have to memorize which tags are and > which aren't bridi operators. On the other hand, the problem with the first > option is that it would actually invalidate a lot of usage! For example, > from The Little Prince: > > (4) do pu djuno noda fi'o fuzme mi > > The intended meaning is (more or less) "It's my fault that you didn't > know." However, if {fi'o fuzme} is treated like any other tag, then the > scope is wrong and the sentence suddenly means "In the past, there was no > thing such that: you know it because of me", which is backwards from the > intended meaning. > Yes, it should have been "fi'o fuzme mi do pu djuno no da". It's a very common mistake with causals. For some reason we always tend to give them wide scope, even when used at the end of the sentence. Very common with "na ... ki'u ..." for instance. > This is sad news. Should we say {tai} (or even {ja'e}) is not a bridi > operator and thus save the construction (and usage) or do we need to update > our usage? Both solutions have their pros and cons, but in the long run, > consistency seems more important. > > I'd be particularly interested in xorxes' opinion. > I guess it should be "ja'e ... tai ..." rather than "tai ... ja'e ...". 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out. --047d7b3a90b282758204dd450c61 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Tue, May 21, 2013 at 9:39 PM, selpa'i <= seladwa@gmx.de><= /span> wrote:
We know that na(ku), quantifiers, connective= s and tenses are bridi operators, but what about non-tense tags? Some clear= ly are bridi operators, for instance the causals:

In general, tags for which the rest = of the bridi is an argument of the tag's underlying selbri would be bri= di operators. Those are also the easiest tags to come up with a clean defin= ition for. Maybe all tags have to be defined that way.

=A0
Either we make every tag, no matter what selma'o it belongs to, a bridi= operator, or we pick some that are operators and some that aren't depe= nding on what is the most useful / easiest to use. The problem with the sec= ond option is that it is a bit annoying to have to memorize which tags are = and which aren't bridi operators. On the other hand, the problem with t= he first option is that it would actually invalidate a lot of usage! For ex= ample, from The Little Prince:

=A0 =A0 =A0(4) do pu djuno noda fi'o fuzme mi

The intended meaning is (more or less) "It's my fault that you did= n't know." However, if {fi'o fuzme} is treated like any other = tag, then the scope is wrong and the sentence suddenly means "In the p= ast, there was no thing such that: you know it because of me", which i= s backwards from the intended meaning.

Yes, it should have been "fi= 9;o fuzme mi do pu djuno no da". It's a very common mistake with c= ausals. For some reason we always tend to give them wide scope, even when u= sed at the end of the sentence. Very common with "na ... =A0ki'u .= .." for instance.
=A0
This is sad news. Should we say {tai} (or even {ja'e}) is not a bridi o= perator and thus save the construction (and usage) or do we need to update = our usage? Both solutions have their pros and cons, but in the long run, co= nsistency seems more important.

I'd be particularly interested in xorxes' opinion.
=

I guess it should be "ja'e ... tai ...&q= uot; rather than "tai ... ja'e ...".

mu'o mi'e xorxes=A0

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban?hl=3Den.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
--047d7b3a90b282758204dd450c61--