What I'm saying is don't use char_filter, and use the token filters chain to achieve that
-- Itamar Syn-Hershko http://code972.com | @synhershko <https://twitter.com/synhershko> Freelance Developer & Consultant Author of RavenDB in Action <http://manning.com/synhershko/> On Sat, Nov 29, 2014 at 9:02 PM, Krešimir Slugan <[email protected]> wrote: > Hi Itamar, > > I don't think this solves my problem. I'm aware that you can preserve > original with ASCIIfolding but since char_filter is applied > before ASCIIfolding then there would not be any umlauts to fold :) If I > could apply char_filter on the end that would be ok, or preserve original > with char_filter. > > Best, > > Kresimir > > On Saturday, November 29, 2014 5:41:11 PM UTC+1, Itamar Syn-Hershko wrote: >> >> You may find the approach I give in the end of this talk helpful: >> https://skillsmatter.com/skillscasts/4968-approaches-to-multi-lingual- >> text-search-with-elasticsearch-and-lucene >> >> -- >> >> Itamar Syn-Hershko >> http://code972.com | @synhershko <https://twitter.com/synhershko> >> Freelance Developer & Consultant >> Author of RavenDB in Action <http://manning.com/synhershko/> >> >> On Tue, Nov 18, 2014 at 12:30 PM, Krešimir Slugan <[email protected]> >> wrote: >> >>> Hi, >>> >>> To handle German language in search I have to be able to provide same >>> results if user searches for e.g über, uber or ueber >>> >>> I would do this at the index time where I would have über in the data. But >>> if I use just asciifolding filter I lose information that this was work >>> with "umlaut" and I can't get ueber token. If I use char_fiter, it is >>> applied before analysis and I would not be able to get uber. >>> >>> Is it possible to preserve original with char filter or apply it after >>> the analysis? >>> >>> Cheers, >>> >>> Kresimir >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "elasticsearch" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit https://groups.google.com/d/ >>> msgid/elasticsearch/f18f94bc-58e0-4bbf-a445-b45ba4db11f3% >>> 40googlegroups.com >>> <https://groups.google.com/d/msgid/elasticsearch/f18f94bc-58e0-4bbf-a445-b45ba4db11f3%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/4d362cd4-21a4-486c-bf57-f2de5949f072%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/4d362cd4-21a4-486c-bf57-f2de5949f072%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZtC14VTg4FQcVv5iiyuuO_nWcR4sbDGScqw9Mj5gsRWPQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
