Received: from mail-la0-f63.google.com ([209.85.215.63]:43720) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XGUNn-0000HR-8K for lojban-list-archive@lojban.org; Sun, 10 Aug 2014 07:46:03 -0700 Received: by mail-la0-f63.google.com with SMTP id hr17sf720399lab.28 for ; Sun, 10 Aug 2014 07:45:55 -0700 (PDT) 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=t37OM12Jc+MikRdx7OCUU//OEEA2LoGreGTb6vF1PEg=; b=EgRtmZ5k5hVXP/CHJBOx49ncWnTyXOWNF6aLsBOLi9zVd6BW1wxErrIqOczP1LRMim sPbqd5p/CgVRNpB9SrxUBLaiIwfs96YTPHQrxyXiEPsooSwP8xVgmchYEbuHNfOqFM54 442Lvn55oQwbZLIe/p3zkhCYpmAJWFUlvsS5KtrWcp8+BImb/KHpgLJapST1KDJ+B4VT V+hueWZamSgBE37sHL/fLSQpmmER9fxem3xewVNaGfe70gYk+YKA6SnCBrBiLt5T9rjO ThYgEVS0oAgzDD4Ij2sXhfOzgVJkO94kLnGXZ2wtA9FabQVyxHgZnIaK6nbYO4Jm3sVn QbWA== X-Received: by 10.180.108.111 with SMTP id hj15mr60183wib.5.1407681955002; Sun, 10 Aug 2014 07:45:55 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.180.99.197 with SMTP id es5ls372932wib.41.gmail; Sun, 10 Aug 2014 07:45:54 -0700 (PDT) X-Received: by 10.180.221.132 with SMTP id qe4mr1217627wic.1.1407681954503; Sun, 10 Aug 2014 07:45:54 -0700 (PDT) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [2a00:1450:400c:c05::234]) by gmr-mx.google.com with ESMTPS id fg8si855867wic.1.2014.08.10.07.45.54 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 10 Aug 2014 07:45:54 -0700 (PDT) Received-SPF: pass (google.com: domain of ilmen.pokebip@gmail.com designates 2a00:1450:400c:c05::234 as permitted sender) client-ip=2a00:1450:400c:c05::234; Received: by mail-wi0-x234.google.com with SMTP id n3so3055948wiv.7 for ; Sun, 10 Aug 2014 07:45:54 -0700 (PDT) X-Received: by 10.180.36.238 with SMTP id t14mr13558646wij.38.1407681954422; Sun, 10 Aug 2014 07:45:54 -0700 (PDT) Received: from [192.168.0.102] (95-210-209-219.ip.skylogicnet.com. [95.210.209.219]) by mx.google.com with ESMTPSA id di7sm32524715wjb.34.2014.08.10.07.45.50 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 10 Aug 2014 07:45:53 -0700 (PDT) Message-ID: <53E78584.6090208@gmail.com> Date: Sun, 10 Aug 2014 16:45:24 +0200 From: Ilmen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: lojban@googlegroups.com Subject: Re: [lojban] CLL Corrections References: <1a05ebdb-5a99-4382-b6a3-4205d1d16ae6@googlegroups.com> <857775fe-c38f-4e84-b3b9-17034a98a989@googlegroups.com> <036a8ae9-4a0b-455c-b014-0b1a97e37d62@googlegroups.com> <20140807124944.GI28465@samsa.fritz.box> <1fa41501-809e-4157-aee4-777215596290@googlegroups.com> <20140807134047.GK28465@samsa.fritz.box> <20140807165332.GL28465@samsa.fritz.box> 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::234 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: 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: text/plain; charset=UTF-8; format=flowed X-Spam-Note: SpamAssassin invocation failed On 09/08/2014, TR NS wrote: > Ah, ok. That at least makes sense. My "gut" sort of revolts at this > ambiguity though --I mean there is no way to designate a sumti in a > sentence while being ambiguous about exactly which slot it is filling, > is there? So it's seems odd to me that one could do that in a > subordinate clause. But in any case, at least that explanation makes > sense. It would be good if the LLC made that clear --adding your very > words, in fact, would have helped me understand that section much better. You can say {fa xi xo'e mi klama} for expressing a relation {klama} among whose sumti there's {mi}, although which sumti slot it fills is left unspecified. {mi jai nu klama} ("I am involved in an event of going") is also a possibility for achieving a similar effect. As for which place a hidden {ke'a} fills in a realtive clause, I always assume it fills the first empty tersu'i (sumti slot). Having it filling an unspecified place by default would force to use {ke'a} much of the times if you want to be precise, adding two more syllables to the relative clause. I don't recall having ever wanted to left which tersu'i a ke'a fills to context, and in the rare case where you would want to do so, you can resort to {do'e} or {fi xi xo'e}, so in my humble opinion always assuming it fills the first empty tersu'i makes things clearer and often saves you a couple of syllables. mu'o mi'e la .ilmen. -- 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.