Return-Path: X-Sender: lojban-out@lojban.org X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_2_3_0); 7 Dec 2002 00:48:04 -0000 Received: (qmail 6876 invoked from network); 7 Dec 2002 00:48:04 -0000 Received: from unknown (66.218.66.217) by m15.grp.scd.yahoo.com with QMQP; 7 Dec 2002 00:48:04 -0000 Received: from unknown (HELO digitalkingdom.org) (204.152.186.175) by mta2.grp.scd.yahoo.com with SMTP; 7 Dec 2002 00:48:04 -0000 Received: from lojban-out by digitalkingdom.org with local (Exim 4.05) id 18KT8V-0005Gg-00 for lojban@yahoogroups.com; Fri, 06 Dec 2002 16:48:03 -0800 Received: from digitalkingdom.org ([204.152.186.175] helo=chain) by digitalkingdom.org with esmtp (Exim 4.05) id 18KT8N-0005G1-00; Fri, 06 Dec 2002 16:47:55 -0800 Received: with ECARTIS (v1.0.0; list lojban-list); Fri, 06 Dec 2002 16:47:54 -0800 (PST) Received: from lmsmtp03.st1.spray.net ([212.78.202.113]) by digitalkingdom.org with esmtp (Exim 4.05) id 18KT8F-0005EQ-00 for lojban-list@lojban.org; Fri, 06 Dec 2002 16:47:47 -0800 Received: from oemcomputer (host81-7-63-172.surfport24.v21.co.uk [81.7.63.172]) by lmsmtp03.st1.spray.net (Postfix) with ESMTP id D82873D10E for ; Sat, 7 Dec 2002 01:47:14 +0100 (MET) To: Subject: [lojban] Re: cmegadri valfendi preti Date: Sat, 7 Dec 2002 00:49:25 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <003201c29d2c$90a68830$abc70950@tanj> X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal X-archive-position: 3177 X-ecartis-version: Ecartis v1.0.0 Sender: lojban-list-bounce@lojban.org Errors-to: lojban-list-bounce@lojban.org X-original-sender: a.rosta@lycos.co.uk Precedence: bulk X-list: lojban-list From: "And Rosta" Reply-To: a.rosta@lycos.co.uk X-Yahoo-Group-Post: member; u=122260811 X-Yahoo-Profile: andjamin X-Yahoo-Message-Num: 17655 Content-Length: 3473 Lines: 72 Lionel: > And Rosta: > > Nora to pier: > > > I realize > > > you are trying to enlarge the area of acceptable names, but (aside from > > > the fact that I support the existing definition as baseline) I think you > > > are > > > doing the LISTENERS a disservice if you wish to have such things as > > > {muSTElaVIson} as a name. The name-maker can take his/her time and > > > analyze > > > what he/she has built. The listener, however, may well be hearing it > > > for the first time (and therefore cannot just pull it out as a known > > > glob). And, the speech stream gives very little time for the listener > > > to analyze new things; if she/he takes too long, the rest of the > > > sentence is gone > > I opine that even the baseline rule is too difficult to apply on > > the fly (though your practical experience as a speaker may prove > > me wrong -- are you speaking from experience or from principle), and > > the same goes for the self-segmentation in general. (Self-segmentation > > is good because it is crucial to unambiguity, but the particular > > algorithm is not sufficient to be of help to real-time comprehension.) > > Hence the benefit to the namer (or namee) weighs more, and maximizing > > the available space for the different morphological classes outweighs > > the negative impact of a slight increase in complexity of an already > > complicated algorithm > > I disagree: you have to consider the job of the listener in a global > perspective, that is from the parsing in words to the semantic > interpretation > IMO Lojban syntax and in a far greater extend semantic are complicated > enough (or you may say just uncommon enough) that to add complexity > in the word parsing may make the language much more difficult to use > in real time, and in much greater proportion that the amount of added > complexity, should the uttered sentences become long or convoluted > enough. (like my last one I am sorry to say :-) I'm not sure that you understood the point I was making. I was claiming that the morphological rules are ALREADY too complex to be used in real time. It is therefore irrelevant that making the rules even more complex will make life even harder for the listener struggling to parse in real time. I think the rules could not be simplified to the point where they could be used in realtime, unless the entire morphology was discarded and redesigned from scratch. As you know, some natural languages do have phonological clues to word-boundaries, but on the whole disambiguation is accomplished pragmatically. So in practise, for actual comprehension, the segmentation algorithm is not important. > In other, I would like the word parsing to be trivial enough so that > I'll have more time to devote to the syntaxic and semantic > interpretation of is what being said As things stand, the word parsing is so complicated that time devoted to it is devoted in vain. > Actually I do think we should strive to simplify the word parsing algorithm, > even if that means to restrain the available space of the morphology > classes. And this not really a problem, as it touches mainly cmene, > the restrictions on the format of cmavo and brivla being already strong > enough to be humanly parsable in real time Do you think so? Personally, I don't think I am capable of parsing the phonological string without the aid of pragmatics (i.e. knowing in advance what it is that you are likely to be saying). --And.