Received: from mail-lb0-f189.google.com ([209.85.217.189]:33067) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.85) (envelope-from ) id 1aMYZe-0005x4-L7 for lojban-list-archive@lojban.org; Fri, 22 Jan 2016 02:04:15 -0800 Received: by mail-lb0-f189.google.com with SMTP id p10sf20998498lbo.0 for ; Fri, 22 Jan 2016 02:04:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-original-sender:x-original-authentication-results :reply-to:precedence:mailing-list:list-id:x-spam-checked-in-group :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe; bh=ZQJxtKvmT/RrEyQ34d4GHIStrcGJDq4hLEL80R9W8VY=; b=ctdHmJmNWLJWv6TQwZtpn36rlbA+YV3c4Wj94zYUUJJj9sqkAocRIxVMzM1r/u8nUn 98qY6r+wwJO4fatn9vfdyriTrzClfjtV5w2gww31UUwQ3iXY9a7Qi12C5Ij1WzMHEacJ n/inFj96SMCNGapoc0Iso+xH7+u1aO+dllj2JbrRU5i/Ozja2Gm3jLIcStSD0eQ+iEHC gINyLegMF/Zl08PF7sCNU693JiaCu2PBhagLhUjx8afbmFFWI9pA4diUQpKKV5Hw5BhS hT57ze30pEGDlQa4e1KHxU+PAjrxTtGSbC09QTmsY0UccvMKCH/Hp2AFRdpeZu6n4OOA ARvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe; bh=ZQJxtKvmT/RrEyQ34d4GHIStrcGJDq4hLEL80R9W8VY=; b=ZMJMWapLBNs6sfDk3uR5ZxKiG8mbRnwDrr/IAUZkqv/53xAdDR0B70Ac97Lmra+BEW N+rtyFeSdOxx8s3wSyZwuci3vX24YFqcTQOCMIE42+/OIbXwMbEOHg+tfcgmKcD41zsy 08R6BpMrXkec2vIYspEzlavfvT7NNyefaiHDCO6FfZS3Xo++Yej5dRRXltddgRu8uF5K j+6vs/4XHcjXERkrKM1tC+HlMFcXDgGBHbzTIGcn0QbueCF5c8M+3wtTo+DJzn0KIXFZ XIkFsFGTE5MTHYuRdMfBTEia7z5qPS/ik1xa3GzmZbYcHY2Aj4msCRrR+Z5HkqIXRz3z qTfA== X-Gm-Message-State: AG10YORwJK1NeyGNS3mRKaGhDYS7DuHoxHzD1tKWJshfXPiNCDr+kD5bxqHLBIg5DOJ87Q== X-Received: by 10.25.134.67 with SMTP id i64mr36103lfd.12.1453457043549; Fri, 22 Jan 2016 02:04:03 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.25.24.168 with SMTP id 40ls131230lfy.18.gmail; Fri, 22 Jan 2016 02:04:02 -0800 (PST) X-Received: by 10.112.72.195 with SMTP id f3mr269060lbv.15.1453457042972; Fri, 22 Jan 2016 02:04:02 -0800 (PST) Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com. [2a00:1450:4010:c07::234]) by gmr-mx.google.com with ESMTPS id jx10si178320lbc.2.2016.01.22.02.04.02 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Jan 2016 02:04:02 -0800 (PST) Received-SPF: pass (google.com: domain of selckiku@gmail.com designates 2a00:1450:4010:c07::234 as permitted sender) client-ip=2a00:1450:4010:c07::234; Received: by mail-lf0-x234.google.com with SMTP id 17so43736246lfz.1 for ; Fri, 22 Jan 2016 02:04:02 -0800 (PST) X-Received: by 10.25.151.71 with SMTP id z68mr725688lfd.122.1453457042869; Fri, 22 Jan 2016 02:04:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.4.1 with HTTP; Fri, 22 Jan 2016 02:03:33 -0800 (PST) In-Reply-To: <8805e2d3-4389-460c-9e5b-b0d5194da1c2@googlegroups.com> References: <6f919681-f16c-4888-aa5a-30518a717c12@googlegroups.com> <569F85BF.8030909@gmx.de> <8805e2d3-4389-460c-9e5b-b0d5194da1c2@googlegroups.com> From: Stela Selckiku Date: Fri, 22 Jan 2016 05:03:33 -0500 Message-ID: Subject: Re: [lojban] {cukta} as a case study for why the dictionary needs clearer, more detailed entries To: lojban@googlegroups.com Content-Type: text/plain; charset=UTF-8 X-Original-Sender: selckiku@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of selckiku@gmail.com designates 2a00:1450:4010:c07::234 as permitted sender) smtp.mailfrom=selckiku@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Spam-Checked-In-Group: lojban@googlegroups.com X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -1.7 (-) X-Spam_score: -1.7 X-Spam_score_int: -16 X-Spam_bar: - On Thu, Jan 21, 2016 at 4:24 AM, Andrew wrote: > > Specifically, I'd like to see an explanation of the meaning and possible > usage notes for all the sumti of each brivla. It's not enough to know just > the main gloss word for a brivla: One must also understand what would be > appropriate and what would be inappropriate to use as the x1 or x2 or x3... > of a given brivla. Well, meaning is a magical thing, so very subtle unexpected problems arise. I'm not actually familiar with any controversy with {cukta}, maybe the first place is unsettled but I don't understand the details. So instead as an example I'll talk about {fenki}. Let's see, what does the good ol' gimste say about {fenki}: x1 (action/event) is crazy/insane/mad/frantic/in a frenzy (one sense) by standard x2 See also bebna, racli, xajmi. crazy It's quite clear that the x1 is an event. A fenki is an event. OK great. But usage doesn't agree. Usage has never agreed. According to how {fenki} is used, a fenki is usually or always a person. So now what? If you bring up such a state of affairs, one perfectly reasonable response is to say, so what, people used {fenki} wrong, the definition was clear enough, they should start putting in the {jai} or saying {fekpre} or something. What's authoritative? What should be? Does it matter more what's in the gimste or what people have traditionally done for years? What other standards of aesthetics or rationality have what weight? Who judges? Interestingly, the definition written in Lojban reflects how {fenki} has actually been used, probably because it was written more recently: x1 to'e racli x2 .i x1 kalsa lo ka zukte x2 .i lo nu x1 cinmo x2 cu vlile racli; kalsa; zukte; cinmo; vlile; bebna created by xorxes This is a clearly worded modern definition in Lojban itself by a very respected authority. So personally I give great weight to those definitions in my personal understanding, and I recommend that wise path to you as well. So there's something vaguely like a consensus on a current meaning for {fenki} (except that some unclear number of people violently disagree). So? So what? So where and how would you like that near consensus more clearly agreed upon or expressed? Any process that approves updated definitions any slower than like one a day certainly can't get through the whole gimste in any reasonable length of time. Any process that churns through more than one a day and somehow produces a robust consensus is some sort of intense process we've never yet invented that unless it's somehow very clever we couldn't all possibly have time for. So here's my proposal. This isn't so much a solution as it is half of a solution. But that's more of a solution than we have at the moment! My half-solution is that when it's disputed or confused what the meaning of a brivla is, we figure out what all of the proposals or options are for its meaning and make new brivla to embody those alternate meanings. Making new words to put all the various possible meanings into doesn't actually solve the problem of reaching a consensus on which meaning to use for the original gismu. But I think it gets us closer. It gives us a vocabulary for discussing the possible meanings clearly and concisely in Lojban. It gives us access to all of the meanings-- importantly, it gives any potential "losing" side a way to retain their desired meaning as a part of the language while yielding just on a specific sound for it. And then when it becomes clear that the clarity we thought we had about one of the replacement words was actually muddled and we still don't yet agree at all, we can make replacement replacement words to tease apart those deeper meanings. I believe that by this process of exploring and allowing meaning to inhabit infinite refined picky vocabulary we can develop Lojban into the obsessively specific language it's always secretly longed to be. <3, mungojelly/selckiku -- You received this message because you are subscribed to the Google Groups "lojban" group. To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at https://groups.google.com/group/lojban. For more options, visit https://groups.google.com/d/optout.