Last updated March 2, 2013. Created by pixelite on September 15, 2011.
Edited by EdNet, jbbourdu, frederickjh, ethanethan. Log in to edit this page.
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.
How to enable translation for particular fields
Once entity translation has been enabled, you can make individual fields for the content type translatable by first editing the field and then going to the 'Field Settings' tab, checking the Users may translate this field checkbox, and saving the settings.
Translation of titles
By default in Drupal 7, titles are not fields. Titles of nodes can be converted to fields using the Title module as follows:
- Download and enable the Title module.
- For the given content type, go to the Manage fields tab.
- In the table of fields, beside the title element, click the replace link under the 'Operations' heading. Select the checkbox "Replace title with a field instance" and hit save.
- The title will be converted to a field, which users can translate by default.
- Since the title is now a field, it will show up under the content of each node, as well as being the title. To hide the title field from the content, go to the Manage display tab for the content type and drag the title field into the Hidden section.
Translation of taxonomy terms
You can choose to allow users to translate taxonomy term references attached to a content type, just like you can do with fields. In the case of taxonomy terms, this will allow users to choose a different term or set of terms for each language. Localization of the terms themselves needs to be handled separately, for example, with the Internationalization (i18n) package's Taxonomy translation module.
Options for multilingual comments
Since only one node is created for content types with entity translation enabled, comments are all added to the same node, regardless of the user's language. By default, all comments will be displayed on the node page. Under the Comment settings tab, there is an option to Filter comments by language which will filter out comments in languages other than the current language.