Whitepaper. SDL TeamWorks What s New 2008 to 2011

Transcription

1 Whitepaper SDL TeamWorks 2011 What s New 2008 to 2011

2 Table of contents 1 About SDL 2 Installation of SDL TeamWorks Overview Detail Desktop Tools Supply Chain Integration 3.1 Studio Package Support AutoSuggest Support SDL MultiTerm Server 2009 SP3 Support Pharma Support 4.1 Improved UCM Support PIM as Core Product Audit Trail Project Management 5.1 Time Recording in Client Not Translated Text Verifier Task XML Verifier Task Task New TeamWorks Reports Add New Target Languages TTX processing as translatable files Start a Project without being the Requester Usability and Productivity 6.1 SDL BeGlobal : SDL Language Weaver Integration German, Spanish and Chinese Language Support Online Editor for ini Files Security Enhancements Additional Platform Support Brand Consistency Title ii

3 6.7 New Portal Configuration SDLXLIFF.ini Fixes from the Development Database Title iii

4 1 About SDL SDL is the leader in Global Information Management solutions. SDL s solutions increase business agility to enterprises by accelerating the delivery of high-quality multilingual content to global markets. The company s integrated Web Content Management, ecommerce, Structured Content and Language Technologies, combined with its Language Services drive down the cost of content creation, management, translation and publishing. SDL solutions increase conversion ratios and customer satisfaction through targeted information that reaches multiple audiences around the world through different channels. Global industry leaders who rely on SDL include ABN-Amro, Bosch, Canon, CNH, FICO, Hewlett-Packard, KLM, Microsoft, NetApp, Philips, SAP, Sony and Virgin Atlantic. SDL has over 1500 enterprise customers, has deployed over 170,000 software licenses and provides access to on-demand portals for 10 million customers per month. It has a global infrastructure of more than 60 offices in 35 countries. For more information, visit Copyright 2010 SDL PLC. All Rights Reserved All company product or service names referenced herein are properties of their respective owners.

5 2 Installation of SDL TeamWorks Overview 2.2 Detail SDL TeamWorks 2011 has been released as an upgrade package to SDL TeamWorks 2008 SP1. This means that for existing users the upgrade to this latest version is straightforward and easy to implement. However, for any users who have customized TeamWorks and are not using it out of the box or who have integrated the solution with other systems, we recommend consulting Professional Services through their Account Manager before going through the upgrade process. The upgrade process requires the installation of three installers; 1. TeamWorks2011Client_ exe 2. TeamWorks2011Server_ exe 3. TW_Dictionary.msi The first two installers are upgrade installers, therefore you can apply them over the top of SDL TeamWorks 2008 SP1. You should only attempt the Server installer after stopping all TeamWorks Services. The TW_Dictionary.msi is a new service and you should install this after the Client and Server have been upgraded. More details on this new service can be found in Section 3.2 of this document. Title 2

6 The Server installation has only three options that require a manual decision as shown in the screenshot below: Remove project TM access restriction By default, TeamWorks controls the Translation Memory access by checking permissions whenever you access the Translation Memory. However, the permission check is expensive when the number of Translation Memories and number of users grow. Considering most organizations do not need to restrict the Project Translation Memory access we have removed this restriction by default from TeamWorks 2008 SP1. Clearing this checkbox allows the administrator to apply this check if required. Use SDL MultiTerm SP3 Title 3

7 This option is selected if you wish to install SDL TeamWorks using SDL MultiTerm Server 2009 SP3 or above. This is covered in more detail in Section 3.3. Spawn execution server tasks in separate process By default the TeamWorks execution server executes tasks in separate threads. Some organizations requested the ability to further isolate the task execution in a separate process for certain customized tasks. The knock on effect of this is that the execution server also performs better with more powerful hardware. Therefore, from this release we have provided this option to allow the administrator to execute tasks in a separate process without having to manually force this through a config file. 2.3 Desktop Tools The translator can use SDL Trados 2007 or SDL Trados Studio 2009 to translate bilingual files created in TeamWorks. It is therefore worth mentioning which versions are needed to ensure full compatibility with this TeamWorks release and enjoy all the enhancements that have been included. SDL Trados 2007 Suite version patched to the cumulative update described in the following Knowledgebase Article: SDL Trados Studio 2009 SP3 version which is cumulative update 9 described in the following Knowledgebase Article: Title 4

8 3 Supply Chain Integration 3.1 Studio Package Support Overview This feature provides the ability for TeamWorks users to create packages that can then be translated in Studio and returned easily to TeamWorks using the Studio return package concept. The TeamWorks package can contain: Source files Bilingual TTX files Reference files Project Translation Memory AutoSuggest Dictionary The TeamWorks analysis report Package xml with relevant metadata The return package from Studio contains: Bilingual TTX files Package xml with relevant metadata Title 5

