README.txt 6.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180
  1. Translation Management Tool (tmgmt)
  2. -------------------------------------
  3. A collection of tools to facilitate the translation of text elements in Drupal.
  4. Requirements
  5. ------------------
  6. Translation Management Tool was built for Drupal 7. There will be no backport.
  7. To use Translation Management Tool you need to install and activate the
  8. following modules:
  9. * Entity API
  10. * Views
  11. * Chaos Tools (Required for Views)
  12. * Views Bulk Operations
  13. * Content Translation
  14. * Locale
  15. * Rules
  16. Optional dependencies:
  17. * Internationalization/i18n
  18. (Only necessary for i18n_string translation)
  19. * Entity Translation (only for entity sources)
  20. Basic concepts
  21. ------------------
  22. With TMGMT installed, the 'translate' tab of a node changes. You can choose
  23. one or more languages to translate the node to and 'Request a translation' with
  24. the corresponding button.
  25. A translation job is created for each language chosen. It will run through the
  26. following states:
  27. Unprocessed Translation requested in the 'translate' tab of a node.
  28. Settings of the job (label set, translator chosen) defined.
  29. The job was saved.
  30. Active The job is in the process of being translated. Depending on
  31. the chosen translator, the actual translation happens auto-
  32. matically or by a human being.
  33. In all cases the job is returned to the job queue for review.
  34. When the review is done, the status of the job item goes from
  35. 'needs review' to 'accepted'.
  36. Finished The job has been accepted and the translated node was created
  37. The project also provides overviews for the supported sources that allow to
  38. translate multiple pieces of content (job items) in a single job and see the
  39. current translation status for your site content.
  40. Getting started
  41. ------------------
  42. The first simple translation job using Microsoft's translation service.
  43. 1) Preparation
  44. - Make sure you have downloaded all of the listed dependencies.
  45. - Define a second language using locale
  46. - Modify one content type to be multilingual. Choose 'Enabled, with translation'
  47. from the Publishing Options / Multilingual support.
  48. 2) Set up Translation Management Tool
  49. - Download tmgmt module
  50. - Download tmgmt_microsoft module
  51. - Enable the following modules, this will also include all dependencies
  52. - Translation Management UI
  53. - Content translation Source UI
  54. - Microsoft Translator
  55. - A translator has been automatically created. Go to the Translator management
  56. page at:
  57. Configuration > Regional and language > Translation Management Translators
  58. Adjust the label to your liking and get a client ID and client secret using
  59. the provided link in the settings. Then save the updated translator.
  60. - Adjust the Auto Acceptance settings to your liking. You can choose to accept
  61. jobs without review by checking 'Auto accept finished translations' for each
  62. of your translators individually.
  63. 3) Translate
  64. - Create a new piece of content of the multilingual content type defined before.
  65. Make sure to choose a language.
  66. - Once the node has been saved, click on the "Translate" tab.
  67. - Choose the language you want to translate the node to with the checkbox.
  68. - Click on 'Request Translation' and the foreign language version of the node
  69. will be created immediately.
  70. - If the auto acceptance is not set, find the job in the jobs queue and choose
  71. the 'review' link. Accept the translation and the translated node is created.
  72. - Check the translated node!
  73. For further options, see the documentation on http://drupal.org/node/1445790.
  74. Features
  75. ----------
  76. This projects consists of 3 major parts. The starting point are the sources,
  77. which expose translatable content like nodes, other entities and i18n strings.
  78. On the other side are the so called translators, which are responsible for
  79. getting the requested sources translated.
  80. The core system combine these two parts and provide the ability to create,
  81. manage and review translation jobs.
  82. The main features of the core system include:
  83. - Creation of translations and managing their progress
  84. - Review of returned translations, ability to request revisions and communicate
  85. with the translator if supported.
  86. - Translation overviews that allow to see which content is available in which
  87. language and what translation jobs are currently ongoing.
  88. - The same information is provided on the translate tab of the supported
  89. sources.
  90. - A suggestions system that makes recommendations about related content that
  91. could be translated with the same job.
  92. - Sources can declare which parts of a source text should not be translated,
  93. for example placeholders for user interface strings.
  94. The following sources are currently supported:
  95. - Content Translation
  96. Integrates with the core translation module to translate nodes.
  97. - Entity Translation
  98. Integrates with the entity_translation module that allows to translate fields
  99. on any entity type.
  100. - Internationalization (i18n)
  101. Integrates with the i18n project (http://drupal.org/project/i18n) and allows
  102. to translate various configuration elements of a site: blocks, terms, fields,
  103. node types, contact categories and many more.
  104. - Locale
  105. Allows to translate locale strings. Currently limited to the default
  106. textgroup (user interface strings passed through t()).
  107. Two translators are included in the project:
  108. - File translator
  109. Allows to export jobs into files and import them once they have been
  110. translated. Contains a pluggable system to support various file formats,
  111. currently XLIFF and HTML.
  112. - Local Translator
  113. The local translator allows to manage translators on your own site so that
  114. they can translate your content in a central place and defined workflows.
  115. Together with the TMGMT Server, it can be used to build your own translation
  116. server. Check the Hermes installation profile for more information:
  117. http://drupal.org/project/hermes
  118. Translators in separate projects:
  119. - Microsoft Translator
  120. Machine translation using Microsoft's Bing translation.
  121. http://drupal.org/project/tmgmt_microsoft.
  122. - Google
  123. Machine translation using Google Translate.
  124. Moved to http://drupal.org/project/tmgmt_google.
  125. - Gengo (Previously named MyGengo)
  126. Human translation that integrates with http://www.gengo.com.
  127. http://drupal.org/project/tmgmt_mygengo.
  128. - Supertext
  129. Human translation that integrates with http://www.supertext.ch.
  130. http://drupal.org/project/tmgmt_supertext.
  131. - Nativy
  132. Human translation that integrates with http://www.nativy.com.
  133. http://drupal.org/project/tmgmt_nativy.
  134. - One Hour Translation
  135. Human translation that integrates with http://www.onehourtranslation.com.
  136. http://drupal.org/project/tmgmt_oht