From pycyn@aol.com Mon Oct 01 09:41:42 2001
Return-Path: <Pycyn@aol.com>
X-Sender: Pycyn@aol.com
X-Apparently-To: lojban@yahoogroups.com
Received: (EGP: mail-7_4_1); 1 Oct 2001 16:41:42 -0000
Received: (qmail 81990 invoked from network); 1 Oct 2001 16:41:41 -0000
Received: from unknown (10.1.10.26)
  by 10.1.1.222 with QMQP; 1 Oct 2001 16:41:41 -0000
Received: from unknown (HELO imo-r08.mx.aol.com) (152.163.225.104)
  by mta1 with SMTP; 1 Oct 2001 16:41:41 -0000
Received: from Pycyn@aol.com
  by imo-r08.mx.aol.com (mail_out_v31_r1.7.) id r.131.25e7f46 (4185)
  for <lojban@yahoogroups.com>; Mon, 1 Oct 2001 12:41:31 -0400 (EDT)
Message-ID: <131.25e7f46.28e9f6ba@aol.com>
Date: Mon, 1 Oct 2001 12:41:30 EDT
Subject: Re: new brivla (was: Re: [lojban] Set of answers encore
To: lojban@yahoogroups.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_131.25e7f46.28e9f6ba_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10535
From: pycyn@aol.com

--part1_131.25e7f46.28e9f6ba_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 10/1/2001 9:39:26 AM Central Daylight Time, 
arosta@uclan.ac.uk writes:


> Myself I don't feel the need to create new brivla to be so pressing, compared
> to sorting out more fundamental (and more interesting...) issues. But it 
> would
> certainly be a great help to have a vlaste that included lujvo, and not just
> lujvo used more than 100 times (-- a threshold mentioned by Lojbab). It
> should probably be a vetted list, to filter out dud lujvo, but otherwise as
> large as possible. This might speed up composition; for example, the text
> you sent me included a very good lujvo for 'saddle', which I would like
> to use should I ever have cause to write in Lojban about saddles, but I
> completely forget what the lujvo was, so would instead have to try to
> reinvent one that would probably be inferior. Far better if I could just
> search for 'saddle' in a very big vlaste, and find there your lujvo.
> 

We need both -- well, all three -- and we are each called to our special 
favorites. But we should not (some long Pauline line goes here) condemn or 
even contemn people with other inclinations, rather get on with our own piece 
of teh work. And a nice comprehensive brivla list would sure be nice.
(Oh, and I don't think even {du'u} creates an intensional environment, it's 
all done with selbri)

--part1_131.25e7f46.28e9f6ba_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><BODY BGCOLOR="#ffffff"><FONT SIZE=2>In a message dated 10/1/2001 9:39:26 AM Central Daylight Time, arosta@uclan.ac.uk writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Myself I don't feel the need to create new brivla to be so pressing, compared
<BR>to sorting out more fundamental (and more interesting...) issues. But it would
<BR>certainly be a great help to have a vlaste that included lujvo, and not just
<BR>lujvo used more than 100 times (-- a threshold mentioned by Lojbab). It
<BR>should probably be a vetted list, to filter out dud lujvo, but otherwise as
<BR>large as possible. This might speed up composition; for example, the text
<BR>you sent me included a very good lujvo for 'saddle', which I would like
<BR>to use should I ever have cause to write in Lojban about saddles, but I
<BR>completely forget what the lujvo was, so would instead have to try to
<BR>reinvent one that would probably be inferior. Far better if I could just
<BR>search for 'saddle' in a very big vlaste, and find there your lujvo.
<BR></BLOCKQUOTE>
<BR>
<BR>We need both -- well, all three -- and we are each called to our special favorites. &nbsp;But we should not (some long Pauline line goes here) condemn or even contemn people with other inclinations, rather get on with our own piece of teh work. &nbsp;And a nice comprehensive brivla list would sure be nice.
<BR>(Oh, and I don't think even {du'u} creates an intensional environment, it's all done with selbri)</FONT></HTML>

--part1_131.25e7f46.28e9f6ba_boundary--

