You can now start translating content this will be divided into four tasks: You can set "Hide shared elements on translation forms" to stop translators from accidentally changing non translatable fields. Visit each one and set its Default language Go back to admin/config/regional/entity_translation and you will see a tab for each of the content types you enabled and their associated bundles (sub types). Use the "Replace" link next to the Title and Description to convert those into translatable fields. Visit the manage fields for each of the Taxonomies/vocabularies you want to localize and Go to manage fields and follow the same instructions as the node types above.Ĥ) Enable Multilingual support for Taxonomies Set set Multilingual support to Enabled, with field translation Visit admin/commerce/products/types and edit each of the product types Press "replace" next to the title this will convert the title into a translatable fieldĮdit each field you want to translate and set it to Enable translationģ) Enable Multilingual support for each of your product types
Go to manage fields and do the following: Under publishing options set Multilingual support to Enabled, with field translation Start by visiting all your node types (this should include the product display) and on the edit tab:
In the Translatable entity types section select the followingĢ) Enable Multilingual support for each of your node types Go to admin/config/regional/entity_translation Go to the blocks section admin/structure/block and position the block "Language switcher (User interface text)" in one of the regions. Import the files you downloaded by going to admin/config/regional/translate/import and selecting a coresponding file and a language.ĥ) provide a Language selector for site visitors: Go to admin/config/regional/language/configure That's pretty much it, if you happen to know any please comment below.Drush en i18n, i18n_translation, i18n_field, i18n_menu -yġ) Make sure your regional settings are correctĪnd add your languages, note that the Default language should correspond to the main language on your site and that includes the development of the site if you name your fields in English and your default language is French Drupal will think that the labels for those fields are in French. Adding multilingual site maps also will help.Making sure enable `hreflang` attribute for pages will help, this attribute specifies the base language.Images and files can be localized so use Entity translation module or any other module to translate images and files as necessary.Using a consistent URLs schema for multilingual content will help, so for example use a single url for content and let Drupal decide and handle the redirects for target language.
Drupal entity tranlsations translate tab full#
Those two modules can handle the content translations very well in Drupal7 so either works and have many configuration options.
Drupal entity tranlsations translate tab upgrade#
That comes to adding Entity translations (this is recommended since D8 upgrade will be easier) or i18n module first to Drupal project.For content translations, the rule of thumb is that focus on SEO of English version then get a good translator to research keywords and translate the content to the target language and work with them to optimize it again in the target language.