Received: from spooler by stryx.demon.co.uk (Mercury/32 v2.01); 23 Aug 98 21:15:47 +0000 Return-path: Received: from punt-11.mail.demon.net (194.217.242.34) by stryx.demon.co.uk (Mercury/32 v2.01); 23 Aug 98 21:15:40 +0000 Received: from punt-1.mail.demon.net by mailstore for ia@stryx.demon.co.uk id 903799107:10:08209:3; Sat, 22 Aug 98 15:18:27 GMT Received: from listserv.cuny.edu ([128.228.100.10]) by punt-1.mail.demon.net id aa1122841; 22 Aug 98 15:18 GMT Received: from listserv (listserv.cuny.edu) by listserv.cuny.edu (LSMTP for Windows NT v1.1b) with SMTP id <2.0004E986@listserv.cuny.edu>; Sat, 22 Aug 1998 11:19:04 -0400 Date: Sat, 22 Aug 1998 11:15:33 -0400 Reply-To: Logical Language Group Sender: Lojban list From: Logical Language Group Subject: Re: A First Words in Lojban X-To: jorge@INTERMEDIA.COM.AR X-cc: lojban@cuvmb.cc.columbia.edu To: Multiple recipients of list LOJBAN Message-ID: <903799090.1122841.0@listserv.cuny.edu> X-PMFLAGS: 33554560 7 1 Y01124.CNM Content-Length: 3419 Lines: 64 >cu'u la lojbab >>Actually, that is PRECISELY what I what people to do when they feel up to >it. > >I agree. I create lujvo casually all the time. That's how the language >works, lujvo are not just words that are created once >and for ever. Most will probably be used only the one time. > >>And I would not expect them to bother with place strcture determination in >>such an ad hoc coinage, but rather rely on what seems obvious for the >context. > >Here I disagree. For example, if someone used {le ro'inre'o} to refer to the >rock thrown by the catapult, no matter how obvious the context, I will still >think it's not a good choice of lujvo. The place structure of the components >is important and has to be taken into account. The x1 of ro'inre'o cannot be >the object thrown. I agree that it is not likely that such would be approved, i agree. HOWEVER, I think that it is essential that the Lojban community be a cooperative-communication one: if a novice coins a lujvo with such a place implied, it is important not to get too crtitical. We can be more careful when words seem to be used many times or to be candidates for dictionary usage. The critical thing is that novices writing "their first Lojban words", and indeed most people in their first year of working with the language, will have little likelihood of understanding, much less mastering, the esoteric elements of lujvo-place struucture conventions. But if such people get the idea that they need to master those conventions before they start making lujvo, then the language will end up being largely a gismu-only dictionary-bound conlang with limited lexicon (like most others). I think part of Esperanto's success hasbeen its easy incorporation of new words -albeit many seem to be borrowings. With Lojban, we want to avoid borrowings and encourage lujvo, and still have the rapid lexicon growth and language accessibility for novices that Esperanto has. This means that nonce lujvo have to beencouraged and adherence to conventions must be the lowest of priorities in teaching/crtitiquing new Lojbanists. (I note that JCB's list has had its first multi-posting thread in several months (i.e. a half dozen messages) and these postings are about this very type of thing - they wanted words for borscht and for Russian hats. rather than try to make lujvo for either,they seem to have chosen instead to borrow the words, and to do so into gismu space nonetheless. Now borscht might be a little harder as a lujvo, but there is no justification for "capka" for a Russian hat in either version of the language.) lojbab ---- lojbab lojbab@access.digex.net Bob LeChevalier, President, The Logical Language Group, Inc. 2904 Beau Lane, Fairfax VA 22031-1303 USA 703-385-0273 Artificial language Loglan/Lojban: ftp.access.digex.net /pub/access/lojbab or see Lojban WWW Server: href="http://xiron.pc.helsinki.fi/lojban/" Order _The Complete Lojban Language_ - see our Web pages or ask me.