Received: from mail-qa0-f56.google.com ([209.85.216.56]:39742) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1SlwDQ-00062B-F4; Mon, 02 Jul 2012 23:04:09 -0700 Received: by qaas11 with SMTP id s11sf4579106qaa.1 for ; Mon, 02 Jul 2012 23:03:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:date:from:to:cc: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=TyWMRuyY8lGP0PFz94vNQT1/AMNeMVMVF2P5BJhr630=; b=GJSFR3X0m6IeuFsKHTohSJpwv1fQhroSycvFitRo4ORtZJV7dXGnRixOIBZKJNgyxQ PlE3tSZay1M12jIeVTvQFQviKjBcwgYP7KVgueAycEHAZIWDU2pjsU7+KgCE7bndrapm AvkrRotQdLTkvGVCn4YNjqAa6Cc789WMcMBa0= Received: by 10.52.94.147 with SMTP id dc19mr398911vdb.17.1341295433728; Mon, 02 Jul 2012 23:03:53 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.52.66.242 with SMTP id i18ls3550437vdt.5.gmail; Mon, 02 Jul 2012 23:03:52 -0700 (PDT) Received: by 10.52.174.167 with SMTP id bt7mr914790vdc.15.1341295432445; Mon, 02 Jul 2012 23:03:52 -0700 (PDT) Date: Mon, 2 Jul 2012 23:03:51 -0700 (PDT) From: gleki To: lojban@googlegroups.com Cc: John E Clifford Message-Id: <4d3c0b67-bb46-42ee-ae73-0570e08b3106@googlegroups.com> In-Reply-To: <1341252212.22198.YahooMailNeo@web184415.mail.bf1.yahoo.com> References: <90a7e54c-42fe-4ee0-9693-8155db9a7646@googlegroups.com> <62818d3a-c188-43d5-ad25-09c4cc9aca6c@googlegroups.com> <1341252212.22198.YahooMailNeo@web184415.mail.bf1.yahoo.com> Subject: Re: [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_1263_2956452.1341295431953" X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / ------=_Part_1263_2956452.1341295431953 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On Monday, July 2, 2012 10:03:32 PM UTC+4, clifford wrote: > > LoCCan3 has been for more than 20 years (and before that there was Loglan= =20 > 2.0) a repository for noting flaws perceived in Lojban (and before that= =20 > Loglan) and for suggested solutions and other improvements (read scare=20 > quotes where you will). The active content has varied over the years: no= =20 > one is hot for adding or dropping phonemes at the moment, for example. B= ut=20 > a few items have endured, usually connected with perceived problems. > 0. A complete redo of the vocabulary (obviously not back-compatible). = =20 > The present vocab clusters in some phonetic spaces and leaves others bare= ,=20 > increasing the likelihood of confusion in noisy environments (if Lojban i= s=20 > ever used in one) and making it harder to find fragments for constructing= =20 > compounds and related cmavo. The only reason for the present word list i= s=20 > the claimed ease of learning, a claim that has never been tested on even= =20 > English speakers, let alone Chinese or other languages or relevant=20 > multilinguals. The evidence presented is either intuitive or anecdotal a= nd=20 > these are countered by anecdotal difficulties ("false friends" they used = to=20 > be called). The revamp includes a revision of the definitions, which cou= ld=20 > be done separately (with a bit more compatibility) to make the definition= s=20 > simpler (generally fewer places, with many places that occur in many=20 > definitions but are rarely used spun off to prepositions) and more unifor= m=20 > (all words of the same sort (you are keeping your supply of scare quotes= =20 > running, I hope) would have the same pattern of places). A general shake= =20 > down of the cmavo system is also part of this, sharpening definitions,=20 > clarifying roles, getting rid of detritus, relieving confusion pressure,= =20 > etc. For the most part, this is not Lojban at all but the beginnings of = a=20 > real third generation from Loglan. So not going to happen until the next= =20 > charismatic nut-case comes along. > Ubykh has 84 phonemic consonants. As J. Quijada writes "Ubykh single-word= =20 sentence wan-t*w-*aan - "they give you to him" ... contains six phonemes,= =20 each of which is a separate morpheme.... If such single-phoneme morphemes= =20 are good enough for real-world natural languages, they=92re good enough for= =20 Ithkuil." Which means that you can never invent a sound system suitable for everyone= =20 but at the same time even most complex phoneme inventory might be=20 naturalistic. In the long run you might end in Piraha-style conlang which= =20 has around 7 consonants > 1. Anaphora. The logical ideal is a way to refer back to any previously= =20 > mentioned thing unambiguously and transparently from anywhere in the late= r=20 > discourse. Practically impossible with pronouns, unless every noun is=20 > assigned a carrier at birth (and there are problems even with that). =20 > Loglan can come remarkably close, but the system barely works with writte= n=20 > text and is just not practical in spoken language beyond very short=20 > intervals. The usable Lojban techniques, official and not, work as well = as=20 > the unofficial for the most part but are also of limited scope. The rule= =20 > "Repetition is also anaphora" seems the best way to go, though even it ha= s=20 > to be used carefully in some Cataphora (referring to something about to= =20 > be mentioned) is always short scope and can be eased by mentioning it now= =20 > already. > So no problem in the current Lojban? :) > 2. Words for individuals and sets and masses arose out of the muddle,=20 > inherited from Loglan and not much tidied up in CLL, about what exactly '= lo=20 > broda' referred to. The old underlying logic had only individuals, some = of=20 > which were sets that contained other individuals (or not). The problem= =20 > then was to deal with groups that did not behave like sets in set theory= =20 > but could still go in for individual variables. For some reason, the=20 > notion that ordinary sets could take properties in different ways from th= e=20 > usual ways for sets did not occur to anyone, so this remained a problem. = =20 > Until xorxes found a book about plural reference/instantiation. Accordin= g=20 > to this, a singular noun could refer to several things at once and a=20 > singular variable could be simultaneously instantiated to several things = at=20 > once. Conceptually differently, but formally the same, sets could be=20 > Lesniewskian rather than Cantorian, so that getting to the members of a s= et=20 > is much easier (as is talking about what happens). Once 'lo broda' was= =20 > taken to refer to an L-set of brodas, much of the rest fell into place. = =20 > Because the theory is also of the part-whole relation, it is sometimes=20 > necessary to distinguish the relevant individuals (ones with no relevant= =20 > parts) and also to be able to talk about wholes (L-sets) in the abstract= =20 > way that one normally talks about C-sets. This means that some of the=20 > gadri need redefinition (or clarification of the given definitions). The= re=20 > are also some residual problems with 'lo' left over from Loglan that need= =20 > sorting out. None of this has much affect on current or past text. > Clarification is great. Again sounds quite reasonable within the current=20 language. > 3, The original four logical connectives, and their derivatives (often= =20 > more interesting) and the handful of non-logical ones have multiplied=20 > sixfold or more. As the language is built, these are needed to preserve= =20 > the underlying logical structure, to provide a way to get back to the=20 > underlying simple sentences connected sententially from the given comple= x=20 > sentence involving connected terms or predicates or bridi tails or=20 > whatever. The quest here has been to find a simpler way of marking these= =20 > transformations without needing a whole new vocabulary at each stage. Th= e=20 > fact that the reconstruction process involved is not proven to be correct= =20 > also needs some looking at. This may be a minor matter of reinterpreting= =20 > given forms or it may take a thorough reworking of the connective parts o= f=20 > the grammar. > .i'a =20 > 4. RHE. Though the grammatical right-hand end problems are mainly solve= d=20 > (with the constant danger of misuse leading to your saying something quit= e=20 > different from what you meant), the logical ones are less well dealt with= =20 > (the "get back to the formula" problem seen in 3). So far, informal=20 > conventions seem to be in place and there are some cmavo for doing some o= f=20 > these jobs. But they are rarely used and not well described. They do no= t=20 > form clear groups in the cmavo lists, though grouping them might not be a= =20 > problem (and the fact that they are very different might be an advantage)= . =20 > Again clarification. That's the job of lojbanists, not loccan3-ists. That is what LoCCan3 actively contains at the moment. > > ------------------------------ > *From:* gleki > *To:* lojban@googlegroups.com=20 > *Sent:* Monday, July 2, 2012 4:41 AM > *Subject:* [lojban] Re: Is there any demand for LoCCan3? > =20 > Let's discuss it now ))). > After reading the article I want new language even less. > *The monkey took the banana and ate it.*=20 > *Pam went home because she felt sick.* =20 > *The dog ate the bird and it died.* (!!!!!!!!!!!) > > In each case I can use {ta} and the context will decide who felt sick (th= e=20 > house or Pam) and who died (the dog or the bird). > > In other cases vo'a, ko'a can solve the problem. > > {sei} can be problematic for me but I hope CLL 1.1 will explain it. > > I can think of no other cases of anaphora. > > And it's still am mystery for me what can be done with > > 2. There should be new cmavo for individuals, sets and masses > 3. new design of connectives > > > On Monday, July 2, 2012 10:26:12 AM UTC+4, la .lindar. wrote: > > It's come up a few times. > https://en.wikipedia.org/wiki/ Anaphora_(linguistics) > > I think we're working on the rest. > > It's a theoretical next-step language, but I don't see it happening any= =20 > time soon since we're changing up our game. > > --=20 > You received this message because you are subscribed to the Google Groups= =20 > "lojban" group. > To view this discussion on the web visit=20 > https://groups.google.com/d/msg/lojban/-/ZqkHTaoWCKAJ. > To post to this group, send email to lojban@googlegroups.com. > To unsubscribe from this group, send email to=20 > lojban+unsubscribe@googlegroups.com. > For more options, visit this group at=20 > http://groups.google.com/group/lojban?hl=3Den. > =20 And therefore > So not going to happen until the next=20 > charismatic nut-case comes along. =20 ban such person immediately from this group when [s]he appears! vau zo'o --=20 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/lo= jban/-/zIhMeLYOEpAJ. 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_1263_2956452.1341295431953 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable

On Monday, July 2, 2012 10:03:32 PM UTC+4, clifford wrote:
LoCCan3 has been for more than 20 years (and before that ther= e was Loglan 2.0) a repository for noting flaws perceived in Lojban (and be= fore that Loglan) and for suggested solutions and other improvements (read = scare quotes where you will).  The active content has varied over the = years: no one is hot for adding or dropping phonemes at the moment, for exa= mple.  But a few items have endured, usually connected with perceived = problems.
0.  A complete redo of the vocabulary= (obviously not back-compatible).  The present vocab clusters in some = phonetic spaces and leaves others bare, increasing the likelihood of confus= ion in noisy environments (if Lojban is ever used in one) and making it har= der to find fragments for constructing compounds and related cmavo.  T= he only reason for the present word list is the claimed ease of learning, a claim that has ne= ver been tested on even English speakers, let alone Chinese or other langua= ges or relevant multilinguals.  The evidence presented is either intui= tive or anecdotal and these are countered by anecdotal difficulties ("false= friends" they used to be called).  The revamp includes a revision of = the definitions, which could be done separately (with a bit more compatibil= ity) to make the definitions simpler (generally fewer places, with many pla= ces that occur in many definitions but are rarely used spun off to preposit= ions) and more uniform (all words of the same sort (you are keeping your su= pply of scare quotes running, I hope) would have the same pattern of places= ).  A general shake down of the cmavo system is also part of this, sha= rpening definitions, clarifying roles, getting rid of detritus, relieving c= onfusion pressure, etc.  For the most part, this is not Lojban at all but the beginnings of a real third generation from Loglan.  So= not going to happen until the next charismatic nut-case comes along.
Ubykh has 84 phonemic consonants. As J= . Quijada writes "Ubykh single-word sentence wan-tw-aan - "they give= you to him" ... contains six phonemes, each of which is a separate morphem= e.... If such single-phoneme morphemes are good enough for real-world = natural languages, they=92re good enough for Ithkuil."

=
Which means that you can never invent a sound system suitable for ever= yone but at the same time even most complex phoneme inventory might be natu= ralistic. In the long run you might end in Piraha-style conlang which has a= round 7 consonants
<= div style=3D"color:#000;background-color:#fff;font-family:times new roman,n= ew york,times,serif;font-size:12pt">
1. Anaphora.  The logic= al ideal is a way to refer back to any previously mentioned thing unambiguo= usly and transparently from anywhere in the later discourse.  Practica= lly impossible with pronouns, unless every noun is assigned a carrier at bi= rth (and there are problems even with that).  Loglan can come remarkab= ly close, but the system barely works with written text and is just not pra= ctical in spoken language beyond very short intervals.  The usable Loj= ban techniques, official and not, work as well as the unofficial for the mo= st part but are also of limited scope.  The rule "Repetition is also a= naphora" seems the best way to go, though even it has to be used carefully = in some   Cataphora (referring to something about to be mentioned= ) is always short scope and can be eased by mentioning it now already.
So no problem in the current Lojban? :)
2.  Words for individuals and sets and masses arose out = of the muddle, inherited from Loglan and not much tidied up in CLL, about w= hat exactly 'lo broda' referred to.  The old underlying logic had only= individuals, some of which were sets that contained other individuals (or = not).  The problem then was to deal with groups that did not behave li= ke sets in set theory but could still go in for individual variables. = For some reason, the notion that ordinary sets could take properties in di= fferent ways from the usual ways for sets did not occur to anyone, so this = remained a problem.  Until xorxes found a book about plural reference/= instantiation.  According to this, a singular noun could refer to seve= ral things at once and a singular variable could be simultaneously instanti= ated to several things at once.  Conceptually differently, but formall= y the same, sets could be Lesniewskian rather than Cantorian, so that getting to= the members of a set is much easier (as is talking about what happens).&nb= sp; Once 'lo broda' was taken to refer to an L-set of brodas, much of the r= est fell into place.  Because the theory is also of the part-whole rel= ation, it is sometimes necessary to distinguish the relevant individuals (o= nes with no relevant parts) and also to be able to talk about wholes (L-set= s) in the abstract way that one normally talks about C-sets.  This mea= ns that some of the gadri need redefinition (or clarification of the given = definitions).  There are also some residual problems with 'lo' left ov= er from Loglan that need sorting out.  None of this has much affect on= current or past text.
Clarificat= ion is great. Again sounds quite reasonable within the current language.
3,  The original four logical connectives, a= nd their derivatives (often more interesting) and the handful of non-logica= l ones have multiplied sixfold or more.  As the language is built, these are needed to preserve the underlying logical= structure, to provide a way to get back to the underlying simple sentences= connected sententially  from the given complex sentence involving con= nected terms or predicates or bridi tails or whatever.  The quest here= has been to find a simpler way of marking these transformations without ne= eding a whole new vocabulary at each stage.  The fact that the reconst= ruction process involved is not proven to be correct also needs some lookin= g at.  This may be a minor matter of reinterpreting given forms or it = may take a thorough reworking of the connective parts of the grammar.
.i'a
 
