Received: from mail-ve0-f188.google.com ([209.85.128.188]:56330) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1W5H6c-0000sw-Eo for lojban-list-archive@lojban.org; Mon, 20 Jan 2014 07:49:52 -0800 Received: by mail-ve0-f188.google.com with SMTP id pa12sf567123veb.5 for ; Mon, 20 Jan 2014 07:49:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:subject:message-id:in-reply-to:references: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 :content-transfer-encoding; bh=5gHkSrCT1l8+tEu89wJwkapVMceYiTLUc9ZmffIzK8E=; b=FYmzrGqDImoO99PjCe2bpf+rAvMMpU12+8kdEzi+8d/zN2UeY63BGU3Zw8I+XvayoO 2cXiVDrkzpC72qWdQgodz5QXP4bADNCZAfVdqX3PNvVt1k3ah5jNd2Jj+lbUmEqGFMl7 zCZ7IHRu+NM5f3ni8SnK0Vq3J1F3QICQEiKlSqTX8Haw4UuN5B4CDocNUoxMkLsEVWIc SGucNUbbUTXTxUCUNeS5YIGbyRHtwFGcsUoGgKBFRV9aCPMh9c8sCWerdJY43h41gTVN uLboZ/7FzuoYiY35ZwKj40E0EVo29O8H2BSSC+SzlqBvBKWFFpXghil+yUZ5Tqmh5xyT /Nzg== X-Received: by 10.50.43.137 with SMTP id w9mr243556igl.14.1390232975951; Mon, 20 Jan 2014 07:49:35 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.50.111.80 with SMTP id ig16ls855295igb.39.canary; Mon, 20 Jan 2014 07:49:35 -0800 (PST) X-Received: by 10.50.49.3 with SMTP id q3mr5518290ign.7.1390232975465; Mon, 20 Jan 2014 07:49:35 -0800 (PST) Received: from omr-d09.mx.aol.com (omr-d09.mx.aol.com. [205.188.108.133]) by gmr-mx.google.com with ESMTPS id t4si353805qcl.3.2014.01.20.07.49.35 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 20 Jan 2014 07:49:35 -0800 (PST) Received-SPF: pass (google.com: domain of almikes@aol.com designates 205.188.108.133 as permitted sender) client-ip=205.188.108.133; Received: from mtaout-mbe02.mx.aol.com (mtaout-mbe02.mx.aol.com [172.26.254.174]) by omr-d09.mx.aol.com (Outbound Mail Relay) with ESMTP id 4C3E0701F5069 for ; Mon, 20 Jan 2014 10:49:35 -0500 (EST) Received: from localhost.localdomain (p549F800E.dip0.t-ipconnect.de [84.159.128.14]) by mtaout-mbe02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id 8546538000098 for ; Mon, 20 Jan 2014 10:49:34 -0500 (EST) Date: Mon, 20 Jan 2014 16:49:30 +0100 From: Wuzzy To: lojban@googlegroups.com Subject: Re: [lojban] New year's resolution: Finish the dictionary Message-ID: <20140120164930.29b296d7@aol.com> In-Reply-To: References: Mime-Version: 1.0 x-aol-global-disposition: G x-aol-sid: 3039ac1afeae52dd458e6fa1 X-AOL-IP: 84.159.128.14 X-Original-Sender: almikes@aol.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of almikes@aol.com designates 205.188.108.133 as permitted sender) smtp.mail=almikes@aol.com; dkim=pass header.i=@mx.aol.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: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Spam_score: 0.0 X-Spam_score_int: 0 X-Spam_bar: / Am Mon, 20 Jan 2014 15:42:44 +0400 schrieb Gleki Arxokuna : > I saw this message in #jbopre channel > "New year's resolution: Finish the dictionary" Well, I=E2=80=99ll do my very best! ;-) But the big questions are: When is the dictionary considered =E2=80=9Cfinished=E2=80=9D? Can it even ever be finished? I think the dictionary can never be possibly finished because language is an ongoing process, even for Lojban. You can express basically any kind of relation with the brivla and concepts come and go. The amount of possible lujvo=E2=80=94for example=E2=80=94is infinite since you can alw= ays attach *another* rafsi. Even in natural languages terms are invented every day. Especially when innovations in technology and science happen, new terms are neccessary to communicate. Since technology is not static, we can=E2=80=99t just make = a bunch of words and say we=E2=80=99re =E2=80=9Cfinished=E2=80=9D. Just wait = 10 years and you will see a lot of techincal innovations for which the =E2=80=9Cfinished vocabulary=E2=80=9D hasn=E2=80=99t the right terms for. So the maybe the stated goal of =E2=80=9Cfinishing=E2=80=9D the dictionary = is flawed or at least very vague. A more concrete goal would probably help more. But this is just opinion, feel free to add your own into this discussion. :-) I also want to stress yet again that I still wait for the selma'o zi'evla (Lojban words for selma'o) to be added to the dictionary: I have posted a CSV file containing definitions, notes and etymology earlier on the mailing list. Twice. Nobody cared. The words already have been discussed and I think the resulting zi'evla are ready to be added into jbovlaste. If the CSV file got somehow lost, I can re-upload it; just ask me. =20 > Is it a top secret or there is some info of the plan, ToDo list etc. > for us? It is interesting you ask this. I have recently developed a strategy for systematically creating new brivla =C3=A9n masse. But this was more lik= e personal ideas, still not very well developed. But I currently try to stick to this strategy when looking for new words to create. So: Yes, there is a =E2=80=9Cplan=E2=80=9D, and you may even consider it a =E2=80=9C= secret=E2=80=9D because it was just private ideas of me. So probably I should make it public then: =3D How to create a lot of brivla systematically =3D 1. lujvo 1.1. direct/=E2=80=9Cmechanical=E2=80=9D derivations from gismu 1.1.1. from alternating/broad definitions 1.1.2. from notes 1.1.3. eliminate annoying places with =E2=80=9Czi'o=E2=80=9D 1.2. semantic derivations from gismu 1.2.1. Think of any gismu=E2=80=93gismu combinations which would make sense 1.2.2. cmavo + gismu 1.2.3 standad lujvo conventions from lujpap.3 (gasnu, rinka, zanru, =E2=80= =A6) 1.2.4. =E2=80=9Cto'e=E2=80=9D and =E2=80=9Cna'e=E2=80=9D variants, when it = makes sense 1.3. fu'ivla/cmavo/lujvo/cmevla + fu'ivla 1.4. cmevla + fu'ivla/lujvo/(cmavo) 2. fu'ivla 2.1. stage 3 2.1.1. semantic derivations from gismu if lujvo is not possible 2.2. stage 4 2.2.1. short established, often used stage-3 fu'ivla (if possible) 2.2.X. other than that, try to prefer stage-3 before stage-4 2.3. any stage 2.3.1 =E2=80=9Croot=E2=80=9D fu'ivla: A new fu'ivla which is created as a = base for a broad range of new lujvo (see 1.3.) This is only a rough stragegy I have worked out for my personal work. But one main benefit of it is that minimizes bias from other languages (at least I hope so), especially the mechanical gismu derivations. Shoehorning words from other languages into lujvo does not always work well in Lojban. However, this strategy is still young and may change. To help you understand what I have just written down, here I give you some examples: 1.1.1. =E2=80=9Cpinji=E2=80=9D is defined as =E2=80=9Cpenis/cliotris=E2=80= =9D =E2=86=92 This leads to two new lujvo, one explicitly for =E2=80=9Cpenis=E2=80=9D (=E2=80=9Cnakpinji=E2=80= =9D) and =E2=80=9Ccliotris=E2=80=9D (=E2=80=9Cfetpinji=E2=80=9D) 1.1.2. The idea is whenever a certain (undefined) lujvo is mentioned in the notes, you have a new lujvo idea. One example is =E2=80=9Ctsapyvu'i=E2=80=9D, mentioned in =E2=80=9Cvrusi=E2=80=9D; it is no= w properly defined. :-) 1.1.3. =E2=80=9Czilkei=E2=80=9D: x1 is a toy. But still problematic for now= ; there is no real broadly used convention how to kill a certain place. This is because the =E2=80=9Czi'o=E2=80=9D behaves grammatically strange because it= acts like a sumti. There is no convention except for killing x1 (=E2=80=9Czi'o brode=E2= =80=9D), which would be =E2=80=9Czilbo'e=E2=80=9D. But what about killing other plac= es? Other gismu which certainly would deserve to get their places killed with =E2=80=9Czi'o=E2=80=9D include: =E2=80=9Clatna=E2=80=9D (x3, x4), =E2= =80=9Cbotpi=E2=80=9D (x4). 1.2.1. Most words I created on jbovlaste recently fall into this category. I looked at =E2=80=9Cbalre=E2=80=9D (blade) for example and came = up with =E2=80=9Cjincyba'e=E2=80=9D (=E2=80=9Cblade=E2=80=9D of scissors). I basica= lly go through the gismu list alphametically and look on gismu X and start to ask myself: =E2=80=9CWhich variants of this gismu are the most obvious to me?=E2=80=9D. 1.2.2. =E2=80=9Cte'o zei dugri=E2=80=9D: natural logarithm (literally e-typ= e of logarithm=E2=80=9D :-)). =E2=80=9Crarna dugri=E2=80=9D sounds too artificia= l to me. 1.2.3. =E2=80=9Cfazgau=E2=80=9D: annoy (non-agentative), =E2=80=9Cfazgau=E2= =80=9D: annoy (agentative) 1.2.4. =E2=80=9Ctaske=E2=80=9D (=E2=80=9Cthirsty=E2=80=9D) lead me to =E2= =80=9Ctoltaske=E2=80=9D (=E2=80=9Cquenched=E2=80=9D) and =E2=80=9Cnortaske=E2=80=9D (roughly =E2=80=9Cneither thirsty nor quenched= =E2=80=9D). Similar for =E2=80=9Cxagji=E2=80=9D. 1.3. =E2=80=9Cxy. zei kantu=E2=80=9D: X-ray (suggested in CLL, no entry i= n jbovlaste yet), but such words would be probably rare 1.4. This is still hypothetical, could be used for concepts which are =E2=80=9Cnamed=E2=80=9D after a person in other languages. One possibility = would be =E2=80=9CTuring machine=E2=80=9D. If we think of the hypothetized lujvo =E2= =80=9Csucyskami=E2=80=9D as =E2=80=9Cabstract machine=E2=80=9D, then =E2=80=9CTuring machine=E2=80=9D c= ould be =E2=80=9Cturing. zei sucyskami=E2=80=9D. All of this is hypothetical. Note that when one wants t= o combine a person name with a /gismu/, one could consider creating a stage-3 fu'ivla insted. Example: =E2=80=9CGraham=E2=80=99s number=E2=80=9D could be lojbanized as =E2=80=9Cgry'ym zei namcu=E2=80=9D or =E2=80=9Cnamcr= gra'ama=E2=80=9D (which destroys the original name a bit). 2.1.1. basically most of flora and fauna =E2=80=A6 Need I say more? Other people are much more skilled in this area than I am. 2.2.1. Hypothetized example: =E2=80=9Cbrodrgrolisi=E2=80=9D =E2=86=92 =E2= =80=9Cgrolisi=E2=80=9D; same definition as the original. I have never seen this in practice yet. :-( Strange, as this strategy is outlined in the CLL. Most people start right away with a stage-4 fu'ivla, even if it=E2=80=99s about a uncommon concept. 2.3.1. Very hypothetical; I could imagine this becoming useful for specialist subjects which have many words sharing a single concept. I hope you will now understand my new strategy. You can see it as a =E2=80=9CToDo list=E2=80=9D if you wish to. ;-) Now back to the New Year=E2=80=99s resolution. Now that I have presented my rough brivla creation stragety, then I could state some clearer goal: Define all lujvo which would result from 1.1.1. and 1.1.2. The lujvo which would result from this would make a) more vocabulary (obviously) and b) probably a solid base for even more complex concepts. --=20 Wuzzy XMPP: Wuzzy2@jabber.ccc.de E-Mail: wuzzy2@mail.ru --=20 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 e= mail 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/groups/opt_out.