From lojbab@lojban.org Wed Feb 05 09:18:04 2003 Return-Path: X-Sender: lojbab@lojban.org X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_2_3_4); 5 Feb 2003 17:18:03 -0000 Received: (qmail 55481 invoked from network); 5 Feb 2003 17:17:51 -0000 Received: from unknown (66.218.66.216) by m8.grp.scd.yahoo.com with QMQP; 5 Feb 2003 17:17:51 -0000 Received: from unknown (HELO lakemtao01.cox.net) (68.1.17.244) by mta1.grp.scd.yahoo.com with SMTP; 5 Feb 2003 17:17:51 -0000 Received: from lojban.lojban.org ([68.100.206.153]) by lakemtao01.cox.net (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with ESMTP id <20030205171750.SQWE16369.lakemtao01.cox.net@lojban.lojban.org> for ; Wed, 5 Feb 2003 12:17:50 -0500 Message-Id: <5.2.0.9.0.20030205121640.00abc6d0@pop.east.cox.net> X-Sender: rlechevalier@pop.east.cox.net X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Wed, 05 Feb 2003 12:18:18 -0500 To: lojban@yahoogroups.com Subject: Re: [lojban] Re: Lexing text with {fa'o} and {zoi} in it In-Reply-To: <200302042126.05978.phma@webjockey.net> References: <5.2.0.9.0.20030204153751.031fcec0@pop.east.cox.net> <5.2.0.9.0.20030203221325.00abe690@pop.east.cox.net> <5.2.0.9.0.20030204153751.031fcec0@pop.east.cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed From: Robert LeChevalier X-Yahoo-Group-Post: member; u=1120595 X-Yahoo-Profile: lojbab At 09:26 PM 2/4/03 -0500, Pierre Abbat wrote: >On Tuesday 04 February 2003 15:48, Robert LeChevalier wrote: > > At 06:48 AM 2/4/03 -0500, Pierre wrote: > > >How would you lex the following?: > > > > My best guess, and I'm not using any algorithm per se. > > > > >/la xidEkel. rIrxe fa'o tIgri se li ni stIka lI te/ > > > > # and abort processing at this point. > >valfendi currently outputs what you say (plus type-of-word annotations). >If it >had fa'o-detection, it would lex it as /la xidEkel rIrxe fa'o tIgri >selinistIkalIte/ with everything from /tIgri/ on resolved as foreign text. >But the words after /fa'o/ are in fact /tIgris elinistI kalIte/, and if there >were a Greek parser which saw an instruction to call the Lojban parser and >then resume when the Lojban was finished, it would lose those three words, >since the Lojban lexer cannot detect {fa'o} until it has read the end of the >piece. That is why I think that {fa'o} should must be always followed by a >pause: not because the algorithm can't lex it otherwise (it does, as well as >lex some other illegally-pronounced phrases such as /kybuladjAn/) but because >not putting a pause forces the algorithm to process text after the {fa'o} >before it can detect the {fa'o}. That seems to be a problem with Greek, which apparently does not require a pause after a non-Greek quote %^). Not our problem. lojbab -- lojbab lojbab@lojban.org Bob LeChevalier, President, The Logical Language Group, Inc. 2904 Beau Lane, Fairfax VA 22031-1303 USA 703-385-0273 Artificial language Loglan/Lojban: http://www.lojban.org