Engineering Your Product Information for Local Markets

STC CarolinaTom KnuppSeptember 19, 2013

ENGINEERING YOUR PRODUCT INFORMATIONFOR LOCAL MARKETS

2 05/01/2023 Teradata Confidential

Engineering Product Information for Local Markets

• Defining Globalization Tasks> Internationalization, localization and globalization

• Developing a Globalization Strategy> Internal and external globalization partnerships

• Identifying Target Markets> Global and local markets for language selection

• Writing for Translation> A development environment for localization

• Tools for Optimizing Localization Processes> Developing an in-house localization toolset

AGENDA


DEFINING GLOBALIZATION TASKS

i18n

L10n

G11n

Internationalization• Character set• Locale• Localizability

Localization• UI• Documentation• Online Help

Globalization


Globalization (G11n) =• Internationalization + Localization

Internationalization (i18n)> International character set support

– Universal character set (Unicode)> Locale and cultural awareness

– Locale-sensitive code for international data formatting– Complex scripts and RTL awareness– Input and fonts

> Localizability– Multiple languages for single application repository– Develop localization kit

> Globalization test– Test all globalization features shown above

Localization (L10n)> Translation

– User interface (resource strings)– Documentation– Online help– Marketing collateral

> Localization test

Some Working Definitions

Design &

Develop

Deploy


Globalization Engineering Partnerships

• Internal Partnerships: Product Design> Product Management> Engineering > Test Engineering> Information Engineering (Tech Pubs)> Local Field Engineers

• External Partnerships: Product Deployment> Localization Service Providers (LSPs)

DEVELOPING A GLOBALIZATION STRATEGY


• Partnering with Product Management> Target market identification> Defect escalation

• Partnering with Engineering> Internationalization (i18n) best practices

– UI labels in resource strings– “Language neutral” design• Support all locales without localization

– Design UI without using string concatenation• Use parameterized strings in complete sentences

• Partnering with Test Engineering> Localization (L10n) verification best practices

– Globalization test in seeded and/or fully localized environment– Regression test for critical i18n/L10n issues– Completed before commercial availability of source-language product

Internal Partnerships: Product Design


• Partnering with Information Engineering (Tech Pubs)> Topic-Based Authoring for Translation

> Localized Documentation Verification> Localized Online Help Generation and Verification

• Partnering with Local Field Engineers> In-Country Terminology Review

Internal Partnerships: Product Design

Architect in DITA &

XML

Develop in DITA &

XML

Compose PDF & help

output


• Partnering with Localization Service Providers (LSPs)> UI/Document Localization and Verification

– UI Translation– UI Language Verification Test (LVT)– Document Translation– Technical Services

External Partnerships: Product Deployment


Language Selection

• Global Market> Transnational languages

• Local Markets> National languages> Secondary languages> Market or industry language(s)

IDENTIFYING TARGET MARKETS


• Transnational Languages> Influence widely acknowledged to transcend national boundaries

> Other possible candidates– Italian, Korean, Swahili, Dutch, Turkish, Tamil, Farsi, Punjabi

Language Selection: Global Market

English French Spanish Mandarin Russian Arabic

N & S America, Europe, Africa,Asia, Australia,

Oceania

Europe, Africa,

N America

Europe, N, S & Ctrl.

America, Africa

E & SE Asia E Europe, N & Ctrl

Asia

Middle East, N & E Africa

Portuguese German Japanese Hindi-Urdu Bengali Malay-Indonesian

S America, Europe, Africa, Asia, Oceania

N, Ctrl & E Europe

E Asia S Asia S Asia SE Asia, Oceania

Arabic

Arabic

English

English

English

English

English

English

English

English

Mandarin

Mandarin

Distribution of the “Transnational Dozen”

Arabic

Arabic

Mandarin

Bengali

Hindi-Urdu

Malay-Indonesian

Teradata Confidential11 05/01/2023


• National languages> May nevertheless represent a significant market

– Examples: Vietnamese, Polish, Thai, Hungarian, Tagalog, Swedish> National lingua franca or simply official status among many

