That's one of ways to make the analysis composition explicit. Another way is to make Analyzer interface to return two token streams: normalizedStream() and unnormalizedStream(). I won't argue which is better. BTW: great thanks for adding possibility of analyzing different fields with different token streams in 1.2, that was the real problem in 1.0.
Michal ----- Original Message ----- From: "Brian Goetz" <[EMAIL PROTECTED]> To: "Lucene Users List" <[EMAIL PROTECTED]> Sent: Friday, January 25, 2002 11:24 AM Subject: Re: Case Sensitivity - and more > > Ok, maybe I misled a point a bit. But Brian's proposal as I see it was to > > _group_ two tokenizers that differ in a single thing. > > I don't think that's what I was proposing... I was recognizing that > sometimes the analysis process is a composite one, and I was advocating > that the composition be made explicit since there are some cases where > only tokenization, but not normalization, is desired. > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
