Received: from mail-oa0-f58.google.com ([209.85.219.58]:41750) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1Uqp2H-0005Xw-4m for lojban-list-archive@lojban.org; Sun, 23 Jun 2013 11:29:30 -0700 Received: by mail-oa0-f58.google.com with SMTP id j1sf3420609oag.3 for ; Sun, 23 Jun 2013 11:29:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-beenthere:date:from:to:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type; bh=dO2aW2OPkhouhkuSyReMd9diqVQ0kP/UQPQCiUOSUPM=; b=USnKZXQG6fnYQB7TyYD21jhKAhSUL6CojCVBKkMNp918+HiytZTeE6xS5f0kejSmsr cXgZOAfY/60+PQeYY5I6biIY/ll6c1Bx/4H88JeQVhcNyhD7A+vlRbNnkvpZg0vkXPfS iV2jInHAfsUoaM/fCKEw1dy2kmKZlj4Qe/6sNv08HiJl88PnuzaL6gfKQxP2sxIjyK5+ pCe9+hVMDnl6LWNjqbZa3t5cvIfW3x03ZuJ3FYWbctaJ6D0Nh0Wn8H+I764pNzW1v9xN G0a3rmUGV1lyN/9bNGPf1iU60fLgKDOxyqrAoPILKe/6dohXaonqDB2UH+KQHn1/DHY1 1NXQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-beenthere:date:from:to:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type; bh=dO2aW2OPkhouhkuSyReMd9diqVQ0kP/UQPQCiUOSUPM=; b=sHeVZS0JX/6Ukz9Rsb98m0V60hhyTdat04sYjBHrMLisazOmiF+0cU68B90kU3j/sB /aHM3oRz9114IfBflPupEGWKnOOL3017JthjFTC7WRmNhimSpQncWgVmBHLxOuc9Kfcw scGCv65zYF0JBnz+xs924hiqVt9Z+tACrCp3RYDlvlJ3PA15ogPRY8vqyqAGXlnM53BO DA3BBtUq5A6L1DSTCm8hA22rm51rYE3f/gb2ooYEQEevTr42q3Jam+G3NKGa8uxSelaH A9L4e2sR0pLNalneyarBWbHzE+cfM7jxSFYCQYuPQzMBiFEQsp+637g5XFBlWj0p3V+5 HV6Q== X-Received: by 10.49.82.50 with SMTP id f18mr186663qey.22.1372012145686; Sun, 23 Jun 2013 11:29:05 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.49.3.226 with SMTP id f2ls1783576qef.2.gmail; Sun, 23 Jun 2013 11:29:04 -0700 (PDT) X-Received: by 10.49.3.37 with SMTP id 5mr490100qez.30.1372012144283; Sun, 23 Jun 2013 11:29:04 -0700 (PDT) Date: Sun, 23 Jun 2013 11:29:03 -0700 (PDT) From: la arxokuna To: lojban@googlegroups.com Message-Id: <274032a8-a7d3-4ef6-9ef3-ede559362a19@googlegroups.com> In-Reply-To: References: <3729f7bd-3aa6-499c-9a20-4b3d040d3ad8@googlegroups.com> <6035ac71-4afd-48f6-9223-49cc81b983d9@googlegroups.com> Subject: Re: [lojban] A bug in the CLL 7.6 example 6.14). MIME-Version: 1.0 X-Original-Sender: gleki.is.my.name@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: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary="----=_Part_2409_28667139.1372012143694" X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / ------=_Part_2409_28667139.1372012143694 Content-Type: text/plain; charset=ISO-8859-1 On Sunday, June 23, 2013 9:50:14 PM UTC+4, tsani wrote: > > On 23 June 2013 09:43, la arxokuna >wrote: > >> On Friday, June 21, 2013 12:04:27 AM UTC+4, tsani wrote: >> >>> Metalinguistic "height" according to CLL: >>> SEI..SEhU, TO..TOI > ordinary bridi > lu-quotes >>> >> >> Oh, nice diagram. >> I have a question. What about {fi'o} (which is (or at least supposed to >> be) bridi relative clause) ? >> >> {mi xusra lo du'u do melbi i go'i}. Here go'i states that {mi xusra lo >> du'u li'o} >> >> I guess in >> {fi'o xusra mi do melbi i go'i} go'i incoroprates {fi'o xusra mi} as well. >> > > Yes. The fi'o-clause adds a term to the bridi, which requires that the > added term be on the same level as the bridi. Thus, it is included in the > go'i brika'i. All other terms are copied over with go'i (except for the > special rules involving {na}), so I don't see why fi'o wouldn't act the > same way. > > >> If we are to create a bridi relative clause (like e.g. {so'o'oi} in >> selmaho SEI) it should also incorporates such "comments" as {so'o'oi mi >> xusra se'u}. >> >> > Do you mean that the bridi relative clause should also be copied over, if > we were to allocate a SEI for bridi relative clauses? I don't really > understand what you're saying here. > I'm not proposing anything. I'm just asking. Should bridi relative clause be copied or not? > > >> Next. I guess in >> {sei mi xusra do melbi i go'i} go'i states that "you're beautiful", but >> not that "I assert that you are beautiful". >> >> Am I right? >> > > Right. I don't think that "metalinguistic comments" should be copied over. > {sei} as described in the CLL is used to refer to the text of the utterance > rather than the meaning per se. Due to it's magic-word-ish nature, I don't > think that it should be copied. > > I have been using {sei} for reference to the meaning of its containing > bridi, using it to make ad hoc attitudinals, in a sense. > > e.g. {.i mi ba'o cliva lo zdani ca lo nicte carmi sei mi troci co mipri be > fi lo mi mamta .i do zu'unai ba'o se frili ku'i lo ka [ce'u] go'i [ra'o]} > "I have left my house, deep in the night, which I tried to hide from my > mother. You, on the other hand, had no trouble, in contrast, doing so > (leaving the house, that is)." > > I think that this more complicated example demonstrates why we wouldn't > want the sei-clause to be copied in go'i: it would make this rather messy. > > Oh, and what about {to ... toi} ? They are also not copied, right? Or they are copied but {to'i ... toi} is not copied? .i mi'e la tsani mu'o > -- 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/groups/opt_out. ------=_Part_2409_28667139.1372012143694 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Sunday, June 23, 2013 9:50:14 PM UTC+4, tsani wrote:
On 23 June 2013 09:43, la= arxokuna <gleki.is...@gmail.com> = wrote:
On Friday, June 21, 2013 12:04:27 AM UTC+4, = tsani wrote:
Metalinguistic "heigh= t" according to CLL:
SEI..SEhU, TO..TOI > ordinary bridi > lu-quot= es

Oh, nice diagram.
I have a question. What about {fi'o}  (whi= ch is (or at least supposed to be) bridi relative clause) ?

<= /div>
{mi xusra lo du'u do melbi i go'i}.  Here go'i states that {= mi xusra lo du'u li'o}

I guess in
{fi'o xusra mi do melbi i go'i} go= 'i incoroprates {fi'o xusra mi} as well.

<= div>Yes. The fi'o-clause adds a term to the bridi, which requires that the = added term be on the same level as the bridi. Thus, it is included in the g= o'i brika'i. All other terms are copied over with go'i (except for the spec= ial rules involving {na}), so I don't see why fi'o wouldn't act the same wa= y.
 
If we are to create a = bridi relative clause (like e.g. {so'o'oi} in selmaho SEI) it should also i= ncorporates such "comments" as {so'o'oi mi xusra se'u}.


Do you mean that the bridi = relative clause should also be copied over, if we were to allocate a SEI fo= r bridi relative clauses? I don't really understand what you're saying here= .

I'm not proposing= anything. I'm just asking. Should bridi relative clause be copied or not?<= /div>
 
 
Next. I gue= ss in 
{sei mi xusra  do melbi i go'i} go'i states that= "you're beautiful", but not that "I assert that you are beautiful".

Am I right?

Right. I don't think that "metalinguistic comments" should be copied over.= {sei} as described in the CLL is used to refer to the text of the utteranc= e rather than the meaning per se. Due to it's magic-word-ish nature, I don'= t think that it should be copied. 

I have been using {sei} for reference to the meaning of= its containing bridi, using it to make ad hoc attitudinals, in a sense.&nb= sp;

e.g. {.i mi ba'o cliva lo zdani ca lo nicte ca= rmi sei mi troci co mipri be fi lo mi mamta .i do zu'unai ba'o se frili ku'= i lo ka [ce'u] go'i [ra'o]}
"I have left my house, deep in the night, which I tried to hide from m= y mother. You, on the other hand, had no trouble, in contrast, doing so (le= aving the house, that is)."

I think that this more= complicated example demonstrates why we wouldn't want the sei-clause to be= copied in go'i: it would make this rather messy.
 


Oh, and what about {to ... toi} ? They are also not copied, right? = Or they are copied but {to'i ... toi} is not copied?


=
.i mi'e la tsani mu'o

--
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+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.
 
 
------=_Part_2409_28667139.1372012143694--