Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Message-ID: <4562724D.5010003@teamware.com>
Date: Tue, 21 Nov 2006 14:28:13 +1100
From: Antony Bowesman <adb@teamware.com>
Organization: Teamware Group
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: java-user@lucene.apache.org
Subject: =?ISO-8859-1?Q?Re=3A_Q=3A_Wildcard_searching_with_germ?=
 =?ISO-8859-1?Q?an_umlauts_=28=E4=2C_=F6=2C_=DF=2C_=2E=2E=2E=29?=
References: <4561A39E.9060405@joanneum.at>
In-Reply-To: <4561A39E.9060405@joanneum.at>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Stephan Spat wrote:
> Hello again!
> 
> It replaces german umlauts, e.g. � <=> a, � <=> u, ... . So no umlauts 
> are in the index. For searching I use the same Analyzer. When I do a 
> simple search for a word with umlauts there is no problem. But if I use 
> addidionally wildcards I suppose the word is not analyzed and so I word 
> with umlauts and wildcards is not found in the index?!! (for example: 
> gr�*). Is this assumption correct?

I came across this class this morning:

AnalyzingQueryParser - Overrides Lucene's default QueryParser so that Fuzzy-, 
Prefix-, Range-, and WildcardQuerys are also passed through the given analyzer, 
but ? and * don't get removed from the search terms.

Read the warning re German though.

Antony


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