Challenges in software localization, SDL Trados Studio vs. SDL Passolo,

1. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
Translating
Software with
SDL Passolo?
Daniel Zielinski, Loctimize GmbH
ETUG 2014, Berlin

2. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
Software localization and
documentation translation
are different!

3. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
SDLTrados Studio is not
the (only) solution!

4. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
Why?

5. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
Document types are different!
Documentation
Self-contained
Sentence-based
Surrounding content =
context
Software
Not self-contained
String-based
IDs = context
UI string separate unique
linguistic asset class

6. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
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

7. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
Workflows are different!
TestingLocalization
TestingLocalizationDevelopment
Development
TestingLocalizationDevelopment
TestingLocalizationDevelopment
TestingLocalizationDevelopment
TestingLocalizationDevelopment
TestingLocalizationDevelopment
TestingLocalizationDevelopment
TestingLocalizationDevelopment
Waterfalll model
Iterative model
Continuous model

8. THE SOLUTION: SDL PASSOLO 2011?
© 2013 Loctimize GmbH 8

9. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
SDL Passolo 2011 - Editions
Professional
Edition
Team Edition
Collaboration
Edition
Translator
Edition
Essential
Edition

10. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
Supported file formats
• Binary files (EXE, DLL, SYS, OCX) with
Windows standard resources
(16, 32, 64 bit)
• Windows resource files
(RC, RC2, DLG)
• Visual BASIC < 6 project files (VBP)
and forms (FRM)
• Binary files for Windows Mobile
(Windows CE, Pocket PC, Windows
Mobile)
• Microsoft installer files (MSI)
• HTML files and HTML derivates
• Unix/Linux Portable Object files (PO)
• Mono- and multilingual XML files
(incl. XLIFF)
• Monolingual text files
• Microsoft .NET binary files
(assemblies) for all frameworks
• Microsoft .NET resource files
(RESX, RESOURCE)
• Borland Delphi/C++ Builder binary
files (EXE, DLL, BPL)
• Java resource files
(PROPERTIES), source files
(JAVA), binary files (CLASS), archive
files (JAR)
• Binary files for Palm OS
applications (PRC)
• ODBC databases (Access, SQL
Server, Oracle, MySQL, IBM DB 2)

11. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
Internationalization support
Pseudo-translation,Testing
Source optimization

12. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
Simulate translation

13. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
Localization project management
Locking, hiding strings
Unifying strings
Adding meta data
Statistics
Pre-translation
Integration with
Studio & MultiTerm
MachineTranslation
Task assignment via
translation bundles
Cascading projects
Sub-projects
Easy update
Change notifications
History & rollback
Alignment
Leverage

14. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
Acrolinx add-in

15. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
Localization workflow with agile
development
Developer
Project
file
External
Translator
Internal
Translator
Reviewer
Localization
Manager
Translation
Bundles
Localization
Kit
Creating ProjectProject Update
Export
New/Changedtextentries
FTP
Invitation
E-Mail

16. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
Translation & review features
WYSIWYG preview
Translation
pane
Navigation
pane
Translation results window

17. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
Quality assurance
File type specific checks
Placeholders, inline patterns, layout (size, overlapping …)
Custom checks via macros or add-ins

18. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
Engineering
Generate localized software
Knowing conventions: file structure, naming…
No access to build environment required

19. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
Automation & Customization
Via macros or add-ins
Integrate into build environment (nightly builds)

20. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
Solution: SDL Passolo and
SDLTrados 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
– ThroughTMs and term bases
– But, not all strings are not segments
– But, UI elements are not terms

21. ETUG 2014, May 16, 2014 – Daniel Zielinski, Loctimize
Questions?
Daniel Zielinski, Loctimize GmbH
zielinski@loctimize.com
www.loctimize.com
facebook.com/Loctimize
twitter.com/loctimize