Best Practice – Localization TT Knowledge Force Software December 5, 2012

TT KNOWLEDGE FORCE SOFTWARE - Best Practice: Localization

Summary Thanks to TT Knowledge Force's 'single sourcing' concept, you can create and localize documentation and e-learning as part of a single integrated production process.  Translate content into 30 languages  Workflow control for the translation process  Export and import all text, incl. the word count for cost calculation  Export and import other resources that are used – such as PowerPoint files or external text that has been imported into Flash  Supports the XLIFF file format used by translation programs  ReRecording with an automatic update of standard text  Multilingual templates with AutoTexts  Filter chains and fallback languages in the Web Publisher

Agenda Multilingual Structures - Process View Language-Sensitive Structures – Course View Translating Content Workflow, Roles and Authorizations Publishing Content

Multilingual Structures Process View

Multilingual Structure - Process Structure The title, description and other metadata of a process object can be maintained in a language-sensitive manner.

Translating multilingual structures via export and import 1. Export the text (title, description etc.) to Word/XML 2. Translate the text 3. Import the text

Author view of processes > The Author view displays all documents in all languages that are associated with a particular process object. > Sort criteria: document type / language / followed by alphabetical order

Reusing sub-processes Location-specific process Template process Referenced sub-processes Referenced processes

Process tree in the Portal (Web Publisher) > Metadata and documents are displayed in the selected language > Restriction possible via role > Fallback languages can be set via customizing

Language-Sensitive Structures - Course View

Language-sensitive structures in the Course view: Author view > The content language is maintained as a single item of metadata for each course or topic. > The documents are stored in the desired languages.

Course view in the Web Publisher

Translating Content

Definition – A document's metadata and content A document always exists in one language. This is the document's content language. Content language Metadata Document content EN

Definition – Variants of a document Variants Variants are used to group documents with the same content but in different languages. In this example, the language of the metadata is the very same as the language of the document's content. EN DE ES

Variants Localization steps, along with the creation of language and location- based variants 1. Duplicate the document as a variant 2. ReRecord the IT simulations 3. Translate via translation interfaces

Workflow, Roles and Authorizations

Example: Steps involved in the creation and localization of content ProductionPost-Production Translation Translator Pre-Production Create variant Create variant Export text Export text AuthorsStudent Import text Import text Student Creation Specialist acceptance Authors Specialist Conceptual design PM Creation Translation

Workflow with 'Translation' status Scenario: When a document has the 'Translation' status, the files that have to be translated are exported and passed on to the translator. Once translated, the files are re-imported. In progress Initial status Access authorization: Documentation manager Process owner Author In progress Initial status Access authorization: Documentation manager Process owner Author Acceptance Access authorization: Documentation manager Process owner Specialist Acceptance Access authorization: Documentation manager Process owner Specialist Released Access authorization: nobody Released Access authorization: nobody Archived Access authorization: nobody Archived Access authorization: nobody Action: 'Release directly' Authorizations for actions (example): 'Release directly' only via Documentation manager, Process owner Translation Access authorization: Documentation manager Translator (*) Translation Access authorization: Documentation manager Translator (*) (*) Assigned for translation Translation is performed via the 'In progress' status + direct assignment to the user

Another example: Workflow with assignment to a translator Scenario: There are translators who work with TT Knowledge Force. nobody In progress Initial status Access authorization: Documentation manager Process owner Author Translator (*) In progress Initial status Access authorization: Documentation manager Process owner Author Translator (*) Acceptance Access authorization: Documentation manager Process owner Specialist Acceptance Access authorization: Documentation manager Process owner Specialist Released Access authorization: nobody Released Access authorization: nobody Archived Access authorization: nobody Archived Access authorization: nobody (*) Assigned for translation Translation is performed via the 'In progress' status + direct assignment to the user Action: 'Release directly' Authorizations for specific actions (example): 'Release directly' only via Documentation manager, Process owner

Benefits for the work process - Workspace

Publishing Content Portal

Web Publisher – Overall language filtering via fallback language

TTS Offices:Germany: Heidelberg/Cologne/BerlinSwitzerland: ZurichUnited Kingdom: London Austria & CEE: Vienna Spain: Barcelona/Madrid BLX / Nordics: Amsterdam Recommended TT Knowledge Force components  Workflow Manager  Process Manager  Web Publisher  QuickAccess Want to find out more? Then simply visit us at

TTS Offices:Germany: Heidelberg/Cologne/BerlinSwitzerland: ZurichUnited Kingdom: London Austria & CEE: Vienna Spain: Barcelona/Madrid BLX / Nordics: Amsterdam Recommended TT Knowledge Force components  Workflow Manager  Process Manager  Web Publisher  QuickAccess

Variants Creating a language variant and localization steps 1. Duplicate the document as a variant 2. ReRecord the IT simulations 3. Translate via translation interfaces EN DE