Received: from mail-bk0-f55.google.com ([209.85.214.55]:54248) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1VzqJL-0005Kh-Vr for lojban-list-archive@lojban.org; Sun, 05 Jan 2014 08:12:40 -0800 Received: by mail-bk0-f55.google.com with SMTP id v15sf1606706bkz.0 for ; Sun, 05 Jan 2014 08:12:16 -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 :content-transfer-encoding; bh=1LqS5760BdJwhLuEPcyGHixPrBwcUzavyghXEKM4Xao=; b=c7Na4ZmT7goWQRczDNXrc1pLKtxdO2q0bxFamwkD/2FhvQP+Nww4zVh9UEsVIhyCYK ogOjxTMIHQqk4mgr8664A//CO6hfbKQz5PO2Egbynin/kWWd6X7O1afUrcuhUNuKjbJ7 m2gHtB5gr7rKJkj8qmVxxYp8iSSbIZPrlrbRr1nGxN4KkZ/+4ksVNTixg2OUtffhmUYj HScFK526UP63XzjsuFaCvXI0NckkV4FM+IxTLl9/YZiIa7ThYUf0BzpiUjNvGVxB7tXK 08JwxpMu8oC1E1thsbk28fWS2nDWuiexA3L8d7oO+S4+cWqnf3FKcSeditTFYx1iKq1t 8Ofg== X-Received: by 10.152.29.72 with SMTP id i8mr10961lah.21.1388938336761; Sun, 05 Jan 2014 08:12:16 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.152.197.36 with SMTP id ir4ls93570lac.18.gmail; Sun, 05 Jan 2014 08:12:16 -0800 (PST) X-Received: by 10.152.143.107 with SMTP id sd11mr39420608lab.5.1388938336335; Sun, 05 Jan 2014 08:12:16 -0800 (PST) Received: from mout.gmx.net (mout.gmx.net. [212.227.15.18]) by gmr-mx.google.com with ESMTPS id b3si279620eez.0.2014.01.05.08.12.16 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 05 Jan 2014 08:12:16 -0800 (PST) Received-SPF: pass (google.com: domain of seladwa@gmx.de designates 212.227.15.18 as permitted sender) client-ip=212.227.15.18; Received: from [192.168.2.108] ([93.220.97.97]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0LlV71-1VRsjY46Mx-00bNiX for ; Sun, 05 Jan 2014 17:12:16 +0100 Message-ID: <52C98461.20200@gmx.de> Date: Sun, 05 Jan 2014 17:12:17 +0100 From: selpa'i User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: lojban@googlegroups.com Subject: Re: [lojban] [oz] Logical connectives References: In-Reply-To: X-Provags-ID: V03:K0:eT+HFIWDZ+O5jmSzfXBr7HaNXoFsMovgRAVD1TiBg4K1dWKk4xR NbGvFd1I1iSk00WndP0/KodeshmMVjZvB99YyJViBZFXmuTqEMvVvDG1tcXGieFV95/2Bzx f8gNlsiKy/EjDW+cTon4eqpoXIjjcf2jgXtzCpE0YI12AnfPv+RywGIqpJeKaensYjyxMq3 OYP0hxAoH5DbdPesZoT/g== X-Original-Sender: seladwa@gmx.de X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of seladwa@gmx.de designates 212.227.15.18 as permitted sender) smtp.mail=seladwa@gmx.de 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: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Spam_score: 0.0 X-Spam_score_int: 0 X-Spam_bar: / la'o me. Felipe Gon=E7alves Assis .me cusku di'e > I was puzzled by the use of logic connectives in several passages. E.g. > > (1) {z=E0sti fa no sai dr=F9sro je no lolnitk=F9'a} > (2) {no tr=ECcu je no zd=E0ni cu zv=E0ti} Ah right, these must have slipped through during my search and replace=20 marathon. They should use {.e} instead of {je}. If you find more such=20 examples, please let me know. > I see there is some consistency in their correlation with quantifiers, > but still I don't get it. What is the logic behind them? Logically, {je} is the same as {.e}, but {je} can't connect sumti under=20 official rules. At some point, the text used GIJA, or the connective=20 unification grammar, but I reverted to the standard grammar. That's why=20 you might still find some {je} that connect sumti; they are leftovers. > They are rejected by both camxes and jboski, but accepted by the parser > you indicated. Nevertheless, the parser also understands {ko'a je ko'e > broda} just like {ko'a .e ko'e broda}. Is it related to expansion order? The parser is overly lenient by treating all connectives as=20 interchangeable. Not only can you use {je} to connect sumti (as was the=20 idea of the (not so) Mad Proposals), but you can also use {.e} to=20 connect tanru units. None of this (should) happen in my Oz translation. mi'e la selpa'i mu'o --=20 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 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. For more options, visit https://groups.google.com/groups/opt_out.