MT is not nearly good enough to allow approach 1 to work.
On Mon, Jan 20, 2014 at 9:25 AM, Erick Erickson <erickerick...@gmail.com> wrote: > It Depends (tm). Approach (2) will give you better, more specific > search results. (1) is simpler to implement and might be "good > enough"... > > > > On Mon, Jan 20, 2014 at 5:21 AM, David Philip > <davidphilipshe...@gmail.com> wrote: >> Hi, >> >> >> >> I have a query on Multi-Lingual Analyser. >> >> >> Which one of the below is the best approach? >> >> >> 1. 1. To develop a translator that translates a/any language to >> English and then use standard English analyzer to analyse – use translator, >> both at index time and while search time? >> >> 2. 2. To develop a language specific analyzer and use that by >> creating specific field only for that language? >> >> We have client data coming in different Languages: Kannada and Telegu and >> others later.This data is basically the text written by customer in that >> language. >> >> >> Requirement is to develop analyzers particular for these language. >> >> >> >> Thanks - David
