Return-path: X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on chain.digitalkingdom.org X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS, T_DKIM_INVALID,T_TO_NO_BRKTS_FREEMAIL autolearn=no version=3.3.0 X-Spam-Personal-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on chain.digitalkingdom.org Envelope-to: rlpowell@digitalkingdom.org Delivery-date: Fri, 30 Apr 2010 11:42:34 -0700 Received: from chain.digitalkingdom.org ([192.168.123.127]) by chain.digitalkingdom.org with esmtp (Exim 4.71) (envelope-from ) id 1O7v9s-0004Qx-27; Fri, 30 Apr 2010 11:42:03 -0700 Received: with ECARTIS (v1.0.0; list jbovlaste); Fri, 30 Apr 2010 11:41:17 -0700 (PDT) Received: from nobody by chain.digitalkingdom.org with local (Exim 4.71) (envelope-from ) id 1O7v9I-0004Qq-SX for jbovlaste-real@lojban.org; Fri, 30 Apr 2010 11:41:17 -0700 Received: from mail-vw0-f53.google.com ([209.85.212.53]) by chain.digitalkingdom.org with esmtp (Exim 4.71) (envelope-from ) id 1O7v9C-0004Pw-IY for jbovlaste@lojban.org; Fri, 30 Apr 2010 11:41:16 -0700 Received: by vws13 with SMTP id 13so146174vws.40 for ; Fri, 30 Apr 2010 11:41:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=AoxCr0iY1JwQAoOuaF++0bnRe3Y8KRdOyR8hZkO/o5U=; b=tbV8HiXkZpzCRxY9vJHFu4aER4W0UA8xHINlnvju8fktb3GWoxF4bQnVnu77/cb0rG Q6KUmPZSyM1sgMUCVuT05jzITdJxpv98rTgoxY0hyK+ruAIb5PxLYbRZDFY6d34Jz1Lt dU/eVTx8o2y1ZibFNCms/riJ045Bc9DRZVmf8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=GCW2v1QMXxTwM9ppEpsk4Zfk1UKL1jBommS6JR5UgFPfaogj26c+EndM/y+Ivo6gU7 uObDEDglY6GS5Dn+ZZYaIexthcKUqZM4FmZoGNC6CV2JT4iVJiigtpuDH7sg/YHmq5W+ YWGt3WARCPb08dnUeXYpldpzRNTmfSBaVWkM4= MIME-Version: 1.0 Received: by 10.220.122.220 with SMTP id m28mr8268370vcr.2.1272652864418; Fri, 30 Apr 2010 11:41:04 -0700 (PDT) Received: by 10.220.75.11 with HTTP; Fri, 30 Apr 2010 11:41:04 -0700 (PDT) Date: Fri, 30 Apr 2010 19:41:04 +0100 X-Google-Sender-Auth: 26f74fa1e244098c Message-ID: Subject: [jbovlaste] jbovlaste checklist From: tijlan To: jbovlaste@lojban.org Content-Type: multipart/alternative; boundary=001636ed677de7f2e10485789529 X-ecartis-version: Ecartis v1.0.0 Sender: jbovlaste-bounce@lojban.org Errors-to: jbovlaste-bounce@lojban.org X-original-sender: jbotijlan@gmail.com Precedence: bulk Reply-to: jbovlaste@lojban.org X-list: jbovlaste Content-Length: 4522 Lines: 85 --001636ed677de7f2e10485789529 Content-Type: text/plain; charset=UTF-8 (This is something I brought up before.) I have been more or less guiding my jbovlaste works with some word list suggesting which words are likely to be more demanded by speakers of the natlangs to which the valsi's definitions belong. The aim is to enrich jbovlaste entries in the order of practical importances and help it enhance in its answerability-to-general-inquiries faster. The list I've been using for Lojban-English entries is the General Service List (about 2000 words). I'm planning to check the Academic Word List as well in the future once I finish for GSL. But the process has been taking longer than I expected. And I was wondering if somebody could collaborate. Not necessarily doing the actual editing in jbovlaste, but even just going through the list and comb out words/concepts that already have an entry in jbovlaste. I created a page on a collaborative-text-editing website (similar to Google Wave but simpler and faster), which anybody can edit without the hassle of registering a new account and logging in: http://meetingwords.com/XKk5bOaYbd (It's even equipped with a chat functionality.) Feel free to come and erase the items you have confirmed exist in jbovlaste. (But please be wary of words with multiple general meanings. For instance, "reserve" can mean "to keep back" or "to make a reservation" and can be a gloss for different valsi.) Some words may be a gloss for a cmavo. I was suggested in the past that the jbovlaste editing should be focused on brivla rather than cmavo. So we can leave them for later, moving them to the section "for CMAVO" at the bottom of the page. We may also want to prioritise verbs over their noun counterparts (e.g. "interfere" over "interference"), since the latter can mostly be derived easily by adding a NU to the former. mu'o mi'e tijlan --001636ed677de7f2e10485789529 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable (This is something I brought up before.)

I have been more or less gu= iding my jbovlaste works with some word list suggesting which words are lik= ely to be more demanded by speakers of the natlangs to which the valsi'= s definitions belong. The aim is to enrich jbovlaste entries in the order o= f practical importances and help it enhance in its answerability-to-general= -inquiries faster. The list I've been using for Lojban-English entries = is the General Service List (about 2000 words). I'm planning to check t= he Academic Word List as well in the future once I finish for GSL. But the = process has been taking longer than I expected. And I was wondering if some= body could collaborate. Not necessarily doing the actual editing in jbovlas= te, but even just going through the list and comb out words/concepts that a= lready have an entry in jbovlaste. I created a page on a collaborative-text= -editing website (similar to Google Wave but simpler and faster), which any= body can edit without the hassle of registering a new account and logging i= n:

=C2=A0= http://meetingwords.com/XKk5bOaYbd

(It's even equipped with = a chat functionality.)

Feel free to come and erase the items you hav= e confirmed exist in jbovlaste. (But please be wary of words with multiple = general meanings. For instance, "reserve" can mean "to keep = back" or "to make a reservation" and can be a gloss for diff= erent valsi.)

Some words may be a gloss for a cmavo. I was suggested in the past that= the jbovlaste editing should be focused on brivla rather than cmavo. So we= can leave them for later, moving them to the section "for CMAVO"= at the bottom of the page. We may also want to prioritise verbs over their= noun counterparts (e.g. "interfere" over "interference"= ;), since the latter can mostly be derived easily by adding a NU to the for= mer.

mu'o mi'e tijlan
--001636ed677de7f2e10485789529--