9 3.1.2 Explanation This section of the document covers the roundtrip from TeamWorks through Studio and back again using the TeamWorks Portal to download and upload the TeamWorks packages for translation in Studio. The following image provides a graphical representation of the process allows the translator work with TeamWorks Packages in Studio without having to use the TeamWorks Client at all. The only software required, apart from Studio, is a compatible web browser. Upload package and complete the task Assign Task to Translator Translator logs onto TWX Portal Translator logs onto TWX Portal Translate in Studio and create a Return Package Accept Task and download package for offline use 1. To allow a Translator to use this feature, and if you wish to avoid having to use the TeamWorks Client, the TeamWorks Project Manager or Administrator should first add the Translator as a new user to the system. Do this through the TeamWorks Manager. Title 6

10 Title 7

11 Complete the three mandatory fields on the Contact Info tab of the New Freelancer dialog box The new users should at least have Translator set as their role on the Roles tab. Select the Create offline packages for external users option. Title 8

12 Add this new Translator to the Project Team. 2. Once the Project is created, you can now create the package by creating a Translate Task and assigning it to a user. Select Create Single Follow-up Task > Translate from the context menu. Title 9

13 Assign the Translate Task to the new user, in this case Free Lancer, and the package is created. Title 10

14 3. The Translator can now download the package through the Client or the Portal. In the Client, simply select Download Package from the context menu. In the TWX Portal, log on and click on your Translate Task to download the package; Title 11

15 Accept the Task in offline mode. Title 12

16 4. If the version of Studio is at least SP2, but not the latest SP3 patched to Cumulative Update 9, then you can still use this package but you will have to manually select the AutoSuggest Dictionary included in the package. To do this: Rename the *.ttp extension of the TeamWorks Package to *.zip and you will find a structure inside like this: Inside the ASD folder you ll find a *.bpm file which is the AutoSuggest Dictionary file for Studio. Title 13

17 Once you have opened the package in Studio, go to Project Settings for the Project that is created and you can add the ASD manually to your Project. This step is not necessary if you have SDL Trados Studio SP3 CU9 installed. 5. Open the Package in Studio using the Open Package wizard. A Project is automatically created for you in Studio along with all the settings and analysis that were available in the TeamWorks Project Manager. Title 14

18 View the analysis report, also included in the TeamWorks Package, can be viewed through Studio in the following location by opening up in a browser. The similar report from TeamWorks looks like this: Title 15

19 6. Translate the file.. The AutoSuggest tool will give you hits similar to those shown in the example below. These are presented as you type allowing a very fast use of resources that have been consistently used before. These come from MultiTerm (if you are using a Termbase) and the AutoSuggest Dictionary as shown below. Green and yellow icons are Dictionary hits based on the contents of the original Translation Memory in TeamWorks; You then finish the translation in Studio as follows; Title 16

20 7. Once complete, the Translator creates a return package in Studio for loading through the TeamWorks Portal to update the Project. Using the TeamWorks Portal, log in and use the Upload Package for Import option to return the completed translation to TeamWorks; Title 17

21 8. Then complete the task. Title 18

22 9. Once this task is satisfactorily completed, check the translation, in this case using the TWX Portal, and you can see the translation is complete. Note: You can also use the TeamWorks Client to upload and download packages but the recommended workflow for simplicity would be to always use the Portal and not take the TeamWorks Client at all. This is easy for distribution, it allows the use of Studio to improve Translation Productivity, and it s simple for the Translator as no additional software is required at all. The workflow becomes; Title 19

23 3.2 AutoSuggest Support Overview This feature provides the ability for users to generate AutoSuggest Dictionaries from their TeamWorks translation memories and provide them to users of SDL Trados Studio 2009 so they can maximize the use of the new desktop applications in the supply chain. Configuration settings allow the AutoSuggest Dictionary to be regenerated at specific time intervals or based on the growth of the Translation Memory ensuring that TeamWorks users can easily benefit from ongoing translation work Explanation In order to set up this feature an additional installer (TW_Dictionary.msi) is provided with the 2011 release. This can be found in the Customer Center. The AutoSuggest dictionary service is installed in the ASD folder and should be installed on the same machine as the Business Server. When the user works with Studio for translation, it is not necessary to install the TeamWorks client. When a package is ready, the user can log on to the web portal to accept the task and download the package. When the user downloads the package, if the dictionary is available, there is an option to control if the dictionary should be downloaded. If this option is selected, the TeamWorks Package will include the dictionary. Title 20

24 To install this service: 1. Run the TW_Dictionary.msi on the Business Server. This will bring up the SDL TeamWorks Dictionary Server Setup Wizard; 2. Click Next and enter your username and password. Title 21

25 3. Click Next. Title 22

26 4. Unless you wish to change the location of the server, click Next again. Title 23

27 5. Now you should be ready for the installation to begin. Title 24

