I combine two fields in one using "Rewrite the output of this field" feature in the fields list.

Here's rewrite:
[name_i18n]
[description_i18n]

where
[description_i18n] == Taxonomy term: Term description (translated)
[name_i18n] == Taxonomy term: Name (translated)

Translated term description is displayed in original language, not in translated language.

Taxonomy translation mode is set to Localize.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

miro_dietiker’s picture

Status: Active » Closed (duplicate)

duplicate of
#346028: Translate taxonomy term names in Views

term translation generally needs work ... no further reports. Will you work on it or support work?

skolesnyk’s picture

Miro, initially I thought the problem was with Internalization Taxonomy, because otherwise why would term name was displayed in correct language while its description only in original.

I'll look at the issue that you suggested, but I'm not up to the skill level to work on it.

sunfire-design’s picture

Status: Closed (duplicate) » Needs review
FileSize
570 bytes

Problem should be solved with following patch

romansta’s picture

Patch works for me.

jdanthinne’s picture

Status: Needs review » Reviewed & tested by the community

Working for me too.

wzoom’s picture

Patch works. Please push it to the project git. Thank you.

sahuni’s picture

OK for me too.

webflo’s picture

Status: Reviewed & tested by the community » Fixed

Commit 2e1a188 on 7.x-3.x. Thanks!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

doublejosh’s picture

Term description (translated) is still just in source language when shown as a field.

doublejosh’s picture

Also rendered term entity should be available as translated.

knalstaaf’s picture

Issue summary: View changes

Still breaks when there are no nodes assigned to it?

Edit: there was an unnecessary filter criterion (content type) obstructing the results. Solved.