Introducing….SDL WorldServer 2011SDL WorldServer 2011

Andrew ThomasSDL WorldServer Product ManagerSDL WorldServer Product Manager

Introducing SDL WorldServer 2011

Objectives

New Features & Enhancements

Installation Considerations

D t d F tDeprecated Features

Product Demonstration

The Year Ahead…

2

SDL WorldServer 2011 Objectives

The only Enterprise-class translation management solution to offer complete localization supply chain integration with SDL Trados Studio

Complete alignment with SDL Trados StudioComplete alignment with SDL Trados Studio Same file processing and segmentation Same translation memory capabilities and leverage Same project scoping and costing

Provides for a complete localization supply chainProvides for a complete localization supply chain Eliminates technology friction between Enterprise and LSP and

Translator Fulfills promise of using SDL WorldServer as the default costing tool

3

Fulfills promise of using SDL WorldServer as the default costing tool without forcing the supply chain to use a mandated CAT tool

New Features & Enhancements

File Type Support (FTS) ServerBilingual Content Model (BCM) & NativeBilingual Content Model (BCM) & Native SDLXLIFF supportProject Scoping ModesProject Scoping ModesAdditional Enhancements

4

File Type Support (FTS) Server

Segmentation Alignment Ensures segmentation data alignment between SDL WorldServer and

SDL Trados Studio Using FTS Server, SDL WorldServer now generates a Bilingual Content

Model (BCM) structured the same as SDL Trados Studio

Adds support for important new file types Microsoft Office 2010 Microsoft Office 2010 Adobe InDesign IDML Adobe InCopy ICML

Allows for streamlining file processing development efforts Future file type support will be delivered as a shared application service

5

Future file type support will be delivered as a shared application service to SDL Trados Studio and SDL WorldServer

File Type Support

Adobe Products FrameMaker MIF

QuarkXPress Export

InDesign CS4-CS5 IDML InCopy CS4-CS5 ICML

Generic Text Rich Text Format (RTF) Plain

HTML, XHTML 1.1 JSP/ASP

Delimited

XMLMicrosoft Office Microsoft Excel

• 2000-2003, 2007-2010

XML Microsoft .NET Resources OASIS DITA OASIS DocBook 4 5

Microsoft PowerPoint• XP-2003, 2007-2010

Microsoft Word• 2000 2003 2007 2010

OASIS DocBook 4.5 W3C ITS Compliant Custom / Any

6

• 2000-2003, 2007-2010

Configuration Comparison

WorldServer 9.x Filter Studio File Type

7

Important Changes

Terminology Change Existing SDL WorldServer 9.x Filters = WorldServer Filters New FTS Filters = Studio File Types

SDL FTS Server Installation Microsoft Windows Server 2003 is required Microsoft Windows Server 2003 is required

• Requirement is similar to current Microsoft Office 2003 filtering requirement, though more mission critical as it applies to all segmentation

Stand alone component p Deployable in a cluster and works with mixed OS environment

WorldServer Filters WorldSer er Filters contin e to be s pported b t not enhanced WorldServer Filters continue to be supported but not enhanced

• Existing enhancement requests will be considered for equivalent Studio File Types

No new WorldServer Filters will be introduced

8

No new WorldServer Filters will be introduced

BCM & Native SDLXLIFF Support

The Bilingual Content Model (BCM) replicates the segmented data structure used in SDL Trados Studio

BCM allows the export of SDLXLIFF, the native bilingual file format created and processed by SDL Trados Studioo at c eated a d p ocessed by S ados Stud o

Rich markup information preserved for improved leverage Future releases will allow for advanced markup editing, better MT

integration Lays foundation for more advanced TM features and placeholder editing

9

BCM and the TM

Existing SDL WorldServer 9.x TM Makes no special use of extended BCM information during leverage

• Stored, but not used• Consistency rules enforced

Default for Upgrade Installations

BCM and TM TMs may contain a mixture of “legacy” and “BCM” translation units BCM stores extended tag information BCM stores extended tag information BCM created when using Studio File Types

Placeholders Placeholder numbers link to “hidden” BCM tags Extended UI in Translation Unit Editor

10

BCM Rich Markup Data

11

Project Scoping Modes

Maintaining SDL WorldServer 9.x Scoping Mode Retains all previous functionality in SDL WorldServer 9.x Supports existing customers to ensure never losing any leverage

unintentionally

Introducing an SDL Trados Studio-aligned Scoping Modeg g p g Aligns word counting, TM scoring, and scoping configuration Ensures smoothest supply chain when using SDL Trados Studio Many intricate parts “under the hood” simplified in one project-level Many intricate parts under the hood simplified in one project level

choice

Represents the massive port of SDL Trados TM capabilitiesAll f fl ibl TM f t / ti i f tAllows for more flexible TM features/options in a future release

12

Studio-aligned Scoping Mode

