Received: from mail-ee0-f60.google.com ([74.125.83.60]:40528) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1UE0J3-0002Zy-DT; Fri, 08 Mar 2013 08:38:16 -0800 Received: by mail-ee0-f60.google.com with SMTP id b57sf706658eek.15 for ; Fri, 08 Mar 2013 08:37:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received:received-spf:date:from:to:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent: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; bh=pv6Le2mCc0zqg5TcvoQA+/aobvZP31fzEnYg9RgkMFE=; b=O3BpvZ9s1/fD2K/KSymNCJw/s8WkXqBzodyD8wOaLeWbAUtZMSN53G1+ptLH9ailVl rE1ukr4QRLTiLqQFwrLvPnkszf3GXAxv3DosHCj7xNV/tsGPoPRr3XwzvJQY2w6Pl//Q tJoIaTvEP7jr7v3xUUKqXrvSZCkPWq1JTGISS02obCFeIEicSQ1+3+B4Aj68MyBf/2ZV G/Wm9gni09sJcgJFh7Ml46tFjsKhPR4ua47Yk8aLgVjEOPpsnnsaUdGmdsXxgUTeg5cY d2Pczh3hxQpayYSthzgtozpDJstFpx+XTOivrVkZeTF1SnrfwKOZ9hcQg72lNLE45HtB shJA== X-Received: by 10.180.81.8 with SMTP id v8mr307014wix.11.1362760677773; Fri, 08 Mar 2013 08:37:57 -0800 (PST) X-BeenThere: lojban-beginners@googlegroups.com Received: by 10.180.8.70 with SMTP id p6ls215352wia.27.gmail; Fri, 08 Mar 2013 08:37:56 -0800 (PST) X-Received: by 10.14.220.131 with SMTP id o3mr3235557eep.3.1362760676849; Fri, 08 Mar 2013 08:37:56 -0800 (PST) Received: from dd17822.kasserver.com (dd17822.kasserver.com. [85.13.138.119]) by gmr-mx.google.com with ESMTPS id 47si1986451eeh.1.2013.03.08.08.37.56 (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 08 Mar 2013 08:37:56 -0800 (PST) Received-SPF: neutral (google.com: 85.13.138.119 is neither permitted nor denied by best guess record for domain of me@v4hn.de) client-ip=85.13.138.119; Received: from samsa (brln-4dbab461.pool.mediaWays.net [77.186.180.97]) by dd17822.kasserver.com (Postfix) with ESMTPA id F1183860AC8 for ; Fri, 8 Mar 2013 17:37:55 +0100 (CET) Date: Fri, 8 Mar 2013 17:37:55 +0100 From: v4hn To: lojban-beginners@googlegroups.com Subject: Re: [lojban-beginners] Frequency of {lo} and {le} Message-ID: <20130308163755.GC7011@samsa.fritz.box> References: <38fba144-850e-49a6-8d74-b954402e042d@googlegroups.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cQXOx3fnlpmgJsTP" Content-Disposition: inline In-Reply-To: <38fba144-850e-49a6-8d74-b954402e042d@googlegroups.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Original-Sender: me@v4hn.de X-Original-Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.13.138.119 is neither permitted nor denied by best guess record for domain of me@v4hn.de) smtp.mail=me@v4hn.de Reply-To: lojban-beginners@googlegroups.com Precedence: list Mailing-list: list lojban-beginners@googlegroups.com; contact lojban-beginners+owners@googlegroups.com List-ID: X-Google-Group-Id: 300742228892 List-Post: , List-Help: , List-Archive: Sender: lojban-beginners@googlegroups.com List-Subscribe: , List-Unsubscribe: , X-Spam-Score: -0.0 (/) X-Spam_score: -0.0 X-Spam_score_int: 0 X-Spam_bar: / Content-Length: 2488 --cQXOx3fnlpmgJsTP Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 07, 2013 at 03:04:42PM -0800, mudri wrote: > Please don't groan about what must be another xorlo question. I also keep asking/discussing and some others do as well, so probably nobody will do that. {.u'i} > I was reading http://www.lojban.org/tiki/How+to+use+xorlo again, and came= =20 > across these two sentences: =E2=80=9CIn my post-xorlo writings, lo outnum= bers le by=20 > about three to one (at a guess). I only use le when I'm talking about a= =20 > specific item.=E2=80=9D. To me, those seem at odds. The first bullet poin= t after=20 > this implies that the =E2=80=9Conly=E2=80=9D here is being used for effec= t, rather than=20 > logic, so I'm still stuck. Why? > I would assume that specific objects are talked > about as frequently, if not more so, than generic descriptions. At least = on > Twitter, where most of my writing practice happens, this seems to be the > case. Yes and I agree. If you find yourself using {le} more often, this is no problem at all. For me, I would assume, it's fifty-fifty. There are a rather large number of cases, where the choice between {le} and= {lo} depends on what you want to say _very accurately_ and therefore is a matter= of preferences... Some, like selpa'i, argue that {lo} does not _exclude_ specificity and can = therefore always be used in place of {le} (see his reply). In these cases it's left up to context whether or not something specific is meant. Others, like me, argue that it is important/useful to have a way of refering to a specific thing - and might not even describe it accurately - _in text_ rather than context. {lo} doesn't provide this. One problem about the usage of {le} is, I suppose, the internet. People often don't have enough common ground here to refer to specific things, which might be described inaccurately. If you use {le} and it's not clear what you're refering to, you're more than unhelpful and violating conversation principles, because people can't fix a proper reference. For social platforms and real-life talk this is probably less of a problem. v4hn --cQXOx3fnlpmgJsTP Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlE6E+MACgkQMBKLZs4+wjyBnACfTihBqxozPEzOeSs+ungpAWOp j7oAoJ/saBMMDpXmV+FLI86chEwzHTi/ =Gtpa -----END PGP SIGNATURE----- --cQXOx3fnlpmgJsTP--