Taxonomy terms are not translated when enabling taxonomy translations

We would need i18n integration, so you could start by looking at the code of the module look how it alters the taxonomy query...

The attached patch implements translation support via Entity Translation. The query has been rewritten to use EntityFieldQuery (for flexibility) and conditional joins have been added as query tags. It also implements an "autocomplete_deluxe" query tag for additional query alters.

Note: this patch also addresses the issue described in https://drupal.org/node/2048563

I confirm that the patch solves the problem.
Thank you gabidrg!

Re-rolling patch to work with drush.make builds

#4 works for me.
Tested on Recruiter Distro.
Thank you

It doesn't work at all. When introducing new terms with the widget, there's a mismatch on the 'language' column when looking on the 'taxonomy_term_data' and 'field_data_name_field'. I've changed the slightly the #4 patch to match the language value in both columns.

I created a field with widget Autocomplete delux module and this was set with translated taxonomy but it was not seeing translated. So I created a patch for this using I18N module. Now it is getting translated but it is little bit slow.

Thanks,
Neeraj

Neeraj, this issue is related to vocabularies with 'Entity translation' translation mode.. Your patch #10 is related to 'Localize' translation mode. Please open a new issue related to this last one.

I am facing same issue as well.

Hello, the patch #8 only work if the vocabulary is translatable and damage any other vocabulary if is not translatable. If you apply the patch and you have vocabularies not translatable this will duplicate any term every time you add it to a node.

This patch fix the problem with vocabularies without translation and have some cleanups

If somebody is having this problem on 2.0.2, here is a patch