You are here

README.txt in Lingotek Translation 6

Same filename and directory in other branches
  1. 7.7 README.txt
  2. 7.4 README.txt
  3. 7.5 README.txt
  4. 7.6 README.txt
Lingotek Collaborative Translation Module

Module Version: 6.x-20110715.x

Requirements:

  1. Drupal 6.18
  2. PHP >= 5.2
  3. PECL hash >= 1.1
  4. PECL json >= 1.2.0
  5. SQL database (MySQL or PostgreSQL are supported)

  Drupal Modules Required:
    1.Locale (core)
    2.Content translation (core)

  Modules for Optional Features:
    1."Menu translation" from i18n (6.x-1.5)


Installation:

    1.Copy the unzipped module and it's folder into your drupal
      sites/all/modules folder
    2.Log in to Drupal as an administrator.
    3.Browse to Administer -> Site Building -> Modules
    4.Check Enabled next to the "Lingotek Collaborative Translation" module.
    5.Click "Save configuration"
    6.Click "Continue" to enable the required core modules.

  If you intend on using the module's "Overwrite Menus" feature, then
  follow these steps:

    1.Copy the unzipped i18n module and it's folder into your drupal
      sites/all/modules folder
    2.Log in to Drupal as an administrator.
    3.Browse to Administer -> Site Building -> Modules
    4.Check Enabled next to the "Menu translation" module.
    5.Click "Save configuration"
    6.Click "Continue" to enable the other required modules.

