Received: from mail-pb0-f61.google.com ([209.85.160.61]:42008) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1Soxt4-0004mt-SV; Wed, 11 Jul 2012 07:27:37 -0700 Received: by pbbro2 with SMTP id ro2sf1656397pbb.16 for ; Wed, 11 Jul 2012 07:27:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:in-reply-to:references:from :date:message-id:subject:to: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=Ug2dt1hYXfFe97MLDjOkvP4XsGwuIBkU5DZl5n2whKc=; b=h01LMLDtU7zrGf5OowvSiTwdTCJmu5nkKMxbyfUt2x4HrZzjhveRjMjw/HbdcYnTOs GC9YCmVG370HmVPRWwjaEN4zDVD1uL7OxfYlHt9iqT+EuME7rWqe0MXZ4bNAWrN7afyY u5VhAPpkUExNg60N1WZL3/PRtWpSYdjPdQzPI= Received: by 10.182.207.67 with SMTP id lu3mr573291obc.17.1342016844490; Wed, 11 Jul 2012 07:27:24 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.182.78.202 with SMTP id d10ls251671obx.9.gmail; Wed, 11 Jul 2012 07:27:23 -0700 (PDT) Received: by 10.236.161.233 with SMTP id w69mr28436899yhk.7.1342016843175; Wed, 11 Jul 2012 07:27:23 -0700 (PDT) Received: by 10.236.161.233 with SMTP id w69mr28436897yhk.7.1342016843156; Wed, 11 Jul 2012 07:27:23 -0700 (PDT) Received: from mail-gh0-f181.google.com (mail-gh0-f181.google.com [209.85.160.181]) by gmr-mx.google.com with ESMTPS id u67si559379yhi.7.2012.07.11.07.27.23 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 11 Jul 2012 07:27:23 -0700 (PDT) Received-SPF: pass (google.com: domain of lytlesw@gmail.com designates 209.85.160.181 as permitted sender) client-ip=209.85.160.181; Received: by mail-gh0-f181.google.com with SMTP id z13so1532369ghb.26 for ; Wed, 11 Jul 2012 07:27:23 -0700 (PDT) Received: by 10.50.184.227 with SMTP id ex3mr14392222igc.26.1342016842809; Wed, 11 Jul 2012 07:27:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.30.68 with HTTP; Wed, 11 Jul 2012 07:26:52 -0700 (PDT) In-Reply-To: References: <90a7e54c-42fe-4ee0-9693-8155db9a7646@googlegroups.com> From: MorphemeAddict Date: Wed, 11 Jul 2012 10:26:52 -0400 Message-ID: Subject: Re: [lojban] Re: Is there any demand for LoCCan3? To: lojban@googlegroups.com X-Original-Sender: lytlesw@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of lytlesw@gmail.com designates 209.85.160.181 as permitted sender) smtp.mail=lytlesw@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=14dae9340d8132c20604c48ea5af X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / --14dae9340d8132c20604c48ea5af Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jul 11, 2012 at 3:41 AM, la gleki wrote: > 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 > I didn't make such a proposal. I only mentioned that I like RPN. There are at least two different areas of improvement for Lojban: vocabulary and grammar. The vocabulary is essentially irrelevent. Any sufficiently concise, flexible, rigorous, and self-segregating (if that's a worthwhile feature) will do. The grammar is the important part for me, and I'm not sufficiently knowledgeable of grammar and logic to work on this. Distinguishing proposals by which area is affected seems a useful thing to do. stevo 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.orgwiki) 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 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. --14dae9340d8132c20604c48ea5af Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Wed, Jul 11, 2012 at 3:41 AM, la glek= i <gleki.is.my.name@gmail.com> wrote:
Let's name=A0
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 = sibling projects.
Let's range them from backward-incompatible to tiny Lojban improve= ments.
(I won't analyse every proposal, though)
1. Backward-incompatible And Rosta's project of CCV-gismu e= qual 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 language
=

I didn't make such a proposal. I only = mentioned that I like RPN.=A0

There are at least two different areas of improvement f= or Lojban: vocabulary and grammar. The vocabulary is essentially irrelevent= . Any sufficiently concise, flexible, rigorous, and self-segregating (if th= at's a worthwhile feature) will do. The grammar is the important part f= or me, and I'm not sufficiently knowledgeable of grammar and logic to w= ork on this. Distinguishing proposals by which area is affected seems a use= ful thing to do.=A0

stevo

https://groups.goog= le.com/forum/#!topic/lojban/64L-yY8ete8/discussion
4. Backward-compatible xorxes's proposal on connectives that sugge= st 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=3DLo= ccan 1.0) that had around 200 cmavo only.

Does Loccan3 have future?
Let's imagine t= hat And Rosta, stevo and la gleki merged their efforts to produce a new Loc= can. 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 reac= hed 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/paper= s/nsn_semantics_paper] where he slightly critisizes selecting sumti pla= ces for lujvo.

For me such play with sumti places is may be the most t= errible drawback of lojban. And therefore I'm for paying more attention= to Deep Gismu structure. I don't like {posydji} =A0but 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 m= ore gismu. They are equivalent in meaning to some lujvo but donot require l= earning them by rot.
However, ordinary lujvo retain broken vague ambiguous internal structu= re 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 un= til ey presents something.

Therefore my choice within the baseline is
* = no lujvo if you can use gismu
* for complex concepts like compute= r terminology, names of plants and animals use lujvo and fu'ivla (you&#= 39;ll have to memorise them by rot anyway)

On Monday, July 2, 2012 10:17:57 AM UTC+4,= la gleki wrote:
Several recent mess= ages 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 curre= nt 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 (b= ut you are free not to use some sumti, to use sumtcita etc.)

Anyway, even if so is there any need to break existing langu= age?


--
You received this message because you are subscribed to the Google Groups "= lojban" group.
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.
--14dae9340d8132c20604c48ea5af--