From nobody@digitalkingdom.org Wed Jun 11 05:58:40 2008 Received: with ECARTIS (v1.0.0; list lojban-list); Wed, 11 Jun 2008 05:58:40 -0700 (PDT) Received: from nobody by chain.digitalkingdom.org with local (Exim 4.69) (envelope-from ) id 1K6PuS-0003v4-Kk for lojban-list-real@lojban.org; Wed, 11 Jun 2008 05:58:40 -0700 Received: from fg-out-1718.google.com ([72.14.220.156]) by chain.digitalkingdom.org with esmtp (Exim 4.69) (envelope-from ) id 1K6PuO-0003um-Ep for lojban-list@lojban.org; Wed, 11 Jun 2008 05:58:40 -0700 Received: by fg-out-1718.google.com with SMTP id e12so2196650fga.0 for ; Wed, 11 Jun 2008 05:58:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=S2AaETmql49MclNSMqYo+oCVekHIBlkjdLTfV2PT3Ds=; b=gpQ5YN2vqVPzlGyzrwKeWWuCTHzFpGQSxTEpk6KCm0w9FNW2L8Odn5VA78ti0QQEq1 M4WKCwAS/ruuBL/TYXoSuoQJFv36JqSj1cPoXiL5EZDJhzqO9JerGmQVRiLK8vyvrGDh qbmdmhSv5X987HO2meQXrBNH5YEsgUCmoM9TA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=n0rTVQuxsQfyGAPx9hITxuxdXZuw3K/ZfQcJgBBh4af8ptlkHYOPbCLbXuT9a+aob9 4GzDW53GPvsoXErx090FoAZ8jR/C9CHsHCBojjEtMA8lnsAuWzVCT10NSZrlJ6htLjKq gKaLM1+c2yFGhsmzOFEuffrVfqxZVZ1iIHgfQ= Received: by 10.86.78.4 with SMTP id a4mr168175fgb.29.1213189115037; Wed, 11 Jun 2008 05:58:35 -0700 (PDT) Received: by 10.86.89.11 with HTTP; Wed, 11 Jun 2008 05:58:35 -0700 (PDT) Message-ID: <925d17560806110558x30871410gb179f0851cceb932@mail.gmail.com> Date: Wed, 11 Jun 2008 09:58:35 -0300 From: "=?ISO-8859-1?Q?Jorge_Llamb=EDas?=" To: lojban-list@lojban.org Subject: [lojban] Re: lujvo list In-Reply-To: <737b61f30806101615g45aee5edv96583b2d649ae90@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <737b61f30806092349v776a1700jd332a7ae5a4c6947@mail.gmail.com> <925d17560806100517g52d0be3dkf5baa340a04386cc@mail.gmail.com> <737b61f30806101615g45aee5edv96583b2d649ae90@mail.gmail.com> X-Spam-Score: 0.0 X-Spam-Score-Int: 0 X-Spam-Bar: / X-archive-position: 14489 X-ecartis-version: Ecartis v1.0.0 Sender: lojban-list-bounce@lojban.org Errors-to: lojban-list-bounce@lojban.org X-original-sender: jjllambias@gmail.com Precedence: bulk Reply-to: lojban-list@lojban.org X-list: lojban-list On 6/10/08, Chris Capel wrote: > > Looking at a few of them, it seems plausible. The & is always the same > gismu as the preceeding. But then I saw this one: > > kangri#with+group:cluster:$girzu1 $girzu2 $girzu3 $girzu4 $=kansa1 > $&kansa2 $=kansa3 > > And if your idea were right, you would think that the last one would > be $&kansa3, which would be a silly way to make a lujvo anyway. The =kansa3 makes no sense there, but the & combines kansa1 and kansa2 in the same place. > My > idea is that it's the start of a new place in the luvjo, like > "&broda1" type tokens, and marks something about that place. Like > maybe the way it's combined with the next one? The problem with that > interpretation is that all of the & tokens wouldn't have to have the > same gismu as the preceeding. I don't think so, I think it always combines with the preceding one. > mitsi'u:mintu+simxu:the same to each other:$simxu1 $=mintu1 $&mintu2 $mintu3 > mitsmuvla:mintu+smuni+valsi:synonym:$valsi1 $=mintu1 $mintu2 $mintu3 $valsi3 > > This is an interesting pair of examples. Why would the & be used in > the first but not the second? Because in the first case mintu1 and mintu2 are combined into one place, but in the second case they remain as separate places. > ritna'aterjvi:brito+nanca+te+jivna:British annual/year-long > competition [e.g. FA Cup]:$jivna3 $jivna1 $&jivna2 $jivna4 > > A lot of them use 'jivna' and 'mintu'. The & is usually between the > first and second place. Which in the case of those two are the ones that could sensibly combine to form one place. > simfra:simxu+frati:interplay:$frati1 $&frati3 $frati2 $frati4 > > Here's one where it's not. Because frati1 can combine with frati3, but combining either with frati2 wouldn't make sense. (I think {frasi'u} is better than {simfra} for the wanted place structure though.) mu'o mi'e xorxes 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.