On Mon, May 11, 2009 at 2:46 PM, Michael Ludwig <m...@as-guides.com> wrote:
> Could you give an example of how the spellcheck.q parameter can be > brought into play to (take non-ASCII characters into account, so > that "Käse" isn't mishandled) given the following example: > You will need to set the correct tokenizer and filters for your field which can handle your language correctly. Look at the GermanAnalyzer in Lucene contrib-analysis. It uses StandardTokenizer, StandardFilter, LowerCaseFilter, StopFilter, GermanStemFilter with a custom stopword list. Use the analysis.jsp on the admin page to see how queries on that field type are tokenizer. Tweak until it works as desired. Once that is setup, you need to send all the spell check queries through the spellcheck.q parameter. The query-time analyzer for that field will be used by spellchecker to analyze the query. -- Regards, Shalin Shekhar Mangar.
