Received: from mail-yk0-f190.google.com ([209.85.160.190]:39797) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XZAsl-0001O1-1T for lojban-list-archive@lojban.org; Tue, 30 Sep 2014 20:47:21 -0700 Received: by mail-yk0-f190.google.com with SMTP id q9sf1727ykb.27 for ; Tue, 30 Sep 2014 20:47:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:subject:in-reply-to:message-id:references:user-agent :mime-version:x-original-sender:x-original-authentication-results :reply-to:precedence:mailing-list:list-id:list-post:list-help :list-archive:sender:list-subscribe:list-unsubscribe:content-type; bh=a/2jDxvFIStZqU4geeXXPW1EYRwNatGP6cEEm8Y+NHw=; b=skpBavCCcxgjmLLJiKiVHByMF+FwOaCpAHEDPYZUEKsPiwHjOPM43XPhCivOM0lAkm kmWlNO+owwPLsqH0aR/J2RSLVOwjR5WtX9le54irsuqu3fzqZhBJ4P3BAUy1ALaNPMcq IbSy9kojxsZlUYdg4TyxCG38uVPskQI1PCPoEGdJKhL7JZegxPLCWOhrZiiPX7L5XGIq MFXM/yVwDWdFHv0lFisIr8IxB5W3m8JsWXHPCO7CeNrmiFAdcBzyhYLmc5Laoq0WobO7 +Gz7IfIWYm4vrtpdVh/x4AEWfDYLa5MEZsEsLY7ziH9osMYyVmUs6dwZa9PdqzKLj8P/ YsHQ== X-Received: by 10.140.92.226 with SMTP id b89mr46qge.33.1412135226811; Tue, 30 Sep 2014 20:47:06 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.140.89.101 with SMTP id u92ls307967qgd.79.gmail; Tue, 30 Sep 2014 20:47:06 -0700 (PDT) X-Received: by 10.224.172.65 with SMTP id k1mr40582552qaz.8.1412135226591; Tue, 30 Sep 2014 20:47:06 -0700 (PDT) Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [2607:f8b0:400d:c01::233]) by gmr-mx.google.com with ESMTPS id z1si1618443qci.3.2014.09.30.20.47.06 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Sep 2014 20:47:06 -0700 (PDT) Received-SPF: pass (google.com: domain of alexkoz@gmail.com designates 2607:f8b0:400d:c01::233 as permitted sender) client-ip=2607:f8b0:400d:c01::233; Received: by mail-qc0-f179.google.com with SMTP id x3so6102qcv.38 for ; Tue, 30 Sep 2014 20:47:06 -0700 (PDT) X-Received: by 10.140.41.103 with SMTP id y94mr16222806qgy.66.1412135226480; Tue, 30 Sep 2014 20:47:06 -0700 (PDT) Received: from [192.168.1.137] (fl-67-233-176-147.dhcp.embarqhsd.net. [67.233.176.147]) by mx.google.com with ESMTPSA id a41sm9971403qgf.5.2014.09.30.20.47.05 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 30 Sep 2014 20:47:05 -0700 (PDT) Date: Tue, 30 Sep 2014 23:46:57 -0400 (EDT) From: Alexander Kozhevnikov To: lojban@googlegroups.com Subject: Re: [lojban] Re: Speaker specificity: {.i da'i na vajni} In-Reply-To: <34b2a9f0-7ccb-4135-8795-7038cc996b42@googlegroups.com> Message-ID: References: <34b2a9f0-7ccb-4135-8795-7038cc996b42@googlegroups.com> User-Agent: Alpine 2.00 (LN8 1167 2008-08-23) MIME-Version: 1.0 X-Original-Sender: alexkoz@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of alexkoz@gmail.com designates 2607:f8b0:400d:c01::233 as permitted sender) smtp.mail=alexkoz@gmail.com; dkim=pass header.i=@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-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - I just wanted to quickly butt in and voice disagreement with this example: On Tue, 30 Sep 2014, Dustin Lacewell wrote: > I'm putting this here because I was asked to do so (probably for > completeness in discourse) > The example I habitually provide is, imagine some men are hanging out by a > water-cooler and some women walking past hear them making sexist remarks. > One women isn't going to confuse the other by saying something like "Those > dogs are disgusting". Does the listener really require such a > front-and-center indication of non-veridicality? As far as I'm concerned > the answer is blaring "no". I think the answer is a clear 'yes' if you are going to effectively communicate with speakers who are not familiar to your culture's metaphors, whether that be primitive AI, hypothetical aliens, or just people from a culture a few countries away where "dogs" is not a metaphor for intellectually-primitive-human-males. I think overall, having an efficient way to say what you really mean is a good thing, and in this case, that means having an ability to specify in a concise manner that something is or isn't metaphorical. Having that means the more literal-minded, or those who struggle with metaphorical speech, such as many autistic individuals for example, can be readily cued in to what you are implying. It means children (and more generally though less commonly mentally mature people as well) will be less likely to pick up mis-conceptions when delving into a new topic - because sure comparing people to animals is conceptually a fairly widespread metaphor in its various permutations - but when you get into less typical/casual matters it's no longer that easy. The inability to distinguish between the literal and metaphorical quickly will also manifest when you have a situation with both literal and metaphorical instances of the thing involved. The above example becomes insta-ambiguous if you also add in a couple of actual dogs doing something disgusting, or appearing disgusting. Of course in your example that doesn't strike me as a likely problem, but I think it's easy enough to run into cases like that in practice. I think we also overlook another value of the ability to be explicitly metaphorical: it enables one to readily introduce new metaphors which otherwise would require more load on the other parties in the conversation to figure out. This is a generalization of my first point about speakers who don't know the metaphor being deployed - except instead of limiting our consideration to metaphors regularly used in one culture being misunderstood by others, consider how much easier it is to throw a truly novel metaphor into a conversation - trying this in English has often generated uncomprehending looks when I've tried it, because I guess some people just aren't good at recognizing metaphors they aren't familiar with on the fly. I think we can have more creative and expressive uses of language if we can readily differentiate the literal meaning from non-literal. Personally, one of the points which currently draw me to Lojban is it's claimed ability to allow unambiguous communication efficiently. I want a one-or-two syllable way to draw the distinction between me being literal and not. (Though I don't have enough lojban knowledge yet to particularly care whether le/lo have anything to do with making this distinction.) Or maybe I missed the whole point of this "veridicality" discussion, in which case apologies for me wasting the time you all had to spend to read this. mu'o mi'e .aleksandr.kojevnikov. do'u -- 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 http://groups.google.com/group/lojban. For more options, visit https://groups.google.com/d/optout.