From araizen@newmail.net Sat Apr 08 13:42:46 2000
Return-Path: <araizen@newmail.net>
Received: (qmail 26771 invoked from network); 8 Apr 2000 20:42:46 -0000
Received: from unknown (10.1.10.26) by m3.onelist.org with QMQP; 8 Apr 2000 20:42:46 -0000
Received: from unknown (HELO out.newmail.net) (212.150.51.26) by mta1 with SMTP; 8 Apr 2000 20:42:45 -0000
Received: from default ([62.0.161.84]) by out.newmail.net ; Sat, 08 Apr 2000 22:44:04 +02:00
To: lojban@onelist.com
Date: Sat, 8 Apr 2000 22:46:17 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: [lojban] games (was: re: new lojban website) 
Reply-to: araizen@newmail.net
Priority: normal
In-reply-to: <20000403205947.18881.qmail@hotmail.com>
X-mailer: Pegasus Mail for Win32 (v3.11)
Message-ID: <95525904401@out.newmail.net>
X-eGroups-From: "Adam Raizen" <araizen@newmail.net>
From: "Adam Raizen" <araizen@newmail.net>

la maikl cusku di'e

> Which brings me to a caution: it is much better to have to coin
> your own, however awkward, lujvo, than to rely on unanalyzed readymades--if 
> too many people learn Lojban this way, it will end
> by causing the meanings of component rafsi to drift away from
> their original gismu...

Indeed, I've noticed that most lujvo are made with meanings that 
are rather ad-hoc, and not really the type of thing that you would 
need to find in a word list or dictionary, or they are made of words 
like 'se', 'gasnu', 'claxu' etc., and their meaning and place structure 
is obvious and doesn't need to be entered into a list (or both). I kind 
of like the idea of the lujvo being an open-ended lexicon, rather than 
needing to be canonized in a dictionary.

co'o mi'e adam