recognized?– “Official” may be local to a state or region rather than nationwide– Number of speakers alone should not be the sole criteria• India: Hindi (lingua franca) vs. Telugu (75 million speakers) and 20 others

• Secondary languages> Belgium

– French (language of government) before Dutch (most widely spoken)?• Market or industry language(s)

> Might not be the most predominant local language> Indian software market

– English (language of technology) rather than Hindi (national language)

Language Selection: Local Markets


A Development Environment for Localization

• Localization Advantages of DITA> Reuse to reduce cost and time to market

• Localization Advantages of a CCMS> Translation processing, workflow and tracking

WRITING FOR TRANSLATION


• Reduce localization cost> Eliminate desktop publishing costs in languages targeted for

localization through the automated application of styles> Isolate and translate only new and changed topics

• Reduce time to market> Write/review/translate in parallel

• Reuse> Reuse content across products and programs> Redeploy content in different distribution channels> Translate topic once, reuse many times

Localization Advantages of DITA


• Global processing> Authorized users can perform batch jobs to make global changes to

content, structure, attribute values within a specified scope• Supports translation workflow

> Identifies content that has been translated previously, and can select only changed topics or elements for subsequent translation.

> Can integrate workflow with common translation tools and vendors> Reloads translated source into the repository for composition into target

languages and formats• Tracks translated content for multiple projects and

languages> Maintains a relationship between English source content and every target

language, allowing selective translation into target languages per product release, based on business requirements.

Localization Advantages of a CCMS


Developing an In-House Localization Toolset

• Translation Repository• In-House Translation Migrator

> From the same product or component• In-House Translation Recycler

>From a different product or component• In-House Automated Translator

TOOLS FOR OPTIMIZING LOCALIZATION PROCESSES


Translation Repository (XML)> Translation Memory designed for translation migration and recycling

– Common format for all applications and documentsIn-House Translation Migrator

> Migrate translations from the same product or component– Reuse UI strings, metadata tables, structured documentation (DITA, RoboHelp)– When translation source has not changed:• Automatically migrate target segment from old version to new version

– Send hybrid file (composed of both source and target segments) to vendor• Log enables better cost estimation for new translation

In-House Translation Recycler> Recycle translations from a different product or component (e.g., UI to doc)

– Reuse UI strings, metadata tables, structured documentation (DITA, RoboHelp)– Share existing translations from repositories without involving:• Localization service providers (LSPs)• Translation memory software (such as Trados)

In-House Automated Translator> Communicate to online translator via in-house interface> Automatically translate new/modified strings without cost (quantity restrictions)

– Support interactive and batch mode

Developing an In-House Localization Toolset


Storing Previous Translations for Reuse

Resource Files

(English)Translation

Resource Files

(Translated)

• Translation Repository (XML)> Allows you to reuse or share translations among different

products/components

Savings Driver


Migrating Unchanged Target to New Version

Resource Files

(English)

In-House Translation Migrator

New Translation

Resource Files

(Translated)

• In-House Translation Migrator> From the same product or component

– If nothing has been changed in the English resource string, translations can be automatically migrated from the old version to the new version

– After receiving migrated source file, LSPs need only translate the new and modified strings

Savings Driver


Recycling Reusable Translations

Resource Files

(English)

In-House Translation

Migrator


RecyclerNew

TranslationResource

Files (Translated)

• In-House Translation Recycler> From a different product or component

– Reuse translations across deliverables without having to rely on:• Translation memory• Localization service provider(s)

Savings Driver


Automating Translation

Resource Files

(English)


Migrator

In-House Pre-

Translator

In-House Automated Translator

ValidationResource

Files (Translated)

• In-House Automated Translator> Tool providing an interface to an online translator> LSP’s role changes as you start to translate everything in-house> New LSP role focuses on reviewing and editing the translation

Savings Driver


Engineering Your Product Information for L10n

CCMS/DITA (IE)

Migrate/ Recycle/

Automate Translation

(G11N)

Localization Cost

Savings

Design &

Develop

Deploy


Preguntas

質問

Fragen

вопросы

Perguntas

问题

Questions?

Engineering Your Product Information for Local Markets

Documents

Transcript of Engineering Your Product Information for Local Markets