SDL Proprietary and Confidential SDL Proprietary and Confidential

“Making the leap” Migration from Trados to Studio Paul Filkin SDL

SDL Trados 2007 End of Life

2

Not to be confused with this…. which is not SDL…

• Translation Memories – Upgrading (TMW, TXT, TMX)

– Exporting (fields and attributes) / Importing

– Variable lists, segmentation rules etc.

– Importing Bilingual Files

• Handling work with legacy providers – TTX, Bilingual Doc

– ini files

Bread and butter stuff… and the Studio Platform

3

… the Studio “Platform” is more than just Studio

4

The SDL OpenExchange… current state of affairs

5

57 Apps on the OpenExchange 42 are completely free

29,804 downloads (August 2012)

7,141 app users (August 2012)

396 developers (August 2012)

Alignment Translation Memories

Alignment

SDL Align

MDB SDLTM

SDL Trados WinAlign

TXT

SDLTM

TMW TMX SDLTM

TMW SDLTM

TMX SDLTM

• Alignment can be performed using SDL Trados WinAlign or SDL Align

– SDL Trados Studio 2011 includes SDL Trados WinAlign

– New alignment tool is in the works

Overview Translation Memories

Taking advantage of 2007 bilingual content…

9

• Legacy bilingual content can be converted to 2011 format:

– Upgrade legacy translation memory databases

• Translator’s Workbench TMW or SDL Maintain MDB (SDL Trados 2007 Suite)

– Upgrade TMX (Translation Memory eXchange) file

– Upgrade TXT (another Workbench Translation Memory format)

– Import TMX file into existing 2011 translation memory

– Import legacy bilingual files into existing 2011 translation memory

• TagEditor TTX and SDLX ITD

– Create or update a Translation Memory from legacy bilingual files

• Bilingual Word DOC and TTX

• Translation Memories created in SDL Trados Studio 2011 can be exported as TMX for users of 2007 and Earlier

– Leverage results may differ because there are differences between TMs created with 2011 and those used in 2007

Studio supports many new features in its TM that the legacy tools cannot understand. The loss of these features in a TM export could lead to leverage differences: Context matching Context information (right hand column in Studio Editor) Segment status and properties Comments below segment level Tracked changes Safe tag pairing and Semi-WYSIWYG formatting Extended tag properties Localizable content inside tags Merged files Preview & Verification QuickInserts Merging and splitting of segments Handling of content between segments Save as target/source Locked content Paragraph unit and segment boundaries New or enhanced filters for all file types

Translation Memory vs TMX… what’s the difference?

10

• Translation memory database settings can be upgraded

– Translation memories created in Translator’s Workbench and SDL Maintain

– Settings include:

• Data inside a segment pair (e.g. formatting, leading and trailing tags)

• Project fields and assigned values

• Language Resources

– Segmentation Rules, Abbreviation Lists, Variable Lists and Ordinal Follower Lists

• TMX files contain limited translation memory data

– Information fields, system fields and tags

• Only information fields associated to the TUs in the TMX file will be recognized

• 3rd party TMX may differ in the storage of field and tag information, which could prevent the data being upgraded as part of the output translation memory

– SDL Trados and SDLX TMX files should be imported to a translation memory and upgraded to SDL Trados Studio 2011 if you want to ensure legacy database settings

• Review and confirm translation memory settings before performing upgrade

Upgrading Translation Memories

TM Upgrade in Batch Mode

12

• Note: Translation memory upgrade can be performed in batch mode with multiple formats and language pairs processed

– The upgrade process will create new 2011 translation memories, *.sdltm

– Existing files will not be deleted when upgrade is complete

Primarily with new, native source files or files processed only with SDL Trados Studio

“Clean up” the imported Translation Units

Closer to what the new filters are likely to produce

TM Compatibility Options

13

Primarily with presegmented legacy SDL Trados ITD or TTX files

Better to leave the TM contents unchanged during migration/import, or only minimally changed

• Fix obvious mistakes in the legacy filters

