Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <5234403.post@talk.nabble.com>
References: <5234403.post@talk.nabble.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <1F4C0193-FDB1-467B-B3FB-AFD2E5D877AF@ehatchersolutions.com>
Content-Transfer-Encoding: 7bit
From: Erik Hatcher <erik@ehatchersolutions.com>
Subject: Re: TermQuery doesn't support non-english charecters
Date: Sun, 9 Jul 2006 06:56:01 -0400
To: java-user@lucene.apache.org


On Jul 8, 2006, at 3:54 PM, dan2000 wrote:
> When non-English word is used in TermQuery, it always returns null.  
> With
> other types query, I could pass in an language specific analyzer.  
> but with
> this TermQuery, I can't find anyway to specify the language.

What other types of queries are you referring to?   No built-in Query  
subclass uses an analyzer.  All terms handed to these Querys must  
"pre analyzed", such that they match how terms were indexed.  You can  
always run through an analyzer to build up queries, just like  
QueryParser does.  Look at AnalyzerDemo (or is it AnalysisDemo?) in  
the Lucene in Action codebase which does this, as well as the  
internals to QueryParser.

	Erik


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org