You're likely going to have to try it and see what works. But here's some suggestions:
If the content is merged inseparably into one field, maybe you could index that field twice, as text_en and text_gr using copyField. You could then have a different analyser for each, and see what results you get when you do your search against both fields. If your code is separable, you could have text_en and text_gr, each with their own language specific analyser chains, and index your content into the field relevant for that language. HTH Upayavira On Thu, 17 Mar 2011 18:18 -0700, "abiratsis" <abirat...@gmail.com> wrote: > Hello everyone, > > I have a index that contains text (several fileds) that can be in English > or > in Greek. I have found the corresponding filters > > solr.GreekLowerCaseFilterFactory > solr.GreekStemFilterFactory > > for the greek language along with the special type text_greek included to > the default schema.xml file, although I need to know if I can use them > with > the existing filters for a text field (embed them to the existing > configuration for english). > > So my 1st question is if I can simply add these two filters to the > existing > field types or an extra configuration needed? > > And the 2nd question is about how to handle the greek > synonyms-stopwords... > should I simply add onether solr.SynonymFilterFactory filter to the > existing > configuration? Should I merge both files (english-greek) together? > > Basicaly I don't know what the best approach is for handling a > multilingual > case like mine e.g:should I create a seperate index for each language? > > Any suggestions appreciated... > > Thanx, > Alex > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Greek-and-English-text-into-the-same-field-tp2696186p2696186.html > Sent from the Solr - User mailing list archive at Nabble.com. > --- Enterprise Search Consultant at Sourcesense UK, Making Sense of Open Source