Configuration:

  1.  Permissions:
    1.  Log in as an administrator
    2.  Browse to Administer -> User management -> Roles and setup any roles you
      want to have different permissions for.
      (Translator, Reviewer, Project Manager, Drupal Administrator, etc)
    3.  Browse to Administer -> User management -> Permissions
    4.  Under lingotek module:
      1.  administer - Enable this for the role you wish
        to be able to edit the system-wide module settings on the module's
        administrative page (see "Administrative settings" below).
      2.  machine_translation - This allows a page creator to set which machine
        translation setting an individual page should use.  Enable this for the
        role you wish to be able to overwrite the default phase template setting
        on a page-by-page basis.  This permission also shows machine translation
        options on each target on the lingotek tab.  It will automatically sync
        when done and overwrite the drupal page, so any changes made from
        drupal to a target page will be lost.
      3.  phase_template - This allows a page creator to set which phase
        template (workflow) an individual page should use.  Enable this for the
        role you wish to be able to overwrite the default phase template setting
        on a page-by-page basis.
      4.  review_phase - This allows a user to click on the review phases,
        or tasks, for a given translation.
      5.  sync - This permission shows download options on each target
        so the user can re-download an up-to-date version of the document.
        It will overwrite the drupal page, so any changes made from
        drupal to the content will be lost.
      6.  tab - This displays the "Lingotek" tab
        on created pages and allows someone such as a project manager
        access to view the translation progress.  Additional permissions
        are required to gain access to translate or review.
      7.  translation_phase - This allows a user to click on the translation
        phases, or tasks, for a given translation.

  2.  Administrative settings:

    Authentication Settings:
      1.Log in in to Drupal as an administrator
      2.Browse to Administer -> Site configuration -> Lingotek
        (admin/settings/community_translation)
        If you are unable to find this page, make sure your role has the
        "administer community_translation" permission discussed above.
      3.Fill in your provided Login ID, Login Key, Lingotek URL, and
        Community ID.  Make sure that the Lingotek URL doesn't include any
        trailing slashes.
      4.Click "Save configuration"

    Dashboard Settings:
      1.Select a Project (or enter a Project ID if the drop-down doesn't appear)
      2.Select a Vault (or enter a Vault ID if the drop-down doesn't appear)
      3.Click "Save configuration"

    Drupal Settings:
      1.  Set the "Neutral Language" to what language Lingotek should
        consider the document when a language isn't specified.
      2.  Enable "Overwrite Menus" if you wish our module to update the
        menu navigation to point to each translation as they
        become available.  Pages that haven't finished being translated
        will point to the source document.  This requires i18n's
        Menu Translation module to be installed and enabled.
        See the above installation guide for details.
    Default Settings:
      1.  "Phase Template" is the template that will be selected as
        default when creating a new page.
      2.  "Machine Translation Engine" is the default
        setting for if the page should be published with Google translate
        or if the publishing will be deferred until after a professional
        translation.
      3.  "Available Machine Translation Options" are what options are available
        on page creation.
      7.  Click "Save configuration"


Usage:

  1.  Create a new page.  While editing the page, note the Phase Template
    setting that has been added.  The drop-down is visible if the user has
    "phase_template" permissions.
    Otherwise, this drop-down is missing and the page creator will be
    required to use the default phase template.
  2.  Publishing options are also shown, allowing you to choose weather to use
    Google translation and immediately publish the results, or if you want
    to use professional translators and defer publication until the process
    is complete.  The drop-down is visible if the user has
    "machine_translation" permissions.
    Otherwise, this drop-down is disabled and the page creator will be
    required to use the default value.
  3.  Save the page.  A new option, "Lingotek" will appear on
    the created page if your user has permissions to "tab".
  4.  Click on "Lingotek" where you can see the progress of
    the page's translations.
  5.  The title only appears once the page
    has been fully translated and reviewed (Total % = 100%) or machine
    translated or synced.
    The title gives a link to the new page with the translated content,
    as well as shows that the page has been published.  Notice that the
    title is also translated as the first segment in the
    translation process.  If "Overwrite Menus" is enabled in the module,
    then the translated title is used as the new title in the translated
    menu.  The source language, however, retains the page creator's title.
  6.  Phase shows us what step in the workflow the document is on.
    The first phase of any phase set will need "translation_phase" permissions
    to complete.  The following phases are only accessible to those with
    "review_phase" permissions.
  7.  Status is the complete percent for the entire translation process.
  8.  Published shows if the node has been marked as published to users.

File

README.txt
View source
  1. Lingotek Collaborative Translation Module
  2. Module Version: 6.x-20110715.x
  3. Requirements:
  4. 1. Drupal 6.18
  5. 2. PHP >= 5.2
  6. 3. PECL hash >= 1.1
  7. 4. PECL json >= 1.2.0
  8. 5. SQL database (MySQL or PostgreSQL are supported)
  9. Drupal Modules Required:
  10. 1.Locale (core)
  11. 2.Content translation (core)
  12. Modules for Optional Features:
  13. 1."Menu translation" from i18n (6.x-1.5)
  14. Installation:
  15. 1.Copy the unzipped module and it's folder into your drupal
  16. sites/all/modules folder
  17. 2.Log in to Drupal as an administrator.
  18. 3.Browse to Administer -> Site Building -> Modules
  19. 4.Check Enabled next to the "Lingotek Collaborative Translation" module.
  20. 5.Click "Save configuration"
  21. 6.Click "Continue" to enable the required core modules.
  22. If you intend on using the module's "Overwrite Menus" feature, then
  23. follow these steps:
  24. 1.Copy the unzipped i18n module and it's folder into your drupal
  25. sites/all/modules folder
  26. 2.Log in to Drupal as an administrator.
  27. 3.Browse to Administer -> Site Building -> Modules
  28. 4.Check Enabled next to the "Menu translation" module.
  29. 5.Click "Save configuration"
  30. 6.Click "Continue" to enable the other required modules.
  31. Configuration:
  32. 1. Permissions:
  33. 1. Log in as an administrator
  34. 2. Browse to Administer -> User management -> Roles and setup any roles you
  35. want to have different permissions for.
  36. (Translator, Reviewer, Project Manager, Drupal Administrator, etc)
  37. 3. Browse to Administer -> User management -> Permissions
  38. 4. Under lingotek module:
  39. 1. administer - Enable this for the role you wish
  40. to be able to edit the system-wide module settings on the module's
  41. administrative page (see "Administrative settings" below).
  42. 2. machine_translation - This allows a page creator to set which machine
  43. translation setting an individual page should use. Enable this for the
  44. role you wish to be able to overwrite the default phase template setting
  45. on a page-by-page basis. This permission also shows machine translation
  46. options on each target on the lingotek tab. It will automatically sync
  47. when done and overwrite the drupal page, so any changes made from
  48. drupal to a target page will be lost.
  49. 3. phase_template - This allows a page creator to set which phase
  50. template (workflow) an individual page should use. Enable this for the
  51. role you wish to be able to overwrite the default phase template setting
  52. on a page-by-page basis.
  53. 4. review_phase - This allows a user to click on the review phases,
  54. or tasks, for a given translation.
  55. 5. sync - This permission shows download options on each target
  56. so the user can re-download an up-to-date version of the document.
  57. It will overwrite the drupal page, so any changes made from
  58. drupal to the content will be lost.
  59. 6. tab - This displays the "Lingotek" tab
  60. on created pages and allows someone such as a project manager
  61. access to view the translation progress. Additional permissions
  62. are required to gain access to translate or review.
  63. 7. translation_phase - This allows a user to click on the translation
  64. phases, or tasks, for a given translation.
  65. 2. Administrative settings:
  66. Authentication Settings:
  67. 1.Log in in to Drupal as an administrator
  68. 2.Browse to Administer -> Site configuration -> Lingotek
  69. (admin/settings/community_translation)
  70. If you are unable to find this page, make sure your role has the
  71. "administer community_translation" permission discussed above.
  72. 3.Fill in your provided Login ID, Login Key, Lingotek URL, and
  73. Community ID. Make sure that the Lingotek URL doesn't include any
  74. trailing slashes.
  75. 4.Click "Save configuration"
  76. Dashboard Settings:
  77. 1.Select a Project (or enter a Project ID if the drop-down doesn't appear)
  78. 2.Select a Vault (or enter a Vault ID if the drop-down doesn't appear)
  79. 3.Click "Save configuration"
  80. Drupal Settings:
  81. 1. Set the "Neutral Language" to what language Lingotek should
  82. consider the document when a language isn't specified.
  83. 2. Enable "Overwrite Menus" if you wish our module to update the
  84. menu navigation to point to each translation as they
  85. become available. Pages that haven't finished being translated
  86. will point to the source document. This requires i18n's
  87. Menu Translation module to be installed and enabled.
  88. See the above installation guide for details.
  89. Default Settings:
  90. 1. "Phase Template" is the template that will be selected as
  91. default when creating a new page.
  92. 2. "Machine Translation Engine" is the default
  93. setting for if the page should be published with Google translate
  94. or if the publishing will be deferred until after a professional
  95. translation.
  96. 3. "Available Machine Translation Options" are what options are available
  97. on page creation.
  98. 7. Click "Save configuration"
  99. Usage:
  100. 1. Create a new page. While editing the page, note the Phase Template
  101. setting that has been added. The drop-down is visible if the user has
  102. "phase_template" permissions.
  103. Otherwise, this drop-down is missing and the page creator will be
  104. required to use the default phase template.
  105. 2. Publishing options are also shown, allowing you to choose weather to use
  106. Google translation and immediately publish the results, or if you want
  107. to use professional translators and defer publication until the process
  108. is complete. The drop-down is visible if the user has
  109. "machine_translation" permissions.
  110. Otherwise, this drop-down is disabled and the page creator will be
  111. required to use the default value.
  112. 3. Save the page. A new option, "Lingotek" will appear on
  113. the created page if your user has permissions to "tab".
  114. 4. Click on "Lingotek" where you can see the progress of
  115. the page's translations.
  116. 5. The title only appears once the page
  117. has been fully translated and reviewed (Total % = 100%) or machine
  118. translated or synced.
  119. The title gives a link to the new page with the translated content,
  120. as well as shows that the page has been published. Notice that the
  121. title is also translated as the first segment in the
  122. translation process. If "Overwrite Menus" is enabled in the module,
  123. then the translated title is used as the new title in the translated
  124. menu. The source language, however, retains the page creator's title.
  125. 6. Phase shows us what step in the workflow the document is on.
  126. The first phase of any phase set will need "translation_phase" permissions
  127. to complete. The following phases are only accessible to those with
  128. "review_phase" permissions.
  129. 7. Status is the complete percent for the entire translation process.
  130. 8. Published shows if the node has been marked as published to users.