Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Managing Translation Workflows in Drupal 7

1,879 views

Published on

Are you building a multilingual Drupal website and wondering how you're going to get everything translated? One of the major challenges of setting up a multilingual site is getting translations into Drupal, and keeping them up-to-date. Whether you're working with a team of translators or translating the site yourself, there are lots of tools and techniques that you can use to improve your translation workflow.

Published in: Technology, Business
  • Be the first to comment

Managing Translation Workflows in Drupal 7

  1. 1. MANAGINGTRANSLATIONWORKFLOWS FORDRUPAL 7
  2. 2. About MeSuzanne Kennedy, Co-founderTraining, Development, Consultingevolvingweb.ca | 514-844-4930@suzanne_kennedy
  3. 3. Multilingual Projects
  4. 4. TranslationWorkflows
  5. 5. Goal of Translation Workflows• Translation is: • Time-consuming • Expensive• How can you speed up the process and reduce the amount of text to be translated?
  6. 6. What are Translation Workflows? Translator
  7. 7. Benefits of an External Translation Tool• Easier for translations to learn• Tracks cost of translation• Provides integration with machine/ community-sourced translations• Advanced features (translation memory)• Integration with multiple translation teams
  8. 8. Benefits of Doing Translation in Drupal• Less overhead• Less expensive• Add translations as you go• Takes advantage of Drupal’s content management tools• Easier to provide context
  9. 9. Two Types of TextUser-Interface Strings Content
  10. 10. Two Types of Text User-Interface Strings ContentIn code + In thedatabase
  11. 11. TranslationWorkflows for UIStrings
  12. 12. Translation Workflow for UI Strings1. Pull in contributed translations 2. Override translations + from localize.drupal.org add translations of user-defined strings
  13. 13. Using TranslationsfromLocalize.Drupal.org
  14. 14. UI Strings in Code
  15. 15. Use Localize.Drupal.org• Each language has a project• Translators contribute translations in their language• Some projects have better coverage than others.
  16. 16. Localize.Drupal.org Project Page
  17. 17. What is a .po file?• Text file storing the original text and the translations.• A .pot file is a template file, containing only the original text to be translated.
  18. 18. Upload .po files to Drupal
  19. 19. Localization Update drupal.org/project/l10n_update
  20. 20. Localization Update
  21. 21. Translation Overview
  22. 22. OverridingTranslations inDrupal
  23. 23. Overriding a Translation
  24. 24. Editing a Translation
  25. 25. Editing a Translation
  26. 26. Override Translations
  27. 27. Use Localization Client drupal.org/project/l10n_client
  28. 28. Sharing Your TranslationsAdd your API key from localize.drupal.org to contribute your translations back to the community.
  29. 29. Overriding/AddingTranslations Outsideof Drupal
  30. 30. Use POEdit to Translate
  31. 31. Translations Spreadsheet
  32. 32. Translating Outside Drupal CSV with Translations Translator CSV Template .po file for each language
  33. 33. Re-using Your Translations
  34. 34. Translating User-Defined Strings
  35. 35. User-Defined Strings• Strings added in the admin UI (not in code)• For example: Views text
  36. 36. Other User-Defined Strings• Block text• Menu items• Field settings
  37. 37. Translate Interface
  38. 38. Translate Tab
  39. 39. Translate Tab
  40. 40. User-Defined Strings
  41. 41. Challenges• Giving translators access to block/field/ menu configuration• Allowing translators to use all input formats• Changing the original values• Changing the default language
  42. 42. TranslationWorkflows forContent
  43. 43. Content Translation Workflow1. Author creates a new node 2. Translators adds a translation TranslatorAuthor
  44. 44. TranslationWorkflows forContent:Translating in Drupal
  45. 45. Translation Interface in Drupal
  46. 46. Node-Level vs. Field-Level Translation Field-Level Translation Node-Level Translation
  47. 47. Creating a Translation Workflow from Scratch• Permissions for translators• Rules and Flag to trigger translation requests• Views for Translators
  48. 48. Permissions for Translation• Content Translation: Translators need to be able to create content• Entity Translation: Permission to edit the Entity Type• No granular translation permissions per content type (use i18n_access)
  49. 49. Typical UI for Translators
  50. 50. Challenges• Different UI for Entity Translation/Content Translation (Confusing)• Professional translators need to learn Drupal• Need to build system for reviewing translations
  51. 51. Modules for Translation Workflow• Translation Management Tool (TMGMT)• Lingotek Collaborative Translation
  52. 52. TranslationWorkflows forContent:TMGMT Module
  53. 53. Translation Management Tool (TMGMT) drupal.org/project/tmgmt
  54. 54. Translation Management Tool (TMGMT)Drupal
  55. 55. Translators• Microsoft (Bing) Translator (machine)• Google Translate (machine)• Nativy (human)• MyGengo (human)• Supertext (human)• One Hour Translation (human)
  56. 56. Microsoft Translator
  57. 57. Microsoft Translator
  58. 58. Requesting Translations
  59. 59. Choosing a Translator
  60. 60. Review Translation
  61. 61. Review Translation
  62. 62. Accepted Translation Appears
  63. 63. Translate in Bulk
  64. 64. Translation ‘Jobs’
  65. 65. Benefits of TMGMT• Works with Entity and Node Translation• Easy to configure• Allows you to hook into your own translation service, if you’re a developer• Translation of UI Strings on its way (blocks, menus, etc.)• Translation UI in Drupal on its way
  66. 66. TranslationWorkflows forContent:Lingotek Module
  67. 67. Lingotek Moduledrupal.org/project/lingotek
  68. 68. LingotekDrupal Individual Translator
  69. 69. Create a Lingotek Account
  70. 70. Connect to Machine Translation Tool
  71. 71. Create a ProjectCreate a new project for each Drupal website
  72. 72. Lingotek Translation Per Content TypeDisables manual translation of content
  73. 73. Lingotek Translation Tool• Enables translation at the field-level• Need to flag fields as being translatable
  74. 74. Send a Node for Translation
  75. 75. Translating a NodeSwitch the site to French, and you’ll see a message:Click on the link to go to the Lingotek Translation UI
  76. 76. Updating the TranslationIn order to accept the translation and publish it to the site, you have to click ‘Update’.
  77. 77. Translation Appears
  78. 78. Project Status
  79. 79. Benefits of Lingotek• Translation memory• Sophisticated translation workflow• Advanced feature set (i.e. settings for tokens to ignore, etc.)• Community-sourced translations• Provides a UI for professional translators
  80. 80. Conclusion
  81. 81. What to Take Away• Map out your translation workflow before you start• Talk to your translators and figure out their needs/role• Use the Localization Update module• Plan for adding more languages• Take advantage of translation management modules
  82. 82. Training Program We offer public and private Drupal training sessions evolvingweb.ca/traininghttp://munich2012.drupal.org/program/training/building- multilingual-websites-drupal-7

×