Translating Software with SDL Passolo?

ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize

TranslatingSoftware withSDL Passolo?Daniel Zielinski, Loctimize GmbHETUG 2014, Berlin


Software localization and documentation translation are different!


SDL Trados Studio is not the (only) solution!


Why?


Document types are different!

Documentation Self-containedSentence-basedSurrounding content = context

Software Not self-containedString-basedIDs = contextUI string separate unique linguistic asset class


Developers are different!Human language no core topic

Create linguistic content in different way

Linguistic quality lower

Content changed more often(code & linguistic data)

High influence on translatability


Workflows are different!

TestingLocalizationTestingLocalizationDevelopment

Development

TestingLocalizationDevelopmentTestingLocalizationDevelopment

TestingLocalizationDevelopment

TestingLocalizationDevelopmentTestingLocalizationDevelopmentTestingLocalizationDevelopmentTestingLocalizationDevelopment

Waterfalll model

Iterative model

Continuous model

THE SOLUTION: SDL PASSOLO 2011?

© 2013 Loctimize GmbH 8


SDL Passolo 2011 - Editions

ProfessionalEdition

TeamEdition

CollaborationEdition

TranslatorEdition

EssentialEdition


Supported file formats• Binaryfiles (EXE,DLL,SYS,OCX)with

Windowsstandard resources (16,32,64bit)

• Windowsresource files (RC,RC2,DLG)

• VisualBASIC<6project files (VBP)and forms (FRM)

• Binaryfiles for WindowsMobile(WindowsCE,PocketPC,WindowsMobile)

• Microsoftinstaller files (MSI)• HTMLfiles and HTMLderivates• Unix/LinuxPortableObject files (PO)• Mono- and multilingualXMLfiles

(incl.XLIFF)• Monolingualtext files

• Microsoft.NETbinary files(assemblies)for allframeworks

• Microsoft.NETresource files(RESX,RESOURCE)

• BorlandDelphi/C++Builder binaryfiles (EXE,DLL,BPL)

• Javaresource files (PROPERTIES),source files (JAVA),binary files(CLASS),archive files (JAR)

• Binaryfiles for PalmOSapplications (PRC)

• ODBCdatabases (Access,SQLServer,Oracle,MySQL,IBMDB2)


Internationalization supportPseudo-translation, TestingSource optimization


Simulate translation


Localization project management

Locking, hiding stringsUnifying stringsAdding meta data

StatisticsPre-translationIntegration withStudio & MultiTermMachine Translation

Task assignment via translation bundles

Cascading projectsSub-projects

Easy updateChange notificationsHistory & rollback

AlignmentLeverage


Acrolinx add-in


Localizationworkflowwithagiledevelopment

Developer

Projectfile

ExternalTranslator

InternalTranslator

Reviewer

LocalizationManager

TranslationBundles

LocalizationKit

CreatingProjectProjectUpdate

Export

New

/Cha

nged

textentrie

s

FTP

InvitationE-Mail


Translation & review features

WYSIWYG preview

Translation pane

Navigationpane

Translation results window


Translation & review features


Quality assuranceFile type specific checks

Placeholders, inline patterns, layout (size, overlapping …)

Custom checks via macros or add-ins


Engineering

Generate localized softwareKnowing conventions: file structure, naming…No access to build environment required


Automation & CustomizationVia macros or add-insIntegrate into build environment (nightly builds)


Solution: SDL Passolo and SDL Trados Studio

• Distinct solutions for documentation translation and software localization– Allows optimal workflows– Reduces friction between software development and localizers– Streamline communication between developers and localizers– Control linguistic quality in source and target languages

• Sharing of assets – Through TMs and term bases– But, not all strings are not segments– But, UI elements are not terms


Questions?Daniel Zielinski, Loctimize [email protected]

facebook.com/Loctimizetwitter.com/loctimize

Translating Software with SDL Passolo?

Documents

Transcript of Translating Software with SDL Passolo?