From jjllambias@hotmail.com Sat Aug 31 15:40:16 2002
Return-Path: <jjllambias@hotmail.com>
X-Sender: jjllambias@hotmail.com
X-Apparently-To: lojban@yahoogroups.com
Received: (EGP: mail-8_1_0_1); 31 Aug 2002 22:40:16 -0000
Received: (qmail 7459 invoked from network); 31 Aug 2002 22:40:16 -0000
Received: from unknown (66.218.66.216)
  by m3.grp.scd.yahoo.com with QMQP; 31 Aug 2002 22:40:16 -0000
Received: from unknown (HELO hotmail.com) (216.33.241.183)
  by mta1.grp.scd.yahoo.com with SMTP; 31 Aug 2002 22:40:16 -0000
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
  Sat, 31 Aug 2002 15:40:16 -0700
Received: from 200.69.6.37 by lw8fd.law8.hotmail.msn.com with HTTP;
  Sat, 31 Aug 2002 22:40:15 GMT
To: lojban@yahoogroups.com
Bcc: 
Subject: Re: [lojban] dictionary - which words?
Date: Sat, 31 Aug 2002 22:40:15 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F183Ov5y4FypKsEgJXO0000877e@hotmail.com>
X-OriginalArrivalTime: 31 Aug 2002 22:40:16.0271 (UTC) FILETIME=[6072A1F0:01C2513F]
From: "Jorge Llambias" <jjllambias@hotmail.com>
X-Originating-IP: [200.69.6.37]
X-Yahoo-Group-Post: member; u=6071566
X-Yahoo-Profile: jjllambias2000


la pier cusku di'e

>What about {ctelr zei kemxasybakni}? No one would use {kemxasybakni} except
>in a zei-lujvo, but one would use {xasybakni} by itself. Should there be an
>entry for {ctelr zei kemxasybakni}, or one for {kemxasybakni}?

I don't know how zei-lujvo should be treated. I would say treat
each component as a separate word, so in that example there would
be an entry for ctelr and one for kemxasybakni. (Though I would think
{ctelr zei xasybakni} should suffice in this case.)
If {kemxasybakni} is only used in a zei-lujvo, that's what its
definition would say.

Hopefully the total number of zei-lujvo in the dictionary will be
countable with the fingers of one hand...

mu'o mi'e xorxes


_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx


