Received: from mail-lb0-f186.google.com ([209.85.217.186]:54583) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XnbVH-00016p-NE; Sun, 09 Nov 2014 15:02:43 -0800 Received: by mail-lb0-f186.google.com with SMTP id b6sf544907lbj.13 for ; Sun, 09 Nov 2014 15:02:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-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=nnXx93u5JZm/gut7XKHvaSL/Tz068matryj7njh/tUk=; b=HaoYBCIFkJuC1fFd+tcWvqwWgrI+xztjGHTNflOOMlX6aGaA1jz33XeTOzkKhlML3s zCnHywenm0PLnhmiFjbKTlmHCouuShABErrO1gsTy7RwKSEWyUm6awbkVlCWX3zyUOIL awrIZUSF5JK5I0wcEff8NNLjAHC+bCgPQ4LZAs7wy1jc3ojJH1ngTjDZ7ztYuN16AH6q zT0KXGhV1hYiPcFQF++tleGbf5SFcvw7zuiuUl4E69TqKcWMCsFxwVsJNtd6Fw+7Km8H S6uxGLrtoT+NJzZkWfQ0ooykb1o6aC47keLRNT4rEOZrivgyv/qePX3attn1kzWF1r81 Lpyw== X-Received: by 10.180.100.163 with SMTP id ez3mr69522wib.13.1415574151754; Sun, 09 Nov 2014 15:02:31 -0800 (PST) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.180.88.194 with SMTP id bi2ls1673277wib.53.canary; Sun, 09 Nov 2014 15:02:31 -0800 (PST) X-Received: by 10.181.27.135 with SMTP id jg7mr3285256wid.5.1415574151363; Sun, 09 Nov 2014 15:02:31 -0800 (PST) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com. [2a00:1450:400c:c05::236]) by gmr-mx.google.com with ESMTPS id p14si483545wie.1.2014.11.09.15.02.31 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 09 Nov 2014 15:02:31 -0800 (PST) Received-SPF: pass (google.com: domain of ilmen.pokebip@gmail.com designates 2a00:1450:400c:c05::236 as permitted sender) client-ip=2a00:1450:400c:c05::236; Received: by mail-wi0-f182.google.com with SMTP id d1so8837454wiv.3 for ; Sun, 09 Nov 2014 15:02:31 -0800 (PST) X-Received: by 10.180.77.79 with SMTP id q15mr25142356wiw.8.1415574151257; Sun, 09 Nov 2014 15:02:31 -0800 (PST) Received: from [192.168.0.102] ([128.140.131.147]) by mx.google.com with ESMTPSA id bl9sm11070525wib.24.2014.11.09.15.02.26 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 09 Nov 2014 15:02:30 -0800 (PST) Message-ID: <545FF27B.2040607@gmail.com> Date: Mon, 10 Nov 2014 00:02:19 +0100 From: Ilmen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: bpfk-list@googlegroups.com Subject: Re: [bpfk] {ro}, existential import and De Morgan References: <20141018011419.GF12268@mercury.ccil.org> <97AABFB42A204E5D97A4EDFEA57A8508@gmail.com> <20141019012930.GF12991@mercury.ccil.org> <676B49242B0D4F6A986D6AFEA1EB3B3C@gmail.com> <20141019170808.GJ12991@mercury.ccil.org> <20141109004632.GL6360@mercury.ccil.org> In-Reply-To: X-Original-Sender: ilmen.pokebip@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ilmen.pokebip@gmail.com designates 2a00:1450:400c:c05::236 as permitted sender) smtp.mail=ilmen.pokebip@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Reply-To: bpfk-list@googlegroups.com Precedence: list Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com List-ID: X-Google-Group-Id: 972099695765 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary="------------050804030807090001080201" X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - Content-Length: 5690 This is a multi-part message in MIME format. --------------050804030807090001080201 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable As for {ro} and existential import, I would like to highlight that if=20 {ro} never implies existential import by itself, there is still a very=20 simple way to add the existential import nuance: {ro su'o (pa)}. In CLL Chapter 18 Section 8 Example=20 18, it is shown how {ro} can be combined with another number, implying=20 that {ro} and this other number have the same value: 8.18) mi viska le rore gerku I saw the all-of/two dogs. I saw both dogs. In a similar way, {ro su'o (pa) da} would mean "everything, which is at=20 least one thing". Another similar option =E2=80=94although longer=E2=80=94 could be {vei ro .= e su'o (pa) da}. mi'e la .ilmen. mu'o On 09/11/2014 19:34, mukti wrote: > On Sunday, November 9, 2014 9:42:50 AM UTC-3, And Rosta wrote: > > 1. What does ro mean, and does it have EI? (A question settled a > dozen years ago.) > 2. Should there be a non-EI universal quantifier? > 3. Should there be an EI universal quantifier? This is the > question John seems to be addressing. > > 4. In any bpfk revision of the CLL specification, which meaning > should be paired with the phonological form /ro/? > > I believe that #1 and #4 are the question I'm trying to ask -- which=20 > hopefully have the same answer -- and I'm sorry if I invited the=20 > detour into other questions. > --=20 You received this message because you are subscribed to the Google Groups "= BPFK" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to bpfk-list+unsubscribe@googlegroups.com. To post to this group, send email to bpfk-list@googlegroups.com. Visit this group at http://groups.google.com/group/bpfk-list. For more options, visit https://groups.google.com/d/optout. --------------050804030807090001080201 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable As for {ro} and existential import, I would like to highlight that if {ro} never implies existential import by itself, there is still a very simple way to add the existential import nuance: {ro su'o (pa)}.
In CLL Chapter 18 Section 8 Example 18, it is shown how {ro} can be combined with another number, implying that {ro} and this other number have the same value:

8.18)  mi viska le rore gerku
       I saw the all-of/two dogs.
       I saw both dogs.

In a similar way, {ro su'o (pa) da} would mean "everything, which is at least one thing".

Another similar option =E2=80=94although longer=E2=80=94 could be {vei = ro .e su'o (pa) da}.

mi'e la .ilmen. mu'o


On 09/11/2014 19:34, mukti wrote:
On Sunday, November 9, 2014 9:42:50 AM UTC-3, And Rosta wrote:

1. What does ro mean, and does it have EI? (A question settled a dozen years ago.)
2. Should there be a non-EI universal quantifier?
3. Should there be an EI universal quantifier? This is the question John seems to be addressing.=C2=A0

4. In any bpfk revision of the CLL specification, which meaning should be paired with the phonological form /ro/?

I believe that #1 and #4 are the question I'm trying to ask -- which hopefully have the same answer -- and I'm sorry if I invited the detour into other questions.

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