4.  RHE.  Though the grammatical right-hand end probl= ems are mainly solved (with the constant danger of misuse leading to your s= aying something quite different from what you meant), the logical ones are = less well dealt with (the "get back to the formula" problem seen in 3).  So far, informal conventions seem to be in place and the= re are some cmavo for doing some of these jobs.  But they are rarely u= sed and not well described.  They do not form clear groups in the cmav= o lists, though grouping them might not be a problem (and the fact that the= y are very different might be an advantage). 
<= /div>
Again clarification. That's the job  of lojbani= sts, not loccan3-ists.

That is what LoCCan3 actively contains at the moment.


From: gleki <gleki.is.my.name@gmail.com>
To: lojban@googlegroups.com
Sent: Monday, July 2, 2012 4:41 AM
Subject: [lojban] Re: Is there any demand for LoCCa= n3?

Let's discuss it now ))).
After reading the article I want new lan= guage even less.
The monkey took the banana and ate it= . 
Pam went home because she felt sick.  
The dog ate the bird a= nd it died.  (!!!!!!!!!!!)

In each case I= can use {ta} and the context will decide who felt sick (the house or Pam) = and who died (the dog or the bird).

In other cases=  vo'a, ko'a can solve the problem.

{sei} can= be problematic for me but I hope CLL 1.1 will explain it.

I can think of no other cases of anap= hora.

And it's still am mystery for me what can be= done with
2. There should be new cmavo for individuals, sets and masse= s
3. new design of connectives

On Monday, July 2, 2012 10:26:12 AM UTC+4, la .lindar. wrote:It's come up a few times.

<= /div>
I think we're working on the rest.

It's = a theoretical next-step language, but I don't see it happening any time soo= n since we're changing up our game.
--
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/-/ZqkHTaoWCKAJ.
=20 To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googl= egroups.com.
For more options, visit this group at http://groups.google.com/group/= lojban?hl=3Den.
 
And therefore
> So= not going to happen until the next 
> charismatic nu= t-case comes along.  

ban such person immediately from this g= roup when [s]he appears! vau zo'o

--
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/-/zI= hMeLYOEpAJ.
=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_1263_2956452.1341295431953--