Configure content types for entity translation

Enabling entity translation for a content type

With Entity Translation enabled for "Node", you can set the translation mode (Entity Translation or Content Translation) for each Content Type. To enable translation mode for a particular content type, you need to edit the content type and click on the 'Publishing options' tab and choose under Multilingual support:

  • "Enabled, with translation" for Content Translation
  • "Enabled, with field translation" for Entity Translation

Note that the i18n submodules "Field Translation"*, "Multilingual Content" and "Multilingual Select" do NOT need to be enabled to use Entity Translation properly, and SHOULD NOT be enabled to use Entity Translation properly with an upgrade path to multilingual websites in Drupal 8.
* Multilingual Select is architecturally incompatible with Entity Translation.
* Field Translation might be needed though if you want to translate field labels.
* Multilingual content and its dependency Content translation might be needed though if you want to translate content type strings such as content type names and descriptions.
See https://drupal.org/node/2107219#comment-7963411

How to enable translation for particular fields

String translation

The String translation module, part of the Internationalization (i18n) package, provides support for other modules to translate user-defined strings. It implements the i18n_strings function, which in Drupal 6 was commonly known as the tt function. The i18n_strings function is an API function that lets other modules (such as the Taxonomy translation and Menu translation submodules) manage translations of user-entered strings. Depending on which modules you have enabled that use this feature, different text groups will be available for translation.

In contrast to Drupal's standard localization system, which always translates from English, strings will be translated from the source language. By default the source language is the site's default language, so changing the default language could break these translations. You can set which language is used as the source language via Administration > Configuration > Regional and language > Multilingual settings > Strings.

Common issues and questions about field translation

Remove node Language field from display

The Internationalization module exposes a new field on the node display, the node language, that was already there but never displayed.

In order to remove it from showing up on the node view, you need to edit your content type's Display settings. Note: The Field UI core module must be enabled to edit these Display settings.

Taxonomy translation

The Taxonomy translation module, part of the Internationalization (i18n) package, provides multiple options to translate taxonomy vocabularies and terms. For each vocabulary, you'll have to choose one of four different modes defining 'multilingual' behaviors for the vocabulary:

  1. No multilingual options for terms. Only the vocabulary will be translatable. (default) [previously called None]
  2. Localize. Terms are common for all languages, but their name and description may be localized. [previously called Localize terms]
  3. Translate. Different terms will be allowed for each language and they can be translated. [previously called Per language terms]
  4. Fixed Language. Terms will have a global language and they will only show up for pages in that language. [previously called Set language to vocabulary]

When a language is set for a vocabulary or term, only those that match the the current language will appear in taxonomy listings and when creating and editing nodes. If the language is set for a vocabulary, all the terms in that vocabulary will be automatically set to that language.

Taxonomy translation

The Taxonomy translation module (part of the Internationalization package) provides multiple options to translate taxonomy vocabularies and terms. For each vocabulary you'll have to choose one of four different modes defining 'multilingual' behaviors for the vocabulary:

  1. None. No multilingual options for this vocabulary (default).
  2. Localize terms. Terms are common for all languages, but their name and description may be localized.
  3. Per language terms. Different terms will be allowed for each language and they can be translated.
  4. Set language to vocabulary. The vocabulary will have a global language and it will only show up for pages in that language.

When a language is set for a vocabulary or term, only those items that match the current language will appear in taxonomy listings and when creating and editing nodes. If the language is set for a vocabulary, all the terms in that vocabulary will be automatically set to that language.

Per language terms

Subscribe with RSS Subscribe to RSS - taxonomy translation