From nobody@digitalkingdom.org Tue Oct 31 01:48:01 2006 Received: with ECARTIS (v1.0.0; list lojban-list); Tue, 31 Oct 2006 01:48:02 -0800 (PST) Received: from nobody by chain.digitalkingdom.org with local (Exim 4.63) (envelope-from ) id 1GeqDf-0007OO-1G for lojban-list-real@lojban.org; Tue, 31 Oct 2006 01:47:43 -0800 Received: from ug-out-1314.google.com ([66.249.92.170]) by chain.digitalkingdom.org with esmtp (Exim 4.63) (envelope-from ) id 1GeqDb-0007NO-PA for lojban-list@lojban.org; Tue, 31 Oct 2006 01:47:42 -0800 Received: by ug-out-1314.google.com with SMTP id 23so1388218ugr for ; Tue, 31 Oct 2006 01:47:38 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=Aej1VKqK3JYFrJg2Sm8gur4NeSV/uzs6D2Ur7SncycPyR3CEWNf5GFBHL4Ag0tz5oTwJLtAZ42Q0B0oIsPSyLKjaCtJQ6JfY9vzlNaTn2BWWfRLy5khm1KPcelvIebHcneGejOsAnrIs1eKK50xuQRFrfiEsUU3wSl71ZuhkjSo= Received: by 10.78.170.17 with SMTP id s17mr6494836hue; Tue, 31 Oct 2006 01:47:37 -0800 (PST) Received: by 10.78.124.16 with HTTP; Tue, 31 Oct 2006 01:47:37 -0800 (PST) Message-ID: Date: Tue, 31 Oct 2006 04:47:37 -0500 From: "Andrii (lOkadin) Zvorygin" To: lojban-list@lojban.org Subject: [lojban] reform MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2886_10208755.1162288057464" X-Spam-Score: -1.8 (-) X-archive-position: 12856 X-ecartis-version: Ecartis v1.0.0 Sender: lojban-list-bounce@lojban.org Errors-to: lojban-list-bounce@lojban.org X-original-sender: andrii.z@gmail.com Precedence: bulk Reply-to: lojban-list@lojban.org X-list: lojban-list ------=_Part_2886_10208755.1162288057464 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline lOjban is great, but it's not as logical as it could be. For the next major revision, should we modify lOjban, or should we call it something else? maybe not so much we as mi. I've been doing a lot of thinking about lOjban, its' structure and implementing it as a programming language. I've come to the conclusion that lOjban, is just far too ambiguous in it's current state to be used as it is. I can understand that when the zo'onai ba'e bAnli fInti la lOjban. were designing lOjban, they had no other logical language (other than loglan) to base themselves off of. Logical Language Group, is well named, they didn't hard code themselves to lOjban. Main reason I don't want to start a new lOjban, off somewhere else: the current lOjban already has a community. Anyways, if we are going to have to conform to the 1993 guidelines, with those gIsmu, well then there is little I can do, and there is really little to no room for flexibility. some proposed revisions, (if you want, for most of these I can give a logical proof): - making cmAvo corelate with gIsmu, no more, la'a and cu'i meaning completly un-intuitive things. - vei removal of ambiguous gIsmu .inaja removal of zAsni gIsmu ve'o .ije vei removal of gIsmu, poi can be defined in terms of other gIsmu .inaja removal of sImsa gIsmu . Obviously, that's a ridiculous proposition, as most gIsmu would have to be removed, and it would be very difficult to speak in high level abstractions all the time, and we'd be killing the whole 1993 backwards compatability, so next point is proposition to save at least some of the gIsmu, (cultural gIsmu must go, they are nothing but to'e socially neutral) - split gIsmu, into at least two classes. sElbri(fAnva) and cmEne(cInfo). how can you tell the difference? two options, can do both: 1. make once class CCVCV formation and another CVCCV formation 2. make the rAfsi of sElbri gIsmu be CVV and the rAfsi of the cmEne be CVC or CCV - change fa fe fi, to pa re ci, no point in wasting CV formation grammar structures. numbers must be declared with a li anyways, gives people more incentive to do so as well. we can claim it to mean that numbers without li is like saying, first, second, third, to get away with it. - modify lUjvo to make them unambiguous, hopefully will be possible by changing how gIsmu work slightly. - ba drAta da -- ta'o(by the way) We With You Network at: http://lokiworld.org .i(and) more on Lojban: http://lojban.org mu'oimi'e lOkadin (Over, my name is lOkadin) ------=_Part_2886_10208755.1162288057464 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline lOjban is great, but it's not as logical as it could be. For the next major revision, should we modify lOjban, or should we call it something else?

maybe not so much we as mi.

I've been doing a lot of thinking about lOjban, its' structure  and implementing it as a programming language.
I've come to the conclusion that lOjban, is just far too ambiguous in it's current state to be used as it is.

I can understand that when the zo'onai ba'e bAnli fInti la lOjban. were designing lOjban, they had no other logical language (other than loglan) to base themselves off of.

Logical Language Group, is well named, they didn't hard code themselves to lOjban.

Main reason I don't want to start a new lOjban, off somewhere else: the current lOjban already has a community.

Anyways, if we are going to have to conform to the 1993 guidelines, with those gIsmu, well then there is little I can do, and there is really little to no room for flexibility.


some proposed revisions, (if you want, for most of these I can give a logical proof):
  • making cmAvo corelate with gIsmu, no more, la'a and cu'i meaning completly un-intuitive things.
  • vei removal of ambiguous gIsmu .inaja removal of zAsni gIsmu ve'o .ije vei removal of gIsmu, poi can be defined in terms of other gIsmu  .inaja removal of sImsa gIsmu . Obviously, that's a ridiculous proposition, as most gIsmu would have to be removed, and it would be very difficult to speak in high level abstractions all the time, and we'd be killing the whole 1993 backwards compatability, so next point is proposition to  save at least some of the gIsmu, (cultural gIsmu must go, they are nothing but to'e socially neutral)
  • split gIsmu, into at least two classes. sElbri(fAnva) and cmEne(cInfo). how can you tell the difference? two options, can do both:
    1. make once class CCVCV formation and another CVCCV formation
    2. make the rAfsi of sElbri gIsmu be CVV and the rAfsi of the cmEne be CVC or CCV
  • change fa fe fi, to pa re ci, no point in wasting CV formation grammar structures. numbers must be declared with a li anyways, gives people more incentive to do so as well.  we can claim it to mean that numbers without li is like saying, first, second, third, to get away with it.
  • modify lUjvo to make them unambiguous, hopefully will be possible by changing how gIsmu work slightly.
  • ba drAta da

--
ta'o(by the way)  We With You Network at: http://lokiworld.org .i(and)
more on Lojban: http://lojban.org
mu'oimi'e lOkadin (Over, my name is lOkadin) ------=_Part_2886_10208755.1162288057464-- To unsubscribe from this list, send mail to lojban-list-request@lojban.org with the subject unsubscribe, or go to http://www.lojban.org/lsg2/, or if you're really stuck, send mail to secretary@lojban.org for help.