Return-path: X-Spam-Personal-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on chain.digitalkingdom.org X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on chain.digitalkingdom.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 Envelope-to: rlpowell@digitalkingdom.org Delivery-date: Thu, 02 Jul 2009 08:42:29 -0700 Received: from chain.digitalkingdom.org ([64.81.66.169]) by chain.digitalkingdom.org with esmtp (Exim 4.69) (envelope-from ) id 1MMOQV-0003yR-BK; Thu, 02 Jul 2009 08:42:22 -0700 Received: with ECARTIS (v1.0.0; list jbovlaste); Thu, 02 Jul 2009 08:41:44 -0700 (PDT) Received: from nobody by chain.digitalkingdom.org with local (Exim 4.69) (envelope-from ) id 1MMOPw-0003yI-FO for jbovlaste-real@lojban.org; Thu, 02 Jul 2009 08:41:44 -0700 Received: from mail-pz0-f178.google.com ([209.85.222.178]) by chain.digitalkingdom.org with esmtp (Exim 4.69) (envelope-from ) id 1MMOPr-0003xS-Ru for jbovlaste@lojban.org; Thu, 02 Jul 2009 08:41:44 -0700 Received: by pzk8 with SMTP id 8so1746451pzk.28 for ; Thu, 02 Jul 2009 08:41:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=AMFzooEd5kId4bg5fDfHzEsniR+Jhv5SalJEoyE1WYk=; b=O4/pMZm3OYtzdV/sydVfJgaAHXvREH3mpc8AvOG2FEcv5h+p8qQMFEoFp763gRDQEf GWPGoMrCBGu20ay/SA3aEKrjgZEXbWsbc41cH2Nxed1rr8GAawcmXvfRoNU0WFCJimH2 gb2L0w+7JDlJ/IAUjv6DDm+IYJVdbOSMufk4E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=mCVGCvNq7i41FdRIHkv6sGa8bv+0JCNwgwkoX1GMhxZYUCm72PlLLvJMHCsgQ+Tj56 FcGzp4icjVTFXozCvWKR8xJoZ7z52tEw03fzUnQPWldlQ4itbIDcqBgVJZtpantpnAGS wvtJG+wh1VSZfl23U/afc9rnhS4Y1cI7UvS1A= MIME-Version: 1.0 Received: by 10.142.133.19 with SMTP id g19mr103675wfd.285.1246549290621; Thu, 02 Jul 2009 08:41:30 -0700 (PDT) In-Reply-To: References: Date: Thu, 2 Jul 2009 11:41:30 -0400 Message-ID: <96f789a60907020841l9bc04c0o14c4fab1c8571a2f@mail.gmail.com> Subject: [jbovlaste] Re: Newbie: How does voting work, esp. with natural words? From: Michael Turniansky To: jbovlaste@lojban.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by Ecartis X-ecartis-version: Ecartis v1.0.0 Sender: jbovlaste-bounce@lojban.org Errors-to: jbovlaste-bounce@lojban.org X-original-sender: mturniansky@gmail.com Precedence: bulk Reply-to: jbovlaste@lojban.org X-list: jbovlaste Content-Length: 2833 Lines: 55 On Thu, Jul 2, 2009 at 10:56 AM, Joshua Choi wrote: > To the Jbovlaste people, > > I'm a newbie at Jbovlaste—my name is Joshua Choi. Pleased to meet all of > you! > > I'm having trouble understanding the voting page at > http://jbovlaste.lojban.org//help/voting.html. I understand the purpose of > voting for certain definitions. But I'd first like to ask for clarification > on the phrases "You can pick one [definition] per language". Does that > really mean that I can vote for only one definition? If I want to say that I > think certain definitions are better in many words, can I only pick one? > What is the reasoning behind the limitation? This first part is easy. It doesn't mean that you can only vote for one word ever. It means that there are some entries in jbovlaste that have more than one definition in a given natural language (see http://jbovlaste.lojban.org//dict/mabla for example). You can only vote for one English gloss for mabla, not both. But you can cast your vote for however many other English glosses for other words as you want, just not more than one per natural language per lojban word. > I'm also having trouble understanding the way the voting system for natural > language words works. What is the relationship between "gloss keywords" and > "place keywords"? And, do new gloss words never show up in search queries > until other people vote for them? Gloss keywords are the {English} words for the entire concept ("go" or "come" for klama, for example). Place keywords are the {English} words for eaxh sumti place ("goer" for x1 of klama, "destination" for the x2 of klama, etc.) Why they only allow one per place, I can't say. I think that was an unwise decision, but there are probably programming reasons why that decision was reached) > Here's an example: I added a bunch of English gloss words to the dictionary. > For instance, "well" (default sense) formerly pointed to "jinto", which > refers to well in the sense of water source. "Well", however, has a lot of > other meanings, such as "in good health" or "satisfactorily done". So I > changed jinto's "well" to "well" in the sense of "source of water or other > fluid", and added glosses for "well" to kanro and xamgu. They show up at > "well"'s page too: http://jbovlaste.lojban.org/natlang/en/well. But when I > search for "well" in the query page, still only the original "well" shows > up. So why don't the other "well" senses show up? They don't show up when you do a "Search Preferred Words" search, I'm guessing, because it's the "preferred" word for well, having 100,000 votes rather than the 2 votes the other translations of "well" has. Apparently, the software doesn't take into account the "in the sense of" field as beig differeentiating when showing entries. --gejyspa