Le 27 oct. 2012 à 11:43, Tom a écrit : > Aha! Exactly the problem! And only because the user-agent is one language, > doesn't mean all search terms will be! > For example, someone might type in the name of an English event (such as > Halloween) first, and then type in the name of their home town second. See > if there are any matches of how this event is celebrated there. Very likely > that the home town will be in the native language, even if the user-agent > or the first search term isn't.
Tom, the Accept-Language header is far richer than a single language. Using this really powers you up quite much into expanding into a useful set of available languages. Also, you could use the whitespace tokenizer as a simple analyzer for an "exact" field. paul
