From lojban-out@lojban.org Sun Jan 07 12:21:47 2007 Return-Path: X-Sender: lojban-out@lojban.org X-Apparently-To: lojban@yahoogroups.com Received: (qmail 75818 invoked from network); 7 Jan 2007 20:11:52 -0000 Received: from unknown (66.218.66.216) by m33.grp.scd.yahoo.com with QMQP; 7 Jan 2007 20:11:52 -0000 Received: from unknown (HELO mail7.sea5.speakeasy.net) (69.17.117.9) by mta1.grp.scd.yahoo.com with SMTP; 7 Jan 2007 20:11:51 -0000 Received: (qmail 11766 invoked from network); 7 Jan 2007 20:11:05 -0000 Received: from chain.digitalkingdom.org ([64.81.66.169]) (envelope-sender ) by mail7.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 7 Jan 2007 20:11:04 -0000 Received: from lojban-out by chain.digitalkingdom.org with local (Exim 4.63) (envelope-from ) id 1H3eM9-0002dz-4B for lojban@yahoogroups.com; Sun, 07 Jan 2007 12:11:02 -0800 Received: from chain.digitalkingdom.org ([64.81.66.169]) by chain.digitalkingdom.org with esmtp (Exim 4.63) (envelope-from ) id 1H3eLc-0002b6-6L; Sun, 07 Jan 2007 12:10:42 -0800 Received: with ECARTIS (v1.0.0; list lojban-list); Sun, 07 Jan 2007 12:09:17 -0800 (PST) Received: from nobody by chain.digitalkingdom.org with local (Exim 4.63) (envelope-from ) id 1H3eK7-0002aQ-Bj for lojban-list-real@lojban.org; Sun, 07 Jan 2007 12:08:55 -0800 Received: from wx-out-0506.google.com ([66.249.82.238]) by chain.digitalkingdom.org with esmtp (Exim 4.63) (envelope-from ) id 1H3eK1-0002aG-Cl for lojban-list@lojban.org; Sun, 07 Jan 2007 12:08:55 -0800 Received: by wx-out-0506.google.com with SMTP id i30so10772556wxd for ; Sun, 07 Jan 2007 12:08:48 -0800 (PST) Received: by 10.90.118.8 with SMTP id q8mr1654907agc.1168200528228; Sun, 07 Jan 2007 12:08:48 -0800 (PST) Received: by 10.90.31.6 with HTTP; Sun, 7 Jan 2007 12:08:48 -0800 (PST) Message-ID: <3ccac5f10701071208j3249b18ao83185aad8a3fdd5e@mail.gmail.com> Date: Sun, 7 Jan 2007 23:08:48 +0300 In-Reply-To: <925d17560701070904g78dba657j8a8510465d3c1cc7@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <925d17560701060757o1c0b3914w2f28416a2858cb29@mail.gmail.com> <611088.72555.qm@web81308.mail.mud.yahoo.com> <925d17560701070458t7243c3a0n2368d08b771cd615@mail.gmail.com> <3ccac5f10701070552o6995a1fetce44cc0fd724ee82@mail.gmail.com> <925d17560701070904g78dba657j8a8510465d3c1cc7@mail.gmail.com> X-Google-Sender-Auth: ce861bae011b9fd9 X-Spam-Score: -2.6 X-Spam-Score-Int: -25 X-Spam-Bar: -- X-archive-position: 13524 X-ecartis-version: Ecartis v1.0.0 Errors-to: lojban-list-bounce@lojban.org X-original-sender: slobin@ice.ru X-list: lojban-list X-Spam-Score: -2.6 X-Spam-Score-Int: -25 X-Spam-Bar: -- X-Spam-Report: Spam detection software, running on the system "chain.digitalkingdom.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: coi xorxes > > Because it is (or should be) a very common pattern, I suggest > > a series of lujvo in form {nupybilga} whith following place stucture: > > x1 = nupre1 = bilga1 "who is promised and therefore obliged", x2 = > > nupre2 = bilga2 "what is promiced and therefore obliged"; bilga3 = > > {le nu nupre} and omitteded from lujvo place structure, x3 = nupre3 > > "beneficiary/victim of a promise". > > How would that differ from plain {nupre}? [...] Content analysis details: (-2.6 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] -0.0 AWL AWL: From: address is in the auto white-list To: lojban@yahoogroups.com X-Originating-IP: 69.17.117.9 X-eGroups-Msg-Info: 1:0:0:0 X-eGroups-From: "Cyril Slobin" From: "Cyril Slobin" Reply-To: slobin@ice.ru Subject: [lojban] Re: Duty, promice etc... X-Yahoo-Group-Post: member; u=116389790; y=uBsJuGJrW6TFJ66L6CYbWgeS4p2OiRKaSxnNO0UHijujie0b7Q X-Yahoo-Profile: lojban_out X-Yahoo-Message-Num: 27963 coi xorxes > > Because it is (or should be) a very common pattern, I suggest > > a series of lujvo in form {nupybilga} whith following place stucture: > > x1 = nupre1 = bilga1 "who is promised and therefore obliged", x2 = > > nupre2 = bilga2 "what is promiced and therefore obliged"; bilga3 = > > {le nu nupre} and omitteded from lujvo place structure, x3 = nupre3 > > "beneficiary/victim of a promise". > > How would that differ from plain {nupre}? I opine {nupre} is "to make/give a promise". I opine this is different concept from "being bound by a promice". Second is implied/motivated/justified by first, but is not the same. ... Laziness has an important impact on efficiency ... -- Cyril Slobin To unsubscribe from this list, send mail to lojban-list-request@lojban.org with the subject unsubscribe, or go to http://www.lojban.org/lsg2/, or if you're really stuck, send mail to secretary@lojban.org for help.