Use Suggestions

TMGMT includes a mechnism to detect content dependent on the source you are about to translate. You can, therefore, let the system suggest additional elements for which to create translation job items.

Let's look at an example. Assume you are using the Media module to manage your media content. And you use the File Entity Module to have your uploaded files registered as an entity. These will have 2 standard fields attached to them (Alt text and Title text).

Translating a node with an image file attached to it will also require to translate those additional fields. Thats where suggestions come in.

To demonstrate this, set up the following modules and types:

  • install Media module, version 2 (requires file entity, latest dev version, min. version 2)
  • activate entity translation for 'file' entity type (Administration > Configuration > Regional and language > Entity translation)
  • activate translation for the fields attached to the image file entity ( Administration > File types, choose 'manage fields' for Image, edit each field and check the 'Users may translate this field' box )
  • setup a content type with an image field. Make sure to choose 'Media File Selector' as the widget for the image field. Use 'Rendered file' as the display formatter on the image field

Request translation for several entities at once

Analog to 'Node Source' there is an 'Entity Sources' listing on which you can manage bulk translation with entities.

Go to Administration > Sources. Here you can access all entity types that have been marked as translatable. In the case below 'node' and 'File'.

Entity Translation

Instead of translating complete nodes it can be interesting to make only some fields of a node translatable. This can be achieved by using the Entity Translation Module (http://drupal.org/project/entity_translation). With it, fieldable entities can be translated without doubling the node itself.

Make entities translatable

As a starting step make sure that you have set the appropriate options for language detection (Administration > Configuration > Regional and language > Languages, choose the 'Detection and selection' tab). This will facilitate finding the translations once they are done.

  • Download and activate the entity_translation module
  • Create a content type with the fields you want to translate
  • Under the publishing option of the type choose 'Enabled, with field translation' in Mulitlingual support
  • In the properties of each field enable the field translation ('Users may translate this field'). You will find this in the 'edit' tab

Fields can now be translated one by one. For a more detailed description see this post by Randy Fay.

Invoke TMGMT

Taxonomy translation

The Taxonomy translation (i18n_taxonomy) 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.

Subscribe with RSS Subscribe to RSS - Entity translation