Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Developers List" <lucene-dev@jakarta.apache.org>
Date: Tue, 11 Dec 2001 03:44:01 -0800
From: Brian Goetz <brian@quiotix.com>
To: Lucene Developers List <lucene-dev@jakarta.apache.org>
Subject: Re: searching words starting with accent characters using UTF-8
Message-ID: <20011211034401.A14573@lx.quiotix.com>
References: <4BC270C6AB8AD411AD0B00B0D0493DF0EE7D74@mail.grandcentral.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <4BC270C6AB8AD411AD0B00B0D0493DF0EE7D74@mail.grandcentral.com>;
 from DCutting@grandcentral.com on Mon, Dec 10, 2001 at 09:38:25PM -0800

> Thanks!  That would be great!

Be careful what you ask for, I foobared it up the last time... :)

> Yes, this is a lot of features, and a lot of syntax.  The query parser is
> already complicated.  Perhaps we should instead write a number of example
> query parsers that do different things, and encourage folks to write their
> own, with these as models.  Unfortunately, I'm not sure many folks would do
> that: instead they would ask why one parser doesn't have a feature that
> another does.  So I'm having a hard time seeing a non-kitchen-sink
> alternative.  Do you?

I don't really object to a kitchen sink approach, but I prefer to have
it done all at once rather than added incrementally. 

So far we have: 
 - Prefix (currently *)
 - Fuzzy ( currently ~)
 - Boost (currently ^nn)
 - AND, OR, NOT, &&, ||, !
 - Phrases ("foo bar")

We want to add: 
 - NEAR/phrase-with-slop


--
To unsubscribe, e-mail:   <mailto:lucene-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:lucene-dev-help@jakarta.apache.org>