Received: from mail-ee0-f55.google.com ([74.125.83.55]:42120) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XZCy4-00028o-Ou for lojban-list-archive@lojban.org; Tue, 30 Sep 2014 23:00:57 -0700 Received: by mail-ee0-f55.google.com with SMTP id b15sf11375eek.0 for ; Tue, 30 Sep 2014 23:00:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :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=HTwPlhyVRbSwPKO4c0zIELFBHaRbrlIVBkpQR1BdjIQ=; b=sUGGUTqCEVX6+7hVBJO3Y4LDDsfFitiGAI4+XWNUVKjBiBk++nBTJDVTOac/1TDSov MTQMzBcn9k51rMmJeRO3l5Il5AmEaGwisHwh19Cy970DASxjd+1jskDkWcdmS7S0O6uF PywnIxRZSbMqjZlANzDTvsfwU1Vjulv/B2IAM+pHhNY8E93plRtACZ54va0J7Jn0Fk58 TWOtWCXaWLI8E4mMwdBy1R8Uys9Ygl/mpKzTvYOX26lK2lqZDeM0x+y4OQCwwtx2pTeK oenncSOnzK9WrtoFjzlhW5iIXsg1RmriewWIsDdSx82AlpjRV7Z4DJq69BQ6vvaNYYDH 2Viw== X-Received: by 10.180.73.81 with SMTP id j17mr65381wiv.11.1412143245532; Tue, 30 Sep 2014 23:00:45 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.180.211.200 with SMTP id ne8ls187659wic.21.gmail; Tue, 30 Sep 2014 23:00:44 -0700 (PDT) X-Received: by 10.180.81.130 with SMTP id a2mr106769wiy.0.1412143244966; Tue, 30 Sep 2014 23:00:44 -0700 (PDT) Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com [2a00:1450:4010:c04::22f]) by gmr-mx.google.com with ESMTPS id fa3si1620300lbc.0.2014.09.30.23.00.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Sep 2014 23:00:44 -0700 (PDT) Received-SPF: pass (google.com: domain of dlacewell@gmail.com designates 2a00:1450:4010:c04::22f as permitted sender) client-ip=2a00:1450:4010:c04::22f; Received: by mail-lb0-f175.google.com with SMTP id u10so107782lbd.20 for ; Tue, 30 Sep 2014 23:00:44 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.170.165 with SMTP id an5mr40839188lbc.6.1412143244830; Tue, 30 Sep 2014 23:00:44 -0700 (PDT) Received: by 10.25.151.66 with HTTP; Tue, 30 Sep 2014 23:00:44 -0700 (PDT) In-Reply-To: <8ac756fd-401a-4778-ae50-e54e232b64d0@googlegroups.com> References: <34b2a9f0-7ccb-4135-8795-7038cc996b42@googlegroups.com> <8ac756fd-401a-4778-ae50-e54e232b64d0@googlegroups.com> Date: Tue, 30 Sep 2014 23:00:44 -0700 Message-ID: Subject: Re: [lojban] Re: Speaker specificity: {.i da'i na vajni} From: Dustin Lacewell To: lojban@googlegroups.com X-Original-Sender: DLacewell@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of dlacewell@gmail.com designates 2a00:1450:4010:c04::22f as permitted sender) smtp.mail=dlacewell@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: multipart/alternative; boundary=001a11c37a247aeded050456382c X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --001a11c37a247aeded050456382c Content-Type: text/plain; charset=UTF-8 It helps if you mention who you are replying to, trans On Tue, Sep 30, 2014 at 10:57 PM, TR NS wrote: > > > On Tuesday, September 30, 2014 11:47:07 PM UTC-4, Alexander Kozhevnikov > wrote: >> >> 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. >> > > I think there might be two different concepts of veridical being confused. > You are talking about speaking non-metaphorically. And I agree there > certainly should be a way to indicate a statement be taken "seriously" or > "literally". However, I'm not sure that is the same as the veridical nature > of {lo}, which is supposed to identify things as they "really are". If we > were to take that literally then it would (almost) always be a sort of lie > because it presupposes omniscience. It is ridiculous to think we know > things as they "really are". So when we use "lo" we can --indeed we are > still being metaphorical. Pink Unicorns are far from reality but we can > still talk about them with "lo xunblabi pavyseljirna". So it's not really > reality, but potentiality. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "lojban" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/lojban/m3RoHDxxc7E/unsubscribe. > To unsubscribe from this group and all its topics, 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. > -- 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. --001a11c37a247aeded050456382c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
It helps if you mention who you are replying to, trans

On Tue, Sep 30,= 2014 at 10:57 PM, TR NS <transfire@gmail.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">

<= br>On Tuesday, September 30, 2014 11:47:07 PM UTC-4, Alexander Kozhevnikov = wrote:
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 f= or
> 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 r= emarks.
> 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 effecti= vely=20
communicate with speakers who are not familiar to your culture's=20
metaphors, whether that be primitive AI, hypothetical aliens, or just= =20
people from a culture a few countries away where "dogs" is no= t a metaphor=20
for intellectually-primitive-human-males.

I think overall, having an efficient way to say what you really mean is= a=20
good thing, and in this case, that means having an ability to specify i= n=20
a concise manner that something is or isn't metaphorical.

Having that means the more literal-minded, or those who struggle with= =20
metaphorical speech, such as many autistic individuals for example, can= be=20
readily cued in to what you are implying. It means children (and more= =20
generally though less commonly mentally mature people as well) will be= =20
less likely to pick up mis-conceptions when delving into a new topic -= =20
because sure comparing people to animals is conceptually a fairly=20
widespread metaphor in its various permutations - but when you get into= =20
less typical/casual matters it's no longer that easy.

The inability to distinguish between the literal and metaphorical quick= ly=20
will also manifest when you have a situation with both literal and=20
metaphorical instances of the thing involved. The above example becomes= =20
insta-ambiguous if you also add in a couple of actual dogs doing someth= ing=20
disgusting, or appearing disgusting. Of course in your example that=20
doesn't strike me as a likely problem, but I think it's easy en= ough to run=20
into cases like that in practice.

I think we also overlook another value of the ability to be explicitly= =20
metaphorical: it enables one to readily introduce new metaphors which= =20
otherwise would require more load on the other parties in the conversat= ion=20
to figure out. This is a generalization of my first point about speaker= s=20
who don't know the metaphor being deployed - except instead of limi= ting=20
our consideration to metaphors regularly used in one culture being=20
misunderstood by others, consider how much easier it is to throw a trul= y=20
novel metaphor into a conversation - trying this in English has often= =20
generated uncomprehending looks when I've tried it, because I guess= some=20
people just aren't good at recognizing metaphors they aren't fa= miliar with=20
on the fly. I think we can have more creative and expressive uses of=20
language if we can readily differentiate the literal meaning from=20
non-literal.

Personally, one of the points which currently draw me to Lojban is it&#= 39;s=20
claimed ability to allow unambiguous communication efficiently. I=20
want a one-or-two syllable way to draw the distinction between me=20
being literal and not. (Though I don't have enough lojban knowledge= yet to=20
particularly care whether le/lo have anything to do with making this=20
distinction.)

Or maybe I missed the whole point of this "veridicality" disc= ussion, in=20
which case apologies for me wasting the time you all had to spend to re= ad=20
this.

I think there might be two= different concepts of veridical being confused. You are talking about spea= king non-metaphorically. And I agree there certainly should be a way to ind= icate a statement be taken "seriously" or "literally". = However, I'm not sure that is the same as the veridical nature of {lo},= which is supposed to identify things as they "really are". If we= were to take that literally then it would (almost) always be a sort of lie= because it presupposes omniscience. It is ridiculous to think we know thin= gs as they "really are". So when we use "lo" we can --i= ndeed we are still being metaphorical. Pink Unicorns are far from reality b= ut we can still talk about them with "lo xunblabi pavyseljirna". = So it's not really reality, but potentiality.

--
You received this message because you are subscribed to a topic in the Goog= le Groups "lojban" group.
To unsubscribe from this topic, visit https://groups.go= ogle.com/d/topic/lojban/m3RoHDxxc7E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to lojban+un= subscribe@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.

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsub= scribe@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 http= s://groups.google.com/d/optout.
--001a11c37a247aeded050456382c--