Hours??? In my case it has been days!!! And I'm desperate (again!)
If Drupal is already counter intuitive by itself in general and even more for translations, taxonomy always has been a hundred times worse.
However, I did achieve a certain (not full) level of taxonomy translation through field (or entity) translation doing something like:
for the vocabulary ("Special") I went to: "Localize" under admin/structure/taxonomy/special/edit
Save&Translate -> NL:"Speciaal", IT:"Speciale", ES:"Especial"
for the term ("To be developed") I went to: nl/taxonomy/term/85/edit/nl or was it taxonomy/term/85/translate?? (this for each language).
On both pages it says I have this URL alias for each language, but when I use that path (eg /nl/speciaal/te-ontwikkelen) I get a "Page not found" error.
Same goes for /it/speciale/da-sviluppare, /es/especial/por-desarrollar
Only Generic (Drupal's "Default") works: special/to-be-developed
Also the translated Terms of "to-be-developed" do not appear as options in the translated version of the "Special" Vocabulary when editing content.
HOW does Taxonomy get to understand that both Vocabulary and Term already exist, have been translated and that these paths should work????
- also did translation under admin/config/regional/translate/edit/9709?destination=admin/config/regional/translate/translate
What should be the next step should to get also the other languages to work (without creating additional term IDs)?
Additionally my hope was to have Taxonomy terms syncronized EVEN with entity translation (new translation of content -> tax term already selected) as is possible with menu items to have just one instance in the list.
Is this actually possible?
Also I have not been able to find the "language is in" option for the "Special" vocabulary in Views: admin/structure/views/view/special
How can I get that?
And last but not least: path is not translated either they all go to /lang/special even if "Special" already has been translated to the other languages in all possible places (although you never know)
BTW one should definitely should NOT FORGET to also activate the field-translation options for Taxonomy (Vocabulary and/or terms) in several other places, before Drupal or Taxonomy even understand you really MEAN to use entity (or field?) translation all over the site (not just in only one expceptional place) and the above can even occur. Unfortunately after days of going through the impossible Drupal-Taxonomy-FieldTranslations labyrinth, I do not remember all the steps, nor the order I have taken, nor which of these steps were actually valid.
Anyway several of these places, randomly (don't know if all) are:
- to keep up common sense, indeed also in the Title module: admin/config/content/title
- in the content type: admin/structure/types/manage/[content-type]/fields/field_category
- of course several additional things under the translation interface admin/config/regional/translate/translate
not forgetting string refreshment admin/config/regional/translate/i18n_string
- and I don't remember if somewhere else in Drupal's translation labyrinth (specifically having to activate entity (or field?) translations for taxonomy or vocabulary or terms...) Maybe some module configuration or special permissions...
Example at: http://europinion.is/special/to-be-developed (if it doesn't break of course) you can see:
1 - the Vocabulary menu item is translated, however linking to non translated path
2 - Term also appears, however linking to a path that gives error
3 - vocabulary/term reference appears translated in the content with "page not found" path again