28 6. Click Finish and now you can look at configuring the settings. Title 25

29 7. Specify your configuration settings: Configuration settings are made by the system administrator in a configuration file located in: C:\Program Files\SDL International\SDLTeamWorks\DictionaryServer Title 26

30 There are basically three settings that can be used to define a fixed time at which the AutoSuggest Dictionary should be generated and also a growth factor; <setting name="checktime" serializeas="string"> <value>9:00pm</value> </setting> <setting name="tuincrement" serializeas="string"> </setting> <value>1000</value> <setting name="checkingimmediatelyafterstart" serializeas="string"> <value>false</value> </setting> The Dictionary server checks the Central Translation Memories once a day at the specified CheckTime. At check time, if the Central Translation Memories have incremented more than TuIncrement the Dictionary Service will regenerate the dictionary for the corresponding Translation Memory, otherwise it will sleep until the next CheckTime to check again. The CheckingImmediatelyAfterStart setting allows you to generate an AutoSuggest Dictionary immediately on starting the Dictionary Service. This is useful for testing or for immediate generation of a dictionary for a new Project. The default is set to False. Title 27

31 Autosuggest Dictionaries are stored in this location: C:\Program Files\SDL International\SDLTeamWorks\DictionaryServer\DictionaryStore Log files containing information on what has been generated and when are stored here; C:\Program Files\SDL International\SDLTeamWorks\DictionaryServer\LogFiles Title 28

32 8. A further requirement to make use of this facility is to ensure that offline packages for external users are enabled in the TeamWorks Manager. 9. Create a Translate Task for the Translator, then when they log on to the TWX portal to collect the translation package, they will have the option to include the AutoSuggest Dictionary within the TeamWorks package as described in section 2.1 Studio Package Support. 3.3 SDL MultiTerm Server 2009 SP3 Support Overview The release of SDL MultiTerm 2009 SP3 required a change in TeamWorks so that it is able to use this new version. The only time you will see this is during the upgrade from 2008 SP1 to 2011 is when you are asked to confirm which version of MultiTerm you wish to work with. Once this decision is confirmed, it cannot be changed without reinstalling SDL TeamWorks Title 29

33 3.3.2 Explanation To install SDL MultiTerm Server 2009 SP3 support, the TeamWorks Server installation program asks you to select a checkbox if you are going to be using the latest version of MultiTerm. Once this is selected, SDL MultiTerm Server 2009 SP3 can be used with SDL TeamWorks If you don t select this box then the previous versions of SDL MultiTerm 2009 or SDL MultiTerm 2007 can be used. For further information on how to set up SDL MultiTerm Server 2009 to work with SDL TeamWorks, consult SDL Professional Services. Title 30

34 4 Pharma Support 4.1 Improved UCM Support Overview The improved support for UCM relates to ongoing changes that have been made to the capabilities in TeamWorks to handle different scenarios arising from the use of TeamWorks in this workflow. Examples of the ongoing work to maintain and improve this feature can be found in the last section on fixes in the Development Database. 4.2 PIM as Core Product Overview The configuration of TeamWorks to allow it to be used within the PIM (Product Information Management) workflow used to require special configuration by Professional Services as an additional feature to the core TeamWorks product. SDL TeamWorks 2011 has incorporated this feature into the installation package by providing an automatic installer for PIM users that completes the installation of the required ini files and additional tasks for the PIM comment review Explanation Once the upgrade to SDL TeamWorks 2011 is complete, the administrator can run PimConfig.exe which is located in: C:\Program Files\SDL International\SDL TeamWorks\TeamWorks Title 31

35 This execution of this file launches a configuration dialog boxwindow where the TeamWorks administrator can add the features for UCM or PIM DES formats as required. Each file type can be configured as required but generic set of ini files and stylesheets for the preview are provided. Note: It is important to work with Professional Services to make sure that these files are tailored to your individual needs. Title 32

36 The two new automatic tasks created are Extract Comments and Merge Comments. Use these to extract comments from the PIM or UCM xml files and include them within the bilingual TTX files, then after review to merge any changes from the TTX back into the xml. Title 33

37 One new manual Task created is called Review Comments. This is used to send a manual task to check and apply the comments made after the translated PIM/UCM xml file has been reviewed within the PIM/UCM workflow outside of SDL TeamWorks. This will only be possible once the required Team members have had the new Comment Review responsibilities added to their role in the Project. Title 34

38 Once this is all set up, the Project can be started by completing the translation and then sending it off for client review. The client reviewer will return a commented PIM/UCM xml file (comments are added outside of TeamWorks through the customer s document management system). This commented file is then added as an auxiliary file in the files view to the translated file. Make sure the Type is PIM/UCM Comments. Title 35

39 Change the status to Ready for Comment Review ; Then create an Extract Comments task. Title 36

