From pycyn@aol.com Mon May 28 17:56:29 2001
Return-Path: <Pycyn@aol.com>
X-Sender: Pycyn@aol.com
X-Apparently-To: lojban@yahoogroups.com
Received: (EGP: mail-7_1_3); 29 May 2001 00:56:29 -0000
Received: (qmail 11263 invoked from network); 29 May 2001 00:56:28 -0000
Received: from unknown (10.1.10.27) by l10.egroups.com with QMQP; 29 May 2001 00:56:28 -0000
Received: from unknown (HELO imo-m07.mx.aol.com) (64.12.136.162) by mta2 with SMTP; 29 May 2001 00:56:28 -0000
Received: from Pycyn@aol.com by imo-m07.mx.aol.com (mail_out_v30.22.) id r.37.15bf7043 (25100) for <lojban@yahoogroups.com>; Mon, 28 May 2001 20:56:17 -0400 (EDT)
Message-ID: <37.15bf7043.28444db1@aol.com>
Date: Mon, 28 May 2001 20:56:17 EDT
Subject: Re: Grammar Clarifications
To: lojban@yahoogroups.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_37.15bf7043.28444db1_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10519
From: pycyn@aol.com

--part1_37.15bf7043.28444db1_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

lojbab-xorxes-lojbab:
<> >A question iswhether one really needs a predicate that
> >totally within itself with no other sumti means &quot;is a Ford&quot;.
>
>Right. And would the same conversion apply to &quot;is a Picasso&quot;?
>And then, would it extend to &quot;is a Beethoven&quot; about a symphony?
>Or &quot;is a Shakespeare&quot; about a play? Or &quot;is aEurhythmics&quot; 
about
>a song?

Sounds English-colloquial to me. srana seems adequate. Though probably 
co'e is even better.>

I kinda like {co'e}, though its total non-commitment to any particular 
relation gets back to what {me} became at a certain point. Of course, with 
{le} we are home free anyhow, but with {lo} we get into complications about 
things made by Ford, things that belong to the (various) Fords, things that 
fell on the (various) Fords, and so on for every. But it does give a device 
for picking the colloquial (but not only English, surely) use of proper names 
in common-noun senses. Of course, that idiom might ruin {co'e} for its main 
invisible use as the predicate suppressed by {tu'a}.



--part1_37.15bf7043.28444db1_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><BODY BGCOLOR="#ffffff"><FONT SIZE=2>lojbab-xorxes-lojbab:
<BR>&lt;&gt; &gt;A question iswhether one really needs a predicate that
<BR>&gt; &gt;totally within itself with no other sumti means &amp;quot;is a Ford&amp;quot;.
<BR>&gt;
<BR>&gt;Right. And would the same conversion apply to &amp;quot;is a Picasso&amp;quot;?
<BR>&gt;And then, would it extend to &amp;quot;is a Beethoven&amp;quot; about a symphony?
<BR>&gt;Or &amp;quot;is a Shakespeare&amp;quot; about a play? Or &amp;quot;is aEurhythmics&amp;quot; 
<BR>about
<BR>&gt;a song?
<BR>
<BR>Sounds English-colloquial to me. &nbsp;srana seems adequate. &nbsp;Though probably 
<BR>co'e is even better.&gt;
<BR>
<BR>I kinda like {co'e}, though its total non-commitment to any particular 
<BR>relation gets back to what {me} became at a certain point. &nbsp;Of course, with 
<BR>{le} we are home free anyhow, but with {lo} we get into complications about 
<BR>things made by Ford, things that belong to the (various) Fords, things that 
<BR>fell on the (various) Fords, and so on for every. &nbsp;But it does give a device 
<BR>for picking the colloquial (but not only English, surely) use of proper names 
<BR>in common-noun senses. &nbsp;Of course, that idiom might ruin {co'e} for its main 
<BR>invisible use as the predicate suppressed by {tu'a}.
<BR>
<BR></FONT></HTML>

--part1_37.15bf7043.28444db1_boundary--

