TRANSFERRING
KNOWLEDGE
TT Knowledge Force Software
Best Practice – Localization
December 5, 2012
TT KNOWLEDGE FORCE SOFTWARE - Best Practice: Localization
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
Export the text
(title, description etc.)
to Word/XML
2. Translate the text
3. Import the text
1.
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
Template process
Referenced
sub-processes
Referenced
processes
Location-specific process
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
Content
language
Metadata
Document
content
EN
A document always exists in one
language. This is the document's
content language.
Definition – Variants of a document
Variants
EN
DE
ES
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.
Localization steps, along with the creation of language and locationbased variants
Variants
EN
Duplicate the document as a variant
2. ReRecord the IT simulations
3. Translate via translation interfaces
1.
Location variants
Language variants
DE
Workflow, Roles and
Authorizations
Example: Steps involved in the creation and localization of content
Pre-Production
PM
Production
Authors
Conceptual
design
Post-Production
Specialist
Specialist
acceptance
Creation
Creation
Authors PM
Create
variant
Student
Export
text
Translator
Translation
Translation
Student
Import
text
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.
Action: 'Release directly'
Authorizations for actions (example):
'Release directly' only via Documentation
manager, Process owner
Translation
Access authorization:
Documentation manager
Translator (*)
In progress
Acceptance
Initial status
Access authorization:
Documentation manager
Process owner
Author
Access authorization:
Documentation manager
Process owner
Specialist
(*) Assigned for translation
Translation is performed via the 'In progress' status + direct assignment to the user
Released
Archived
Access authorization:
nobody
Access authorization:
nobody
Another example: Workflow with assignment to a translator
Scenario:
There are translators who work with TT Knowledge Force.
Action: 'Release directly'
Authorizations for specific actions (example):
'Release directly' only via Documentation manager, Process
owner
In progress
Acceptance
Released
Archived
Initial status
Access authorization:
Documentation manager
Process owner
Author
Translator (*)
Access authorization:
Documentation manager
Process owner
Specialist
Access authorization:
nobody
Access authorization:
nobody
(*) Assigned for translation
Translation is performed via the 'In progress' status + direct assignment to the user
nobody
Benefits for the work process - Workspace
Publishing Content
Portal
Web Publisher – Overall language filtering via fallback language
Transferring Knowledge
Recommended TT Knowledge
Force components
 Workflow Manager
 Process Manager
 Web Publisher
 QuickAccess
Want to find out more? Then simply visit us at www.tt-s.com
TTS Offices:
Germany: Heidelberg/Cologne/Berlin
Austria & CEE: Vienna
Amsterdam
Switzerland: Zurich
Spain: Barcelona/Madrid
United Kingdom: London
BLX / Nordics: