Return-Path: <@SEGATE.SUNET.SE:LOJBAN@CUVMB.BITNET> Received: from SEGATE.SUNET.SE by xiron with smtp (Linux Smail3.1.28.1 #1) id m0sOKd0-0000YnC; Wed, 21 Jun 95 10:55 EET DST Message-Id: Received: from segate.sunet.se by SEGATE.SUNET.SE (LSMTP for OpenVMS v0.1a) with SMTP id 0DA9A7DC ; Wed, 21 Jun 1995 9:44:23 +0200 Date: Wed, 21 Jun 1995 03:43:31 -0400 Reply-To: Logical Language Group Sender: Lojban list From: Logical Language Group Subject: scales, tolcipni X-To: lojban@cuvmb.cc.columbia.edu To: Veijo Vilva Content-Length: 1459 Lines: 38 >> >traji cipni >> >mutce cipni >> >milxe cipni >> >tolmutce cipni >> >na'e cipni >> >> Some things wrong with this scale. I'm not sure what the difference is >> between milxe and tolmutce, for one. > >I see {milxe} more as {normutce}. {tolmutce} is very little. So we are starting with different ideas of milxe. Given a scalar function, my intent for these was: <- - - - - - - - - - - - - - - - - | - - - - - - - - - - - - - - - - - - > traji na mutce na milxe na | milxe mutce traji to'e no'e je'a | na'e | Given that each of these words have particular places on the scale, treating each term as its own scale is at best ambiguous. Is to'e milxe some kind of mutce? Or some kind of milxe na >>> And you are missing no'e cipni, >>> which should be somewhere above na'e cipni but not sure where > >What would that be? For that to make any sense, you would need a scale >going from bird to anti-bird, and {no'e cipni} would be the midpoint. >If {no'e cipni} makes sense, so does {to'e cipni}. It does, kinda of. It is just that I would have trouble describing one. archeopteryx, or possibly the dinosaurs, qualify in my mind as no'e cipni, and depending on exactly your parameters for a bird, maybe even a bat (scientists might call a bat "na'e cipni", but non-science-aware cultures might reject that classification". lojbab