What if there is no standard localization already? The case I'm specifically interested in is Ojibwe.
So should I really be researching how the JRE does localization instead of Solr? On Fri, Apr 22, 2011 at 2:01 PM, Robert Muir <rcm...@gmail.com> wrote: > On Fri, Apr 22, 2011 at 2:37 PM, Bently Preece <preec...@umn.edu> wrote: > > Thank you. This looks like the right direction. > > > > I see the docs say ICUCollationKeyFilterFactory is deprecated in favor of > > ICUCollationField. So ... I'd implement a subclass of ICUCollationField, > > and use that as the fieldtype in schema.xml. And this means - what? - > that > > I'd also implement a custom SortField to be returned by > > MyCollationField.getSortField(...), which would also require me to write > a > > custom FieldComparator? Am I on the right track? > > no, you don't have to write any code in either case: > > solr 3.1: > > <fieldType name="sort_haw" class="solr.TextField"> > <analyzer> > <tokenizer class="solr.KeywordTokenizerFactory"/> > <filter class="solr.ICUCollationKeyFilterFactory" locale="haw" > strength="secondary"/> > </analyzer> > </fieldType> > > solr 4.0: > > <fieldtype name="sort_haw" class="solr.ICUCollationField" locale="haw" > strength="secondary"/> > > then just copyField or whatever to get your data in there. >