40 Finally, create a Review Comments task for the Translator/Reviewer. The Translator/Reviewer goes to the web portal to accept their task. Click on the Task and accept it. Title 37

41 Note the summary below the Task Details box identifies that the status is Comments Extracted and is therefore ready for the review; Open the file for review by clicking Open; Title 38

42 This opens the file for editing as follows. Title 39

43 Closing the TM and standard Comments window makes for a better working environment for some users as it s easier to see the comments and work through them. Title 40

44 The basic functionality here is easy to follow, so in this example we jump to the 4 th comment and you can see this is in segment 77 with the original text highlighted in the target. The suggested alternative translation from the reviewer in on the bottom right SEZNAM OTAZEK PRO PACIENTA. If the editor agrees with this translation then Accept it and it will be inserted into the target automatically. If the editor doesn t agree with it then reject it, and enter the reasons why. These are added to the file for the client reviewer to see in the next stage of the workflow. Title 41

45 Once the editing review is complete, the file can be saved and uploaded. Then finally complete the task. Title 42

46 Back in the TeamWorks Client, the Project Manager (once happy that the editing task has been completed satisfactorily) can now create a Merge Comments Task, which will take all the changes and reasons for rejection etc. and place them inside the PIM/UCM xml file. Title 43

47 Carry out a quick check, if needed, by going to the Files View where you can view the changes with a text editor. This process will repeat as often as is required until the translation is accepted by the customer. This task can also be used as part of a compound task. 4.3 Audit Trail Overview This feature has been added to SDL TeamWorks 2011 to provide an Audit Trail of all the tasks carried out within the system at Project, File and Task level. This work is also part of the ongoing improvements to help customers who are subject to the requirements of 21 CFR Part II Explanation Manage this feature through the TeamWorks Manager where three new nodes have been added: Title 44

48 Using the context menu, set a specific range for the report. Change the dates as required. Title 45

49 Then the range will be available for browsing in the TeamWorks manager as follows: Project creation File audit trail Task Audit Trail Title 46

50 You can also export the list and then save it as *.txt or *.csv. You can easily convert these to Excel, for example, where you can more easily manipulate the data. Title 47

51 5 Project Management 5.1 Time Recording in Client Overview This feature provides an estimated time calculated for a task based on an analysis report. To do this, the user sets up different categories in the TeamWorks Manager that are identified by a custom field and whichever tasks are used in that category. The result is the estimated duration, in hours, displayed in a column against the relevant task. The Project Manager can also change the basis of this calculation through the cost calculator on the fly and can also compare the actual time against the estimated to help with refining future planning Explanation 1. Decide which types of work are relevant for you and then create a Custom Field with picklist values relevant to the types of work. In this example we have created three types of work; 1. General Translation work 2. Legal Translation work, and 3. Technical Documentation These are all added to a Custom Field called we have named Product Category. Title 48

52 2. Create the Categories. These will mirror the values in the picklist that were added to Product Category. The General Category is always there by default and this will be used if none of the others are specified when creating the Project. 3. Define the condition under which each set of Tasks Duration Rules will be used. Looking at the Legal Category we add the value Legal from the picklist presented. Title 49

53 4. Now set the rules themselves. There are no default values provided so the TeamWorks Administrator needs to agree what values to use for each type of work and how quickly, in seconds, they can be carried out for each task. The start screen looks like this. This is split up into: Task Type Translate Edit Proofread Fix Problems Review Comments Task Time (sec) The Task Time (sec) is there to provide a base time that can be used for additional time to prepare for work in addition to the act of translating itself, or Title 50

54 as a base value to be used where the task is not based on the size of the document or number of words for example. So for example, the administrator could create a new rule for a review task where the only value populated is a Task Time of 1800 seconds and zero in every other column. Match Bands This is the average time per word that it would take to complete the task based on a fixed amount of time per word per match value in the following bands; o Context TM o Repetitions o 100% o 95-99% o 85-94% o 75-84% o 50-74% o No Match 5. Rules can be added for each Task Type within each of the Categories, so for this example we did the following; 6. Now open the TeamWorks client and prepare a new project making sure to select the correct Category for this translation work. Title 51

55 7. Once the analysis is complete, the duration column is populated with an estimate of how long the work is expected to take which enables the Project Manager to plan resources accordingly. 8. Once the work is complete, the Project Manager can edit the recorded time for the task allowing a useful feedback loop that can be used to refine the estimated values in the Task Duration Rules for future planning. Title 52

56 9. This brings up the small dialog box where you can manually enter a revised number of hours and. 10. Then compare the two columns side by side and use the values for an instant comparison as well as in more detailed reporting. Title 53

57 5.2 Not Translated Text Verifier Task Overview This task carries out two checks to ensure that all segments have a translation and that the translation isn t a copy of the source. A missing translation produces an error and an exact copy of the source produces a warning Explanation This is an Automatic Task that you can create and run for files with the following statuses: Title 54

