Received: from mail-ob0-f186.google.com ([209.85.214.186]:33757) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1YrReg-0006G7-LY for lojban-list-archive@lojban.org; Sun, 10 May 2015 06:53:06 -0700 Received: by obbnt9 with SMTP id nt9sf29582071obb.0 for ; Sun, 10 May 2015 06:52:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-original-sender:x-original-authentication-results :reply-to:precedence:mailing-list:list-id:list-post:list-help :list-archive:sender:list-subscribe:list-unsubscribe; bh=Thu/A+QkmGFtyxf1amzE1dafoZdyByy0iZImlmjzWdM=; b=c5TR37Wcx+BrxE7WTjZEiZ1CFt6SxSXxvYYM2WRRQbIPdJDFZQHe8OdZrnfww2Z3gd i3i7j7f63bdrCEfESxZX1MrgXGafFQes79Wzze59x02g9u9QqY6Q3M9D0LiphfRTSgpz LEr1DLWT7KPq7KbY1vhoRuF0oIcmUbsz0i6G68XSfdEmvTECm5+1mnYRymDtHJZRs+YW VSQOldJakUdtzPhTrF/DBGrdRgFU2IyFnAWkvfiUn3wvCoNRdcC6i43u9ipK9dDlt7xG UxHeuzCkVYUa7O5CH6Ww4OVywEH1/zhV4PnyBb+tJFmX7VTNIjdTfJ9+tfgy+82CH5uC Rqew== X-Received: by 10.50.97.104 with SMTP id dz8mr133113igb.10.1431265944564; Sun, 10 May 2015 06:52:24 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.107.8.135 with SMTP id h7ls1335618ioi.100.gmail; Sun, 10 May 2015 06:52:24 -0700 (PDT) X-Received: by 10.67.23.36 with SMTP id hx4mr11418726pad.45.1431265944270; Sun, 10 May 2015 06:52:24 -0700 (PDT) Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com. [2607:f8b0:400d:c01::22a]) by gmr-mx.google.com with ESMTPS id g10si1605620qci.2.2015.05.10.06.52.24 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 10 May 2015 06:52:24 -0700 (PDT) Received-SPF: pass (google.com: domain of blindbravado@gmail.com designates 2607:f8b0:400d:c01::22a as permitted sender) client-ip=2607:f8b0:400d:c01::22a; Received: by mail-qc0-x22a.google.com with SMTP id k17so57900838qcy.1 for ; Sun, 10 May 2015 06:52:24 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.140.41.148 with SMTP id z20mr7909727qgz.40.1431265944114; Sun, 10 May 2015 06:52:24 -0700 (PDT) Received: by 10.140.104.149 with HTTP; Sun, 10 May 2015 06:52:24 -0700 (PDT) In-Reply-To: <6fa4fb48-8814-416f-b1fb-f25e2dcc75dc@googlegroups.com> References: <6fa4fb48-8814-416f-b1fb-f25e2dcc75dc@googlegroups.com> Date: Sun, 10 May 2015 09:52:24 -0400 Message-ID: Subject: Re: [lojban] selma'o Documentation (or, rewriting the CLL?) From: Ian Johnson To: lojban@googlegroups.com Content-Type: multipart/alternative; boundary=001a11c121482db6f20515ba92bd X-Original-Sender: blindbravado@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of blindbravado@gmail.com designates 2607:f8b0:400d:c01::22a as permitted sender) smtp.mail=blindbravado@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.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: , List-Unsubscribe: , X-Spam-Score: -1.7 (-) X-Spam_score: -1.7 X-Spam_score_int: -16 X-Spam_bar: - --001a11c121482db6f20515ba92bd Content-Type: text/plain; charset=UTF-8 While there are problems, I don't think this is as bad as you are making it out to be. Xorlo did not change syntax. The cmevla-brivla merge (if that is semi-official now) makes a minor change in syntax; basically LA works the same as LE did to begin with, which is pretty much exactly what you would expect. Perhaps we could compile a list of the completely new selma'o that actually get used in practice. I know I in particular have made a point of trying to use existing selma'o with my coined cmavo. Four of my cmavo in JVS have a selma'o I made up, two of these cmavo being in the same selma'o. Details: {jai'a} was made for fun because I saw a use case for it, but it is only useful in the same way that {jai} is, and is much less frequently applicable. {no'oi} and {po'oi} were made for symmetry back when I was actively working on fancylojban-ish stuff. We don't really have the brivla to make good use of them right now, and I doubt we will anytime soon. {ju'ei} is quite useful when it is desirable, but that is infrequent. Indeed I can't think of a situation where I would want to use {ju'ei} in a literal translation of well-written English, because in English this is either bad style or simply unintelligible. My remaining nine cmavo all use official selma'o, specifically ZO, ME, LAhE, NAhE, KE, XI, ZOhU, LE. I would strongly encourage people with ideas for cmavo to try to twist them into existing selma'o if at all possible. The unofficial selma'o I have actually seen a fair bit in chat: ZOhOI, LOhAI/SAhAI/LEhAI, MEhOI, ZEhEI. The rest? Easily able to be ignored for a long time, in my view. mi'e la latro'a mu'o On Sun, May 10, 2015 at 1:14 AM, Spheniscine wrote: > So I faced a problem: One could look up what a cmavo is supposed to mean, > and see the selma'o it belongs to. The problem is that there is no current > reference as to what the selma'o mean, and its syntax; little things like > whether {na'e fetsi mlatu} refers to a cat that is non-female or something > that isn't a female cat (turns out, it's the first. To express the second, > you need {na'e ke fetsi mlatu [ke'e]}, or {na'e fetsi bo mlatu}). And sure, > one could use the ilmentufa parser, but that won't tell you about the > little details like the possible different functions of certain selma'o > like BO and NAI, depending on position. I also wanted very rough > correspondences of certain selma'o to common parts of speech like > "prepositions" "articles" etc., which you can't find on a simple search. Of > course, I do realize that these correspondences are in fact very rough, and > that the selma'o resist any strict classification to those terms, but I > wanted there to be at least a starting point. > > So then, I brought up the idea of writing a documentation for the selma'o; > after some encouragement, I started this wiki page: > http://mw.lojban.org/papri/lo_selma%27o_ca%27irvei_(selma%27o_Documentation) > > *However*, I soon ran into a second problem - defining the Lojbanic > metalinguistic terms that we keep throwing around, like {selbri}, {sumti}, > {tanru}, and of course, {selma'o}. You can see the results of my attempt on > that page; I just ended up tying myself in knots defining each term in > terms of other terms. This won't quite do; they need to be defined from the > ground up, and a mere glossary is not quite sufficient for that. > > So then I got to thinking... that's what the CLL is supposed to do, right? > {la selpa'i} even pointed out a page in the CLL that has much the same > function as my page was meant to be for: http://lojban.github.io/cll/20/ > > But the problem is that the CLL is fossilized; it has not been updated in > years, maybe decades. It does not reflect the various reforms over the > years; not the cmevla-brivla merge, not any of the new cmavo or selma'o, > not even xorlo. It's also not reflected any changes and tightening in > meta-linguistic terminology; it uses {cmene} instead of {cmevla}, for > example. > > Of course, though, this "new CLL" has to be on the Wiki, and able to be > edited to reflect any future reforms; otherwise it's just end up like the > current CLL, or Loglan before it. It can't belong to me, to la gleki, to la > selpahi, or anyone, but everyone. > > {.ie pei doi ro do} > > -- > 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 > email 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/d/optout. > -- 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 email 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/d/optout. --001a11c121482db6f20515ba92bd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
While there are pr= oblems, I don't think this is as bad as you are making it out to be. Xo= rlo did not change syntax. The cmevla-brivla merge (if that is semi-officia= l now) makes a minor change in syntax; basically LA works the same as LE di= d to begin with, which is pretty much exactly what you would expect. Perhap= s we could compile a list of the completely new selma'o that actually g= et used in practice.

I know I in particular have made a point= of trying to use existing selma'o with my coined cmavo. Four of my cma= vo in JVS have a selma'o I made up, two of these cmavo being in the sam= e selma'o. Details:
{jai'a} was made for fun because I saw a use= case for it, but it is only useful in the same way that {jai} is, and is m= uch less frequently applicable.
{no'oi} and {po'oi} were made f= or symmetry back when I was actively working on fancylojban-ish stuff. We d= on't really have the brivla to make good use of them right now, and I d= oubt we will anytime soon.
{ju'ei} is quite useful when it is desir= able, but that is infrequent. Indeed I can't think of a situation where= I would want to use {ju'ei} in a literal translation of well-written E= nglish, because in English this is either bad style or simply unintelligibl= e.

My remaining nine cmavo all use official selma'o, specifical= ly ZO, ME, LAhE, NAhE, KE, XI, ZOhU, LE. I would strongly encourage people = with ideas for cmavo to try to twist them into existing selma'o if at a= ll possible.

The unofficial selma'o I have actually s= een a fair bit in chat: ZOhOI, LOhAI/SAhAI/LEhAI, MEhOI, ZEhEI. The rest? E= asily able to be ignored for a long time, in my view.

mi&= #39;e la latro'a mu'o
=




=
On Sun, May 10, 2015 at 1:14 AM, Spheniscine <spheniscine@gmail.com> wrote:
So I faced a problem: One could look up what a cmavo= is supposed to mean, and see the selma'o it belongs to. The problem is= that there is no current reference as to what the selma'o mean, and it= s syntax; little things like whether {na'e fetsi mlatu} refers to a cat= that is non-female or something that isn't a female cat (turns out, it= 's the first. To express the second, you need {na'e ke fetsi mlatu = [ke'e]}, or {na'e fetsi bo mlatu}). And sure, one could use the ilm= entufa parser, but that won't tell you about the little details like th= e possible different functions of certain selma'o like BO and NAI, depe= nding on position. I also wanted very rough correspondences of certain selm= a'o to common parts of speech like "prepositions" "artic= les" etc., which you can't find on a simple search. Of course, I d= o realize that these correspondences are in fact very rough, and that the s= elma'o resist any strict classification to those terms, but I wanted th= ere to be at least a starting point.

So then, I brought = up the idea of writing a documentation for the selma'o; after some enco= uragement, I started this wiki page:=C2=A0h= ttp://mw.lojban.org/papri/lo_selma%27o_ca%27irvei_(selma%27o_Documentation)=

However, I soon ran into a second prob= lem - defining the Lojbanic metalinguistic terms that we keep throwing arou= nd, like {selbri}, {sumti}, {tanru}, and of course, {selma'o}. You can = see the results of my attempt on that page; I just ended up tying myself in= knots defining each term in terms of other terms. This won't quite do;= they need to be defined from the ground up, and a mere glossary is not qui= te sufficient for that.

So then I got to thinking.= .. that's what the CLL is supposed to do, right? {la selpa'i} even = pointed out a page in the CLL that has much the same function as my page wa= s meant to be for:=C2=A0http://lojban.github.io/cll/20/

Bu= t the problem is that the CLL is fossilized; it has not been updated in yea= rs, maybe decades. It does not reflect the various reforms over the years; = not the cmevla-brivla merge, not any of the new cmavo or selma'o, not e= ven xorlo. It's also not reflected any changes and tightening in meta-l= inguistic terminology; it uses {cmene} instead of {cmevla}, for example.

Of course, though, this "new CLL" has to b= e on the Wiki, and able to be edited to reflect any future reforms; otherwi= se it's just end up like the current CLL, or Loglan before it. It can&#= 39;t belong to me, to la gleki, to la selpahi, or anyone, but everyone.

{.ie pei doi ro do}

--
You received this message because you are subscribed to the Google Groups &= quot;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/d/optout.

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsub= scribe@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 http= s://groups.google.com/d/optout.
--001a11c121482db6f20515ba92bd--