Received: from mail-pb0-f61.google.com ([209.85.160.61]:58818) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1SorY7-0000Ra-02; Wed, 11 Jul 2012 00:41:32 -0700 Received: by pbbro2 with SMTP id ro2sf1261928pbb.16 for ; Wed, 11 Jul 2012 00:41:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:date:from:to:message-id:in-reply-to:references:subject :mime-version: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; bh=TetCHl5XQ6EL4lbIFg2Uu0u0SvgIS9FGoBd4rYncm6E=; b=6VQ9VfLt20ZtLvidMtKHpo3Btuni1mxk0pc1uCpxBrqrp6MAlCdXooPTAZYYcMauw3 SojOcYIj96NjQU2E1gHopV7KyeP7UXWCbvXwrLW5Jz62M2dqT+QnzAw4RogO5cbu/43T qSoxm5uu2jjhp4+gOGAMU93zNlQuKdn9U8V3Y= Received: by 10.52.26.18 with SMTP id h18mr194707vdg.0.1341992480786; Wed, 11 Jul 2012 00:41:20 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.52.88.68 with SMTP id be4ls70846vdb.3.gmail; Wed, 11 Jul 2012 00:41:20 -0700 (PDT) Received: by 10.52.68.141 with SMTP id w13mr898961vdt.18.1341992480085; Wed, 11 Jul 2012 00:41:20 -0700 (PDT) Date: Wed, 11 Jul 2012 00:41:19 -0700 (PDT) From: la gleki To: lojban@googlegroups.com Message-Id: In-Reply-To: <90a7e54c-42fe-4ee0-9693-8155db9a7646@googlegroups.com> References: <90a7e54c-42fe-4ee0-9693-8155db9a7646@googlegroups.com> Subject: [lojban] Re: Is there any demand for LoCCan3? MIME-Version: 1.0 X-Original-Sender: gleki.is.my.name@gmail.com X-Original-Authentication-Results: ls.google.com; spf=pass (google.com: domain of gleki.is.my.name@gmail.com designates internal as permitted sender) smtp.mail=gleki.is.my.name@gmail.com; dkim=pass header.i=@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: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary="----=_Part_1646_11137975.1341992479397" X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / ------=_Part_1646_11137975.1341992479397 Content-Type: text/plain; charset=ISO-8859-1 Let's name Loglan = LoCCan 1.0 Lojban = LoCCan 2.0 Lojban after xorlo reform = LoCCan 2.1 Preliminary analysis of this topic. I can see several proposals on LoCCans including LoCCan > 2.1 and Loccan sibling projects. Let's range them from backward-incompatible to tiny Lojban improvements. (I won't analyse every proposal, though) 1. Backward-incompatible And Rosta's project of CCV-gismu equal to rafsi and CCVrCCV lujvo where "r" is a buffer consonant. This lowers signal-to-noise ratio but makes learning rafsi=gismu much easier (no separate forms for gismu/rafsi). This can possibly remove the need in many modal tags that are actually duplicates and compressed versions of gismu 2. Backward-incompatible stevo's proposal of syntax that is always left-grouping. This can also increase the simplicity of the language 3. Backward-compatible la gleki's idea of rafybri packing bridi into lujvo-like structure retaing internal predicate relations as opposed to ordinary lujvo (by adding 4 new rafsi for x2...x5 place tags and extensively using {-jve-} for x1 tag). https://groups.google.com/forum/#!topic/lojban/64L-yY8ete8/discussion 4. Backward-compatible xorxes's proposal on connectives that suggest learning a smaller set of connectives. 5. Backward-compatible massive introduiction of experimental cmavo by some lojbanists. This might improve language flexibility but make learning harder. (Compare Loglan=Loccan 1.0) that had around 200 cmavo only. Does Loccan3 have future? Let's imagine that And Rosta, stevo and la gleki merged their efforts to produce a new Loccan. Let's imagine that they succeeded in rewriting the dictionary and the CLL. What next? The answer is very short. The project will become viable if they have enough resources to adapt the whole lojban corpus (including lojban.org wiki) and grow the number of students to ~100. Then the schism will be successful and I will for sure leave Lojbanistan. Needless to say that this goal is not likely to be reached in the nearest future. And I won't accept any half-done work. Still it would be nice to read it (just like with Ithkuil). Comment on rafybri. I have to say a word of rafybri and And Rosta's proposals. We can start reading a very old (but still valid) paper by Nick Nicholas [http://www.lojban.org/files/papers/nsn_semantics_paper] where he slightly critisizes selecting sumti places for lujvo. For me such play with sumti places is may be the most terrible drawback of lojban. And therefore I'm for paying more attention to Deep Gismu structure. I don't like {posydji} but like {ko'a djica lo nu ko'e ponse ko'i}. And Rosta's suggests relexing gismu. Still lujvo in eir language will have no internal predicate structure. Rafybri compress some bridi preserving sumti places between two or more gismu. They are equivalent in meaning to some lujvo but donot require learning them by rot. However, ordinary lujvo retain broken vague ambiguous internal structure of tanru with no places. I don't think And Rosta's CCV suggestion is much better than rafybri (rafybri can be used immediately as they add new rules but donot destroy any old rules). But let's wait until ey presents something. Therefore my choice within the baseline is * no lujvo if you can use gismu * for complex concepts like computer terminology, names of plants and animals use lujvo and fu'ivla (you'll have to memorise them by rot anyway) On Monday, July 2, 2012 10:17:57 AM UTC+4, la gleki wrote: > > Several recent messages mentioned the need for LoCCan3. > I wonder is there really any demand for it? > lojban.org wiki mentions nothing > special. > > 1. Fewer cmavo (but you are free to use fewer cmavo in current lojban) > 2. There should be new cmavo for individuals, sets and masses > 3. connectives > 4. anaphoric pronouns > (sorry, I didn't understand a word in #2,3,4, can you explain it to me in > plain language?). > 5. gismu with another number of sumti (but you are free not to use some > sumti, to use sumtcita etc.) > > Anyway, even if so is there any need to break existing language? > -- You received this message because you are subscribed to the Google Groups "lojban" group. To view this discussion on the web visit https://groups.google.com/d/msg/lojban/-/XSyeN_zFGqoJ. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en. ------=_Part_1646_11137975.1341992479397 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Let's name 
Loglan =3D LoCCan 1.0
Lojban =3D = LoCCan 2.0
Lojban after xorlo reform =3D LoCCan 2.1
Preliminary analysis of this topic.

I = can see several proposals on LoCCans including LoCCan > 2.1 and Loccan s= ibling projects.
Let's range them from backward-incompatible to t= iny Lojban improvements.
(I won't analyse every proposal, though)=

1. Backward-incompatible And Rosta's project of C= CV-gismu equal to rafsi and CCVrCCV lujvo where "r" is a buffer consonant. = This lowers signal-to-noise ratio but makes learning rafsi=3Dgismu much eas= ier (no separate forms for gismu/rafsi). This can possibly remove the need = in many modal tags that are actually duplicates and compressed versions of = gismu
2. Backward-incompatible stevo's proposal of syntax that is= always left-grouping. This can also increase the simplicity of the languag= e
3. Backward-compatible la gleki's idea of rafybri packing bridi= into lujvo-like structure retaing internal predicate relations as opposed = to ordinary lujvo (by adding 4 new rafsi for x2...x5 place tags and extensi= vely using {-jve-} for x1 tag). https://groups.google.com/forum/#!topic/loj= ban/64L-yY8ete8/discussion
4. Backward-compatible xorxes's propos= al on connectives that suggest learning a smaller set of connectives.
=
5. Backward-compatible massive introduiction of experimental cmavo by = some lojbanists. This might improve language flexibility but make learning = harder. (Compare Loglan=3DLoccan 1.0) that had around 200 cmavo only.
=

Does Loccan3 have future?
Let's imagine that = And Rosta, stevo and la gleki merged their efforts to produce a new Loccan.= Let's imagine that they succeeded in rewriting the dictionary and the CLL.= What next?
The answer is very short. The project will become via= ble if they have enough resources to adapt the whole lojban corpus (includi= ng lojban.org wiki) and grow the number of students to ~100. Then the schis= m will be successful and I will for sure leave Lojbanistan.

<= /div>
Needless to say that this goal is not likely to be reached in the= nearest future. And I won't accept any half-done work. Still it would be n= ice to read it (just like with Ithkuil).

Comment o= n rafybri.
I have to say a word of rafybri and And Rosta's propos= als.
We can start reading a very old (but still valid) paper by N= ick Nicholas [http://www.lojban.org/files/papers/nsn_semantics_paper] where= he slightly critisizes selecting sumti places for lujvo.

For me such play with sumti places is may be the most terrible draw= back of lojban. And therefore I'm for paying more attention to Deep Gismu s= tructure. I don't like {posydji}  but like {ko'a djica lo nu ko'e pons= e ko'i}.

And Rosta's suggests relexing gismu. Stil= l lujvo in eir language will have no internal predicate structure.

Rafybri compress some bridi preserving sumti places betwee= n two or more gismu. They are equivalent in meaning to some lujvo but donot= require learning them by rot.
However, ordinary lujvo retain bro= ken vague ambiguous internal structure of tanru with no places.
I= don't think And Rosta's CCV suggestion is much better than rafybri (rafybr= i can be used immediately as they add new rules but donot destroy any old r= ules). But let's wait until ey presents something.

Therefore my choice within the baseline is
* no lujvo if you can= use gismu
* for complex concepts like computer terminology, name= s of plants and animals use lujvo and fu'ivla (you'll have to memorise them= by rot anyway)

On Monday, July 2, 2012 10:17:57 AM UTC= +4, la gleki wrote:
Several rec= ent messages mentioned the need for LoCCan3.
I wonder is there really a= ny demand for it?
lojban.org wiki mentions nothing special.

1. Few= er cmavo (but you are free to use fewer cmavo in current lojban)
= 2. There should be new cmavo for individuals, sets and masses
3. = connectives
4. anaphoric pronouns
(sorry, I didn't unde= rstand a word in #2,3,4, can you explain it to me in plain language?).
<= /div>
5. gismu with another number of sumti (but you are free not to us= e some sumti, to use sumtcita etc.)

Anyway, even i= f so is there any need to break existing language?

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To view this discussion on the web visit https://groups.google.com/d/msg/lojban/-/XS= yeN_zFGqoJ.
=20 To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com.
For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.
------=_Part_1646_11137975.1341992479397--