58 The Task is listed in the TeamWorks Manager under Automatic Tasks and the Automatic Task Properties dialog box is accessed from here; Automatic Task Properties Dialog Box There are basically two options: The first is to set how many errors to allow before the task fails. The second is to set how many alerts to allow. Title 55

59 In this Task we use Error and Alert for the following scenarios; Error : no target translation Alert : source = target Warnings are not used in this task. You can set the number of Errors or Alerts that you wish to allow, or not allow any by selecting the Ignore checkbox in the Translation Verification Options tab. If you do not allow any Errors or Alerts, they still show in the report at the end. Title 56

60 There is no SQL server report available, but you can deliver the report to a customer as an independent package (rpt file). To run the Task, create a single task or add it as part of a Compound task. Here we run it as a single follow up task; The Task is added to the Task list where you can see the progress in the Task Center; Missing a translation altogether shows as an Error and where source equals target it shows as an Alert. These values are not customizable through the application. Title 57

61 If you set values in the Properties dialog box to limit the number of errors and alerts allowed and the task exceeded the limit, then it will fail as shown here: You can then use the report to locate the problem segments and correct them. Title 58

62 5.3 XML Verifier Task Overview This task carries out two checks on an XML file to ensure that it is well formed and valid XML. The task is independent and you can run it before a project is prepared to ensure compliance, or it you can run it at any stage of the project Explanation 1. The Task is listed in the TeamWorks Manager under Automatic Tasks and the Automatic Task Properties dialog box is accessed from here. Title 59

63 2. Here we see it is an Automatic task and you can define report definition files as well as setting the status of the files after the task is complete. Title 60

64 3. This setting is a Global setting so you can check for either DTD validation, or Scheme validation, but you can t have them both at the same time, or different validation for different Projects. You can add as many as are going to be needed to handle the different filetypes you are given for translation. Here we have added three DTD files; Title 61

65 4. To run the Task, create a single task or add it as part of a Compound task. Here we run it as a single follow up task; 5. Return to the Task Center after the task has completed and you can see immediately whether it failed or not. We can see that the task is showing that the validation of XML has failed and the reason is displayed in the Result column for each file. Title 62

66 6. To troubleshoot this, download and checkout the file and then make the necessary changes to the XML to comply with the DTD. 7. Once corrected, Upload and Checkin. 8. Then go back and restart the failed task. Title 63

67 This time it ran successfully Task Overview This task is only available in the desktop client and it provides the ability for the Project Manager to files from TeamWorks as an Automatic task that can be run as a single task or as part of a compound task to simplify the file handling that used to be a manual process outside of TeamWorks. This is also an audited process using the new Audit Trail functionality in this release Explanation Specify the following settings and then run the task: By default, this task is available for the following statuses: Title 64

68 1. To add the task to more statuses, simply select the Files task for any status for which you wish it to be available. Here we have added this to the Ready for Comment Review status. Title 65

69 2. Configure the mail server under the Configuration Settings node. 3. Configure the server user details under the Users node in User Management. Title 66

70 4. One more setting is required, and this is the address of the Customer for the Projects you are working on as this is used as the mailto address. 5. To use this feature, you can create a single follow-up task. Title 67

71 6. Then draft the content of your , using html markup if needed. The resultant looks something like this: Title 68

72 Title 69

73 5.5 New TeamWorks Reports Overview We have added two new standard reports to TeamWorks Overview Report and the Project Detail Report. The Project Explanation Project Overview Report This report shows all Projects and their current status but without task or language details. Title 70

74 Project Detail Report This report shows the status of all selected Projects with status, language details and all manual tasks. By default, the new Project reports only provide standard fields that we have defined in the application. However, it is possible to allow the use of custom fields in the reports by updating the ProjectReportDefinition.xml file with the appropriate details. This file is located in the Business Server here; C:\Program Files\SDL International\SDLTeamWorks\TeamWorks Title 71

75 For example, we have created a custom field called ProductCategory that must be displayed as Product Category in the report. This is entered in the ProjectReportDefinition.xml file as follows; <field id="productcategory" display="product Category" origin="projectmetadatatable"/> This will retrieve the Custom field ProductCategory and in the report is displayed as Product Category. Any new custom fields added, that you wish to report on, must be in this format. Once added, the Project Overview reports and Project Detail reports that are subsequently created will show the corresponding custom fields. Title 72

76 5.6 Add New Target Languages Overview We added in SDL TeamWorks 2008 SP1 the ability to add a new target language after the Project had started Explanation 1. To complete this operation simply right-click on the Project and select Add Project Target Languages. 2. Select the required language from the available languages. Title 73

