Received: from spooler by stryx.demon.co.uk (Mercury/32 v2.01); 1 Dec 98 22:24:30 +0000 Return-path: Received: from punt-11.mail.demon.net (194.217.242.34) by stryx.demon.co.uk (Mercury/32 v2.01); 1 Dec 98 22:24:20 +0000 Received: from punt-1.mail.demon.net by mailstore for ia@stryx.demon.co.uk id 912514814:10:15484:0; Tue, 01 Dec 98 12:20:14 GMT Received: from pop.onelist.com ([209.207.164.159]) by punt-1.mail.demon.net id aa1015220; 1 Dec 98 12:19 GMT Received: (qmail 3288 invoked by alias); 1 Dec 1998 12:24:48 -0000 Received: (qmail 3279 invoked from network); 1 Dec 1998 12:24:46 -0000 Received: from unknown (HELO mail.camelot.de) (195.30.224.10) by pop.onelist.com with SMTP; 1 Dec 1998 12:24:46 -0000 Received: from robin.camelot.de (uucp@robin.camelot.de [195.30.224.3]) by mail.camelot.de (8.8.8/8.8.8) with ESMTP id NAA03326 for ; Tue, 1 Dec 1998 13:18:20 +0100 (CET) (envelope-from oas.a2e.de!a2e.de!phm@camelot.de) Received: from oas.a2e.de (uucp@localhost) by robin.camelot.de (8.8.8/8.8.8) with UUCP id NAA03322 for onelist.com!lojban; Tue, 1 Dec 1998 13:18:20 +0100 (CET) (envelope-from oas.a2e.de!a2e.de!phm) Received: from wtao97.oas by wtao97 with smtp (Smail3.1.29.1 #3) id m0zkpfC-000RqAC; Tue, 1 Dec 98 14:16 CET Date: Tue, 1 Dec 1998 14:16:21 +0100 (CET) From: PILCH Hartmut X-Sender: phm@wtao97.oas To: lojban@onelist.com Message-ID: Mailing-List: list lojban@onelist.com; contact lojban-owner@onelist.com Delivered-To: mailing list lojban@onelist.com Precedence: bulk List-Unsubscribe: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [lojban] Re: UNL, Lojban and MLHT X-PMFLAGS: 34078848 7 1 Y040AA.CNM Content-Length: 1859 Lines: 44 From: PILCH Hartmut > >Could a Lojban parser output intelligible English some day? > > No doubt an approach similar to whjat you describe of converting parse to > Prolog to Lisp to English would be more effective than what Nora is > doing, but Nora's solution is easy (if she only had time to work on it) I would find time to work on a lojlisp2english program. Also, I suspect it's more easy to do than what Nora seems to be attempting, if only I have a Lisp representation of the parsing result available. > A good glosser is a useful learning tool. A good translator would also be > good. But the main thing needed to make either very useful is some kind > of AI based error correction - something that couild look at a bad parse and > figure out what was likely to be wrong (a missing "cu", two selbri in the > bridi, etc.) and perhaps even suggest the corrections. That again is a very difficult tenth step The first step is done (John Cowan's parser). I only need a commandline switch that will output the parsing result in Lisp (foo bar baz) notation. The second step is a lojlisp2english converter that will allow people to read existing correctly written lojban texts in [Logician's] English and, by comparing with the original and the lojlisp version, understand the original structure without having to look up every word. -- Hartmut Pilch http://www.a2e.de/phm/ ------------------------------------------------------------------------ To unsubscribe from this mailing list, or to change your subscription to digest, go to the ONElist web site, at http://www.onelist.com and select the User Center link from the menu bar on the left. ------------------------------------------------------------------------ To unsubscribe, send mail to lojban-unsubscribe@onelist.com