From b.gohla@gmx.de Mon Jun 17 12:48:59 2002 Return-Path: X-Sender: b.gohla@gmx.de X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_0_3_2); 17 Jun 2002 19:48:58 -0000 Received: (qmail 41684 invoked from network); 17 Jun 2002 19:48:57 -0000 Received: from unknown (66.218.66.217) by m9.grp.scd.yahoo.com with QMQP; 17 Jun 2002 19:48:57 -0000 Received: from unknown (HELO mail.gmx.net) (213.165.64.20) by mta2.grp.scd.yahoo.com with SMTP; 17 Jun 2002 19:48:57 -0000 Received: (qmail 6229 invoked by uid 0); 17 Jun 2002 19:48:55 -0000 Received: from b7a13.pppool.de (HELO linux) (213.7.122.19) by mail.gmx.net (mp005-rz3) with SMTP; 17 Jun 2002 19:48:55 -0000 Content-Type: text/plain; charset="utf-8" To: lojban@yahoogroups.com Subject: Re: [lojban] Automatic Lojban -> English translation? Date: Mon, 17 Jun 2002 20:52:26 +0200 X-Mailer: KMail [version 1.2] References: In-Reply-To: MIME-Version: 1.0 Message-Id: <02061720522600.01303@linux> Content-Transfer-Encoding: quoted-printable From: =?utf-8?q?Bj=C3=B6rn=20Gohla?= Reply-To: b.gohla@gmx.de X-Yahoo-Group-Post: member; u=36703491 X-Yahoo-Profile: badbirdde -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 17 June 2002 10:41, pmak0 wrote: > Since Lojban is supposed to be unambiguously parsible, would it be > theoretically possible to write a computer program that parses Lojban and > outputs readable English (or any other language) without loss of meaning? i do think so, i did once post about this in message=20 <01121721050200.01120@linux>. [...] - --=20 The Internet was invented as a highly dependable,=20 high-speed, distributed, secure, and powerful network=20 so that in the event of a nuclear crisis, military=20 officials would always have access to pornography. pub 1024D/834F4976 2001-01-07 Bjrn Gohla (Wissenschaftler, Weltbrger)=20 Key fingerprint =3D 9FF4 FEDA CCDF DA0E 14D5 8129 6C14 3C39 834F 4976 sub 1024g/29571FE2 2001-01-07 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9Di/vbBQ8OYNPSXYRAonOAJ92ZY3RZ0eJQ5mAjTj/vCG+fVSSiQCeLk7Y CRC7rgGhK+5Ejqmx69E537o=3D =3DVQJm -----END PGP SIGNATURE-----