README.txt

Same filename in this branch
  1. 8.x-1.x README.txt
  2. 8.x-1.x translators/tmgmt_local/README.txt
Translation Management Tool (tmgmt)
-------------------------------------

A collection of tools to facilitate the translation of text elements in Drupal.

Requirements
------------------

Translation Management Tool was built for Drupal 7. There will be no backport.

To use Translation Management Tool you need to install and activate the
following modules:

 * Entity API
 * Views
 * Chaos Tools (Required for Views)
 * Views Bulk Operations
 * Content Translation
 * Locale
 * Rules

Optional dependencies:
 * Internationalization/i18n
   (Only necessary for i18n_string translation)
 * Entity Translation (only for entity sources)

Basic concepts
------------------

With TMGMT installed, the 'translate' tab of a node changes. You can choose
one or more languages to translate the node to and 'Request a translation' with
the corresponding button.

A translation job is created for each language chosen. It will run through the
following states:

Unprocessed     Translation requested in the 'translate' tab of a node.
                Settings of the job (label set, translator chosen) defined.
                The job was saved.
Active          The job is in the process of being translated. Depending on
                the chosen translator, the actual translation happens auto-
                matically or by a human being.
                In all cases the job is returned to the job queue for review.
                When the review is done, the status of the job item goes from
                'needs review' to 'accepted'.
Finished        The job has been accepted and the translated node was created

The project also provides overviews for the supported sources that allow to
translate multiple pieces of content (job items) in a single job and see the
current translation status for your site content.

Getting started
------------------

The first simple translation job using Microsoft's translation service.

1) Preparation

- Make sure you have downloaded all of the listed dependencies.
- Define a second language using locale
- Modify one content type to be multilingual. Choose 'Enabled, with translation'
  from the Publishing Options / Multilingual support.

2) Set up Translation Management Tool

- Download tmgmt module
- Download tmgmt_microsoft module
- Enable the following modules, this will also include all dependencies
  - Translation Management UI
  - Content translation Source UI
  - Microsoft Translator
- A translator has been automatically created. Go to the Translator management
  page at:

    Configuration > Regional and language > Translation Management Translators

  Adjust the label to your liking and get a client ID and client secret using
  the provided link in the settings. Then save the updated translator.

- Adjust the Auto Acceptance settings to your liking. You can choose to accept
  jobs without review by checking  'Auto accept finished translations' for each
  of your translators individually.

3) Translate

- Create a new piece of content of the multilingual content type defined before.
  Make sure to choose a language.
- Once the node has been saved, click on the "Translate" tab.
- Choose the language you want to translate the node to with the checkbox.
- Click on 'Request Translation' and the foreign language version of the node
  will be created immediately.
- If the auto acceptance is not set, find the job in the jobs queue and choose
  the 'review' link. Accept the translation and the translated node is created.
- Check the translated node!

For further options, see the documentation on http://drupal.org/node/1445790.

Features
----------

This projects consists of 3 major parts. The starting point are the sources,
which expose translatable content like nodes, other entities and i18n strings.

On the other side are the so called translators, which are responsible for
getting the requested sources translated.

The core system combine these two parts and provide the ability to create,
manage and review translation jobs.

The main features of the core system include:

- Creation of translations and managing their progress
- Review of returned translations, ability to request revisions and communicate
  with the translator if supported.
- Translation overviews that allow to see which content is available in which
  language and what translation jobs are currently ongoing.
- The same information is provided on the translate tab of the supported
  sources.
- A suggestions system that makes recommendations about related content that
  could be translated with the same job.
- Sources can declare which parts of a source text should not be translated,
  for example placeholders for user interface strings.

The following sources are currently supported:

- Content Translation
  Integrates with the core translation module to translate nodes.

- Entity Translation
  Integrates with the entity_translation module that allows to translate fields
  on any entity type.

