From pycyn@aol.com Mon Apr 16 09:39:09 2001 Return-Path: X-Sender: Pycyn@aol.com X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-7_1_2); 16 Apr 2001 16:39:09 -0000 Received: (qmail 94986 invoked from network); 16 Apr 2001 16:39:08 -0000 Received: from unknown (10.1.10.27) by m8.onelist.org with QMQP; 16 Apr 2001 16:39:08 -0000 Received: from unknown (HELO imo-m08.mx.aol.com) (64.12.136.163) by mta2 with SMTP; 16 Apr 2001 16:39:07 -0000 Received: from Pycyn@aol.com by imo-m08.mx.aol.com (mail_out_v29.14.) id r.99.13a29728 (16934) for ; Mon, 16 Apr 2001 12:38:52 -0400 (EDT) Message-ID: <99.13a29728.280c7a1c@aol.com> Date: Mon, 16 Apr 2001 12:38:52 EDT Subject: Re: [lojban] sodna, kliru, navni To: lojban@yahoogroups.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_99.13a29728.280c7a1c_boundary" Content-Disposition: Inline X-Mailer: AOL 6.0 for Windows US sub 10519 From: pycyn@aol.com --part1_99.13a29728.280c7a1c_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 4/16/2001 7:01:00 AM Central Daylight Time, phma@oltronics.net writes: > >Sodium, chlorine, and neon are just the prototypes. > > So what should we call sodium, chrorine, and neon in particular? > Presumably {sodna, kliru, navni} with no second place -- the prototype unless some modification is specified. What is more interesting is exactly how to specify lithium or iodine or argon, i.e., what goes in the second place? --part1_99.13a29728.280c7a1c_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 4/16/2001 7:01:00 AM Central Daylight Time,
phma@oltronics.net writes:


>Sodium, chlorine, and neon are just the prototypes.

So what should we call sodium, chrorine, and neon in particular?

Presumably {sodna, kliru, navni} with no second place -- the prototype unless
some modification is specified.  What is more interesting is exactly how to
specify lithium or iodine or argon, i.e., what goes in the second place?
--part1_99.13a29728.280c7a1c_boundary--