ICE Matches Not affected by scoping mode Reported and displayed as Perfect

Repetitions WorldServer 9.x mode requires

segments to be identical Reported and displayed as Perfect Matches in Studio

• Will be changed to Context Match in a future release

Auto-Translate

g Studio-aligned uses repairs to increase

repetitions• “I ate 5 applies.” & “I ate 6 apples.” are

repetitions

Applies to number-only, measurement-only, URL-only segments

Auto-Substitution and Auto-Localization

Penalties Missing formatting penalty

• Lookup segment has no tags, but TU doesLocalization

Numbers, Measurements, Date, Time Auto-substitution: “repair” Auto-localization: adapt to target

language during auto substitution

Different formatting penalty• Tags cannot be fully aligned between

lookup and TU source segment

Auto-substitution penaltyA li d if A t S b tit ti li dlanguage during auto-substitution

• 5,000.123 -> 5.000,123• January 20, 2010 -> 20. Januar 2010

Language Support & Fallbacks

• Applied if Auto-Substitution was applied

Multiple exact match penalty• Shared with WorldServer 9.x mode

PenaltiesS

13

Language fallback for region-neutral cultures

• “en” -> “en-US”, “fr” -> “fr-FR”, …

• WorldServer 9.x: 0.00-1.00• Studio-aligned: 0-100

Important Changes

Performance Implications Studio-style tokenization & matching are more expensivey g p

• Particularly if segments involved contain lots of paired tags Performance impact around x2-3

• Detailed analysis WIP• Detailed analysis WIP

Disabled in Studio-aligned Scoping ModeDisabled in Studio aligned Scoping Mode All WorldServer 9.x penalties and repairs Customizations:

• Repair engines • Word breakers • Auto-translate components

14

Project Scoping Alignment

WorldServer 2011 Scoping Report

St di 2009 A l i St ti tiStudio 2009 Analysis Statistics

15

Additional Enhancements

Ad Hoc Job Cleanup Removes old ad hoc data during garbage collection Increases database performance

BWB Error Reporting Improvements Adds permission for clearing reported errors Allows comments to be logged against locked segments

Bulk User Management Updates Increases performance when editing users already assigned to a group

Infrastructure Changes Oracle 11G Supported Microsoft Internet Explorer 8 Supported

SDK Changes Updated samples

• Text Changed, Calculate Repetitions, and Generate Scoping Report

16

New tokenization (word breaking) infrastructure File Type Support can be called programmatically the same as WS Filters

Installation Considerations

Upgrade Database schema changes, scripts provided as usual FTS must be installed on Microsoft Windows Server 2003

Settings and Configuration g g Performance metrics still being developed No TM or SDL WorldServer Filter migration offered in this release Database size requirements increased x3 due to content rich BCM Database size requirements increased x3 due to content rich BCM

• Segments binary file types more efficiently• Aggressive garbage collection mitigates somewhat

17

Deprecated Features

Oracle 9 Removing support after superseding support for Oracle 11 Continues standard process of supporting two versions of backend

system components

Desktop Workbenchp No longer distributed with releases Still functions with previous releases Still functions with current release under specific legacy condition: Still functions with current release under specific legacy condition:

• Any project using SDL WorldServer 9.x Filters and 9.x Project Scoping mode• Not supported in any other use case scenario for SDL WorldServer 2011

18

More on Desktop Workbench

Why now? SDL WorldServer 2011 provides for a similar DWB experience with SDL

Trados Studio FTS and new TM features won’t work with DWB Upcoming SDL Trados Studio 2011 release will deliver remaining

“missing pieces”• SDL Studio Express

– Freely distributable for existing customers• Live connection to SDL WorldServer

– Project export/import– TM: leverage, concordance, and update

19

Product DemonstrationProduct Demonstration

Focus for the year ahead

Data Migration Asset Alignment / TM

Improved UX Project Creationg

Migration SDL WorldServer Filter

configuration

j Reporting Scoping/Costing G l li tico gu at o

GIM Integration

German localization

Infrastructure SDL Tridion SDL MultiTerm SDL B Gl b l

Infrastructure Windows Server 2008 Java 6

SDL BeGlobal SDL Passolo

Internet Explorer 9 64-bit Database Support

21

More Information

Attend SDL Innovate 2011: March 1-2 | Santa Clara, CA The Premiere Global Information Management Conference www.sdl.com/innovate

SDL WorldServer 2011 Exclusive Launch Dinner March 1 at 6:30-8:30pm (following the Innovate Conference cocktail reception)p ( g p ) Location: Parcel 104 Restaurant, Santa Clara Marriott Seats are limited! : Email Liz Grotzke at egrotzke@sdl.com to reserve your seat.

22

Connect with SDL! @sdltechnologies sdlplc

To ask a question, please use the Q&A panel in the q , p Q pright hand corner of your screen.

www.sdl.com

24

Copyright © 2008-2010 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.