I've been looking over the docs and FAQ (which is really good) to get a feel for Lucene and I've ran across a few minor typos (patch below). So far it looks really nice, I'll know more once I've finished reading and get a chance to play with it a bit. Steve Stock [EMAIL PROTECTED] PS: english doesn't do postfix well :-) diff -u -w -r1.7 chapter.search.faq --- faq/chapter.search.faq 2001/06/20 05:20:05 1.7 +++ faq/chapter.search.faq 2001/06/22 21:27:33 @@ -94,7 +94,7 @@ :: What is the syntax of queries parsed by the QueryParser class ? -(Note: the syntax of the query parser has been extended by Doug Cutting Brian Goetz and +(Note: the syntax of the query parser has been extended by Doug Cutting and Brian +Goetz to support prefix queries and boost factors respectivlty, at the time of writing this answer (June 2001), the new code has not been released yet.) <p> @@ -183,7 +183,7 @@ phrase query 'winding road' should match 'winding road' but not 'road winding' (with the exception of more relaxed slop factors as discussed below). <p> -Phrase queries are represented in Lucene's API by instances of the PharseQuery class. +Phrase queries are represented in Lucene's API by instances of the PhraseQuery class. These instances contain an ordered list of Term objects that represent the terms to match. For obvious reasons, all terms in a PhraseQuery must refer to the same field. <p> _______________________________________________ Lucene-dev mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/lucene-dev