• Adjust for special/changed behavior of the new ITD/TTX filters

• Most cleanup heuristics affect the tags and how they are represented

Primarily used in mixed scenarios

An imported Translation Unit from a known legacy TMX format may lead to, at most, two Translation Units

• Both Translation Units will be imported **SHOULD THEY DIFFER**

• If they don’t differ only one will be imported

• The advantage is recall optimisation, downside is potential multiple translations with different TM match scores

Language Resources

14

Upgrading Language Resources

Appended

• Abbreviation Lists

Overwritten

• Segmentation Rules, Variable Lists and Ordinal Follower Lists

Fields and Attributes

15

Same field name, different types (picklist vs text for example)

Studio will rename one of them for the upgrade

Same field name, same type, different properties (multiple values vs single value or different single values for example)

Studio will retain all the values and create a multiple value property

Connecting to… Translation Memories

Just connect to a Translation Memory

17

• The SDL Trados 2007 TM Provider plugin – Can connect directly to a 2007 Translation Memory (TMW format)

• Filebased TMs is available now

• Server based… still in Beta

– SDL Trados 2007 TM Server

– SDL Trados TeamWorks

Exporting Translation Memories

TMX (Translation Memory eXchange) - exporting

19

• Studio can export a full or filtered TMX

TMX (Translation Memory eXchange) - exporting

20

• But you need to know what the TMX will be used for? – To send to another Studio user, or

– To send to someone using SDL Trados 2007?

• A TMX from Studio works in both cases

• But there are important differences….

TMX (Translation Memory eXchange) - exporting

21

• There is an Open Exchange application called “SDL Translation Memory Management”

– Exports in 2007 TMX format, removes duplicates, reverses the indexes

– Exports placeholder tags converted to generic 2007 tags as Studio does not hold this information

– Custom fields such as attributes and text fields are mapped to 2007 requirements

– Language codes are mapped to those used in Trados 2007 where language variants or locale codes differ

TMX (Translation Memory eXchange) - exporting

22

• Custom fields such as attributes and text fields are mapped to 2007 requirements

TMX (Translation Memory eXchange) – general rule for exporting

23

• To ensure all Fields and Attribute values are correctly exported to SDL Trados 2007 always use the OpenExchange Tool

• To ensure lossless exchange between Studio instances always use Studio

Importing Bilingual Files Translation Memories

• You can import TTX, ITD and of course SDLXLIFF files

• Context information can be imported from these files – Produces higher-quality context matches in a 2011 Translation Memory

• Translation Memory settings (segmentation rules, information and system fields) are not stored within bilingual files – You can apply fields and attributes during the import

• Tags and formatting are not always maintained in TMX format but they will be there in a bilingual file

• Bilingual Doc/RTF files need to be converted to SDLXLIFF first

About importing your Bilingual Files?

25

Bilingual Doc Bilingual Files

Why do we still have these bilingual doc files?

27

• Because the client uses Trados 2007? – To update their TM. Why?

• To be able to analyse successfully and quote for future work?

• Just so we have a record of the translations but we don’t use it?

• Because we always have… don’t ask me why ;-)

– To clean up the target translation. Why? • We review the bilingual and then clean up ourselves

– To work with the fully formatted doc. • Also provides for a horizontal translating and reviewing environment

– Too much process automation around word macros and/or the 2007 SDK… often part of an ISO accreditation

• Because the client uses a Wordfast workflow?

PRE-

TRAN

SLAT

E O

RIG

INA

L

CLE

AN U

P IN

WO

RK

BEN

CH

SAVE

AS

BIL

ING

UAL

DO

C

TRAN

SLAT

E

In terms of analysis is there a substitute when your client uses Trados 2007?

28

01_TEST.doc

Trados

Studio

Wordfast

memoQ

01_TEST.doc

Trados

Studio

Wordfast

memoQ

Translating the files?

29

Creating the Bilingual Doc

30

01_TEST.doc

Trados

Studio

Wordfast

memoQ

Cleanup – all done with SDL Trados Workbench

31

01_TEST.doc

