Received: from mail-oa0-f61.google.com ([209.85.219.61]:49853) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1V364t-0003tw-2S for lojban-list-archive@lojban.org; Sat, 27 Jul 2013 08:06:48 -0700 Received: by mail-oa0-f61.google.com with SMTP id i4sf1269671oah.6 for ; Sat, 27 Jul 2013 08:06:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-beenthere:date:from:to:subject:message-id:in-reply-to:references :mime-version:x-aol-global-disposition:x-aol-scoll-score :x-aol-scoll-url_count:x-aol-sid:x-aol-ip:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type :content-transfer-encoding; bh=iX0lfLdPHJsiBPd3yZNfvCcYWvOF1ogNUkYnKEclJy0=; b=jcaMjR+uq9Q/63IMruSXSFyF2SOZJcniOL/Enh6HIT4C5mRrZpvuz7a6TkVHrl25kC iMUXyOMrpQE5tFF1mGuvfemmvhOhpusJUCL8FAFs5rdZ4QxfKkuulYxYE+Bbg6osqg2p w7vd/tWCVvk7aNl/KSuJUqoV+Ghwf/7pnpuwdFmprbGQGB7K1iGe/2mEDfh0BKT20if2 hJJhUwyT7XiPALBYeWeXwLv64rWKyqX1MP6Jl5LMSFrkQcrO4V4IvUN/cDucO0+usukX 8F/ku46vq4FUxUWcNbdZRvgkRpufRXI/MfCn5EO2kAt2yUYNDZVErhgbdUTes8vLm5Ei ZkpQ== X-Received: by 10.49.25.227 with SMTP id f3mr1953112qeg.33.1374937592889; Sat, 27 Jul 2013 08:06:32 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.49.82.101 with SMTP id h5ls1469170qey.91.gmail; Sat, 27 Jul 2013 08:06:32 -0700 (PDT) X-Received: by 10.236.54.135 with SMTP id i7mr28256821yhc.33.1374937592549; Sat, 27 Jul 2013 08:06:32 -0700 (PDT) Received: from omr-m07.mx.aol.com (omr-m07.mx.aol.com. [64.12.143.81]) by gmr-mx.google.com with ESMTPS id en4si1343540qcb.2.2013.07.27.08.06.32 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 27 Jul 2013 08:06:32 -0700 (PDT) Received-SPF: pass (google.com: domain of almikes@aol.com designates 64.12.143.81 as permitted sender) client-ip=64.12.143.81; Received: from mtaout-mb06.r1000.mx.aol.com (mtaout-mb06.r1000.mx.aol.com [172.29.41.70]) by omr-m07.mx.aol.com (Outbound Mail Relay) with ESMTP id 2EDBF70035472 for ; Sat, 27 Jul 2013 11:06:31 -0400 (EDT) Received: from localhost.localdomain (p549FA1E7.dip0.t-ipconnect.de [84.159.161.231]) by mtaout-mb06.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id 0AEADE0000B6 for ; Sat, 27 Jul 2013 11:06:29 -0400 (EDT) Date: Sat, 27 Jul 2013 17:06:26 +0200 From: Wuzzy To: lojban@googlegroups.com Subject: Re: [lojban] idea: selma'o fu'ivla Message-ID: <20130727170626.0c3047f8@aol.com> In-Reply-To: References: <20130725021725.3ce55578@aol.com> Mime-Version: 1.0 x-aol-global-disposition: G X-AOL-SCOLL-SCORE: 0:2:424015712:93952408 X-AOL-SCOLL-URL_COUNT: 0 x-aol-sid: 3039ac1d294651f3e1f57ccc X-AOL-IP: 84.159.161.231 X-Original-Sender: almikes@aol.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of almikes@aol.com designates 64.12.143.81 as permitted sender) smtp.mail=almikes@aol.com; dkim=pass header.i=@mx.aol.com Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Spam_score: 0.0 X-Spam_score_int: 0 X-Spam_bar: / Warning: Long text ahead. This e-mail in a nutshell: - I agree to rename =E2=80=9Cselma'o fu'ivla=E2=80=9D to =E2=80=9Cselma'o z= i'evla=E2=80=9D. - I give comments on possible lojban definitions for selma'o zi'evla - I propose a new naming scheme for those selma'o names that start with a vowel. At Wed, 24 Jul 2013 on 23:45:37 -0400, Jacob Errington wrote: > What's important when making up definitions is not what they are in > English, but rather what they are in *Lojban*. Good point! > (Also, the more correct term in this case > is {zi'evla}. It doesn't make sense to call {cmavr}, a > fu'ivla as it isn't a loanword by any stretch.) Correct. I have updated the wikipage and moved it to . =20 > I'd probably define these in Lojban with {x1 se cmavo zo bai .e > zo ...} and list all the elements + {fo lo lojbo}. The concise > definition would be be {x1 se cmavo zo bai ra'u fo lo lojbo}. Almost okay, I would change =E2=80=9Clojbo=E2=80=9D to something which expl= icitly refers to the language. Like =E2=80=9Clo banjubu'o=E2=80=9D, =E2=80=9Clo jb= obau=E2=80=9D or =E2=80=9Cla lojban.=E2=80=9D. I am not sure, but I think that =E2=80=9Cmu'a=E2=80=9D instead of =E2=80=9C= ra'u=E2=80=9D would be more logically here. With =E2=80=9Cra'u=E2=80=9D, it could be interpreted that = =E2=80=9Cbai=E2=80=9D is somehow more important than the other BAI cmavo. But in fact it=E2=80=99s j= ust a name-giver, an example. The name-giving cmavo look to me as if they were randomly chosen and not because they are somehow more important than the other ones. Here is my example short definition for BAI: =E2=80=9C$x_1$ se cmavo zo bai mu'a fo lo banjubu'o=E2=80=9D Additionally, since the =E2=80=9Cofficial=E2=80=9D selma'o name is so impor= tant, we should include it in the =E2=80=9Cnotes=E2=80=9D field: Notes: =E2=80=9Cla'o sy WhATEVER sy cu drata cmene $x_1$=E2=80=9D where =E2= =80=9CWhATEVER=E2=80=9D is of course the =E2=80=9Cofficial=E2=80=9D selma'o name. I chose the =E2=80=9Csy=E2=80=9D delimeter for =E2=80=9Cselma'o=E2=80=9D. A= lso =E2=80=9Csy=E2=80=9D can=E2=80=99t be a selma'o name, because =E2=80=9Csy=E2=80=9D is already in= BY. So this template should work for all selma'o imaginable and therefore is usable for automation. > Customarily, when the zi'evla-head begins with a vowel, we prefix > [x], not [lr], e.g. the fu'ivla for "anime" {skinrxanime}.. I come back to it. > > Here=E2=80=99s the list of irregegular selma'o fu'ivla produced with ab= ove > > rules: > > A cmavlra > zo cmavrxa .e'u A newbie may be tempted to believe that this is the selma'o =E2=80=9CXA=E2= =80=9D. ;-) I come back to it. > > UI cmavlrui > the [u] in {ui} is a consonant, so {cmavrui} is fine. But it isn=E2=80=99t a stage-3 zi'evla and I want to start with stage-3 zi'= evla for all selma'o. It=E2=80=99s just pure luck that =E2=80=9Ccmavrui=E2=80=9D= is at least morphologically correct, it=E2=80=99s a stage-4 zi'evla. You don=E2= =80=99t have this luck all the time. =E2=80=9Ccmavri=E2=80=9D (for selma'o I), for examp= le, would be a lujvo. And although the =E2=80=9Cu=E2=80=9D in =E2=80=9Cui=E2=80=9D is sp= oken like a consonant, in morphology, that =E2=80=9Cu=E2=80=9D is still considered a vowel IIRC. > > I cmavlri > Sadly, adding [x] doesn't work here as it clashes with selma'o XI. > Your proposal for the l-hyphen works, but in my opinion, it should be > limited as much as possible to the case where it is necessary, i.e. > between r and n. And the entire idea of using =E2=80=9Cx=E2=80=9D breaks down. Additionally,= =E2=80=9Ccmavrxa=E2=80=9D could be interpreted =E2=80=9Cselma'o XA=E2=80=9D. Yeah, of course one can = _know_ that this is _not_ the case here since I=E2=80=99d create a clear definition. Bu= t it may cause some confusion. I had some reasons to pick the hyphen letters. I just didn=E2=80=99t explai= n them yet. Now the time has come. The main reason is to provide a ruleset contains =E2=80=9CY=E2=80=9D =E2=86=92 use brivla starts with other vowel (no Y) =E2=86=92 =E2=80=9Clr=E2=80=9D =E2=80=9Chyph= en=E2=80=9D + selma'o starts with =E2=80=9CR=E2=80=9D =E2=86=92 =E2=80=9Cn=E2=80=9D hyphen + se= lma'o starts with other consonant =E2=86=92 =E2=80=9Cr=E2=80=9D hyphen + selma'o The choices for the consonants were no-brainers since the CLL gives a good default here. I did pick =E2=80=9Clr=E2=80=9D because I wanted it to be different from = =E2=80=9Cr=E2=80=9D and =E2=80=9Cn=E2=80=9D.=20 See the difference between =E2=80=9Ccmavrxa=E2=80=9D and =E2=80=9Ccmavlra= =E2=80=9D: =E2=80=9Ccmavrxa=E2=80=9D breaks down into =E2=80=9Ccmav=E2=80=9D, =E2=80= =9Cr=E2=80=9D and =E2=80=9Cxa=E2=80=9D (selma'o XA?) =E2=80=9Ccmavlra=E2=80=9D breaks down into =E2=80=9Ccmav=E2=80=9D, =E2=80= =9Cl=E2=80=9D, =E2=80=9Cr=E2=80=9D and =E2=80=9Ca=E2=80=9D (clearly selma'o= A). The =E2=80=9Cr=E2=80=9D is neccessary here because =E2=80=9Ccmavla=E2=80=9D= would be a lujvo. If you see a =E2=80=9Cn=E2=80=9D or =E2=80=9Cr=E2=80=9D hyphen, then what f= ollows behind it is either the selma'o name in lower-case or a brivla which descibes the selma'o. It should always be possible to reconstruct the =E2=80=9Cofficial=E2=80=9D = selma'o name if in the first case. If you look at =E2=80=9Ccmavrbai=E2=80=9D and =E2=80=9Ccmavrdepsna=E2=80=9D= , you can extract =E2=80=9Cbai=E2=80=9D and =E2=80=9Cdepsna=E2=80=9D, respectively. =E2=80=9Cbai=E2=80=9D is clearly a = cmavo, write it in upper-case and you have the =E2=80=9Cofficial=E2=80=9D selma'o name =E2=80= =9CBAI=E2=80=9D. =E2=80=9Cdepsna=E2=80=9D is clearly a lujvo, so it can=E2=80=99t refer to the selma'o =E2=80=9CDEPSNA= =E2=80=9D (doesn=E2=80=99t exist anyways). So you know that =E2=80=9Ccmavrdepsna=E2=80=9D refers the t= he selma'o which has something to do with =E2=80=9Cdepsna=E2=80=9D. You simply have to= know that it is =E2=80=9CI=E2=80=9D in this case. Luckily, there are just two border = cases so far. So far, so good. But now I noticed that the coice =E2=80=9Cl=E2=80=9D + =E2= =80=9Cr=E2=80=9D was actually a bad one. =E2=80=9Ccmavlra=E2=80=9D, =E2=80=9Ccmavlri=E2=80=9D and =E2=80= =9Ccmavlrui=E2=80=9D aren=E2=80=99t stage-3 zi'evla, they are stage-4. Whoops. I have changed my mind and suggest this instead: If the selma'o starts with a vowel, use the =E2=80=9Cr=E2=80=9D hyphen and = append =E2=80=9Cxr=E2=80=9D to it and after that the lower-cased selma'o name. So: =E2=80=9Ccmavrxrui=E2=80=9D =E2=86=92 =E2=80=9Ccmav=E2=80=9D + =E2=80=9Cr= =E2=80=9D + =E2=80=9Cxr=E2=80=9D + =E2=80=9Cui=E2=80=9D =E2=86=92 clearly s= elma'o UI =E2=80=9Ccmavrxri=E2=80=9D =E2=86=92 =E2=80=9Ccmav=E2=80=9D + =E2=80=9Cr=E2= =80=9D + =E2=80=9Cxr=E2=80=9D + =E2=80=9Ci=E2=80=9D =E2=86=92 clearly the s= elma'o I =E2=80=9Ccmavrxra=E2=80=9D =E2=86=92 =E2=80=9Ccmav=E2=80=9D + =E2=80=9Cr=E2= =80=9D + =E2=80=9Cxr=E2=80=9D + =E2=80=9Ca=E2=80=9D =E2=86=92 clearly the s= elma'o A You can't break =E2=80=9Ccmavrxrui=E2=80=9D down into =E2=80=9Ccmav=E2=80= =9D + =E2=80=9Cr=E2=80=9D + =E2=80=9Cxrui=E2=80=9D and come to the conclusion that it stands for the selma'o XRUI. Because no cmavo is allowed to start with two consonants. Compare this to =E2=80=9Ccmavrxui=E2=80=9D =E2=86=92 Breaks this down into =E2=80=9Ccmav=E2= =80=9D + =E2=80=9Cr=E2=80=9D + =E2=80=9Cxui=E2=80=9D? Or to =E2=80=9Ccmav= =E2=80=9D + =E2=80=9Cr=E2=80=9D + =E2=80=9Cx=E2=80=9D + =E2=80=9Cui=E2=80=9D? It could = be interpreded as UI or as XUI. XUI may be an experimental selma'o invented at some day in the future, so there=E2=80=99s= a potential collision. =E2=80=9Ccmavrxi=E2=80=9D =E2=86=92 already taken by XI. This problem is ob= vious. =E2=80=9Ccmavrxa=E2=80=9D =E2=86=92 no collision, but slightly misleading, = one may be tempted think of the non-existant selma'o =E2=80=9CXA=E2=80=9D here. So I suggest these new slightly changed building rules for selma'o zie'vla: selma'o name contains =E2=80=9CY=E2=80=9D =E2=86=92 use brivla starts with other vowel =E2=86=92 =E2=80=9Cr=E2=80=9D hyphen + =E2=80=9Cxr= =E2=80=9D + selma'o starts with =E2=80=9CR=E2=80=9D =E2=86=92 =E2=80=9Cn=E2=80=9D hyphen + se= lma'o starts with other consonant =E2=86=92 =E2=80=9Cr=E2=80=9D hyphen + selma'o Now the =E2=80=9Crxr=E2=80=9D idea is much better than the =E2=80=9Clr=E2= =80=9D idea. It shares the spirit of the =E2=80=9Cx=E2=80=9D convention (thanks for pointing it out) b= ecause it=E2=80=99s very similar to it=E2=80=94it's basicly just the =E2=80=9Cx=E2=80=9D conven= tion with an =E2=80=9Cr=E2=80=9D appended. I wait for comments before I apply these changes to the wiki. --=20 Wuzzy XMPP: Wuzzy2@jabber.ccc.de E-Mail: wuzzy2@mail.ru --=20 You received this message because you are subscribed to the Google Groups "= lojban" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban. For more options, visit https://groups.google.com/groups/opt_out.