Re: case preserving for data but not for indexing

2008-08-07 Thread Ian Connor
Thanks for the feedback and corrections - the definition was wrong indeed. So, I have settled on this definition:

Re: case preserving for data but not for indexing

2008-08-07 Thread Norberto Meijome
On Wed, 6 Aug 2008 21:35:47 -0700 (PDT) Otis Gospodnetic <[EMAIL PROTECTED]> wrote: > > > > > 2 Tokenizers? i wondered about that too, but didn't have the time to test... B _ {Beto|Norberto|Numard} Meijome "Always listen to experts. They'll t

Re: case preserving for data but not for indexing

2008-08-06 Thread Norberto Meijome
On Wed, 6 Aug 2008 20:21:28 -0400 "Ian Connor" <[EMAIL PROTECTED]> wrote: > In order to preserve case for the data, but not for indexing, I have > created two fields. One is type Author that is defined as: > > sortMissingLast="true" omitNorms="true"> > >

Re: case preserving for data but not for indexing

2008-08-06 Thread Otis Gospodnetic
Maybe I'm missing something (it's late) but why not just index+store? The stored value will be the original and indexing can lowercase (as you set it), so it's case-insensitive. Also, does this actually work for you: 2 Tokenizers? Otis -- Sematext -- http://sem