Voting starts in March for the Drupal Association Board election.
- There are two main methods to choose from to configure a multilingual Drupal website:
- Entity Translation is the newer method
- Content Translation is the older method
- Entity Translation is now in Drupal 8 core. It is available for both Drupal 7 and 8. With an upgrade path from Drupal 7 to 8;
- Content Translation is available for both Drupal 6 and 7;
- Below is the documentation for Entity Translation
The Entity Translation module allows entities (such as nodes) to be translated into different languages. Entity Translation provides field-level translation, so that site builders can select which fields should be translatable. It provides a UI for users to translate these fields into other languages. Entity Translation is now in Drupal 8 core. With an upgrade path from Drupal 7 to 8. Entity Translation is not a replacement for the Internationalization (i18n) package, which includes many other important multilingual features such as multilingual taxonomies, menus, and blocks.
Entity Translation is particularly useful for content that should be language-independent and should always exist in all languages in the same state. Entities that include membership signups (groups), workflow status (issues), or that are involved in transactions (products) are good candidates for Entity Translation.
When using Entity Translation, you need to use the Title module to allow entity titles to be translated. Note: Don't confuse the Entity Translation module with the Field translation module. The Field translation module allows for translation of field settings, such as the field's title and description, and is part of the Internationalization (i18n) package.