77 In this example, we added Spanish and this is now available for receiving tasks. 5.7 TTX processing as translatable files Overview In SDL TeamWorks 2008 SP1, we provided the ability to set up TeamWorks so that TTX files could be processed as translatable source files by adding an additional task. In TeamWorks 2011, this is no longer necessary and you can add TTX files as any other file as long as the language pairs in the TTX match those of the Project Explanation You can add TTX files through the application and process them as per any other translatable file. Title 74

78 5.8 Start a Project without being the Requester Overview This feature has been added for users who make use of the Request Portal. The Project Manager can now force the start of a Project without being the Requester Explanation The feature works by making use a new checkbox in the Scope Project dialog box, which will allow, when selected, the Project Manager to start the Project even if they were not the Requester. Title 75

79 6 Usability and Productivity 6.1 SDL BeGlobal : SDL Language Weaver Integration Overview SDL Language Weaver integration is used in SDL TeamWorks 2011 as an automatic task that can be scheduled to run as part of a compound or manual task before translation by the Translator. The results of the Language Weaver translation task are saved to the Project Translation Memory, which allows all subsequent Translation work to take advantage of the machine translation result from the Translation Memory Explanation The Language Weaver integration is based around the Rest interface and is configured from within the TeamWorks Manager under the Automatic Tasks node. Title 76

80 In the Settings tab of the Automatic Task Properties dialog box, you can specify the supported language pairs. This brings up the properties window where you can click Test to be presented with a list of the available language pairs. For each language pair, the implementation needs to specify the DLL and class to implement. The default value for the REST implementation should be: "Trados.MachineTranslation.LwRestImpl,Trados.MachineTranslation.LanguageWeaver" In addition, the Connection URL/User ID/API key is required and will be provided as part of a Language Weaver implementation. It is generally required to test the connection first and then select the correct language map. Once tested successfully, a dialog box is presented that shows all the supported language pairs from the Language Weaver server. The user needs to select the language pair so that the language codes are mapped to the TeamWorks language code (The language codes from TeamWorks and Language Weaver are different); Title 77

81 There are also a few other parameters, which are explained as follows: Polling Interval (seconds): When a translation is submitted to the Language Weaver server, the TeamWorks application will query Language Weaver frequently. This setting relates to the number of seconds the TeamWorks application waits before the next query. Timeout (seconds): If TeamWorks cannot get a response from the Language Weaver Server before the number of seconds specified in this setting, then TeamWorks will fail the task. TM check before Machine Translation: The translation is only performed for sentences where the Translation Memory fails to return a value above the level specified. Title 78

82 Weighting Factors for Analysis Reports: Use the weighting factors to multiply the analysis results for the Machine Translation task report. To run the task in the TeamWorks Client, either use this as part of a Compound task or create a single follow up task as below; Title 79

83 Then when you open the file, shown here in the TeamWorks online browser, the segments are populated from the Translation Memory as you work. Title 80

84 6.2 German, Spanish and Chinese Language Support Overview SDL TeamWorks 2011 now provides interface support in four languages: English, German, Spanish and Chinese Explanation You can easily change the interface by going to Tools > Options after logging onto the TeamWorks Server and changing the user interface to the language required. Note: the placeholders for Japanese and French are still there but they are inactive. The next time you log onto the server, the change will take effect. Title 81

85 6.3 Online Editor for ini Files Overview In SDL TeamWorks 2008 SP1, we introduced the ability to edit tag settings files within the TeamWorks Manager Explanation A new option is available in the context menu called Edit Settings. Selecting this option opens the tag settings file in a notepad style editor where you can quickly and easily make changes. Title 82

86 6.4 Security Enhancements Overview In TeamWorks 2008 SP1, we added security enhancements to prevent the ability of users to enter malicious code into the text fields presented in the web portal Explanation Enhancements have been made to the product so that it can withstand testing for these main areas of concern; 1. Script (or code) injection and SSI, and XSS a. The application will not allow the user to enter any script (JavaScript, Server-Side Includes or Cross Site Scripting) into the text fields on the web forms. If the user is able to do this and the script is stored in the database then it can also be executed when the fields are rendered the next time the web page is used. 2. SQL Server Injection a. All DB queries are run parameterized and not constructed by string concatenation. This means that the attacker should not be able to inject any SQL statements (SQL code) through the web request (either via text fields or in the web address) that would then be executed against the database. Title 83

87 6.5 Additional Platform Support Overview SDL TeamWorks 2001 has been tested and certified across more environments than previous versions to provide greater choice than before Explanation The following table summarizes the additional environments that we officially support in the TeamWorks 2011 release. Environment Client WXP SP3 (32-bit) Vista (32-bit) WXP SP3 (32-bit) Vista (32-bit) W7 (32-bit and 64-bit) Server W2003 (32-bit) W2003 (32-bit and 64-bit) Database Oracle 10g SQL Server 2005 Oracle 10g Oracle 11g SQL Server 2005 SQL Server 2008 Title 84