- Internationalization (i18n)
  Integrates with the i18n project (http://drupal.org/project/i18n) and allows
  to translate various configuration elements of a site: blocks, terms, fields,
  node types, contact categories and many more.

- Locale
  Allows to translate locale strings. Currently limited to the default
  textgroup (user interface strings passed through t()).

Two translators are included in the project:

- File translator
  Allows to export jobs into files and import them once they have been
  translated. Contains a pluggable system to support various file formats,
  currently XLIFF and HTML.

- Local Translator
  The local translator allows to manage translators on your own site so that
  they can translate your content in a central place and defined workflows.
  Together with the TMGMT Server, it can be used to build your own translation
  server. Check the Hermes installation profile for more information:
  http://drupal.org/project/hermes

Translators in separate projects:

- Microsoft Translator
  Machine translation using Microsoft's Bing translation.
  http://drupal.org/project/tmgmt_microsoft.

- Google
  Machine translation using Google Translate.
  Moved to http://drupal.org/project/tmgmt_google.

- Gengo (Previously named MyGengo)
  Human translation that integrates with http://www.gengo.com.
  http://drupal.org/project/tmgmt_mygengo.

- Supertext
  Human translation that integrates with http://www.supertext.ch.
  http://drupal.org/project/tmgmt_supertext.

- Nativy
  Human translation that integrates with http://www.nativy.com.
  http://drupal.org/project/tmgmt_nativy.

- One Hour Translation
  Human translation that integrates with http://www.onehourtranslation.com.
  http://drupal.org/project/tmgmt_oht

Credits
-------

- The TMGMT icon in the menu bar (the globe) is from the IcoMoon's free icon pack.
  Licenced by GNU General Public License / Creative Commons Attribution 4.0 International (CC BY 4.0).
  It is available on the following URL: https://icomoon.io/#icons-icomoon
  The only change made was the change of the color to grey.

Support for paragraphs_demo
---------------------------

- TMGMT demo module supports the translation of paragraphs. To enable this, do the following:
  - Enable paragraphs_demo module
  - Enable tmgmt_demo module

File

README.txt
View source
  1. Translation Management Tool (tmgmt)

  2. -------------------------------------

  3. 

  4. A collection of tools to facilitate the translation of text elements in Drupal.

  5. 

  6. Requirements

  7. ------------------

  8. 

  9. Translation Management Tool was built for Drupal 7. There will be no backport.

  10. 

  11. To use Translation Management Tool you need to install and activate the

  12. following modules:

  13. 

  14.  * Entity API

  15.  * Views

  16.  * Chaos Tools (Required for Views)

  17.  * Views Bulk Operations

  18.  * Content Translation

  19.  * Locale

  20.  * Rules

  21. 

  22. Optional dependencies:

  23.  * Internationalization/i18n

  24.    (Only necessary for i18n_string translation)

  25.  * Entity Translation (only for entity sources)

  26. 

  27. Basic concepts

  28. ------------------

  29. 

  30. With TMGMT installed, the 'translate' tab of a node changes. You can choose

  31. one or more languages to translate the node to and 'Request a translation' with

  32. the corresponding button.

  33. 

  34. A translation job is created for each language chosen. It will run through the

  35. following states:

  36. 

  37. Unprocessed     Translation requested in the 'translate' tab of a node.

  38.                 Settings of the job (label set, translator chosen) defined.

  39.                 The job was saved.

  40. Active          The job is in the process of being translated. Depending on

  41.                 the chosen translator, the actual translation happens auto-

  42.                 matically or by a human being.

  43.                 In all cases the job is returned to the job queue for review.

  44.                 When the review is done, the status of the job item goes from

  45.                 'needs review' to 'accepted'.

  46. Finished        The job has been accepted and the translated node was created

  47. 

  48. The project also provides overviews for the supported sources that allow to

  49. translate multiple pieces of content (job items) in a single job and see the

  50. current translation status for your site content.

  51. 

  52. Getting started

  53. ------------------

  54. 

  55. The first simple translation job using Microsoft's translation service.

  56. 

  57. 1) Preparation

  58. 

  59. - Make sure you have downloaded all of the listed dependencies.

  60. - Define a second language using locale

  61. - Modify one content type to be multilingual. Choose 'Enabled, with translation'

  62.   from the Publishing Options / Multilingual support.

  63. 

  64. 2) Set up Translation Management Tool

  65. 

  66. - Download tmgmt module

  67. - Download tmgmt_microsoft module

  68. - Enable the following modules, this will also include all dependencies

  69.   - Translation Management UI

  70.   - Content translation Source UI

  71.   - Microsoft Translator

  72. - A translator has been automatically created. Go to the Translator management

  73.   page at:

  74. 

  75.     Configuration > Regional and language > Translation Management Translators

  76. 

  77.   Adjust the label to your liking and get a client ID and client secret using

  78.   the provided link in the settings. Then save the updated translator.

  79. 

  80. - Adjust the Auto Acceptance settings to your liking. You can choose to accept

  81.   jobs without review by checking  'Auto accept finished translations' for each

  82.   of your translators individually.

  83. 

  84. 3) Translate

  85. 

  86. - Create a new piece of content of the multilingual content type defined before.

  87.   Make sure to choose a language.

  88. - Once the node has been saved, click on the "Translate" tab.

  89. - Choose the language you want to translate the node to with the checkbox.

  90. - Click on 'Request Translation' and the foreign language version of the node

  91.   will be created immediately.

  92. - If the auto acceptance is not set, find the job in the jobs queue and choose

  93.   the 'review' link. Accept the translation and the translated node is created.

  94. - Check the translated node!

  95. 

  96. For further options, see the documentation on http://drupal.org/node/1445790.

  97. 

  98. Features

  99. ----------

  100. 

  101. This projects consists of 3 major parts. The starting point are the sources,

  102. which expose translatable content like nodes, other entities and i18n strings.

  103. 

  104. On the other side are the so called translators, which are responsible for

  105. getting the requested sources translated.

  106. 

  107. The core system combine these two parts and provide the ability to create,

  108. manage and review translation jobs.

  109. 

  110. The main features of the core system include:

  111. 

  112. - Creation of translations and managing their progress

  113. - Review of returned translations, ability to request revisions and communicate

  114.   with the translator if supported.

  115. - Translation overviews that allow to see which content is available in which

  116.   language and what translation jobs are currently ongoing.

  117. - The same information is provided on the translate tab of the supported

  118.   sources.

  119. - A suggestions system that makes recommendations about related content that

  120.   could be translated with the same job.

  121. - Sources can declare which parts of a source text should not be translated,

  122.   for example placeholders for user interface strings.

  123. 

  124. The following sources are currently supported:

  125. 

  126. - Content Translation

  127.   Integrates with the core translation module to translate nodes.

  128. 

  129. - Entity Translation

  130.   Integrates with the entity_translation module that allows to translate fields

  131.   on any entity type.

  132. 

  133. - Internationalization (i18n)

  134.   Integrates with the i18n project (http://drupal.org/project/i18n) and allows

  135.   to translate various configuration elements of a site: blocks, terms, fields,

  136.   node types, contact categories and many more.

  137. 

  138. - Locale

  139.   Allows to translate locale strings. Currently limited to the default

  140.   textgroup (user interface strings passed through t()).

  141. 

  142. Two translators are included in the project:

  143. 

  144. - File translator

  145.   Allows to export jobs into files and import them once they have been

  146.   translated. Contains a pluggable system to support various file formats,

  147.   currently XLIFF and HTML.

  148. 

  149. - Local Translator

  150.   The local translator allows to manage translators on your own site so that

  151.   they can translate your content in a central place and defined workflows.

  152.   Together with the TMGMT Server, it can be used to build your own translation

  153.   server. Check the Hermes installation profile for more information:

  154.   http://drupal.org/project/hermes

  155. 

  156. Translators in separate projects:

  157. 

  158. - Microsoft Translator

  159.   Machine translation using Microsoft's Bing translation.

  160.   http://drupal.org/project/tmgmt_microsoft.

  161. 

  162. - Google

  163.   Machine translation using Google Translate.

  164.   Moved to http://drupal.org/project/tmgmt_google.

  165. 

  166. - Gengo (Previously named MyGengo)

  167.   Human translation that integrates with http://www.gengo.com.

  168.   http://drupal.org/project/tmgmt_mygengo.

  169. 

  170. - Supertext

  171.   Human translation that integrates with http://www.supertext.ch.

  172.   http://drupal.org/project/tmgmt_supertext.

  173. 

  174. - Nativy

  175.   Human translation that integrates with http://www.nativy.com.

  176.   http://drupal.org/project/tmgmt_nativy.

  177. 

  178. - One Hour Translation

  179.   Human translation that integrates with http://www.onehourtranslation.com.

  180.   http://drupal.org/project/tmgmt_oht

  181. 

  182. Credits

  183. -------

  184. 

  185. - The TMGMT icon in the menu bar (the globe) is from the IcoMoon's free icon pack.

  186.   Licenced by GNU General Public License / Creative Commons Attribution 4.0 International (CC BY 4.0).

  187.   It is available on the following URL: https://icomoon.io/#icons-icomoon

  188.   The only change made was the change of the color to grey.

  189. 

  190. Support for paragraphs_demo

  191. ---------------------------

  192. 

  193. - TMGMT demo module supports the translation of paragraphs. To enable this, do the following:

  194.   - Enable paragraphs_demo module

  195.   - Enable tmgmt_demo module