Trados

Studio

Wordfast

memoQ

Cleanup – consistent update to the Translation Memory?

32

01_TEST.doc

Trados

Studio

Wordfast

memoQ

Effectiveness of pretranslate based on the previous cleanup?

33

01_TEST.doc

Trados

Studio

Wordfast

memoQ

• Segmentation differences between the tools

• Some of the filter differences – Formatting differences

– Use of special symbols like this ¬ for example

– Header and Footnote handling

– Non translatable styles – “Do not translate”

– Hyperlink handling

– Maths equations

– Image handling

– Index entries

Why do we see these differences?

34

• Because the client uses Trados 2007? – To update their TM. Why?

• To be able to analyse successfully and quote for future work?

• Just so we have a record of the translations but we don’t use it?

• Because we always have… don’t ask me why ;-)

– To clean up the target translation. Why? • We review the bilingual and then clean up ourselves

– To work with the fully formatted doc. • Also provides for a horizontal translating and reviewing environment

– Too much process automation around word macros and/or the 2007 SDK… often part of an ISO accreditation

• Because the client uses a Wordfast workflow?

If future leverage is required, then there is no substitute, otherwise any tool that can create a bilingual doc will suffice

Studio fared better in this test… but it will be content dependent and even Trados 2007 isn’t perfect!

Substitute with compromises

… legacy converter may be acceptable unless a fully formatted doc is required

… although Wordfast and memoQ both create a file you could use in this way as long as the future analysis is not important

Substitute with compromises

… although Wordfast and memoQ both create a file you could use in this way as long as the future analysis is not important

… or maybe use the Export for External Review as this supports the round trip and supports tracked changes and a horizontal layout

Isn’t a problem on it’s own, depends on the answers to the previous questions

Studio itself may negate many reasons for needing to use these macros in the first place, and the Studio SDK may provide a solution to many more complex requirements… also development effort may be a barrier

Not a Trados concern, just another reason for Bilingual Doc being around…

… but in theory you always have the bilingual doc to start with… or just use Wordfast Classic to prepare the file first as it is inexpensive

So is there an effective substitute for Trados 2007?

35

Bilingual TTX Bilingual Files

Creating Bilingual - TTX Files

37

• You can still use Workbench for this… advantages are – You can pretranslate the TTX first against a legacy TM

– The TTX is fully segmented because a TM is used

Creating Bilingual - TTX Files

38

• If you don’t have Workbench you can use the OpenExchange app called TTXiT… advantages are – You don’t need Trados 2007 at all

– Studio can finish the segmentation for you

• … disadvantages are – The TTX is not fully

segmented based on a Trados 2007 TM

Working with Bilingual files – TTX and ITD

39

40

• Options for TTX Support

– Smart Tag Pairing Mode (placeholders converted to proper tag pairs)

– Compatibility Mode (placeholders as used by TagEditor)

Working with Bilingual files – TTX (improve performance)

Working with Bilingual files – TTX (improve performance)

41

– Generate Document Structure (enabled)

– Generate Document Structure (disabled)

ini files Bilingual Files

Upgrading ini files… or tag settings files

43

• You can upgrade legacy tag settings files created in SDL Trados and SDLX

– SDL Trados INI tag settings files • Supports files created in SDL Trados 7.x, SDL Trados 2006 and SDL Trados 2007

• Used for XML, SGML/HTML filetypes

– SDLX ANL tag settings files • Supports files created in SDLX 2007

• One process to upgrade all the filetypes

Upgrading ini files… or tag settings files

44

Upgrading ini files… what do you get?

45

Creating a new filetype in Studio requires many less rules and ….

Upgrading ini files… old to new?

46

The old….

The new….

SDL Trados 2007 End of Life

47

The King is dead…

… long live the King

Copyright © 2008-2012 SDL plc. All rights reserved.. All company names, brand names, trademarks, service marks, images and logos are the property of their respective owners. This presentation and its content are SDL confidential unless otherwise specified, and may not be copied, used or distributed except as authorised by SDL.