88 6.6 Brand Consistency SDL own, and develop, a number of Enterprise Translation Memory Systems. As part of the SDL Global brand, all the Translation Management Systems (TMS) have adopted a similar look and feel when it comes to the branding of the product. The new themes for SDL follow these styles; Style and branding SDL Global AMS SDL MultiTerm Translator Productivity SDL Trados Studio SDL Passolo SDL Automated Translation Solutions Title 85

89 SDL Automated Translation Solutions Translation Process Automation SDL TeamWorks, TMS and WorldServer SDL TeamWorks 2011 follows this theme for Translation Process Automation. Title 86

90 6.7 New Portal Configuration Overview This feature allows the TeamWorks Administrator to easily add new custom fields to TeamWorks that can then be used in the Request Portal Explanation To use this feature, add custom fields through the TeamWorks Manager in the normal fashion. Here there are two fields added, one text field and one date/time field: Title 87

91 Now add these new fields to the WebPortal configuration file here: C:\Program Files\SDL International\SDL TeamWorks\Web\Portal\Requests\data\CustomFieldSettings.xml An example of how you should use this is provided in the file and you can copy and populate this with the names of the Custom Fields created in TeamWorks Manager. There is also an attribute you can set whether the completion of this field is mandatory or not. Once this is complete, the new fields will be visible in the TeamWorks Request Portal when logging in to initiate a request. In this example, both fields are mandatory and are flagged as such with a *. Title 88

92 6.8 SDLXLIFF.ini Overview This feature has been introduced to make it possible for users to process files through TeamWorks, such as IDML or ICML files, that can only be processed with the new 2009 filter framework in SDL Trados Studio It involves the use of a new tag settings file for SDLXLIFF Explanation In SDL TeamWorks 2011, the new SDL Xliff tag settings file is shipped as standard. Title 89

93 To use this feature, the original source files need to be prepared in SDL Trados Studio 2009 first, and it is important that they are prepared as follows: 1. Open the IDML/ICML file in Studio without a TM (or with an empty TM). a. It might be worth reducing the size of the embedded file in Studio to zero. This will cut the size of the sdlxliff down significantly and reduce the processing time for TeamWorks. Increasing this is only necessary if you wish to create the target or source files from the SDLXLIFF itself without having the original IDML file available when you do it. 2. Copy all source to target (not necessary, but may be preferable for users). 3. Add the target language SDLXLIFF files to TeamWorks. 4. Translate in TeamWorks and then replace the target SDLXLIFF files in Studio. 5. Save the target IDML/ICML files. The converted file in TeamWorks takes the filename adopted by Studio and adds ttx on the end so the full name shows it was, in this case, an IDML converted to SDLXLIFF and finally to TTX. Title 90

94 You can then send the file for translation and complete the work in TagEditor. You could also complete the work in the TeamWorks online portal. Title 91

95 Finally opening the completed translation in Studio, you will note that the status is still untranslated. This is because the two toolsets are not aware of each other s form for this. However, this is not required to obtain the translation so from here the Project Manager can select File Save Target As and generate the target IDML. Title 92

96 7 Fixes from the Development Database Number Summary Release Send finished files to customer as attachment TWX Automate steps after Finalize (" translation request handling") TWX Add target language to existing project TWX 2008 SP Registering the local package no longer results in error message "The path is too long after being fully qualified." TWX Template complex task are no longer kicked off if the project contains no files Column 'FileLanguageId' is constrained to be unique. Value 'n' is already present' error in Update Center/ current problem--> File filters now work correctly Project Settings: irrelevant warning when changing General/Custom Fields tabs settings no longer occurs Online editor preview: Preview, then edit, then preview no longer leads to an error that file already exists TWX 2008 SP1 TWX 2008 SP1 TWX 2011 TWX Portal, sorting on the My Tasks page is now remembered TWX Inconsistent capitalization in toolbar in Online Editor has been TWX 2008 SP1 corrected Error condition on TM server (TM not found) no longer leads to an ugly error message in Online Editor with stack trace TWX Online Editor - Comments no longer cause Javascript errors TWX 2008 SP Added option "Do not create new translation units if only text TWX 2008 SP1 fields differ." "The operation has timed out" error when displaying analysis report in TW client for project with 2500 files TWX 2008 SP Request portal users are allowed to upload files based on configurable options, so even *.exe files could be allowed TWX 2008 SP Comments added in TeamWorks Online are no longer garbled TWX 2008 SP1 when not using Paging View Event are no longer sent before a check is done TWX 2008 SP TeamWorks Manager: It is now possible to view and edit an.ini TWX 2008 SP1 file from TW Manager Kazakh is now supported in TeamWorks / TeamWorks costings TWX 2008 SP TeamWorks reminders now work with ORACLE Backend TWX 2008 SP File status information is now displayed in TWX client Files view TWX 2008 SP Screen update/refresh problems in the Create Project Template Wizard resolved by Microsoft Hotfix TWX 2011 Title 93

