On Wed, Sep 12, 2012 at 3:44 AM, Toke Eskildsen
wrote:
>
> That would be a serious impediment. For some of our uncontrolled fields,
> the same word can be cased very differently: CD, cd, Cd. To be of the
> safe side, the client would have to ask for 3 times the wanted amount of
> facet informatio
On Wed, Sep 12, 2012 at 3:44 AM, Toke Eskildsen
wrote:
>
> I seem to be missing something here. The ICUCollationKeyFilter can be at
> the end of the analyzer chain, so why can't the input be normalized
> before entering this filter?
>
ICUCollationKeyFilter is gone.
--
lucidworks.com
-
On Tue, 2012-09-11 at 17:23 +0200, Robert Muir wrote:
> Just a concern where things could act a little funky:
>
> today for example, If I set strength=primary, then its going to fold
> Test and test to the same unique term,
> but under this scheme you would have Test and test as two terms.
>
> thi
Just a concern where things could act a little funky:
today for example, If I set strength=primary, then its going to fold
Test and test to the same unique term,
but under this scheme you would have Test and test as two terms.
this could be undesirable in the typical case that you just want
case-
On Tue, Sep 11, 2012 at 10:43 AM, Toke Eskildsen
wrote:
>
> ICU sort keys are always null (00) terminated and when two keys are
> compared, the comparison stops as soon as null is reached(?)
> http://userguide.icu-project.org/collation/architecture
>
> If we concatenate the keys with the original
