From olivia@sonicblond.com Thu Oct 12 07:30:50 2000 Return-Path: X-Sender: olivia@sonicblond.com X-Apparently-To: lojban@egroups.com Received: (EGP: mail-6_1_0); 12 Oct 2000 14:30:50 -0000 Received: (qmail 21145 invoked from network); 12 Oct 2000 14:30:49 -0000 Received: from unknown (10.1.10.26) by m1.onelist.org with QMQP; 12 Oct 2000 14:30:49 -0000 Received: from unknown (HELO erika.sixgirls.org) (209.208.150.50) by mta1 with SMTP; 12 Oct 2000 14:30:49 -0000 Received: from localhost (localhost [[UNIX: localhost]]) by erika.sixgirls.org (8.11.0+3.3W/8.9.3) with ESMTP id e9CEUjV21361 for ; Thu, 12 Oct 2000 10:30:45 -0400 (EDT) Date: Thu, 12 Oct 2000 10:30:45 -0400 (EDT) X-Sender: olivia@erika.sixgirls.org To: lojban@egroups.com Subject: Re: na nei In-Reply-To: <20001012142252.6425.qmail@web3304.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII From: Olivia X-Yahoo-Message-Num: 4550 > > I can't think of any context where {nei} would be useful. perhaps in poetry: i'm working on translating a poem that has a fair amount of phrase repetition for poetic effect. i think 'nei' might be useful in this case. but maybe poetic repetition is not very 'lojbanic' anyway....(?) olivia -- Of course, the product assurance architecture necessitates that urgent consideration be applied to the evolution of specifications over a given time period.