Received: from mail-ie0-f191.google.com ([209.85.223.191]:43820) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XYCH7-0005A2-K7 for lojban-list-archive@lojban.org; Sun, 28 Sep 2014 04:04:29 -0700 Received: by mail-ie0-f191.google.com with SMTP id lx4sf393769iec.18 for ; Sun, 28 Sep 2014 04:04:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:date:message-id:subject:from: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=bgljtBqQV4bGgWx0/uVD5rRNBub0J6kUQhvhJHxiVSw=; b=l4AhANRa2NkiUq1JOcLjSrkcwIs9/A/5exA1FNUhzTvUyoRSc+nYgkwwk/ve7qNc7x 4ZmWn5tqWjxJ5psp564hdOijEErP52KDznfvpfF/PQAFO5TTCZ9ObbdiSER1IXHlFHDc CPCp6kgrccHxZqpsPXBAsOO2Dv/MgzwRE+yoW8PuKg71gSMj7PEnxGfkPD9XcvYYdKza Tb2gpUkoYRS0Up9l5+SYjTNZVjUEMpWy9A0PRB5ZpiZ4pDpCGbl70ah8w2hHVgXt2zzl 5HMFfPU145gvd0mhG5T6VNHtV4kdxUj34lvCUxl0bXtrKkYIrUbZ0rdZ/oi8K8EZkhdk 60ig== X-Received: by 10.182.2.106 with SMTP id 10mr1795obt.11.1411902255004; Sun, 28 Sep 2014 04:04:15 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.182.143.7 with SMTP id sa7ls980386obb.95.gmail; Sun, 28 Sep 2014 04:04:14 -0700 (PDT) X-Received: by 10.182.28.10 with SMTP id x10mr29512290obg.13.1411902254365; Sun, 28 Sep 2014 04:04:14 -0700 (PDT) Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [2607:f8b0:400e:c02::233]) by gmr-mx.google.com with ESMTPS id pz1si580985pbb.0.2014.09.28.04.04.14 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 28 Sep 2014 04:04:14 -0700 (PDT) Received-SPF: pass (google.com: domain of and.rosta@gmail.com designates 2607:f8b0:400e:c02::233 as permitted sender) client-ip=2607:f8b0:400e:c02::233; Received: by mail-pd0-f179.google.com with SMTP id r10so963006pdi.24 for ; Sun, 28 Sep 2014 04:04:14 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.70.35.15 with SMTP id d15mr63990223pdj.48.1411902254207; Sun, 28 Sep 2014 04:04:14 -0700 (PDT) Received: by 10.70.37.198 with HTTP; Sun, 28 Sep 2014 04:04:14 -0700 (PDT) Received: by 10.70.37.198 with HTTP; Sun, 28 Sep 2014 04:04:14 -0700 (PDT) Date: Sun, 28 Sep 2014 12:04:14 +0100 Message-ID: Subject: [lojban] {da poi} (was: Re: tersmu 0.2 From: And Rosta To: lojban@googlegroups.com X-Original-Sender: and.rosta@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of and.rosta@gmail.com designates 2607:f8b0:400e:c02::233 as permitted sender) smtp.mail=and.rosta@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=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: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=047d7bfea42251d94105041e1c3c X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --047d7bfea42251d94105041e1c3c Content-Type: text/plain; charset=UTF-8 On 28 Sep 2014 02:34, "Martin Bays" wrote: > the compositionality > of restrictive clauses (which admittedly is already broken in some other > cases, e.g. {da poi broda}). I agree {da poi} looks broken. What are the remedies? (1) To allow noncompositional idioms? (2) To define /poi/ as an allomorph of /noi/ in this syntactic environment? (3) To accept that, given the internal logic of the language, {da poi} as habitually used is simply wrong? (4) To seek and find a consistent definition for {poi} and {noi} such that {da poi} usage becomes correct? --And. -- 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. For more options, visit https://groups.google.com/d/optout. --047d7bfea42251d94105041e1c3c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 28 Sep 2014 02:34, "Martin Bays" <mbays@sdf.org> wrote:
> the compositionality
> of restrictive clauses (which admittedly is already broken in some oth= er
> cases, e.g. {da poi broda}).

I agree {da poi} looks broken. What are the remedies? (1) To= allow noncompositional idioms? (2) To define /poi/ as an allomorph of /noi= / in this syntactic environment? (3) To accept that, given the internal log= ic of the language, {da poi} as habitually used is simply wrong? (4) To see= k and find a consistent definition for {poi} and {noi} such that {da poi} u= sage becomes correct?

--And.

--
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+unsub= scribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http:= //groups.google.com/group/lojban.
For more options, visit http= s://groups.google.com/d/optout.
--047d7bfea42251d94105041e1c3c--