• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Managing Translation Workflows for Drupal 7
 

Managing Translation Workflows for Drupal 7

on

  • 5,674 views

 

Statistics

Views

Total Views
5,674
Views on SlideShare
5,534
Embed Views
140

Actions

Likes
5
Downloads
62
Comments
0

2 Embeds 140

http://www.acquia.com 139
https://twitter.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Managing Translation Workflows for Drupal 7 Managing Translation Workflows for Drupal 7 Presentation Transcript

    • MANAGINGTRANSLATIONWORKFLOWS FORDRUPAL 7
    • About MeSuzanne Kennedy, Co-founderTraining, Development, Consultingevolvingweb.ca | 514-844-4930@suzanne_kennedy
    • Multilingual Projects
    • TranslationWorkflows
    • 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?
    • What are Translation Workflows? Translator
    • 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
    • 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
    • Two Types of TextUser-Interface Strings Content
    • Two Types of Text User-Interface Strings ContentIn code + In thedatabase
    • TranslationWorkflows for UIStrings
    • Translation Workflow for UI Strings1. Pull in contributed translations 2. Override translations + from localize.drupal.org add translations of user-defined strings
    • Using TranslationsfromLocalize.Drupal.org
    • UI Strings in Code
    • Use Localize.Drupal.org• Each language has a project• Translators contribute translations in their language• Some projects have better coverage than others.
    • Localize.Drupal.org Project Page
    • 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.
    • Upload .po files to Drupal
    • Localization Update drupal.org/project/l10n_update
    • Localization Update
    • Translation Overview
    • OverridingTranslations inDrupal
    • Overriding a Translation
    • Editing a Translation
    • Editing a Translation
    • Override Translations
    • Use Localization Client drupal.org/project/l10n_client
    • Sharing Your TranslationsAdd your API key from localize.drupal.org to contribute your translations back to the community.
    • Overriding/AddingTranslations Outsideof Drupal
    • Use POEdit to Translate
    • Translations Spreadsheet
    • Translating Outside Drupal CSV with Translations Translator CSV Template .po file for each language
    • Re-using Your Translations
    • Translating User-Defined Strings
    • User-Defined Strings• Strings added in the admin UI (not in code)• For example: Views text
    • Other User-Defined Strings• Block text• Menu items• Field settings
    • Translate Interface
    • Translate Tab
    • Translate Tab
    • User-Defined Strings
    • Challenges• Giving translators access to block/field/ menu configuration• Allowing translators to use all input formats• Changing the original values• Changing the default language
    • TranslationWorkflows forContent
    • Content Translation Workflow1. Author creates a new node 2. Translators adds a translation TranslatorAuthor
    • TranslationWorkflows forContent:Translating in Drupal
    • Translation Interface in Drupal
    • Node-Level vs. Field-Level Translation Field-Level Translation Node-Level Translation
    • Creating a Translation Workflow from Scratch• Permissions for translators• Rules and Flag to trigger translation requests• Views for Translators
    • 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)
    • Typical UI for Translators
    • Challenges• Different UI for Entity Translation/Content Translation (Confusing)• Professional translators need to learn Drupal• Need to build system for reviewing translations
    • Modules for Translation Workflow• Translation Management Tool (TMGMT)• Lingotek Collaborative Translation
    • TranslationWorkflows forContent:TMGMT Module
    • Translation Management Tool (TMGMT) drupal.org/project/tmgmt
    • Translation Management Tool (TMGMT)Drupal
    • Translators• Microsoft (Bing) Translator (machine)• Google Translate (machine)• Nativy (human)• MyGengo (human)• Supertext (human)• One Hour Translation (human)
    • Microsoft Translator
    • Microsoft Translator
    • Requesting Translations
    • Choosing a Translator
    • Review Translation
    • Review Translation
    • Accepted Translation Appears
    • Translate in Bulk
    • Translation ‘Jobs’
    • 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
    • TranslationWorkflows forContent:Lingotek Module
    • Lingotek Moduledrupal.org/project/lingotek
    • LingotekDrupal Individual Translator
    • Create a Lingotek Account
    • Connect to Machine Translation Tool
    • Create a ProjectCreate a new project for each Drupal website
    • Lingotek Translation Per Content TypeDisables manual translation of content
    • Lingotek Translation Tool• Enables translation at the field-level• Need to flag fields as being translatable
    • Send a Node for Translation
    • Translating a NodeSwitch the site to French, and you’ll see a message:Click on the link to go to the Lingotek Translation UI
    • Updating the TranslationIn order to accept the translation and publish it to the site, you have to click ‘Update’.
    • Translation Appears
    • Project Status
    • 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
    • Conclusion
    • 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
    • Training Program We offer public and private Drupal training sessions evolvingweb.ca/traininghttp://munich2012.drupal.org/program/training/building- multilingual-websites-drupal-7