Received: from mail-vb0-f61.google.com ([209.85.212.61]:47155) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1Softg-0003Bu-7z; Tue, 10 Jul 2012 12:15:03 -0700 Received: by vbzb23 with SMTP id b23sf342910vbz.16 for ; Tue, 10 Jul 2012 12:14:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:sender: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 :list-subscribe:list-unsubscribe:content-type; bh=vbyGMpTE83L7AElF1p3twjXewoYggbzXq788kh9ypwo=; b=WoyzXQN4n/MRu0l4+34zJgYxa2zOc4gFzihhy/GpNgSA1fVJxAgVOjVbi6PbcShpn3 m5QwmsikOPPR1U8pRTDJmQ0eJ1+PcrkYP+rtEIw3Ws3rUxTqlsyYg7CFUjP98DLkIO3h MQg51Ult1Pw5QkVe9GEOZ/27HJlTYDLBxBOk4= Received: by 10.236.114.193 with SMTP id c41mr1185504yhh.17.1341947689345; Tue, 10 Jul 2012 12:14:49 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.236.120.18 with SMTP id o18ls3860895yhh.0.gmail; Tue, 10 Jul 2012 12:14:48 -0700 (PDT) Received: by 10.236.178.3 with SMTP id e3mr31617734yhm.3.1341947688778; Tue, 10 Jul 2012 12:14:48 -0700 (PDT) Received: by 10.236.178.3 with SMTP id e3mr31617731yhm.3.1341947688758; Tue, 10 Jul 2012 12:14:48 -0700 (PDT) Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by gmr-mx.google.com with ESMTPS id t29si6608981yha.0.2012.07.10.12.14.48 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 10 Jul 2012 12:14:48 -0700 (PDT) Received-SPF: pass (google.com: domain of rpglover64@gmail.com designates 209.85.161.172 as permitted sender) client-ip=209.85.161.172; Received: by mail-gg0-f172.google.com with SMTP id c4so449728ggn.17 for ; Tue, 10 Jul 2012 12:14:48 -0700 (PDT) Received: by 10.60.18.114 with SMTP id v18mr47344021oed.34.1341947688490; Tue, 10 Jul 2012 12:14:48 -0700 (PDT) MIME-Version: 1.0 Sender: lojban@googlegroups.com Received: by 10.182.113.6 with HTTP; Tue, 10 Jul 2012 12:14:28 -0700 (PDT) In-Reply-To: <4FFC7C3C.8090705@gmail.com> References: <90a7e54c-42fe-4ee0-9693-8155db9a7646@googlegroups.com> <9aee28ed-4b47-4f34-a377-92e8c3a33bdc@googlegroups.com> <4FFC7C3C.8090705@gmail.com> From: ".arpis." Date: Tue, 10 Jul 2012 15:14:28 -0400 Message-ID: Subject: Re: [lojban] Re: Is there any demand for LoCCan3? To: lojban@googlegroups.com X-Original-Sender: rpglover64@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of rpglover64@gmail.com designates 209.85.161.172 as permitted sender) smtp.mail=rpglover64@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: List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=f46d0444eba54796e304c47e8bd6 X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / --f46d0444eba54796e304c47e8bd6 Content-Type: text/plain; charset=ISO-8859-1 What the heck is a "co-filled argument place" and does it have anything to do with a categorical dual? On Tue, Jul 10, 2012 at 3:02 PM, And Rosta wrote: > la gleki, On 09/07/2012 06:08: > > >> >> On Sunday, July 8, 2012 10:44:50 PM UTC+4, la .lindar. wrote: >> >> Curious... >> >> Why not just make it already? >> Quit talking and just do it. >_> >> >> >> Indeed. And Rosta, please present something. >> > > Alas, Gleki, it is on my list of projects, but with relatively low > priority on that list. Specifically, there are two relevant projects: one > is an essay describing a possible solution to the core problem of loglangs > (namely, representation of co-filled argument places); the other is an > essay describing a modular approach to the creation of a logical language. > The second is not stunningly original, but might serve to frame and focus > any collaborative effort that ever emerges. As for the first, I'm not > convinced the solution is processable by the human language faculty, and > the problem may instead remain unsolved; I suppose publishing it might spur > others to seek better solutions, but shortage of time for publishing one's > projects is the bane of my life. > > I could sit down and jot down in an email a sketch of something patently > better as a loglang than Lojban, but the only worthwhile loglang is the one > that cracks that fundamental problem of ergonomically representing > co-filled argument places; without that, any other incremental improvement > to Lojban has lost its appeal to me. > > --And. > > > -- > 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 . > > -- mu'o mi'e .arpis. -- 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. --f46d0444eba54796e304c47e8bd6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable What the heck is a "co-filled argument place" and does it have an= ything to do with a categorical dual?

On = Tue, Jul 10, 2012 at 3:02 PM, And Rosta <and.rosta@gmail.com> wrote:
la gleki, On 09/07/2012 06:08:



On Sunday, July 8, 2012 10:44:50 PM UTC+4, la .lindar. wrote:

=A0 =A0 Curious...

=A0 =A0 Why not just make it already?
=A0 =A0 Quit talking and just do it. >_>


Indeed. And Rosta, please present something.

Alas, Gleki, it is on my list of projects, but with relatively low priority= on that list. Specifically, there are two relevant projects: one is an ess= ay describing a possible solution to the core problem of loglangs (namely, = representation of co-filled argument places); the other is an essay describ= ing a modular approach to the creation of a logical language. The second is= not stunningly original, but might serve to frame and focus any collaborat= ive effort that ever emerges. As for the first, I'm not convinced the s= olution is processable by the human language faculty, and the problem may i= nstead remain unsolved; I suppose publishing it might spur others to seek b= etter solutions, but shortage of time for publishing one's projects is = the bane of my life.

I could sit down and jot down in an email a sketch of something patently be= tter as a loglang than Lojban, but the only worthwhile loglang is the one t= hat cracks that fundamental problem of ergonomically representing co-filled= argument places; without that, any other incremental improvement to Lojban= has lost its appeal to me.<= br>
--And.


--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@goo= glegroups.com.
For more options, visit this group at http://groups.google.com/grou= p/lojban?hl=3Den.




--
mu'o mi= 'e .arpis.

--
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.
--f46d0444eba54796e304c47e8bd6--