From LOJBAN@CUVMB.CC.COLUMBIA.EDU Sat Mar 6 22:56:55 2010 Return-Path: Delivered-To: veion@XIRON.PC.HELSINKI.FI Received: (qmail 18580 invoked from network); 29 Jan 1997 21:09:23 -0000 Received: from segate.sunet.se (192.36.125.6) by xiron.pc.helsinki.fi with SMTP; 29 Jan 1997 21:09:23 -0000 Received: from segate.sunet.se by SEGATE.SUNET.SE (LSMTP for OpenVMS v1.1a) with SMTP id <14.88F85AF6@SEGATE.SUNET.SE>; Wed, 29 Jan 1997 22:09:18 +0100 Date: Wed, 29 Jan 1997 16:07:43 -0500 Reply-To: "Mark E. Shoulson" Sender: Lojban list From: "Mark E. Shoulson" Subject: selma'o X-To: lojban@cuvmb.cc.columbia.edu To: Veijo Vilva Content-Length: 1468 Lines: 40 Message-ID: <7tL_spia9hK.A.rcB.340kLB@chain.digitalkingdom.org> -----BEGIN PGP SIGNED MESSAGE----- Something in one of lojbab's forwardings to conlang set me thinking. How many selma'o do we really use regularly? Obviously not all of them; MEX is hardly ever used; when was the last time you said ke'e, etc etc. Several possible projects can stem from this... 1. try, a priori, to decide on a relatively small set of selma'o and see if you can work comfortably within it. 2. try, a priori, to minimize the set of selma'o, as small as you can without getting "too" cramped (subjective judgement). 3. analyze existing texts and see the relative proportions of selma'o in use (e.g. replace all words with their selma'o and count up totals). Anyone find these fun? Let's see, off the top of my head, what selma'o would I really need? BRODA (of course. Gismu and counting lujvo), LE, LA, CMENE, NU, PU, A, UI, NA, NAI, BAI, COI/DOI, PA, ZOI, I, JA, KOhA, SE, FA, GOI, NOI are among the biggies... sometimes KU, KEI, even KUhO, BE, ... ROI, GOhA,... I'm pretty sure I missed a couple of really important ones, especially really common ones that have very few cmavo (like I nearly left out NA and NAI...) Thoughts? ~mark -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface iQB1AwUBMu+8HMppGeTJXWZ9AQHYuQL/Zq+V3dCyVaLlsUzCOxuFP5U2SOJzrNSk EuUGbh1Rs81RebtdTsF2ik3NzT6d7AHPnwNt9R1Kqo8RUX//pSILAmXgHUcaKEhS 8YOL5oixhMXVgFb7X+xM7WF2n5AbtXoi =ztd3 -----END PGP SIGNATURE-----