You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Daniel Naber <lu...@danielnaber.de> on 2005/08/05 20:54:50 UTC
ISOLatin1AccentFilter + KeywordAnalyzer to core?
Hi,
shouldn't only those analyzers be in contrib that are language specific?
ISOLatin1AccentFilter and KeywordAnalyzer are useful for all/many
languages, so I'd suggest to move them to core. Opinions?
Regards
Daniel
--
http://www.danielnaber.de
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
Re: ISOLatin1AccentFilter + KeywordAnalyzer to core?
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
On Aug 5, 2005, at 2:54 PM, Daniel Naber wrote:
> shouldn't only those analyzers be in contrib that are language
> specific?
I don't see this as a necessary distinction. It seems fine to allow
all sorts of various analyzers and filters/tokenizers to aggregate in
that contrib area, for pieces that don't belong in the core. It
really isn't necessary for any of the concrete analyzers/filters/
tokenizers to live in Lucene's core.
> ISOLatin1AccentFilter and KeywordAnalyzer are useful for all/many
> languages, so I'd suggest to move them to core. Opinions?
It really doesn't matter to me one way or another: +0. No objections
whatsoever other than Lucene's JAR increasing in size.
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org