1. Install Drupal 8.3.x and patch it with this patch: https://www.drupal.org/files/issues/drupal-2451657-288-join-untranslated... (Issue: https://www.drupal.org/project/drupal/issues/2451657 - this solves part of the untranslatable fields problem... but not the problem described in this issue)
2. Create at least 2 languages
3. Create translatable node type
4. Create taxonomy term reference filed for the created node type, but leave unchecked the checkbox "users may translate this field"
5. Create some terms and translate them.
6. Create a content for the node type - choose some terms
7. Create a translation for the node type - the terms should be the same, but when creating the translation in the form you will see the translated version of terms - in the edit form this works fine.
8. Create a view which displays list of nodes and related taxonomy terms.
9. Visit the view and you will see that the terms will be visible in the originally created node language - no matter in which language you are switching the user interface.

I believe that this is because of each Drupal field has language reference (field in the database filled as en, lv, ru, de etc... ). If the field is not translatable - the language reference is filled with the originally created node language code. And when displaying the node - this field language setting is joined with the taxonomy term language setting and as the result in both languages we see terms in the originally created language.
The same problem is when you use Panelizer to display node fields - also the language of the terms displayed will be in the language in which the node was created.

Comments

Nor4a created an issue. See original summary.

Nor4a’s picture

Nor4a CreditAttribution: Nor4a as a volunteer commented
Issue summary: View changes
Nor4a’s picture

Nor4a CreditAttribution: Nor4a as a volunteer commented
Title: Translated version of taxonomy term not displayed when using not-translatable reference field to taxonomy term » Translated version of taxonomy term not displayed when using not-translatable reference field to taxonomy term in views
Issue summary: View changes

Version: 8.3.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Branches prior to 8.8.x are not supported, and Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.