Hello Govindarajan P.S.
I tested this in 2017 SR1 and it does work, but you have to be careful about how you set your termbase up. For example, I tested these three:
Note the language codes as these represent the following:
ta(IN) - Tamil (India)
en(US) - English (United States)
ta - Tamil
en - English
When you create your termbase you can specify the full language code with the variant, or just the main language code. You should not mix them, and I think this is what you did. If I use the first one which is default in my list and activated, I get this:
Now, I said you should not mix this and I always recommend people use fully qualified for all languages, or only the main languages. However, in this case ONLY using the fully qualified languages works. So you need to specify the specific flavour of Tamil when creating your termbase to match that of the Studio project and the specific flavour of English.
Try that and see if it helps.