Received: from mail-gg0-f192.google.com ([209.85.161.192]:33852) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1Ts47M-00053L-2j; Sun, 06 Jan 2013 20:15:32 -0800 Received: by mail-gg0-f192.google.com with SMTP id c2sf11395797ggn.19 for ; Sun, 06 Jan 2013 20:15:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received:x-received:received-spf :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=mcbcxXrupLXSDEW8uSxPxqNvCqC9pr/yZvD5IIfkim8=; b=HvhIhE3vsN6irR7qBBjb95JHV0Brwa0WjjS1AaP6NVjdNCyBaf8vgAVGZlsDdAEPJM 52fYURELZ+LONhleTtpDo6J5hX3vuZ1zs8XWwP5u3YPyCvBP4AsqqIHIo2e4CDmb+LSh NbURstATJMbDA+l9Ahux5JejedGRDN/1WzT4tVDInMWxlhN/K6jOPyvTEUZe2GQ+478K hY/wXeEBeaiGky28b/yYN4w1n5wOwBE18n/7GWJB8WY6/TGcFZntEf/r1VGdG7Ubiqmt UbSolTfjiaAN3OGqjgAm+dRhHnEVCDD4A1FFEQHD1/QxxikYLIrhTnhxe679MrxEklU1 i9Ug== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:x-beenthere:x-received:x-received:received-spf :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=mcbcxXrupLXSDEW8uSxPxqNvCqC9pr/yZvD5IIfkim8=; b=jnZKu16HloNzootc9CeLF7wQDASNkYkF5sV3K1qZj6FOEG4isvuODqUXrcnZjTiu0W B9DEiMTmS9CfZMkQgaJCSCShBbb0mMt3e+6AztNBTw9x0Q3lLscbqtIhxL9hjjsremfU OlotWO/liP39Vu7wSQGYDS9RsxXjX0EOjG7uzLlNWMEzvn4A3jSgajhxx+gKRH8Hy1xW rmDjA7Z5MCk0g9RaFjjnVM5sA0rugJgNpohJkjBKoUYM9seU3A5CxNX4rO1QQmXkYhJW kauN1Y7da1hja0eVTODFgNC789auScqIfKfzlYnL7t9+8O00oI/Nwfr/hjcSKfs5AaFt DiIA== X-Received: by 10.49.12.238 with SMTP id b14mr10088469qec.18.1357532113212; Sun, 06 Jan 2013 20:15:13 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.49.35.73 with SMTP id f9ls8842825qej.27.gmail; Sun, 06 Jan 2013 20:15:11 -0800 (PST) X-Received: by 10.58.170.6 with SMTP id ai6mr27999741vec.35.1357532111867; Sun, 06 Jan 2013 20:15:11 -0800 (PST) X-Received: by 10.58.170.6 with SMTP id ai6mr27999740vec.35.1357532111843; Sun, 06 Jan 2013 20:15:11 -0800 (PST) Received: from mail-vc0-f173.google.com (mail-vc0-f173.google.com [209.85.220.173]) by gmr-mx.google.com with ESMTPS id h20si16743297vdg.3.2013.01.06.20.15.11 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 06 Jan 2013 20:15:11 -0800 (PST) Received-SPF: pass (google.com: domain of blindbravado@gmail.com designates 209.85.220.173 as permitted sender) client-ip=209.85.220.173; Received: by mail-vc0-f173.google.com with SMTP id f13so18845476vcb.18 for ; Sun, 06 Jan 2013 20:15:11 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.107.5 with SMTP id z5mr82121560vco.22.1357532111717; Sun, 06 Jan 2013 20:15:11 -0800 (PST) Received: by 10.220.13.197 with HTTP; Sun, 6 Jan 2013 20:15:11 -0800 (PST) In-Reply-To: References: Date: Sun, 6 Jan 2013 23:15:11 -0500 Message-ID: Subject: Re: [lojban] Quantifier exactness From: Ian Johnson To: lojban@googlegroups.com X-Original-Sender: blindbravado@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of blindbravado@gmail.com designates 209.85.220.173 as permitted sender) smtp.mail=blindbravado@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=f46d043c7bd44a435004d2ab1320 X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / --f46d043c7bd44a435004d2ab1320 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable ...Actually, both of the above situations are the same. {ci prenu cu zvati lo zdani} when 5 are present is an "inexact quantifier", but it can be sneakily worked around by playing with the universe of discourse (i.e. we're excluding them from the discussion). There's no such workaround in the first example, because the quantifier range is explicit. mi'e la latro'a mu'o On Sun, Jan 6, 2013 at 10:51 PM, Ian Johnson wrote= : > Not {su'o}, no. Instead it's more like "at least one, and probably about > one." As for the example, trivial examples don't really help (since the > issue could basically be left up in the air and trivial cases would still > be resolvable in context), while universe-of-discourse-based examples see= m > pedantic at best. > > mi'e la latro'a mu'o > > On Sun, Jan 6, 2013 at 7:49 PM, Felipe Gon=E7alves Assis < > felipeg.assis@gmail.com> wrote: > >> I don't understand what you mean by "inexact quantifers". Do you mean >> that {pa} >> should be understood as {su'o}? I don't see why that is necessary, or wh= y >> you >> would need such a convoluted example to exemplify the different >> interpretations. >> >> mu'o >> mi'e .asiz. >> >> On 6 January 2013 15:59, Ian Johnson wrote: >> > The issue of quantifier exactness has come up a few times already. The >> most >> > recent example was "context and precision" which was forked by aionys >> from >> > another thread. You can look at that thread On IRC today, playing arou= nd >> > with functions we stumbled upon a combination of a sentence and >> situation >> > such that one stance on quantifier exactness makes the sentence false >> while >> > the other makes it true. Here's the setup: >> > >> > There are 4 people, mi, do, la alis, la bab; the latter two are groupe= d >> > under {lo re prenu}. >> > I like la alis a little bit, but hate la bab. >> > You like la alis and la bab a lot. >> > Now consider >> > {mi zmadu do lo ni ce'u nelci pa lo re prenu} >> > (If the ni confuses you, pretend it's ka, as that part's not important >> here. >> > We can talk about ka-ni elsewhere.) >> > >> > If quantifiers are exact, this is true. {do nelci pa lo re prenu} is >> > completely false (you like two of them, not one), while {mi nelci pa l= o >> re >> > prenu} is true, if only a little bit, so I do exceed you in that aspec= t. >> > Note that the CLL says this is how the language works, but if you look >> at >> > the previous discussions you'll find that this is clumsy fairly >> frequently. >> > If quantifiers are not exact, this is false or at least false-ish, >> since {ro >> > da poi me lo re prenu zo'u do zmadu mi lo ni ce'u nelci da}. >> > >> > I thought this example warranted discussion primarily because it does >> not >> > arise because of annoying, semi-ontological issues related to the >> universe >> > of discourse. Instead there's only two people being quantified over, >> but the >> > two interpretations still differ with respect to this (relatively >> simple) >> > sentence. >> > >> > .i do ma jinvi >> > >> > .i mi'e la latro'a mu'o >> > >> > -- >> > 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@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/lojban?hl=3Den. >> >> -- >> You received this message because you are subscribed to the Google Group= s >> "lojban" group. >> To post to this group, send email to lojban@googlegroups.com. >> To unsubscribe from this group, send email to >> lojban+unsubscribe@googlegroups.com. >> For more options, visit this group at >> 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. --f46d043c7bd44a435004d2ab1320 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable ...Actually, both of the above situations are the same. {ci prenu cu zvati = lo zdani} when 5 are present is an "inexact quantifier", but it c= an be sneakily worked around by playing with the universe of discourse (i.e= . we're excluding them from the discussion). There's no such workar= ound in the first example, because the quantifier range is explicit.