97 Title 94 Number Summary Release TWX 2008 Business Server no longer allows downloading of files TWX 2008 SP1 for some customers - resolved TWX Execution Server crashed upon receiving a deadlock error for some customers - resolved TeamWorks Serbian TM issue reported by two customers is resolved TeamWorks: Confirming / Closing the Project Settings dialog by clicking on the 'OK' button for an already completed project no longer updates the 'Completed At' field Project creation wizard. Notification for not assigned manual tasks now only occurs once Security Fix : To avoid Script and SSI Injection and Cross-site scripting TeamWorks on Oracle backend: It is now possible to the delete a project template if still used by an existing, but archived project TWX 2008 SP1 TWX 2008 SP1 TWX 2008 SP1 TWX 2008 SP1 TWX 2008 SP1 TWX 2008 SP Security Fix : Web form javascript and html injections TWX Creating new project based on a reference project no longer TWX 2011 causes an Object Reference error TTX files can now be loaded as source files in TeamWorks TWX 2008 SP XML Verifier Task TWX Not Translated Text Verifier Task TWX Time recording/estimating feature TWX Universal Project Data Report TWX Universal Task Data Report TWX TeamWorks standard fields and TeamWorks custom fields can now be made available in the Portal TWX AutoSuggest Dictionary Generation and inclusion in a TeamWorks TWX 2011 Package New 2010 TMS branding for TWX TWX File's content is not displayed in TWPortal over Mozilla TWX TWX Users can now access Serbian project TMs on ORACLE TWX 2011 database Error no longer appears when open Bilingual Preview for the file with PIM comments in online editor TWX Hide TagEditor View for the file with PIM comments in the online editor Merge task is failed for section-level comments (icelandic language) : Removed crash by inserting the correct tags, but this case is not possible to support for comments starting and ending in the same in-between segments. TWX 2011 TWX 2011

98 Number Summary Release TeamWorks SP1: Portal no longer shows outdated files, i.e. TWX 2011 images on TW 2006 state Can now find in PimComments auxiliary file the reasons for TWX 2011 rejected text-level comments Report dialog fields overlap field labels. TWX Refreshing the screen changes your folder view to your set TWX 2011 default Audit Trail provision TWX Rebranding of the TWX UI TWX Adding Language Weaver Machine Translation capability to TWX TWX User Name with umlauts is now shown correctly in TeamWorks TWX 2011 portal online Setting up TTX processing in TeamWorks as for any other TWX 2011 supported filetype Button to insert bold, italic, etc... formatting in the Online Editor TWX Highlight differences between match and text to be translated in the Online Editor works correctly TWX Allow concordancing to master memory from the Online Editor TWX Show metadata on concordance search results in the Online TWX 2011 Editor Delete button for comments, etc... in the Online Editor TWX In the Online Editor deleting formatting tags left text still be TWX 2011 formatted (deleting still had the text remain in bold). This is resolved with a new button in the toolbar Reassigning a manual task from one user to another is now correctly reflected on the TeamWorks Portal TWX UCM : Reason Text now extracted from latest UCM format TWX UCM : Tag Settings file is now available for the latest UCM format TWX "Object reference not set to an instance of an object" error TWX 2011 message no longer appears when clicking browse in a reference project Task completion process now more robust in the Online Editor TWX German TeamWorks Localisation Errors are all corrected. TWX UCM - opening tags of second comment starting before closing tag of first comment no longer strips text on merging. TWX UCM - No more duplicated multisegment comments TWX UCM - Rejected comment where additional space is present no TWX 2011 longer duplicates the space Title 95

99 Number Summary Release TWX 2008 SP1: Setting any condition for the subscription TWX 2011 'Request Created' no longer generates an error message UCM : You're no longer allowed to delete comments even if the TWX 2011 Comments window is closed Convert to Original format task is no longer failed for doc file TWX UCM : No more error in Bilingual and Target Preview for icelandic file with Pim/UCM comments TWX UCM : HAComment now always has a comment level attribute TWX 2011 for the HAComment Node No more error in Bilingual Preview after accepting comment with TWX 2011 number 38 for czech language file Can now create a Translation Memory with Japanese target TWX 2011 language SP1 rounding of numbers in cost estimates : fixed by not using TWX 2011 the localized currency format Ensure compatibility with MultiTerm Server SP3 TWX Can't connect server using online set-up with connection mode - TeamWorks Anywhere : There are some restriction for TW anywhere. It only runs when TW anywhere was installed using the web. The windows service installation does not work anymore due to a Microsoft bug. For the Microsoft bug: We need a Microsoft hotfix (it was marked with from the readme file but the link is not really relevant to our issue) to fix the.net remoting. However this hotfix only addresses the binary remoting, but the soap remoting is not fixed for cross.net versions. TWX 2011 Title 96