mi'e la latro'a mu'o

On S= un, Jan 6, 2013 at 10:51 PM, Ian Johnson <blindbravado@gmail.com&= gt; wrote:
Not {su'o}, no. Instead it's more li= ke "at least one, and probably about one." As for the example, tr= ivial examples don't really help (since the issue could basically be le= ft up in the air and trivial cases would still be resolvable in context), w= hile universe-of-discourse-based examples seem pedantic at best.

mi'e la latro'a mu'o

On Sun, Jan 6, 2013 at 7:49 PM, F= elipe Gon=E7alves Assis <felipeg.assis@gmail.com> wrot= e:
I don't understand what you mean by &quo= t;inexact quantifers". Do you mean that {pa}
should be understood as {su'o}? I don't see why that is necessary, = or why you
would need such a convoluted example to exemplify the different interpretat= ions.

mu'o
mi'e .asiz.

On 6 January 2013 15:59, Ian Johnson <blindbravado@gmail.com> wrote:
> The issue of quantifier exactness has come up a few times already. The= most
> recent example was "context and precision" which was forked = by aionys from
> another thread. You can look at that thread On IRC today, playing arou= nd
> with functions we stumbled upon a combination of a sentence and situat= ion
> such that one stance on quantifier exactness makes the sentence false = while
> the other makes it true. Here's the setup:
>
> There are 4 people, mi, do, la alis, la bab; the latter two are groupe= d
> under {lo re prenu}.
> I like la alis a little bit, but hate la bab.
> You like la alis and la bab a lot.
> Now consider
> {mi zmadu do lo ni ce'u nelci pa lo re prenu}
> (If the ni confuses you, pretend it's ka, as that part's not i= mportant here.
> We can talk about ka-ni elsewhere.)
>
> If quantifiers are exact, this is true. {do nelci pa lo re prenu} is > completely false (you like two of them, not one), while {mi nelci pa l= o re
> prenu} is true, if only a little bit, so I do exceed you in that aspec= t.
> Note that the CLL says this is how the language works, but if you look= at
> the previous discussions you'll find that this is clumsy fairly fr= equently.
> If quantifiers are not exact, this is false or at least false-ish, sin= ce {ro
> da poi me lo re prenu zo'u do zmadu mi lo ni ce'u nelci da}. >
> I thought this example warranted discussion primarily because it does = not
> arise because of annoying, semi-ontological issues related to the univ= erse
> of discourse. Instead there's only two people being quantified ove= r, but the
> two interpretations still differ with respect to this (relatively simp= le)
> sentence.
>
> .i do ma jinvi
>
> .i mi'e la latro'a mu'o
>
> --
> You received this message because you are subscribed to the Google Gro= ups
> "lojban" group.
> To post to this group, send email to lojban@googlegroups.com.
> To unsubscribe from this group, send email to
> lojban+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/lojban?hl=3Den.

--
You received this message because you are subscribed to the Google Groups &= quot;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.
--f46d043c7bd44a435004d2ab1320--