sdl trados 2007 suite - file formats reference guide

8/7/2019 SDL Trados 2007 Suite - File Formats Reference Guide

http://slidepdf.com/reader/full/sdl-trados-2007-suite-file-formats-reference-guide 1/335

File Formats

Reference

Guide



COPYRIGHT

FILE FORMATS REFERENCE GUIDE

Copyright © 2008 SDL plc.

All rights reserved. No part of this documentationmay be duplicated in whole or in part or reproducedin any form without the express written permissionof SDL plc.

All trademarks are the property of their respectiveowners. The names of other companies andproducts mentioned herein may be the trademarksof their respective owners. Unless stated to thecontrary, no association with any other company orproduct is intended or should be inferred.

Although SDL takes all reasonable measures toprovide accurate and comprehensive informationabout the product, this guide is provided “as is”without warranty, either express or implied.

This guide accompanies SDL Trados 2007.

May 2008

DC-T27-FF-03-EN




i

Chapter 1 Introduction

About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Audience Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Accessing Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Key Term Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Supported File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

TradosTag Bilingual File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Chapter 2 HTML, XML, and SGML Files

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Supported ML File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Key Term Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Translation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

What is a DTD? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Managing Tag Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Tutorial: Tag Settings Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Editing Tag Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Using Conditional ML Tags in Tag Settings Files . . . . . . . . . . . . . . . . . . 2-23

Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31Translating Files Using Conditional ML Tags . . . . . . . . . . . . . . . . . . . . . 2-32Verifying Translated Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33Cleaning Up Translated Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

Post-translation Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34

Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35

TABLE OF CONTENTS




v

Translation of Microsoft Word Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9

Post-translation Production for Word Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14

Working with RTF Help Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15

Preparation of RTF Help Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17

Translation of RTF Help Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23Translating RoboHelp Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25

Post-translation Production for RTF Help Files . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26

Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26

Chapter 9 Translating Word Files in TagEditor

Selecting a Workflow for Word Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2TTX Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Preparation of Microsoft Word Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4About the Conversion Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4Setting the TTX Workflow Translation Memory Option . . . . . . . . . . . . . 9-5Testing the TTX Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6Word Document Preparation Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6Modifying the Word Filter Settings File . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11

Translation of Microsoft Word Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16Understanding Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16

Field Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17Headers and Footers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20Inserted Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21Non-translatable Footnotes and Endnotes . . . . . . . . . . . . . . . . . . . . . . . 9-21Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23RTF Help Translation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24

Post-translation Production for Word Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25

Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27

Chapter 10 Microsoft PowerPoint Documents

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2Key Term Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2Translation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4

Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5About the Conversion Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5

Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11




i

Chapter 13 Translating SDLX Files

About Working with SDLX Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2Translation Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

SDLX Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2SDLX Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3TagEditor Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4Confirming Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4SDLX>Confirm Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5SDLX> Confirm All Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5SDLX> Go To Next Unconfirmed Translation . . . . . . . . . . . . . . . . . . . . . 13-6SDLX> Go To Previous Unconfirmed Translation . . . . . . . . . . . . . . . . . . 13-6SDLX> Open/Get Next Unconfirmed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6SDLX> Set/Close Next Unconfirmed Open/Get . . . . . . . . . . . . . . . . . . . 13-6Cleaning up SDLX Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6

Chapter 14 Translating Generic Delimited Text Files

Generic Delimited Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2

Chapter 15 Translating OpenOffice and StarOffice Files

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2Supported Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2Supported File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2

The SDL OpenOffice Filter Settings File . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2Translation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3Previewing OpenOffice and StarOffice Files . . . . . . . . . . . . . . . . . . . . . . 15-3Defining Java Virtual Machine Size filter settings . . . . . . . . . . . . . . . . . . 15-4

Chapter 16 Translating Text-based Files

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2Using the Filter Settings Application for the Regular Expressions Filter 16-2Modifying the Regular Expression Settings File . . . . . . . . . . . . . . . . . . . . 16-5

Glossary

Index


http://slidepdf.com/reader/full/sdl-trados-2007-suite-file-formats-reference-guide 10/335xFILE FORMATS REFERENCE GUIDE



Chapte

INTRODUCTION

This chapter introduces the File Formats Reference Guide and

some key concepts.

Sections include:

C About this Guide

C Key Term Definition

C Supported File Formats

C TradosTag Bilingual File Format

1



Abou t th i s Gu ide1

1-2FILE FORMATS REFERENCE GUIDE

ABOUT THIS GUIDE

The File Formats Reference Guide contains file format specific information that is relevant to

translation workflows when working with SDL Trados 2007. This guide deals with each file format

individually: this means that you can quickly and easily access the information you need duringtranslation and determine what to watch out for during translation of this file format. See Supported

File Formats on page 1-5.

If you are working with SDL Trados Synergy, the project creation and management tool in SDL

Trados 2007, many sections of this guide will not be relevant to you, as Synergy allows you to add

many file types directly without formatting the files and also performs many of the pre- and post-

translation steps for you, such as analysis, pre-translation and clean-up. You can also verify your files

from within Synergy. All applications mentioned in this guide, such as the SDL Trados Filter

Settings, Tag Settings Manager and Verification Plug-ins are also accessible via Synergy. However,

you may still need to prepare your files for translation and/or set filter settings for your files. Anychapters or sections that are not relevant to you if you work using Synergy are marked with a note.

For more information about Synergy, see the SDL Trados 2007 Synergy User Guide .

Audience Profile

This guide is most useful to project managers, localization specialists or translators who are working

with the file formats described in this guide.

Related Documentation

Below is a list of the documentation included with SDL Trados 2007:

C SDL Trados Installation Guide – contains information for the installation and configuration of

all the SDL Trados components, including Synergy, the translation tools and the server

components.

C SDL Trados Administrator Guide – contains information about the SDL Trados server

components, including TM Server, Server Manager and Synergy Server.

C SDL Trados Synergy User Guide – introduces the main concepts in SDL Trados Synergy,

including project creation and the translation workflow in Synergy.

C Translator’s Workbench User Guide – contains information about Translator’s Workbench

and the TagEditor and Microsoft Word editing environments.

C WinAlign User Guide – contains information about file alignment with WinAlign.



Conc lu s ion1


1-

TradosTag Files

TradosTag files are composed of three sections:

C Front matter – contains tools settings, user settings and information that has been extracted

from the native file format.

C Body – contains the document text plus formatting tags.

C Back matter – contains ancillary text. This is translatable text that is shared throughout the

document, for example variable or cross-reference text. Not all TradosTag files have back

matter. It depends on the format of the file before you converted it to TradosTag.

When you open a TradosTag file for translation in TagEditor, the body text and formatting

information appears. The back matter section also appears as it requires translation. The front

matter section is not visible in TagEditor.

CONCLUSION

Now that you have read this chapter, you know where to find the information you need for the file

format you are translating.



Conc lu s ion1


Overv i ew2


OVERVIEW

You can translate HTML, XML and SGML files directly with a minimum of preparation using

Translator’s Workbench and TagEditor. This chapter describes the HTML, XML and SGML

translation process.

It explains the role of the tag settings file in processing these file types and shows you how to use the

Tag Settings Wizard to create and edit tag settings files.

NOTED

You can also translate files in other standardized XML formats, such as XLIFF, DITA, SVG,RESX etc.

Supported ML File FormatsSDL Trados provides explicit support for the following ML file formats:

C HTML documents (HTM, HTML) up to version 4.0, including any derivatives such as ActiveServer Pages (ASP), Active Server.NET (ASP.NET), ASP.NET (ASPX and ASCX), Java ServerPages (JSP), Include files (INC) and Hypertext Preprocessor (PHP) files.

C SGML documents (SGM, SGML).

C Standardized XML formats, such as XLIFF, DITA, SVG, RESX etc.

C XML documents (XML, XSL). XML files with unrecognized file extensions are also supportedas long as the file includes the XML declaration, <?xml version='1.0'...?>, and the extensiondoes not conflict with file extensions for other supported file types.

C .NET Resource documents (RESX). This file written in XML and uses the resx.ini tagsettings file. See Predefined Tag Settings on page 2-6 for more information about using INIfiles.

The XML filter can support any language, but the file encoding must be in Unicode. The

SGML/HTML filter supports any language that has language support installed on the computer.

NOTE

D Throughout this guide, HTML, XML and SGML files are referred to collectively as ML files.Note however that, in practice, not all HTML, XML and SGML files have an .*ml extension.



Overv i ew2


2-

Key Term Definition

The following terms occur frequently in this chapter:

CXML – Extensible Markup Language. XML is a metalanguage, which enables a generalavailability and interchange of information that is structured according to its content. BothDTD and schema-based XML formats are supported.

C SGML – Standard Generalized Markup Language. SGML is a powerful metalanguage fordefining and standardizing the structure of documents. It also describes a grammar whichyou can use to design other markup languages (examples include HTML).

C HTML – Hypertext Markup Language. HTML is the system of marking up a document so itcan be published on the Internet and viewed with a browser. Its most distinguishing feature isthe hypertext, which means pages can be linked to anything else on the Internet.

CDTD – Document Type Definition. A DTD is a text file that stores the structure of an HTML,SGML, or XML document and it also defines the structure, elements and conventions towhich a document must conform. A DTD is separate from the HTML, SGML, or XMLdocument itself.

C Schema – Text file describing the structure of an XML document.

C Tag Settings File – Document that contains information necessary for processing documentsthat conform to a particular DTD, schema or other formatting source. For example a tagsettings file is required to process and format HTML, XML, and SGML documents fortranslation or alignment purposes. Tag settings files (also known as initialization files) havethe extension *.ini.



P repara t ion2


2-

PREPARATION

In general, the ML files themselves need no preparation prior to translation. However, in order to

process and format the files, a tag settings file is required.

What is a DTD?

The structure of HTML, XML, and SGML documents is usually stored in a text file that is separate

from the document itself. This file is called the document type definition (DTD). The DTD for a

particular document type defines the structure, elements and conventions to which a document

must conform. An example of a widely-used DTD is the HTML 4.0 DTD: all HTML 4.0 documents

are based on this DTD. Many other standard DTDs have been designed, such as the book, article and

serial DTDs included in ISO 12083. You can also develop your own DTD.

What is a Schema?

An XML schema is a text file describing the structure of an XML document and is an alternative to

DTD. It is also referred to as XML Schema Definition (XSD).You can use a predefined schema or

create your own.

Both DTD-based and schema-based XML files are supported. For both types of XML files you need

to use the Tag Settings Wizard to set up a tag settings file, so that Synergy, Translator’s Workbench,

TagEditor, or WinAlign can distinguish between, for example, structural and inline elements. For

more information, see “Tutorial: Tag Settings Wizard” on page 2-8.

Tag Settings File

A tag settings file contains information necessary for processing documents that conform to a

particular DTD or schema. Tag settings files are also known as initialization files, and have the

extension *.ini.

SDL Trados requires a tag settings file to process and format HTML, SGML, or XML documents for

translation purposes. For example, Synergy, TagEditor, Translator’s Workbench and WinAlign use

the tag settings file to scan the document for translation and define whether tags are external

(structural tags) or internal (formatting or other inline tags). The tag settings file also instructs the

Trados applications on how to handle HTML, SGML or XML elements, such as tags and character

entities.

Use the Tag Settings Manager to manage the tag settings files on your system. Use the Tag Settings

Wizard to create new or edit existing tag settings files. You can access both the Tag Settings Manager

and the Tag Settings Wizard from Synergy, Translator’s Workbench, TagEditor, or WinAlign.



P repara t ion2


2-

C Translation of ML files in TagEditor.

C Verification of ML files in Synergy or TagEditor.

Managing Tag Settings

Use the Tag Settings Manager to manage the tag settings files that are available on your computer.

NOTED

Although TagEditor is used to describe the steps below, the Tag Settings Manager is equallyaccessible from Synergy, Translator’s Workbench and WinAlign.

To access the Tag Settings Manager:

1

Go to Start > Programs > SDL International > SDL Trados 2007 >Trados > TagEditor to launchTagEditor.

2 From the Tools menu in TagEditor, choose Tag Settings. The Tag Settings Manager

dialog box is displayed:

Use the Tag Settings Manager dialog box to perform the following tasks:

C Add new or existing tag settings files to the list. You can create a new tag settings file usingthe Tag Settings Wizard, as outlined in the tutorial below.

C Remove existing tag settings files from the list.

C Edit existing tag settings files (for example, the predefined HTML settings file that shipswith software) using the Tag Settings Wizard. For more information, see “Editing TagSettings” on page 2-19.



P repara t ion2


Tutorial: Tag Settings Wizard

This tutorial shows you how to use the Tag Settings Wizard to create a new tag settings file. We

recommend that you work through the tutorial on your own computer. The tutorial is based on the

wizard as seen from TagEditor. Minor differences are evident when accessing the wizard fromSynergy, Translator’s Workbench or WinAlign. For more information, see the Synergy User Guide ,

Translator’s Workbench User Guide or the WinAlign User Guide .

Before you start, make sure that you have access to the following files which are installed by default

to C:\Documents and Settings\All Users\Documents\SDL Trados\Samples\TagEditor\SGML \:

C The document type definition file (DTD), in this case the file Letter.dtd . This DTD definesrules for writing letters in SGML. In normal circumstances, you may have to contact theoriginator of the DTD to obtain a copy.

CA sample letter written in SGML that makes use of this DTD, Letter.sgm.

NOTED

There is also a sample letter written in XML that makes use of this DTD, Letter.xml . This tutorialuses the SGML file, but you can use the XML file to work through it. Letter.xml is located inC:\Documents and Settings\All Users\Documents\SDL Trados\Samples\TagEditor\XML \

To create a new tag settings file using the Tag Settings Wizard:

1 In TagEditor, select Tools > Tag Settings. In the Tag Settings Manager dialog box, select New.The Tag Settings Wizard is displayed.



P repara t ion2


2-1

6 The Emphasis tag is a typical example of an internal tag for which you can define

formatting. In this tutorial, we assign bold formatting to any text that appears between

the opening and closing Emphasis tags as follows:

C In the Elements list, select the Emphasis tag and click Properties. This opens the ElementProperties dialog box. Click the Formatting tab.

C Select Bold and click OK to confirm. The new text formatting is displayed in the previewpane of the wizard. Repeat this procedure for each tag whose formatting properties youwant to change.

FOR MORE INFORMATION

V For further information about the Element Properties dialog box and the General and Attribute tabs, see the Tag Settings Help.

P repara t ion2


2-1

C Select Do not allow translation of any strings in scripts to protect all text within stringsfrom translation.

For more information about script translation, see Defining Tag Settings to Handle Script Translation on page 2-19 .

In the <META charset> tags group box, define how the charset value in the <META> tag

should be handled when translating HTML documents into a language requiring a different

codepage such as Asian, Eastern European, Greek.

C Select Change charset value; add <META> tag if not present if you want TagEditor tochange the charset value if it is present in the document. If no charset value is found,TagEditor adds it to the document.

C Select Change charset value only if <META> tag is present if you want TagEditor to changethe charset value only if it was present in the source document.

C Select Do not change charset value if you want TagEditor to ignore the charset value. This

is only needed if the HTML document is processed by tools outside the SDL Tradosenvironment which rely on the charset value to remain unchanged during translation.

In the Display Options group box, define how TagEditor displays tags and treats line

breaks.

C Select the Disable formatting for tags option when translating into Asianlanguages. It disables the WYSIWYG effect for fonts in the TagEditor document window.As a result, single-byte fonts such as Arial are no longer interfering with translation usingDBCS fonts such as MS Mincho and the Copy Source command.

C Select the Keep all line breaks option if you need to keep the exact structure of line breaks

in the file(s) you wish to translate.

FOR MORE INFORMATIONV

See the Tag Settings Help for more information on line breaks.

The XML Options group box indicates if the settings are case sensitive or not.

C Element and Attribute names are case sensitive is always disabled, since setting casesensitivity is only be possible at the time settings are created. This option allows you tocheck if a certain tag settings file uses case sensitive tag names or not.

In the xml:lang attribute values group box, specify the language to be used in the xml:lang

attribute (this specifes the language used in the contents of any subsequent elements in theXML document):

C Select Change source language to target language if you always want the xml:lang attributeto be changed from the source language to the target language.

C Select Always change to target language if you always want the xml:lang attribute to bechanged to the target language, regardless of what language the attribute specifies.

C Select Do not change if you do not want to change the xml:lang attribute.

P repara t ion2


Declaring Localizable Strings

If you want to ensure that only localizable strings are accessible during translation you need to

identify these strings. To allow SDL Trados to automatically identify the localizable strings, declare

them as "L_" strings as shown in the examples below.

JavaScript

The example below contains three localizable string resources. They are highlighted in bold.

<script type="text/javascript">function validate(){x=document.myFormat=x.myEmail.value.indexOf("@")code=x.myCode.value

firstname=x.myName.valuesubmitOK="True"if (at==-1){alert("Not a valid e-mail")submitOK="False"}if (code<1 || code>5){alert("Your code must be between 1 and 5")submitOK="False"}if (firstname.length>10)

{alert("Your name must be less than 10 letters")submitOK="False"}if (submitOK=="False"){return false}}</script>

P repara t ion2


2-2

To identify these string resources as localizable:

1 Separate the localizable text from the script code by declaring them as variables.

2 Prefix the variable name with "L_".

3 Use the variable in the script code.

<script type="text/javascript">

var L_InvalidEmail="Not a valid e-mail"

var L_WrongCode="Your code must be between 1 and 5"

var L_NameTooLong="Your name must be less than 10 letters"

function validate(){x=document.myForm

at=x.myEmail.value.indexOf("@")code=x.myCode.valuefirstname=x.myName.valuesubmitOK="True"if (at==-1){alert(L_InvalidEmail)submitOK="False"}if (code<1 || code>5){alert(L_WrongCode)submitOK="False"

}if (firstname.length>10){alert(L_NameTooLong)submitOK="False"}if (submitOK=="False"){return false}}</script>



P repara t ion2


2-2

3 Click Add to add a new element.

Type the element into the Name field on the General tab. If the element already exists in the

tag settings file, you can edit it by selecting the element in the Tag Settings Properties dialog

box and clicking Properties.

4 Click Conditions.

The Element Conditions dialog box opens.

5

Click Attribute to specify an attribute/value pair.

The Attribute Condition dialog box opens.



P repara t ion2


Create attribute/value pairs such as text="donotchange" or translate="Y". You can have

multiple attribute conditions. Attribute names can be selected from the drop-down list or

typed manually. The attribute names follow the same case sensitivity as the rest of the tag

settings.

Click OK to return to the Element Conditions dialog box.

NOTED

If you type an attribute name that does not exist for the element that attribute name will be usedfor the condition but is not added to the current list of attributes for the element in the ElementProperties.

6 Click Parent Element to select parents and grandparents for the current element. The

Select Element dialog box opens.

Only elements that have no attribute conditions are shown in the drop-down list. You can

select an element name from the drop-down list or type it manually in the list box. You can add

additional parent elements by selecting the top element and clicking Parent Element. You

cannot specify a blank parent element.

Click OK to return to the Element Conditions dialog box.

NOTED

If you type an element name that does not exist that element name is used for the condition butis not added as a new element in the tag settings. You can add the element in the ElementProperties.

P repara t ion2


2-2

A Content type setting of Normal for the PARA element makes the element translatable. Setting up

an XPath for the attribute translate="N" defines an exception to make PARA elements

untranslatable based on the attribute translate="N" when the Element Content option Not

translatable is checked. Checking the Element Content option Always translatable for the nested PARA

element with the attribute translate="Y" makes the element available again inside thenontranslatable elements.

All the elements in this example use attributes with values. A single attribute value pair is

demonstrated by the <PARA translate="N"> element. A multiple attribute/value pair is shown in

the <PARA translate="Y" color="Blue"> element.

Element Content Settings

The Element Content setting for an element is used to determine if the content is translatable. For

example, an element called PARA can be configured in the Tag Settings Wizard or Tag SettingsManager using the Element Content settings as shown in the following example:

Element Option in tag settings file Result

<PARA>

...

</PARA>

Set the Content type to Normal

in the General tab of the

Element Properties

You can translate content inside the

tag

<PARA translate="Y">...

</PARA>

Set the Element Content toAlways translatable in the

General tab of the Element

Properties

You can always translate contentinside the tag, even when content is

nested inside an element marked non-

translatable

<PARA translate="N">

...

</PARA>

Set the Element Content to Not

translatable in the General tab

of the Element Properties

You cannot translate content inside

the tag



Trans la t ion2


Translating Files Using Conditional ML Tags

You may see files containing conditional ML elements. In the following example of a file in

TagEditor, the text in the PARA translate="N" element is not available for translation, but the text

in the PARA translate="Y" element is available.

Make sure you have the correct tag settings file before attempting to translate the documents. If one

does not exist you may need to create one. See Using Conditional ML Tags in Tag Settings Files on

page 2-23 for details.



Trans la t ion2


2-3

Verifying Translated Files

When you have finished translating tagged text files, you should verify the tag content of the target

files against the tag content of the original source files. Verification is necessary in order to ensure

that the syntax of tags in each target file is correct. If the syntax of tags is correct and verification issuccessful, the target file can then be converted back to its original format.

NOTED

If you are using Synergy, you can define verification settings and verify files from directlywithin Synergy.

The following verification options are available for HTML, SGML and XML files:

C Use the Generic Tag Verifier plug-in in TagEditor or Synergy to verify the tag content of eachof the above file types.

C Use the XML Validator to validate the tag content of target XML files. The XML Validator canbe used in conjunction with the Generic Tag Verifier and the XML Validator Filter plug-ins.


For more information about verifying the tag content of translated HTML, SGML and XMLdocuments, see the Translator’s Workbench User Guide or the Synergy User Guide.

Cleaning Up Translated Files

When translation, editing and tag verification are complete, the bilingual target files are ready for

clean up. The clean up process removes source language data and segment delimiting tags, thus

allowing the target file to be converted back to its original format. There are two methods of cleaning

up your translated files. The method you choose depends on whether you have used Translator’s

Workbench throughout for translation and editing.

Using the Save Target As Command in TagEditor

The Save Target As command in TagEditor cleans the translated file independently of Translator’s

Workbench and does not update the translation memory. This method of clean up is suitable if youhave used Translator's Workbench to translate and edit the document at all times, keeping the

translation memory up to date with the latest bilingual data. In the Save Target As dialog box, select

the original file type (XML, HTML, SGML) from the Save as type drop-down list. As the document

is being saved and converted back to its original format, TagEditor removes all source segments and

segment delimiters, leaving only a ‘clean’ target language version.



P ost - t r ans la t ion P rodu c t ion2


Using the Clean Up Command in Translator’s Workbench

If you have made changes to the target segments without using Translator's Workbench, these

changes have not yet been made in the current translation memory.

There are several reasons why Translator's Workbench may not be active at all times during the

document editing stage:

C You may have corrected typing errors without first re-opening the translation unit and savingthe revised translation in the translation memory afterwards.

C You may have used the Replace command to make global text changes.

In this case, use the Clean Up command in Translator’s Workbench to remove the source language

segments and to update the translation memory at the same time. Follow these steps:

1 In TagEditor, use the Save Bilingual As command (File menu) to save the tagged document asTradosTag (TTX) and close it.

2 Select Clean Up from the Tools menu in Translator’s Workbench to clean up the

document. Select Update TM in the Clean Up Files dialog box to update the translation

memory in accordance with any changes you made to the target language version

outside Workbench.

POST-TRANSLATION PRODUCTION

Once you have finished translating, verifying tags and cleaning up your translated files, they are

ready for final DTP and proofing.

Some typical tasks in post-translation production include:

C Verify that stylesheets are still correctly applied to the files.

C Ensure that links are accurate and work correctly.

C Make sure graphics are correctly placed.

NOTEDIf at this stage you choose to update any text or tags, remember to run the Clean Up commandin Translator’s Workbench to update the translation memory.



Conc lu s ion2


2-3

CONCLUSION

Now that you have completed this chapter you should know how to complete the following tasks:

Task Checked?

Prepare the ML files for translation using the Tag Settings Wizard to

create or edit tag settings files.

✔

Verify the tag content of the target files against the tag content of the

original source files.

✔

Clean up the translated files in Translator’s Workbench. ✔

Finalize translated files. ✔



Conc lu s ion2




Chapte

FRAMEMAKER AND

INTERLEAF/QUICKSILVER

FILES

This chapter explains how to work with FrameMaker and

Interleaf/QuickSilver files. Sections include:

C FrameMaker and Interleaf/QuickSilver translation

workflow

C Preparing FrameMaker and Interleaf/QuickSilver files

using the S-Taggers

C Translating FrameMaker and Interleaf/QuickSilver files

C Converting translated files back to original format using

the S-Taggers

C General post-production tasks

NOTED

If you are working with SDL Trados Synergy, this chapteris not relevant to you, as you can add MIF files directly toSynergy projects. For more information, see the Synergy User Guide . 3



Overv i ew3


OVERVIEW

This chapter gives a high level view of working with FrameMaker and Interleaf/QuickSilver file

formats.To translate FrameMaker and Interleaf/QuickSilver files, you need to convert the text in the

files to a format that is easily translated. The S-Taggers facilitate this conversion.

TIPE

If you are using SDL TeamWorks, follow the steps for downloading files in the TeamWorks User Guide and use the steps in this guide to prepare and translate the file contents.

There are two S-Taggers: S-Tagger for FrameMaker and S-Tagger for Interleaf/QuickSilver.

Installing the S-Taggers

The S-Taggers are installed as part of your SDL Trados package. By default, the S-Taggers are

installed to C:\Program Files\SDL International\T2007\TT .

Version Information

S-Tagger for FrameMaker supports MIF files generated by FrameMaker version 4.0 or later,

FrameBuilder, and FrameMaker+SGML 5.0 or later. It also supports Unicode-based MIF files

generated by FrameMaker 8.0 or later.

S-Tagger for Interleaf/QuickSilver supports IASCII and catalog files saved from Interleaf 5.2 or later.

Interleaf 7 which is included as part of the QuickSilver XML application suite and QuickSilver 3.0

are also supported.

Key Term Definition

The following key terms occur frequently in this chapter:

C FM – FrameMaker files have an FM extension.

CMIF – Maker Interchange Format. A text format used by FrameMaker which allows you toexchange information between FrameMaker and other applications. All formatting and page

layout information is retained in the MIF document.

C ILDOC – Interleaf 7 and QuickSilver files have an ILDOC extension. Older versions of

Interleaf produce files with a DOC extension.



Overv i ew3


3-

C ILSTY – Interleaf 7 catalog files have an ILSTY extension. Catalog files in

Interleaf/QuickSilver function as master style sheets. The author of the original

Interleaf/QuickSilver files sets up components, shared components, page numbering, and

headers and footers in the catalog and exports these components to other files in the

Interleaf/QuickSilver book. Older versions of Interleaf produce files with a STY extension.

C STF file – File produced when you convert MIF or IASCII files to STF using S-Tagger for

FrameMaker or S-Tagger for Interleaf/QuickSilver. It is a tagged text format that is compatible

with Translator’s Workbench and other SDL Trados tools. Formatting from the FrameMaker

and Interleaf/QuickSilver documents is represented by brief coded statements (S-Tags).

C CAT file – a file created by S-Tagger from Interleaf/QuickSilver catalog files when converting

them to STF.

C IASCII – Interleaf ASCII. IASCII is a text file format that allows you to exchange information

between Interleaf/QuickSilver and other applications. All formatting, file and page layout isretained in the IASCII file.

C S-Tags – Coded statements that the S-Taggers use to represent document formatting. These

tags can be either external or internal.

C Conversion – Refers to the conversion of MIF/IASCII files to STF format. It also refers to the

conversion of the STF files back to their original file format (MIF/IASCII) after translation.

C Verification – Refers to the comparison process where the tags in the target STF file are

compared and verified against the tags in the source STF file. During and after translation,

translators should verify that they have placed all the tags in the translated files in the correctsequence and position.

How the S-Taggers Work

The S-Taggers are conversion utilities that convert FrameMaker MIF files and Interleaf/QuickSilver

IASCII files into STF, which is the umbrella name for the tagged text formats that are compatible

with Translator’s Workbench and TagEditor. STF files can be RTF, TXT or TTX files. You can

translate these STF files using TagEditor or Microsoft Word.

After translation, you can use the tag verification features in TagEditor and in the S-Taggers to verifythe tag content of your target STF files. Successful verification guarantees successful backward

conversion to MIF/IASCII. When your STF files have been verified, you can convert the STF files

back to their original file format.

The S-Taggers are used in conjunction with the Font Mappers, which specifies the fonts that you

wish to map quickly and easily. This is necessary when working with Asian languages such as

Japanese. There are two Font Mappers: Font Mapper for FrameMaker and Font Mapper for

Interleaf/QuickSilver.



Overv i ew3


Translation Workflow

Translation of a FrameMaker or an Interleaf/QuickSilver file involves the following stages:

1

Create a folder structure. An orderly folder structure helps you to keep track of all your sourceand target files.

2 Prepare your FrameMaker or Interleaf/QuickSilver files for translation.

3 Save your FrameMaker files as MIF or your Interleaf/QuickSilver files as IASCII.

4 Select your conversion settings in the S-Taggers.

5 Convert your MIF/IASCII files to STF format using the appropriate S-Tagger.

6 Analyse and pre-translate the documents for translation in Translator’s Workbench,

using the Analyse and Translate batch tools.

7 Translate the STF files.

8 Verify the tag content of the target files.

9 Clean up the translated files using the Clean Up command in Translator’s Workbench.

10 Convert the translated STF files back to MIF/IASCII format.

11 Open the new MIF/IASCII files in FrameMaker or Interleaf/QuickSilver and save

them in FM/ILDOC format. You can now carry out the final DTP work, such asgenerating the index and table of contents.

NOTED

C If you are translating into an Asian language you need to map your fonts so that thetranslated documents can be opened and viewed. See the online help for the Font Mappersfor more information.

C For more information on translating files in TagEditor or Word and the batch features inTranslator’s Workbench, see the Translator’s Workbench User Guide.



Trans la t ion3


Text only (TXT) files have the extension .txt and can be opened in any text editor that supports ANSI

text. The tags have no special formatting. If you are going to translate ANSI text files and the files are

very large, you may not be able to edit them in Notepad or other small text editors. Always open and

save the files as text only, without formatting. It is very important that you never open or save the

files as MS-DOS text or in a DOS-based editor. ANSI text format is mainly used for communicationwith document management or machine translation systems and is not recommended for

interactive translation.

NOTED

C The default setting for this option is Rich text format (RTF). If you are using SDL GXT, youmust change this setting to TradosTag (TTX).

C When translating into Asian languages, you must choose Rich text format (RTF) orTradosTag (TTX) as the file format.

C

We recommend that you use the same STF file format setting for forward and backwardconversion of files.

C The option you choose for the STF file format is written to the registry and does not changeuntil you manually change it.

You should:

C Create folder structure for your translation project

C Prepare your FrameMaker or Interleaf/QuickSilver files for translation

C Save your FrameMaker or Interleaf/QuickSilver files as MIF/IASCII

C Select your conversion settings in the S-Taggers

C Convert your MIF/IASCII files to STF format.

TRANSLATION

Translate your FrameMaker and Interleaf/QuickSilver files using Translator's Workbench and

TagEditor. The following steps offer a high level view of the translation process for FrameMaker and

Interleaf/QuickSilver files:

1 In Translator’s Workbench, activate any translation project and filter settings that are required.


using the Analyse and Translate batch tools. During pretranslation, Workbench RTF

can be converted to TradosTag (TTX) format on the fly.

3 Translate your documents in TagEditor or Word.



Conc lu s ion3


CONCLUSION

Now that you have completed this chapter you should understand the FrameMaker or

Interleaf/QuickSilver translation process and know where to find detailed information on all tasks

involved in this process:

Task Checked?

Understand how S-Taggers works and how to install the S-Taggers ✔

Prepare FrameMaker and Interleaf/QuickSilver files for translation ✔

Verify the tag content of the target files against the tag content of the

original source files

✔

Clean up the translated files in Translator’s Workbench ✔

Finalize translated files ✔



Chapte

PAGEMAKER FILES

This chapter explains how to work with the PageMaker DTP

file format. Sections include:

C PageMaker translation workflow

C Preparing and exporting PageMaker files for translationusing Story Collector for PageMaker

C Translating PageMaker files

C Importing translated files back into PageMaker usingStory Collector for PageMaker

4



Overv i ew4


4-

Key Term Definition


CP65 – PageMaker 6.5 files have a P65 extension.

C PMD – PageMaker 7 files have a PMD extension.

C Export file – a tagged text file in TXT format containing untranslated text. This file is producedwhen you export stories from a PageMaker file.

C Import file – a tagged text file in TXT format containing translated text. You import this fileinto a copy of the source PageMaker file overwriting the source language text contained in it.

C Story order – the order in which stories are arranged in a PageMaker file. It is important thatstories be presented for translation in a logical sequence. Story Collector allows you to changethe order of the stories without affecting the layout of your file.


Translation of a PageMaker file involves the following stages:

1 Install Story Collector for PageMaker.

2 Prepare your PageMaker source files for translation.

3 Create a folder structure for your PageMaker translation project.

4 Set the story order in your PageMaker source file.

5 Export all stories from the PageMaker file to a text file (TXT).

6 Translate the file.

7 Import the file back into PageMaker.

8 Cut and paste any inline graphics from your PageMaker source file into your translated

PageMaker file.

NOTED

If you are working in SDL Trados Synergy, you can add the file to a Synergy project once it hasbeen converted to TXT format. The file can then be translated and reviewed in Synergy. When itis returned from the Synergy workflow, you must then import the file back into PageMaker.



Overv i ew4


Installing Story Collector for PageMaker

Story Collector for PageMaker is included as part of your SDL Trados installation. These files are

installed by default to the following location:

C C:\Program Files\SDL International\T2007[_FL]\FI\PM .

Before you install the Story Collector plug-in, make sure that PageMaker is installed on your system

and that it is not running.

1 Copy the following files from the default Story Collector installation folder to the Plugins

folder in the Adobe PageMaker installation folder. The Plugins folder will normally be

found in the C:\Program Files\Adobe\PageMaker 7.0\Rsrc\Lang\ folder, where Lang is the

language of your installation.

C

Trados Story Collector.addC StoryCollectorPM1033.HLP

C StoryCollectorPM1033.cnt

2 Open PageMaker and the file which contains the text you wish to export. On the

Utilities menu, point to Plug-ins and choose Trados Story Collector from the submenu.

The Trados Story Collector dialog box is displayed, ready for use.

NOTED

The Plugins folder of a PageMaker 6.5 default installation is located inC:\PM65\Rsrc\Lang\ folder, where Lang is the language of your installation.

Online Help

Story Collector installs a comprehensive help system into the Story Collector installation folder. To

access help from within Story Collector, make sure you copy the HLP and CNT files into the

PageMaker Plugins folder.

Sample File

You can use the sample PageMaker 6.5 file (sample.p65) to work with the Story Collector for

PageMaker that ships with SDL Trados. This sample file is installed to

C:\Documents and Settings\All Users\Documents\SDL Trados\Samples\Story Collector for

PageMake r. You should use the sample file to work through the Story Collector process example that

follows in this chapter.



P repara t ion and Expor t4


4-

Opening Story Collector for PageMaker

In PageMaker, choose Trados Story Collector from the Plug-ins submenu in the Utilities menu. The

Trados Story Collector dialog box is displayed:

Setting the Story Order

By default, the stories on each page in your PageMaker document are exported in the order in which

they were originally created. However, this may not correspond to the order in which they flow

logically. The story order function in Story Collector allows you to choose the order in which stories

are exported to the tagged text file so that they are presented in a logical sequence for translation.

This will not affect the layout of the PageMaker file.

NOTED

Before you select the story order for the export file, go through your PageMaker document andmake sure that the page views you have set allow you to see all the stories and read the text oneach page.



Trans la t ion4


TRANSLATION

Once you have created TXT versions of your files, you can either add the files to Synergy for

translation or translate them using Translator’s Workbench and TagEditor.

NOTED

If you add files to Synergy, you will not need to carry out steps 2, 3 and 4 below. This is becausefiles are automatically converted to bilingual TradosTag (TTX) format when projects are createdin Synergy, files can be verified directly in Synergy and clean-up happens automatically whenfiles are finalized in Synergy.

The following steps offer a high level view of the translation process for PageMaker files.

1 Export your file to your source TXT folder, and then place a copy of it in your target TXT folder.

2 Translate the file in your target TXT folder using TagEditor, saving the file in bilingualTradosTag (TTX) format during translation.

3 When you have finished translating, verify the tag content of the translated file using

the Generic Tag Verifier in TagEditor. Successful verification ensures that the syntax of

tags in the translated file is correct and guarantees backward conversion.

4 After verification, use the Clean Up command in Translator’s Workbench to remove

bilingual data from the translated file and to convert the file back to TXT format. If

necessary, you can also use the Clean Up command to update the translation memory

with the latest bilingual data.

5 Save the file to your target TXT folder.

6 Open the source file you previously placed in your target P65 folder in PageMaker.

Import the file back from your target TXT folder using Story Collector for PageMaker,

and save.

NOTED

For more information about translating files in TagEditor and the clean up feature inTranslator’s Workbench, see the Translator’s Workbench User Guide.





4-1


This section explains how to import translated files back into PageMaker.

Importing Translated Stories

1 Open the copy of the original PageMaker file that you placed in the target P65/PMD folder

earlier.

2 Choose Trados Story Collector from the Plug-ins submenu in the Utilities menu. The

Trados Story Collector dialog box is displayed.

3 In the Trados Story Collector dialog box, click Import to open the Select Import File

dialog box. Use this dialog box to locate the file that now contains the translated storiesin your target TXT folder.

4 Click Open. Story Collector imports the translated stories back into the PageMaker file

in the correct sequence.

5 The progress and results of the import operation are displayed in the Results window

of the Trados Story Collector dialog box. After import, you can save the contents of this

window to a results file by clicking Save Results. The Save Results As dialog box is

displayed where you can specify the location and name of the results file.

6Cut and paste any inline graphics from your PageMaker source file into your translatedPageMaker file.

After import, the file is ready for final DTP and proofing.

Trou b leshoot ing4


TROUBLESHOOTING

This section helps you to deal quickly and effectively with problems you may encounter while using

Story Collector in conjunction with PageMaker.

Tips for Export

The following tips should help you export stories from PageMaker.

Non-printing Elements

Story Collector does not support the export of stories that have been formatted as non-printing

elements in the PageMaker file. If you wish non-printing elements to be included in the export file

for translation, remove the non-printing attribute before export and re-apply it manually in the

translated PageMaker file after import.

Index Entries

C Index entries are not exported if they appear at the very end of a story. Before export, makesure that all index entries are contained within a body of text.

C PageMaker does not support special characters in index entries during export/import. Specialcharacters include quotation marks (“ ”) or the greater than (>) and less than (<) characters.

These characters should be removed from the PageMaker file before export.

C The page range for index entries is reset to standard (Current Page) during export/import.After import, review all index entry page ranges in the target file.

Cross-references

PageMaker does not support the export of cross-references. Cross-references must be manually

inserted and translated in the target file after import.

Special Characters

C PageMaker does not support the greater than (>) and less than (<) characters during export/import. If the tagged text file for import contains either of these characters, import will fail.

C PageMaker does not support the use of quotation marks in color tags during export/import.Before export, make sure that there are no quotation marks in your PageMaker colordefinitions.

Tag Re fe rence Mate r i a l4


Tips for Japanese PageMaker 6.5 and 7

C Japanese PageMaker 6.5 and 7 do not support European extended characters in color names.If your target language is Japanese and you are using Japanese PageMaker 6.5 or 7 to import

translated text, it is important to ensure that there are no European extended characters in thecolor name tags of the translated text file. The presence of these characters in color name tagswill cause the import to fail. To avoid this situation, check all color names in the source PageMaker file before export. Where necessary, rename colors using low ASCII characters(numbers 1-127 in the ASCII character set) only.

C Japanese PageMaker 6.5 and 7 do not support European extended characters in index entries.If your target language is Japanese and you are using Japanese PageMaker 6.5 and 7 to importtranslated text, it is important to ensure that all European extended characters in the indexentries of the translated text file have been replaced with their Japanese equivalents.

C If you used Japanese PageMaker 6.5 or 7 during export, you must also use it to import the

translated text file back into the PageMaker file. This ensures that tags containing Japanesecharacters are correctly interpreted during import.

C If your source language is Japanese and you are using Japanese PageMaker 6.5 or 7, yourPageMaker file may contain paragraph styles that are named in Japanese. During export, thenative PageMaker filter formats these style names as tags. However, tags with Japanesecharacters may cause the import of stories back into the target PageMaker file to fail, evenwhen Japanese PageMaker 6.5 or 7 is being used. For this reason, we recommend that youalways check whether or not the export file can be imported successfully back into thePageMaker file before you proceed with translation.

TAG REFERENCE MATERIAL

This section outlines the tags that Story Collector for PageMaker adds to the tagged text file as well

as the tags that PageMaker itself introduces.

Story Collector for PageMaker Tags

In addition to the PageMaker tags that will appear in the tagged text file, Story Collector includes

some of its own tags. Story Collector tags use the ‘$’ symbol to differentiate them from the normalPageMaker tags. Each Story Collector tag will appear on a separate line.

This table lists the Story Collector tags.

Tag Description

<$PMExtTags1.0win> Extended PageMaker tags file signature

4-1

Tags in PageMaker Tagged Text Files

The tables below contains an overview of the different kinds of tags in PageMaker tagged text files.

Types of tag include:

C general tags

C character attribute tags

C structural tags

C paragraph tags

General Tags

<$storystart> Beginning of story

(might contain a single text block)

<$storyend> End of story

<$stname "name"> Story name

Tag Type Category

<m> Em space Placeholder

<!m> Non-breaking Em space Placeholder

<n> En space Placeholder

<!n> Non-breaking En space Placeholder

<t> Thin space Placeholder

<!t> Non-breaking thin space Placeholder

<w> Word space Placeholder

<!w> Non-breaking space Placeholder

<r> Soft return Placeholder

<d> Discretionary hyphen Placeholder

<\!-> Non-breaking hyphen Placeholder

Tag Description

<\!/> Non-breaking slash Placeholder

<\#(number)> Any character, encoded. Placeholder\< The character < Placeholder

\> The character > Placeholder

<&#### ### ###

"path and filename">

Inline graphics file Placeholder

<*INDEX # # #

("text" "" "") ("text" ""

"")>

Index marker Placeholder

Note: Text within quotes needs

to be localized!

Tag Type Category

4-2

<ghyphenation #

### #>

Hyphenation method Structural

<g0> No hyphenation Structural

<g1> Only manual hyphenation Structural

g2> Manual + dictionary hyphenation Structural

<g3> Manual + algorithm hyphenation Structural

<gktogether> Keep paragraphs together Structural

<gkt> Keep paragraphs together Structural

<gkbegin> Keep paragraphs together - beginning Structural

<gkb> Keep paragraphs together - beginning Structural

<gkend> Keep paragraphs together - end Structural

<gke> Keep paragraphs together - end Structural

<gknext ###> Keep with next Structural

<gkn###> Keep with next Structural

<gkwidow ### Widow control Structural

<gkw###> Widow control Structural

<gkorphan ###> Orphan control Structural

<gko###> Orphan control Structural

<g+page> Page break Placeholder

<g+p> Page break Placeholder

<g+column> Column break Placeholder

<g+c> Column break Placeholder

<gcontents> Include in TOC Structural

<gc> Include in TOC Structural

Tag Type Category



Conc lu s ion4


CONCLUSION


Task Checked?

Prepare PageMaker files for translation. ✔

Set a logical story order in a PageMaker file. ✔

Export stories for translation. ✔

Import translated stories. ✔


Troubleshoot common problems. ✔

Know where to find detailed tag information. ✔



Overv i ew5


OVERVIEW

To translate QuarkXPress files, you need to convert the text in the files to a format that is easily

translated.

Story Collector for QuarkXPress facilitates the export of tagged text from QuarkXPress and the

subsequent re-import of text after translation, minimizing the amount of time that needs to be spent

on preparatory and post-translation work.

Story Collector for QuarkXPress works with QuarkXPress 4.1, 5.x, 6.x. It converts files in QXD and

QXT format to a text format (QSC) that can be easily added to SDL Trados Synergy projects and

translated using Translator's Workbench and TagEditor.

NOTED

You can also easily translate XTG, TTG, and TAG file formats. These are produced directly byQuarkXPress and CopyFlow export functionality. See QuarkXPress documentation for moredetails.

Using QuarkXPress 7.x

QuarkXPress 7.x is only supported through the third-party application, CopyFlow. You must use

CopyFlow to translate your QuarkXPress 7.x files and then export the translated files back from

CopyFlow to use with SDL Trados. For more information, please see the CopyFlow documentation.

NOTEDTagEditor only supports Unicode UTF-16 encoding of exported CopyFlow files.

How Story Collector for QuarkXPress Works

Story Collector for QuarkXPress is a QuarkXPress 4.1, 5.x, and 6.x XTension. This means that it uses

the Application Programming Interface (API) provided by QuarkXPress to add extra functionality to

QuarkXPress itself. Once you have placed certain files in the XTension of QuarkXPress, you can

access Story Collector functionality via the Trados menu.

Story Collector has three basic functions which are presented in the Trados menu in QuarkXPress.

These are the story order, export and import functions. These functions are duplicated for batch

operations.

C Story Order: Before exporting stories from your QuarkXPress document, you can determine

the order in which they appear in the export file. This means that stories are presented for

translation in a sequence that is as logical as possible.



Overv i ew5


5-

C Exporting Stories: After setting the story order, you specify a name and location for the tagged

text export file. After exporting all stories to this file, you then open the file in TagEditor. The

file is translated in the normal way, using Translator’s Workbench.

C Importing Stories: After translation, you save the file to QuarkXPress tagged text format, and

import the translated stories into a copy of the original QuarkXPress file, using Story

Collector.



Overv i ew5


5-


Translation of a QuarkXPress file involves the following stages:

1Install Story Collector for QuarkXPress.

2 Prepare your QuarkXPress source files for translation.

3 Create a folder structure for your QuarkXPress translation project.

4 Set the story order in your QuarkXPress source file.

5 Export all stories from the QuarkXPress file to a text file (QSC).


7 Import the file back into QuarkXPress.

8 Reposition any inline graphics into their original position. Use your QuarkXPress

source files as a reference if necessary.

NOTED

C If you are working in SDL Trados Synergy, you can add the file to a Synergy project once ithas been converted to TXT format. The file can then be translated and reviewed in Synergy.When it is returned from the Synergy workflow, you must then import the file back intoQuarkXPress.

C You can also use Story Collector for QuarkXPress to process a batch of QuarkXPress files.For more information, See “Batch Functions in Story Collector for QuarkXPress” on page 5-14.

Installing Story Collector for QuarkXPress

Story Collector for QuarkXPress is included as part of your SDL Trados installation. These files are


C C:\Program Files\SDL International\T2007[_FL]\FI\QXP

There are folders for each supported version of QuarkXPress in English and Japanese in the QXP

folder:

C 4.1_E

C 4.1_J

C 5.0_E





To keep a copy of each file and file format:

1 Place the files to be translated in the source QXD folder.

2 Place a copy of the same files in the target QXD folder.

3 Export the source files from the source QXD folder to your source QSC folder.

4 We recommend that you copy the files in your source QSC folder into your target QSC

folder as it makes it less likely that you overwrite the source QSC files by mistake.

5 Either add the TXT files to a Synergy project to be translated or translate them directly

using Translator's Workbench and TagEditor. Save the translated files in your target

QSC folder.

6 Open the copy of the source files you placed in the target QSD folder earlier, import the

translated files from the target QSC folder.

7 Reposition any inline frames in your translated files and save.

Opening Story Collector for QuarkXPress

Open a QuarkXPress document. A Trados menu is visible on the top menu bar. To open Story

Collector, select an option from this menu.





5-


By default, the stories on each page in your QuarkXPress document are exported in top-down order.

However, this may not correspond to the order in which they flow logically. The story order function

in Story Collector allows you to choose the order in which stories are exported to the tagged text fileso that they are presented in a logical sequence for translation. This will not affect the layout of the

QuarkXPress file.

To set the story order for the tagged text export file:

1 From the Trados menu select Story Order. The Story Order dialog box appears.

2 The Page List box displays an entry for the master page, and one entry for each page of the document. Clicking on an entry displays the stories in that page in the Story List box directly below. QuarkXPress also displays the selected page behind the Story Order dialog box so you can see the page in question.

3 You may change the story order by clicking on a story in the Story List box, and use thearrows to the left of the Story List box to reorder them. This activates the Custom orderradio button in the Story Order box. Alternatively, you may set the story order for all

pages by clicking on the Top-Down order or Left-Right order radio buttons in the StoryOrder box.

C Top-down order: Story Collector for QuarkXPress starts at the top of the page and movesfrom left to right at each height. Therefore, stories situated higher on the page than otherstories are always exported first, even if the other story is farther left.

C Left-right order: Story Collector for QuarkXPress starts at the left of the page and exports allleftmost stories beginning at the top and finishing at the bottom of the page. It thenreturns to the top of the page, and so on. Therefore, leftmost stories are exported first evenif one story is higher than another on a page.





C Custom order: You may rearrange the story order on each page in any order you wish. Todo this, select each story in turn and use the arrows to move them. You can also drag anddrop the stories into position.

NOTED

When you click on a story in the Story List box, the text associated with that story appears inthe Selected Story Text box. It is also highlighted in the QuarkXPress document behind thedialog box.

4 When you are satisfied with the story order for the tagged text export file, click OK to

confirm the story order, Reset to start again, and Export if you wish to export this file

immediately.

C Even if you are working with multiple page spreads in QuarkXPress, you can onlyrearrange the story order within a single page at a time. Stories that spread over more thanone page appear under the page they start on.

C If you do not set the story order for an individual file, Story Collector for QuarkXpress willuse the story order set in the Settings dialog box by default.





5-1

Exporting Stories

To export all the stories in your QuarkXPress file to a single text file:

1Open the QuarkXPress file you wish to export.

2 From the Trados menu, select Export. The Select Export File dialog box appears.

3 In the Select Export File dialog box, specify the location of your source QSC folder, and a

name for the extended tagged text file. The same file name as the source file is

automatically suggested.

4 Click Save, a series of progress bars appear and Story Collector for QuarkXPress

creates an export file in the folder you specified. The Export Results dialog box opens. Ittells you if the export has been successful and how many stories have been exported.

5 Click OK to finish the export process, or click Save As to save the export results to a log

file. The Save Log File dialog box opens.

6 Browse to where you want to save the log file, name it and click Save. Story Collector

for QuarkXPress saves it under the name and in the location you specified.

7 Click OK in the Export Results dialog box and the export process is finished.

All stories are collected and placed in a QSC file in the source QSC folder you specified. Werecommend that you copy the files in your source QSC folder into your target QSC folder as it makes

it less likely that you overwrite the source QSC files by mistake. You can now translate the files in

your target QSC folder.

NOTED

If you have the index extension palette open in QuarkXPress, you can export full index entries.If it is closed, you can export only partial index entries.



Trans la t ion5


TRANSLATION

Once you have created TXT versions of your files, you can either add the files to Synergy for

translation or translate them using Translator’s Workbench and TagEditor.

NOTED


The following steps offer a high level view of the translation process for QuarkXPress files.

1 Export your file to your source QSC folder, and then place a copy of it in your target QSC folder.

2 Translate the file in your target QSC folder using TagEditor, saving the file in bilingualTradosTag (TTX) format during translation.





bilingual data from the translated file and to convert the file back to QSC format. If



5 Save the file to your target QSC folder.

6 Open the source file you previously placed in your target QXD folder in QuarkXPress.

Import the file back from your target QSC folder using Story Collector for

QuarkXPress, and save.

NOTED




Batch Fu nc t ions in S to r y Co l l ec to r fo r Qu arkXP ress5


NOTED

C If you have the index extension palette open in QuarkXPress, you can import full indexentries. If it is closed, you can import only partial index entries.

C

If your QuarkXPress file contains inline frames, QuarkXPress places them at the start of thetranslated file when you import your translated file back into QuarkXPress. You need tomove these inline frames back into their original position. Use your source QXD files as areference if necessary.

BATCH FUNCTIONS IN STORY COLLECTOR FORQUARKXPRESS

When dealing with multiple files, the story order, the export and import operations differ slightly to

those of single files described earlier on in this chapter.


To set the story order for a batch export operation:

1 From the Trados menu, choose Settings. The Settings dialog box is displayed.

2 In the Default Story Order box, select either Top-down order or Left-right order.

C Top-down order: This means Story Collector for QuarkXPress starts at the top of the pageand moves from left to right at each height. Therefore, stories situated higher on the pagethan other stories are always exported first, even if the other story is farther left.

C Left-right order: This means Story Collector for QuarkXPress starts at the left of the pageand exports all leftmost stories beginning at the top and finishing at the bottom of thepage. It then returns to the top of the page, and so on. Therefore, leftmost stories areexported first even if one story is higher than another on a page.

The order you choose applies to all subsequent batch export files, and to individual files if you

do not set a story order in the Story Order dialog box.





5-1

NOTED

For batch operations, story order is limited to Top-down or Left-right. There is no custom orderoption.

3 Select default batch import and export directories in the Default Batch Directories box.You must specify these or the Batch Export and Batch Import buttons in the in the

Batch Export and Batch Import dialog boxes remains greyed out. These settings are

retained and used as default settings until you change them again.

4 Click OK to confirm the settings.

NOTED

The Settings dialog box allows you to include stories left on the pasteboard. These are placedafter the Master page stories and before the main page stories in the export file.

Exporting Stories

To export stories from multiple files at the same time:

1 Select a default Batch export folder for the batch files. You do this in the Settings dialog box.

You must set this before you can export multiple files. The Batch Export button in the Batch

Export dialog box remains greyed out until you select an export folder.

2 From the Trados menu, choose Batch Export. The Batch Export dialog box appears.





3 Click Add. The Add Files dialog box is displayed.

4 Browse to your source QXD folder and select the files that contain stories for export.

Click Open to confirm your selection. The selected files are added to the Files To Export

list in the Batch Export dialog box.

5 In the Batch Export dialog box, your source QSC folder appears as you previously

selected it in the Settings dialog box. You can change this if you wish by selecting

another folder using the Browse button, but it reverts to the folder specified in the

Settings dialog box for subsequent batch export operations.

6 In the Batch Export dialog box, click Export to run the export operation. The Batch

Export progress bar is displayed and Story Collector for QuarkXPress creates an export

file(s) in the folder you specified. The Batch Export Results dialog box opens. It tells

you if the export has been successful, the time and the date of the export and how

many stories have been exported.

7 Click OK to finish the export process, or click Save As to save the batch export results to

a log file. The Save Log File dialog box opens.




Story Collector for QuarkXPress creates an export file (QSC) for each Quark source file in the source

QSC folder. Each export file has the same name as its corresponding QXD file.

NOTED

You must close the index palette before undertaking a batch export. The Batch Export menuoption is greyed out until the index extension palette is closed.





5-1

Importing Stories

To import multiple files at the same time:

1Select a default Batch import folder for the batch files. Select your target QSC folder. You dothis in the Settings dialog box. You must set this before you can export multiple files. The Batch

Import button in the Batch Import dialog box remains greyed out until you select an import

folder.

2 From the Trados menu in QuarkXPress, select Batch Import. The Batch Import dialog

box is displayed.

3 Click Add. The Add Files dialog box is displayed.

4 Browse to your target QXD folder, and select the untranslated files that you wish to

overwrite. Click Open to confirm. The selected files are added to the Files to Import list

in the Batch Import dialog box.

5 In the Batch Import dialog box, your target QSC folder appears as you previously

selected it the Settings dialog box. You can change this if you wish, but it reverts to the

folder specified in the Settings dialog box for subsequent batch import operations.





6 In the Batch Import dialog box, click Import to run the import operation. The Batch

Import progress bar is displayed and Story Collector for QuarkXPress overwrites the

copy of the original source file(s) in the target QXD folder with the import file(s). The

Batch Import Results dialog box opens. It tells you if the import has been successful,

the time and the date of the import and how many stories have been imported.

7 Click OK to finish the import process, or click Save As to save the batch import results

to a log file. The Save Log File dialog box opens.



9 Click OK in the Import Results dialog box and the import process is finished.

Story Collector for QuarkXPress overwrites existing files of the same name in the target QXD folder.

Therefore each target QXD file has the same name as its corresponding source QXD file, but islocated in the target folder.

NOTED

C You must close the index palette before undertaking a batch import. The Batch Import menu option is greyed out until the index extension palette is closed.

C If your QuarkXPress file contains inline frames, QuarkXPress places them at the start of thetranslated file when you import your translated file back into QuarkXPress. You need tomove these inline frames back into their original position. Use your source QXD files as areference if necessary.

The tables below contains an overview of the different kinds of tags in PageMaker tagged text files.

Types of tag include:

C document structure tags

C special character tags

C character formatting tags

C paragraph formatting tags

C style sheet definition tags

Document Structure Tags

Tag Type Category Comment

<1.6x> XPress 3.2 generated file Structural Version number for tag

language.


language.


language.


language.

<A...> Application XTension

specific tag

Emphasis This can be anything...

<e0> Macintosh character set Structural Appears after version

tag.

<e1> Windows ANSI character

set

Structural Appears after version

tag.

<e2> ISO Latin 1 character set Structural Appears after version

tag.

<XO> Start of XPress index

marker

Structural Applies to version 4.1

and higher

<XC,"…"> Index level tag Structural Appears after <XO> tag.

TIPE

Character formatting can be combined in one tag, for example <BI> for Bold Italic. Wherethere is a second occurrence of a character formatting tag following an initial characterformatting tag, the second tag turns the corresponding formatting off.

<\!h> Non-breaking discretionary

hyphen

Placeholder

<\2> Previous text box page number Placeholder

<\3> Current text box page number Placeholder

<\4> Next text box page number Placeholder

<\c> New column Placeholder

<\b> New box Placeholder

<\#character code> Any character Placeholder

Note: The character depends on

the code page. The # charactermust appear.

<\!#character code> Non-breaking character Placeholder

Note: The character depends on

the code page. The # character

must appear.

<\@> The @ character Placeholder

<\<> The < character Placeholder

<\\> The \ character Placeholder

<\#13> Hard return Placeholder

<\#9> Tab character Placeholder

Tag Type Category

5-2

Character Formatting Tags

Tag Type Category

 Plain text Emphasis

 Bold on/off Emphasis

 Italic on/off Emphasis

<O> Outline on/off Emphasis

<S> Shadow on/off Emphasis

 Underline on/off Emphasis

<W> Word Underline on/off Emphasis

</> Strikethrough on/off Emphasis

<K> All Caps on/off Emphasis

<H> Small Caps on/off Emphasis

<+> Superscript on/off Emphasis

<-> Subscript on/off Emphasis

<V> Superior on/off Emphasis

<$> Default paragraph style EmphasisNote; Prior to QuarkXPress

version 4.0, these tags also

appear after each 254 characters,

and should in be removed before

translation.

<f"font name"> Change font Emphasis

<f$> Default paragraph font Emphasis

<z###.##> Font size Emphasis

<z$> Default paragraph size Emphasis

<c"color name"> or <cC, cM,

cY, cK, cW>

color change Emphasis

<c$> Default paragraph color Emphasis

<s###> Change shade Emphasis

NOTED

The # symbol represents a number.

<s$> Default paragraph shade Emphasis

<h###> Horizontal scaling Emphasis

<h$> Default horizontal scaling Emphasis

<y###> Vertical scaling Emphasis

<y$> Default vertical scaling Emphasis

<k###.##> Kern next two characters Miscellaneous

<t###.##> Track text Emphasis

<t$> Default text tracking Emphasis

<b###.##> Set baseline shift Emphasis

<b$> Default baseline shift Emphasis

Conc lu s ion5


Style Sheet Definition Tags

CONCLUSION


Tag Type Category

@Stylesheetname=<definition>

Style sheet definition StructuralNote; Stylesheetname is a user

defined name.

Task Checked?Prepare QuarkXPress files for translation. ✔

Set a logical story order in a QuarkXPress file. ✔

Export stories for translation. ✔

Import translated stories. ✔


Know how to use the Story Collector batch functions. ✔

Know where to find detailed tag information. ✔



Chapte

INDESIGN FILES

Chapter 6 deals with translating the InDesign files. Files from

InDesign CS2/CS3 can be exported to the InDesign

Interchange Format (INX) and added directly to SDL Trados

Synergy projects or opened directly in TagEditor. Files from

InDesign 2 and InDesign CS have to be prepared for

translation using the Story Collector for InDesign.

NOTED

If you are using INX files from InDesign CS2/CS3, only thefinal part of this chapter from page 6-46 on is relevant.

C Translating InDesign CS2/CS3 INX files

C Preparing and exporting InDesign files for translationusing Story Collector for InDesign

C Translating InDesign files

C Importing translated files back into InDesign using StoryCollector for InDesign

C Defining Java Virtual Machine Size filter settings6



Trans la t ing InDes ign CS2/CS3 f i l e s6


TRANSLATING INDESIGN CS2/CS3 FILES

Synergy and TagEditor support InDesign CS2/CS3 files which are exported directly from InDesign

CS2/CS3 as InDesign Interchange Format (INX). INX is an XML-based exchange format file. The

INX files are often smaller than the InDesign INDD files as they do not contain graphics but ratherreferences to the graphics.

WARNINGF

Although InDesign CS files could be exported to InDesign Interchange Format, only INX filesfrom InDesign CS2/CS3 are supported by Synergy or TagEditor. INX files from earlier versionsare not supported.

In InDesign use the File > Export option to export the file you want to translate to InDesign

Interchange Format (INX). This operation can be performed on either Mac or PC.

Using the Filter Settings Application for the InDesign CS2/CS3 Filter

You can use the InDesign CS2/CS3 Filter Settings to modify a number of filter settings:

C Process content on master pages

C Process content on hidden and locked layers

C Process forced returns

C

Show display formattingC Use font mapping

C Make destinations of external locations translatable

C Make hyperlinks translatable

C Process INX files derived from PageMaker documents

C Switch directionality (for translations from/to bidi lanaguges)





6-

You can also reset the filter settings back to the default values.

To run the Filter Settings application:

1 Select Start > Programs > SDL International > SDL Trados 2007 > Trados > Filters > Filter

Settings. Alternatively, click the link in the Start view in SDL Trados Synergy. The Filter

Settings application opens.

2 Click InDesign CS2/CS3 and select any options you want to include in the filter.

3 Click Save to save your changes.

4 Click Exit to close the application.

TIPE

If you do not want to save the changes, and you have not clicked Save, clicking Exit will closethe application without saving.





Modifying the InDesign CS2/CS3 Filter Settings File

During conversion to and from TradosTag, the filter processes content according to instructions that

are outlined in the InDesign CS2/CS3 filter settings file. The name of this file is

IndesignFilter_1_0_0_0.xml and it is installed by default to C:\Documents and Settings\All Users\Application Data\SDL International\Filters .

Note that the Application Data folder may be hidden and you will have to set it to be visible if you

want to see this folder and any subfolders. Also, if you want to make any changes to files in this

folder, you must have read/write access to this folder. Consult your IT department for more

information.

The settings in the filter settings file determine which elements of the InDesign CS2/CS3 document

will be converted, and how. The default settings are suitable for most conversion tasks, however, in

certain situations, you may wish to modify one or more of the default settings. By default, you do this

in the SDL Trados Filter Settings application, as outlined above. You may also wish to changesettings manually by opening the XML file directly in an appropriate editor.

NOTED

C We recommend that only advanced XML users modify the InDesign CS2/CS3 filter settingsfile. Before making any changes, create a backup of the original file.

C For more information about modifying the InDesign filter settings file, contact SDLConsultancy.

Translating InDesign CS2/CS3 Interchange Format Files

You can add files which have an .inx extension directly to Synergy projects or open them directly in

TagEditor.

NOTED

If you add the files to a Synergy project, you can open them for translation from directly withinSynergy and do not need to carry out the steps below. For more information, see the Synergy User Guide .

To translate files with an .inx extension in TagEditor:

1 Select Start > Programs > SDL International > SDL Trados 2007 > Trados > TagEditor to launch

TagEditor.

2 From the File menu choose Open. From the Open dialog choose InDesign CS2/CS3

Interchange (*.inx) from the list of available file types.

3 Browse to the location of your InDesign CS2/CS3 Interchange files.





6-

4 Select the file you want to translate and the file opens in TagEditor.

5 Translate the file in TagEditor

6 You can save the file as target to generate the target INX file or do a Clean-Up.

7 You can open the target INX in InDesign CS2/CS3 and then save it as INDD. The INX

files do not actually contain elements such as images but only contain a reference to

those elements. This is why such elements should be stored at the corresponding

locations. If the user has deleted images, they will not be visible when opening the

target INX file, as the referenced resources no longer exist.

8 You can use the TradosTag Viewer Plug-in to preview the InDesign CS2/CS3 files. In

TagEditor go to Tools-> Plug-ins, activate TradosTag Viewer Plug-in, click Properties,

Select InDesign CS2/CS3 from the list of available Stylesheets. Click OK.

9 When clicking a Preview tab in TagEditor, Internet Explorer will open and provide a

basic preview of the files. The preview stylesheet can be adapted to individual

requirements. For more information on adapting the preview stylesheet contact SDL

Consulting.



Trans la t ing InDes ign F i l e s6


TRANSLATING INDESIGN FILES

Overview

To translate InDesign files, you need to convert the text in the files to a format that is easily

translated.

Story Collector for InDesign facilitates the export of tagged text from InDesign and the subsequent

re-import of text after translation, minimizing the amount of time that needs to be spent on

preparatory and post-translation work.

Story Collector for InDesign works with Adobe InDesign 2.0. It converts files in INDD and INDT

format to a text format (ISC) that can be easily added to SDL Trados Synergy projects and translated

using Translator's Workbench and TagEditor.

How Story Collector for InDesign Works

Story Collector for InDesign is an InDesign 2.0 and CS plug-in. This means that it uses the

Application Programming Interface (API) provided by InDesign to add extra functionality to

InDesign itself. Once you have placed certain files in the Plug-ins\Utility folder in the

InDesign installation directory, you can access Story Collector functionality via the Trados menu.

Story Collector has three basic functions which are presented in the Trados menu in InDesign.

These are the story order, export and import functions. These functions are duplicated for batch

operations.

C Story Order: Before exporting stories from your InDesign document, you can determine the

order in which they appear in the export file. This means that stories are presented for

translation in a sequence that is as logical as possible.

C Exporting Stories: After setting the story order, you specify a name and location for the tagged

text export file. After exporting all stories to this file, you then open the file with TagEditor and

translate it as usual, using Translator's Workbench.

C Importing Stories: After translation, you save the file to InDesign tagged text format, and

import the translated stories into a copy of the original InDesign file, using Story Collector.





6-

Key Term Definition

The following terms occur frequently in this chapter:

CINDD – InDesign files have an INDD extension.

C INDT – InDesign templates have an INDT extension.

C ISC – a tagged text format that is used for the export and import files.

C Export file – a tagged text file (ISC) containing untranslated text. This file is produced when

you export stories from an Adobe InDesign file.

C Import file – a tagged text file (ISC) file containing translated text. You import this file into a

copy of the source InDesign file overwriting the source language text contained in it.

C Story – a word we use in Story Collector for InDesign to refer to what InDesign

documentation calls a text frame. All text in Adobe InDesign resides inside containers called

text frames.

C Log file – a file containing information on export, import, batch export and batch import

operations. You can choose to create a log file while exporting or importing single or multiple

files.

C For export and import operations, it contains details on whether the operation was

successful or not and the number of stories exported or imported.

C For batch export and import operations it contains the time and date of the operation,details on whether the operation was successful or not for each batch file and the number

of stories in each batch file exported or imported.

C Inline frame – a frame containing text or graphics placed in a sentence or word. It behaves as

if it were a single character of text. Story Collector for InDesign relies on the InDesign

Application Programming Interface (API) to collect and export/import the translatable text

from InDesign documents. Inline frames, however, cannot be manipulated via the API, which

is why Story Collector cannot export or re-import them.

C INX – INX interchange format is an XML-based exchange format which is available in

InDesign CS2/CS3.

NOTED

If your InDesign file contains inline frames, InDesign places them at the start of the translatedfile when you import your translated file back into InDesign. You need to move these inlineframes back into their original position. Use your source INDD files as a reference if necessary.






Translation of an InDesign file involves the following stages:

1

Install Story Collector for InDesign.

2 Prepare your InDesign source files for translation.

3 Create a folder structure for your InDesign translation project.

4 Set the story order in your InDesign source file.

5 Export all stories from the InDesign file to a text file (ISC).


7 Import the file back into InDesign.

8 Reposition any inline graphics into their original position. Use your InDesign source

files as a reference if necessary.

NOTED

C If you are working in SDL Trados Synergy, you can add the file to a Synergy project once ithas been converted to ISC format. The file can then be translated and reviewed in Synergy.When it is returned from the Synergy workflow, you must then import the file back intoInDesign.

C You can also use Story Collector for InDesign to process a batch of InDesign files. For moreinformation, see “Batch Functions in Story Collector for InDesign” on page 7-18.

Installing Story Collector for InDesign

SDL Trados includes Story Collector for InDesign files as part of your installation. These files are


C C:\Program Files\SDL International\T2007[_FL]\FI\IND .

Before you install the Story Collector plug-in, make sure that InDesign 2.x or CS is installed on yoursystem and is not running.

1 Copy the following files from the default Story Collector installation folder to the

Plug-ins\Utility folder in the InDesign installation folder.

C InDesign Interface.dll

C Story Collector Common.dll





6-

C Story Collector Gui.dll

C Story Collector Kernel.dll

C Story Collector Plugin.pln

C StoryCollectorIND1033.hlp

C StoryCollectorIND1033.cnt

2 Open InDesign. The toolbar now contains a Trados menu through which you can

access Story Collector functionality.

Online Help

Story Collector installs a comprehensive help system into the Story Collector installation folder. To

access help from within Story Collector, click on a Help button or press F1.

Sample File

You can use the sample InDesign file (sample.indd) to work with the Story Collector for InDesign

that ships with SDL Trados. This sample file is installed to

C:\Documents and Settings\All Users\Documents\SDL Trados\Samples\Story Collector for

InDesign . You should use the sample file to work through the Story Collector process example that

follows in this chapter.





6-1

Creating a Folder Structure

As this process produces an INDD and ISC file for each language, it is vital to set up a folder

structure for the project. Otherwise files may be lost or misplaced.

To retain copies of each file we suggest the following structure:

C A source folder with a subfolder for INDD files and a subfolder for ISC files.

C A target folder per target language with a subfolder for INDD files and a subfolder for ISC

files.


1 Place the files to be translated in the source INDD folder.

2 Place a copy of the same files in the target INDD folder.

3 Export the source files from the source INDD folder to your source ISC folder.

4 We recommend that you copy the files in your source ISC folder into your target ISC

folder as it makes it less likely that you overwrite the source ISC files by mistake.

5 Either add the ISC files to a Synergy project to be translated or translate them directly


ISC folder.

6 Open the copy of the source files you placed in the target INDD folder earlier, importthe translated files from the target ISC folder.

7 Reposition any inline frames in your translated files and save.





Opening Story Collector for InDesign

Open an InDesign document. A Trados menu is visible on the top menu bar. To open Story

Collector, select an option from this menu.


By default, the stories on each page in your InDesign document are exported in top-down order.

However, this may not correspond to the order in which they flow logically. The story order function

in Story Collector allows you to choose the order in which stories are exported to the tagged text file

so that they are presented in a logical sequence for translation. This will not affect the layout of the

InDesign file.





6-1

NOTED

C Even if you are working with multiple page spreads in InDesign, you can only rearrange thestory order within a single page at a time. Stories that spread over more than one pageappear under the page they start on.

C If you do not set the story order for an individual file, Story Collector for InDesign will usethe story order set in the Settings dialog box by default.

Exporting Stories

To export all the stories in your InDesign file to a single text file:

1 Open the InDesign file you wish to export.

2

From the Trados menu, select Export. The Export dialog box appears.

3 In the Export dialog box, specify the location of your source ISC folder and a name for

the extended tagged text file. The same file name as the source file is automatically

suggested.

4 Click Save, a series of progress bars appears and Story Collector for InDesign creates

an export file in the folder you specified. The Export Results dialog box opens. It tells

you if the export has been successful and how many stories have been exported.

5 Click OK to finish the export process, or click Save As to save the export results to a log

file. The Save Log File dialog box opens.


for InDesign saves it under the name and in the location you specified.



Trans la t ion6



All stories are collected and placed in an ISC file in the source ISC folder you specified. We

recommend that you copy the files in your source ISC folder into your target ISC folder as it makes it

less likely that you overwrite the source ISC files by mistake. You can now translate the files in your

target ISC folder.

NOTED

Story Collector for InDesign does not export stories that are located in hidden layers.

TRANSLATION

Once you have created ISC versions of your files, you can either add the files to Synergy for

translation or translate them using Translator's Workbench and TagEditor.

NOTED


The following steps offer a high level view of the translation process for InDesign files.

1 Export the file to your source ISC folder, and then place a copy of it in your target ISC folder.

2 Translate the file in the target ISC folder using TagEditor, saving the file in bilingual

TradosTag (TTX) format during translation.





bilingual data from the translated file and to convert the file back to ISC format. If



5 Then save the file to your target ISC folder.

6 Open the copy of the source file you previously placed in your target INDD folder in

InDesign. Import the file back from your target ISC folder using Story Collector for

InDesign, and save.



Batch Fu nc t ions in S to r y Co l l ec to r fo r InDes ign6


7 Browse to where you want to save the log file, name it and click Save. Story Collectorfor InDesign saves it under the name and in the location you specified.

8 Click OK in the Import Results dialog box and the import process is finished.

After import, the file is ready for final DTP and proofing.

NOTED

If your InDesign file contains inline frames, InDesign places them at the start of the translatedfile when you import your translated file back into InDesign. You need to move these inlineframes back into their original position. Use your source INDD files as a reference if necessary.

BATCH FUNCTIONS IN STORY COLLECTOR FORINDESIGN

When dealing with multiple files, the story order, the export and import operations differ slightly to

those of single files described earlier on in this chapter.


To set the story order for a batch export operation:

1 From the Trados menu, choose Settings. The Settings dialog box is displayed.

2 In the Default Story Order box, select either Top-down order or Left-right order.

C Top-down order: This means Story Collector for InDesign starts at the top of the page andmoves from left to right at each height. Therefore, stories situated higher on the page thanother stories are always exported first, even if the other story is farther left.





6-1

C Left-right order: This means Story Collector for InDesign starts at the left of the page andexports all leftmost stories beginning at the top and finishing at the bottom of the page. Itthen returns to the top of the page, and so on. Therefore, leftmost stories are exported firsteven if one story is higher than another on a page.

The order you choose applies to all subsequent batch export files, and to individual files if youdo not set a story order in the Story Order dialog box.

NOTED

For batch operations, story order options are limited to Top-down order or Left-right order.

3 Select default batch import and export directories under Default Batch File Directories

box. You must specify these or the Batch Export and Batch Import buttons in the Batch

Export and Batch Import dialog boxes remain greyed out. These settings are retained

and used as default settings until you change them again.

4 Click OK to confirm the settings.

NOTED

The Settings dialog box allows you to include stories left on the pasteboard. These are placedafter the master page stories and before the main page stories in the export file.





6-2

5 In the Batch Export dialog box, your source ISC folder appears as you previously

selected it in the Settings dialog box. You can change this if you wish by selecting

another folder using the Browse button, but it reverts to the folder specified in the

Settings dialog box for subsequent batch export operations.

6 In the Batch Export dialog box, click Export to run the export operation. The Batch

Export progress bar is displayed and Story Collector for InDesign creates an export

file(s) in the folder you specified. The Batch Export Results dialog box opens. It tells

you if the export has been successful, the time and the date of the export and how

many stories have been exported.

7 Click OK to finish the export process, or click Save As to save the batch export results to

a log file. The Save Log File dialog box opens.


for InDesign saves it under the name and in the location you specified.


Story Collector for InDesign creates an export file (ISC) for each InDesign source file in the source

ISC folder. Each export file has the same name as its corresponding INDD file.

This section outlines the tags that Story Collector for InDesign adds to the tagged text file as well as

the tags that InDesign itself introduces.

Story Collector for InDesign Tags

In addition to the InDesign tags that will appear in the tagged text file, Story Collector for InDesign

includes some of its own tags.

Tags in InDesign Tagged Text Files

All InDesign tags begin with < and end with >. Type the tag immediately before the text you want to

format.

For paragraph-level attributes, type the tag at the start of the paragraph.

For character-level attributes, type the tag at the start of the text you want to change. The type

attributes you specify remain in effect until you use codes to cancel them or until you apply other

attributes. For example, to apply underline to one word in a paragraph, you type <cUnderline:1>

before the word and <cUnderline:> after the word.

The type specifications for the InDesign tags are:

C Start file, color table, and style definition tags

C Character tags

Tag Description

<TRADOSStoryCollector SCVersion="5.5"

DTPPackage="InDesign"DTPPackageVersion="2"

Encoding="UNICODE">

Introduction tag specifying the version of the

Story Collector, the software used with the StoryCollector, the version of this software and the

encoding used by the file.

</TRADOSStoryCollector> End of the file

<STORY NAME="0" LOCATION="P1"> Tag indicating the beginning of a story. It

specifies the name of the story and the location

of it.

</STORY> End of a story

6-2

C Paragraph tags

C Table tags

C Hyperlink and index tags

C Special character tags.

Start File, Color Table and Style Definition Tags

The following are the tags that InDesign uses for start files, color tables and style definitions.

Attribute Format Example and Notes

Start file tag <Encoding format-Platform> <ASCII-MAC>

Specify the encoding format

(ASCII, ANSI, UNICODE, BIG5, or

SJIS) followed by the platform

(MAC or WIN).

Color table <ColorTable:=<Swatch name 1: Swatch

Type (COLOR, TINT, or GRAD): Color

Type (CMYK, RGB, or LAB): Color Mode

(Process or Spot):Values of color, tint, or

gradient><Swatch name 2>...> A

COLOR swatch requires 4 values forCMYK and 3 values for RGB and

LAB.GRADIENT syntax:

<Gradient name:GRAD:Fill

type:StopPosition1;StopColor1;

Midpoint1 | StopPosition2;StopColor2;

Midpoint2>TINT syntax: <Base

Color:TINT:Tint value>

<ColorTable:=

<Black:COLOR:CMYK:Process:0,0,

0,1><Green:COLOR:CMYK:Process

:1,0,1,0><Blue:COLOR:CMYK:Proc

ess:1,1,0,0><G/B:GRAD:Linear:0.0;

Green;0.5 |1.0;Blue;0.5><Blue:TINT:Blue;20>>

The color table is a list of all colors,

tints, and gradients defined in the

Swatches palette and used in the

text. You can use the abbreviation

<Table>.

Paragraph style

definition

<DefineParaStyle:Paragraph style

name=<attr1><attr2>...> A paragraph

style definition includes the character

and paragraph attributes as well as

<Nextstyle:style name> and

<BasedOn:style name>

<DefineParaStyle:Heading

1=<Nextstyle:Body

Text><cFont:Adobe

Garamond><cSize:18><pBodyAlig

nment:Center>>The paragraph

style definition includes a list of all

styles defined in the Paragraph

Styles palette and used in the text.

Color: character

fill

cColor:String or Color

Definition

cc <cColor:Green> or

<cColor:COLOR:RGB:Process:0.5,1,0>

Color: character

stroke

cStrokeColor:String or Color

Definition

cst <cStrokeColor:Green> or

<cColor:COLOR:RGB:Process:0.5,1,0

>

Color: fill gradient

angle

cGradientAngle:Real cga <cGradientAngle:45>Color: fill

gradient angle cGradientAngle:Real

cga <cGradientAngle:45>

Color: fill gradientcenter cGradientCenter:Real,Real cgc <cGradientCenter:-145,-145>This tagindicates the x and y values of the

center point of a radial gradient or the

starting point of a linear gradient.

Color: fill gradient

length

cGradientLength:Real cgl <cGradientLength:2>This tag

indicates the length of a linear

gradient ramp or radius of a radial

gradient.

Color: stroke

gradient angle

cStrokeGradientAngle:Real csga <cStrokeGradientAngle:-45>Angle of

linear gradient fill from -180 to 180degrees.

Color: stroke

gradient center

cStrokeGradientCenter:

Real,Real

csgs <cStrokeGradientCenter:-145,-

145>This tag indicates the x and y

values of the center point of a radial

gradient or the starting point of a

linear gradient.

Color: stroke

gradient length

cStrokeGradientLength:Real csgl <cStrokeGradientLength:2>This tag

indicates the length of a linear

gradient ramp or radius of a radial

gradient.

Color: stroke tint cStrokeTint:Real cst <cStrokeTint:80>Specify a tint

percentage.

Color: stroke

weight (thickness)

cStrokeWeight:Real csw <cStrokeWeight:0.5>Specify a value

between 0 and 800.

Attribute Tag NameTag

Abbr.Examples and Notes

OpenType: figure

style

cFigureStyle:Enum cfs <cFigureStyle:Proportional

Oldstyle>Valid values include TabularLining (default), Proportional

Oldstyle, Proportional Lining, and

Tabular Oldstyle.

OpenType:

contextual

alternate

cOTFContAlt:Boolean cotfsalt <cOTFContAlt:0>1=on (default),

0=off

OpenType:

discretionary

ligatures

cOTFDiscLig:Boolean cotfdl <cOTFDiscLig:1>1=on, 0=off (default)

OpenType: feature

list

cOTFeatureList:String cotfl <cOTFeatureList:zero\,1>

OpenType:

fractions

cOTFFractions:Boolean) cotff <cOTFFractions:1>1=on, 0=off

(default)

OpenType:

position

cPosition:Enum ?? <cPosition:Numerator>Valid values

include None (default), Superior,

Inferior, Numerator, and

Denominator.OpenType:

ordinals

cOTFOrdinal:Boolean cotfo <cOTFOrdinal:1>1=on, 0=off

(default)

OpenType: titling

alternates

cOTFTitlAlt:Boolean cotfttlt <cOTFTitlAlt:1>1=on, 0=off (default)

OpenType: swash

alternates

cOTFSwaAlt:Boolean cotff <cOTFSwaAlt:1>1=on, 0=off (default)

Overprint

character fill

cOverprint:Boolean co <cOverprint:1>1=on, 0=off (default)

Overprint

character stroke

cStrokeOverprint:Boolean cso <cStrokeOverprint:1>1=on, 0=off

(default)

Prev/Next page

number

cPageNumType:Enum cpnt <cPageNumType:Next>Valid values

include Next, Previous, and Current.

Current is the default value.

6-3

Rotate character cCharRotate:Real cchr <cCharRotate:45>Specify a value

between -360 and 360 to rotate thecharacter on its center axis. Positive

values rotate the character counter-

clockwise.

Scaling: horizontal cHorizontalScale:Real chs <cHorizontal Scale:2>The value 1.0

equals 100%. You can use values

between 1% (.01) and 1000% (10.0).

Scaling: vertical cVertical Scale:Real cvs <cVerticalScale:2>The value 1.0

equals 100%. You can use values

between 1% (.01) and 1000% (10.0).

Small cap

percentage

cSmallCapPercentage:Real cscp <cSmallCapPercentage:70>Specify a

percentage value.

Strikethrough cStrikethru:Boolean cstrike <cStrikethru>1=on, 0=off (default)

Strikethrough gap

color

cStrikethroughGapColor:Real cugc <cStrikethroughGapColor:C\=100

M\=0 Y\=0 K\=0>

Strikethrough gap

overprint

cStrikethroughGapOverprint:

Boolean

cugo <cStrikethroughGapOverprint:1>

1=on, 0=off (default)

Strikethrough gap

tint

cStrikethroughGapTint:Real cugt <cStrikethroughGapTint:30>

Strikethrough

offset

cStrikethroughOffset:Real cuoff <cStrikethroughOffset:3>

Strikethrough

weight offset

cStrikethroughWeight

Offset:Real

cugo <cStrikethroughWeightOffset:3>

Strikethrough type cStrikethroughType:Definition cutype <cStrikethroughType:ThickThin>

Superscript orsubscript

character position

cPosition:Enum cp <cPosition:Superscript> Valid valuesinclude Superscript, Subscript, or

Normal (default).

Tracking cTracking:Real ct <cTracking:50>Specify a value

between -1000.0 and 10000 (1000ths

of an em).

Underline cUnderline:Boolean cu <cUnderline:1>1=on, 0=off (default)

Paragraph Tags

Paragraph tags in InDesign tagged text files have the following characteristics:

C Each tag includes a value type:

C String includes a list of characters, such as the name of a color. (When the information is atext string, the case of the characters does not matter unless you are typing a specific color

or style name.)

C Integer includes only whole numbers for values, such the number of drop cap characters.

Real can include any number such as "23.578."

C Boolean includes on/off toggle values: "0" for off and "1" for on.

C Enum includes only specific string values such as "Small Caps."

C Numeric measurements are expressed as points.

C While creating the tagged text file in a word-processing application or text editor, any

characters, tabs, and spaces you type outside the angle brackets (< >) will appear in the

InDesign text frame when the file is placed. To begin a new paragraph with no paragraph style

assigned, type <ParaStyle:> on a new line.

Underline gap

color

cUnderlineGapColor:Real cugc <cUnderlineGapColor:C\=100 M\=0

Y\=0 K\=0>

Underline gap

overprint

cUnderlineGap

Overprint:Boolean

cugo <cUnderlineGapOverprint:1>


Underline gap tint cUnderlineGapTint:Real cugt <cUnderlineGapTint:30>

Underline offset cUnderlineOffset:Real cuoff <cUnderlineOffset:3>

Underline weight

offset

cUnderlineWeightOffset:Real cuwoff <cUnderlineWeightOffset:3>

Underline type cUnderlineType:Definition cutype <cUnderlineType:ThickThin>Multi-master

optical size

cMultiMasterOpticalSize:Real cmmos <cMultiMasterOpticalSize:10>

Glyph scaling:

minimum

pMinGlyphScale:Real pmings <pMinGlyphScale:0.9>Specify a value

between 50% (0.5) and the desiredglyph scaling value.The default value

is 1.0 (100%).

Grid Alignment: first

line

pGridFirstLine:Boolean pgfl <pGridFirstLine:1>This value

determines whether only the first line

in the paragraph is aligned to the

grid. 1=on, 0=off (default)

Grid Alignment:

location

pGridAlign:Enum pga <pGridAlign:EmCenter> This value

sets what metric in the line is aligned

to the corresponding metric in thegrid. Valid values include Baseline,

EmTop, EmCenter, EmBottom,

ICFTop, ICFBottom, and None.

Hyphenate all capital

words

pHyphenateCapitals:Boolea

n

phc <pHyphenateCapitals:1>1=on, 0=off

(default)

Hyphenation: hyphen

limit

PHyphenationLadderLimit:I

nteger

phll <pHyphenationLadderLimit:5>Value

indicates maximum number of

consecutive

Hyphenation:

minimum number of

characters after

hyphen

pMinCharAfterHyphen:

Integer

pmcah <pMinCharAfterHyphen:3> Specify a

value from 1 to 15.The value 3 is the

default.

Hyphenation:

minimum number of

characters before

hyphen

pMinCharBeforeHyphen:

Integer

pmcbh <pMinCharBeforeHyphen:3> Specify

a value from 1 to 15.The value 3 is the

default.

Hyphenation: number

of characters in

shortest word allowed

to be hyphenated

PshortestWordHyphenated:

Integer

pswh <pShortestWordHyphenated:3>This

range of this value is from 3 to 25.The

default value is 7.

Hyphenation: on or off pHyphenation:Boolean ph <pHyphenation:1>1=on (default),

0=off

6-3

Hyphenation: zone pHyphenationZone:Real phz <pHyphenationZone:48>Value (in

points) is valid only if Single-lineComposer is turned on. Specify a

value between 0 and 8640.The

default value is 36 points.

Keep first n lines

together (widow

control)

pKeepFirstNLines:Integer pkfnl <pKeepFirstNLines:4>Specify a value

from 1 to 50 (1 is equivalent to off).

Keep last lines

together (orphan

control)

pKeepLastNLines:Integer pknl <pKeepLastNLines:2>Specify a value

from 1 to 50 (1 is equivalent to off).

Keep lines together pKeepLines:Boolean pkl <pKeepLines:1>1=on, 0=off (default)

Keep whole paragraph

together

pKeepPara

Together:Boolean

pkpt <pKeepParaTogether:1>1=on, 0=off

(default)

Keep with next lines pKeepWithNext:Integer pkwn <pKeepWithNext:4>Specify a value

from 0 to 5 (0 means off).

Leading: auto leading

percentage

pAutoLeadPercent:Real palp <pAutoLeadPercent:1.2>The value 1.0

equals 100%.Specify a value between

0

Left indent pLeftIndent:Real pli <pLeftIndent:6>

Letter spacing: desired pDesiredLetterspace:Real pdl <pDesiredLetterspace:1.0>Specify a

value between -1.0 (-100%) and 50

(500%).The default value is 1.0

(100%).

Letter spacing:

maximum

pMaxletterspace:Real pmaxl <pMaxletterspace:1.2>The value 1.0

equals 100%.Specify a value between

the desired letter spacing value and50 (500%).The default value is 0.

Letter spacing:

minimum

pMinLetterspace:Real pminl <pMinLetterspace:0.9>The value 1.0

equals 100%. Specify a value between

-1 (-100%) and the desired letter

spacing value.The default value is

0%.

6-4

Cell: bottom stroke

tint

tCellAttrBottom-StrokeTint:Real tcabst <tCellAttrBottomStrokeTint:70>

Cell: bottom stroke

type

tcBottomStrokeType:Enum tcbst <tcBottomStrokeType:ThinThick>

Cell: bottom stroke

gap tint

tCellBottomStroke

GapTint:Real

tcbsgt <<tCellBottomStrokeGapTint:95>

Cell: bottom stroke

gap color

tCellbottomStroke

GapColor:Real

tcbsgc <tCellBottomStrokeGapColor:C\=1

00 M\=0 Y\=0 K\=0>

Cell: bottom stroke

gap overprint

tCellBottomStrokeGap

Overprint:Boolean

tcbsgo <tCellBottomStrokeGap

Overprint:0>


Cell: default cell

type

tCellDefaultCellType:Enum tcdct <tCellDefaultCellType:1>

Cell: fill color tCellFillColor:Enum:Definition tcfc <tCellFillColor:Blue>

Cell: fill tint tCellAttrFillTint:Real tcaft <tCellAttrFillTint:20>

Cell: first line offset tTextCellFirstLineOffset:Enum tcflo <tTextCellFirstLineOffset:2>Valid

values include 1 (Ascent), 2 (Cap

Height), 3 (Lead-ing),4 (x Height),

and 5 (Fixed). 1 is the default.

Cell: left inset tCellAttrLeftInset:Real tcali <tCellAttrLeftInset:9>

Cell: left stroke

color

tCellLeftStrokeColor:Definition tclsc <tCellLeftStrokeColor:Blue>

Cell: left stroke tint tCellAttrLeftStrokeTint:Real tcalst <tCellAttrLeftStrokeTint:70>

Cell: left stroke type tcLeftStrokeType:Enum tclst <tcLeftStrokeType:ThinThick>

Cell: left stroke gap

tint

tCellleftStrokeGap

Tint:Real

tclsgt <tCellLeftStrokeGapTint:95>


color

tCellLeftStrokeGap

Color:Real

tclsgc <tCellLeftStrokeGapColor:C\=100

M\=0 Y\=0 K\=0>


overprint

tCellLeftStrokeGap

Overprint:Boolean

tclsgo <tCellLeftStrokeGapOverprint:0>


Cell: outer bottom

stroke color

tCellOuterBottomStroke-Color:

Definition

tcobsc <tCellOuterBottomStrokeColor:

Blue>

Attribute Tag Name Tag Abbr. Examples and Notes

Cell: outer bottom

stroke type

tOuterBottomStroke-

Type:Enum

tobst <tOuterBottomStrokeType:

ThinThick>

Cell: outer left

stroke color

tCellOuterLeftStroke-

Color:Definition

tcolsc <tCellOuterLeftStrokeColor:Blue>

Cell: outer left

stroke type

tOuterLeftStrokeType:Enum tolst <tOuterLeftStrokeType:

ThinThick>

Cell: outer right

stroke color

tCellOuterRightStroke-

Color:Definition

tcorsc <tCellOuterRightStrokeColor:

Blue>

Cell: outer right

stroke type

tOuterRightStrokeType:Enum torst <tOuterRightStrokeType:

ThinThick>

Cell: outer top

stroke color

tCellOuterTopStroke-

Color:Definition

tcotsc <tCellOuterTopStrokeColor:Blue>

Cell: outer top

stroke type

tOuterTopStrokeType:Enum totst <tOuterTopStrokeType:

ThinThick>

Cell: right inset tCellAttrRightInset:Real tcari <tCellAttrRightInset:9>

Cell: right stroke

color

tCellRightStrokeColor:

Definition

tcrsc <tCellRightStrokeColor:Blue>

Cell: right stroke tint tCellAttrRightStrokeTint:Real tcarst <tCellAttrRightStrokeTint:70>Cell: right stroke

type

tcRightStrokeType:Enum tcrst <tcRightStrokeType:ThinThick>

Cell: right stroke

gap tint

tCellRightStrokeGap

Tint:Real

tcrsgt <tCellRightStrokeGapTint:95>

Cell: right stroke

gap color

tCellRightStrokeGap

Color:Real

tcrsgc <tCellRightStrokeGapColor:C\=10

0 M\=0 Y\=0 K\=0>

Cell: right stroke

gap overprint

tCellRightStrokeGap

Overprint:Boolean

tcrsgo <tCellRightStrokeGapOverprint:0>

1=on, 0=off (default)Cell: rotation tCellAttrRotation:Enum tcar <tCellAttrRotation:180>Valid

values include 0 (default), 90, 180,

and 270.

Cell: stroke weight

bottom

tCellAttrBottomStroke-

Weight:Real

tcabsw <tCellAttrBottomStrokeWeight:3>

6-4

Cell: stroke weight

left

tCellAttrLeftStroke-Weight:Real tcalsw <tCellAttrLeftStrokeWeight:3>

Cell: stroke weight

right

tCellAttrRightStroke-

Weight:Real

tcarsw <tCellAttrRightStrokeWeight:3>

Cell: stroke weight

top

tCellAttrTopStroke-Weight:Real tcatsw <tCellAttrTopStrokeWeight:3>

Cell: top inset tCellAttrTopInset:Real tcati <tCellAttrTopInset:9>

Cell: top stroke

color

tCellTopStroke

Color:Definition

tctsc <tCellTopStrokeColor:Blue>

Cell: top stroke tint tCellAttrTopStrokeTint:Real tcatst <tCellAttrTopStrokeTint:70>Cell: top stroke type tcTopStrokeType:Enum tctst <tcTopStrokeType:ThinThick>

Cell: top stroke gap

tint

tCellTopStrokeGap

Tint:Real

tctsgt <tCellTopStrokeGapTint:95>


color

tCellTopStrokeGap

Color:Real

tctsgc <tCellTopStrokeGapColor:C\=100

M\=0 Y\=0 K\=0>


overprint

tCellTopStrokeGap

Overprint:Boolean

tctsgo <tCellTopStrokeGapOverprint:0>


Cell: type tCellType:Enum tct <tCellType:1>

Cell: vertical

composition

tTextCellVerticalComposition:

Enum

tcvc <tTextCellVerticalComposition:1>

Cell: vertical

justification

tTextCellVerticalJustification:

Enum

tcvj <tTextCellVerticalJustification:2>Va

lid values include 0 (Top), 1

(Bottom), 2 (Center), and 3(Justify)

Cell: vertical

justification

paragraph spacinglimit

TTextCellAttrMaxVJInterPara

Space:Real

ttcamvjips <tTextCellAttrMaxVJInterPara

Space:40>

Column width tColAttrWidth:Real tcaw <tColAttrWidth:120>

Column: fill pattern

(first color)

tColFillPatFirstColor:Enum tcfpfcl <tColFillPatFirstColor:ThinThick>

Column: fill pattern

(second color)

tColFillPatSecondColor:Enum tcfpscl <tColFillPatSecondColor:

ThinThick>

Column: stroke

pattern (first color)

tColStrokePatFirstColor:Enum tcspfcl <tColStrokePatFirstColor:

ThinThick>

Column: stroke

pattern (first type)

tColStrokePatternFirstType:

Enum

tcspft <tColStrokePatternFirstType:

ThinThick>

Column: stroke

pattern (second

color)

tColStrokePatSecondColor:

Enum

tcrspscl <tColStrokePatSecondColor:

ThinThick>

Column: stroke

pattern (second

type)

TColStrokePatternSecondType:

Enum

tcspst <tColStrokePatternSecondType:

ThinThick>

Column:strokepattern first weight

tColStrokePatternFirstWeight:Real

tcspfw <tColStrokePatternFirstWeight:9>

Column: stroke

pattern second

weight

TColStrokePatternSecond

Weight:Real

tcspsw <tColStrokePatternSecond

Weight:9>

Column: stroke type tColStrokeType:Enum tcst <tColStrokeType:ThickThin>

Row height tRowAttrHeight:Real trah <tRowAttrHeight:20>

Row: AutoGrow tRowAutoGrow:Enum trag <tRowAutoGrow:1>

Row: fill pattern

(first color)

tRowFillPatFirstColor:Enum trfpfcl <tRowFillPatFirstColor:

ThinThick>

Row: fill pattern

(second color)

tRowFillPatSecondColor:

Enum

trfpscl <tRowFillPatSecondColor:

ThinThick>

Row: row size

maximum

tRowAttrMaxRowSize:Real tramars <tRowAttrMaxRowSize:40>

Row: row size

minimum

tRowAttrMinRowSize:Real tramirs <tRowAttrMinRowSize:9>

Row: stroke pattern

(first color)

tRowStrokePatFirstColor:

Enum

trspfcl <tRowStrokePatFirstColor:

ThinThick>

Row: stroke pattern

(first type)

tRowStrokePatternFirstType:

Enum

trspft <tRowStrokePatternFirstType:

ThinThick>

Hyperlink and Index Tags


Hyperlink Hyperlink:Definition hpl <Hyperlink:=<HyperlinkName:Page 3>>

Hyperlink

destination

definition

HyperlinkDestDefn:

Definition

hpldestdfn <HyperlinkDestDefn:=<Hyperlink

Name:Page 3>>

Hyperlink name HyperlinkName:Real hplname <HyperlinkName:Page 3>

Hyperlink

destination

HyperlinkDest:Real hpldest <HyperlinkDest

Hyperlink length HyperlinkLength:Real hpllen <HyperlinkLength:6> Specify thenumber of characters in the

hyperlink.

Hyperlink

destination name

HyperlinkDestName:Real hpldest-name <HyperlinkDestName:Page 3>

Hyperlink

destination URL >

HyperlinkDestUrl:Real hpldesturl <HyperlinkDestUrl:http\:/\/www.s

dl.com>

Hyperlink

destination index

HyperlinkDestIndex:Real hpldestidx <HyperlinkDestIndex:1>

Hyperlink

destination page

HyperlinkDestPage:Real hpldestpage <HyperlinkDestPage:3>

Hyperlink

destination page

zoom type

HyperlinkDestPageZoomT

ype:Real

Hpldestpag-

ezoomtype

<HyperlinkDestPageZoom

Type:Fixed> Valid values include

Fixed, Fit View, Fit in Window, Fit,

Width, Fit Height, Fit Visible, and

Inherit Zoom.

Hyperlink

destination pagezoom factor

HyperlinkDestPageZoomF

actor: Real

hpldestpag-

ezoomfactor

<HyperlinkDestPageZoomFactor:1.

7> 1=100% magnification

Hyperlink hidden Hidden:Boolean hid <Hidden:0>

Hyperlink border

width

BrdrWidth:Real brdrw <BrdrWidth:2>

Hyperlink border

visible

BrdrVisible:Boolean brdrv <BrdrVisible:1>



Chapte

VENTURA FILES

Chapter 7 deals with the following aspects of translating the

Ventura DTP file type:

C Ventura translation workflow summary

C Preparing and exporting Ventura files for translation

C Translating Ventura files

C Importing translated files back into Ventura

7





7-

PREPARATION AND EXPORT

You may need to prepare your Ventura file(s) before using Ventura to export. The extent of your

preparation will depend on the formatting of your document and the source and target languages of

your translation.

You should:

C create folder structure for your Ventura translation project

C prepare the text in Ventura files

C export the text in the Ventura file to a TXT file.

Creating a Folder Structure Organization

Create a target folder for each language you are translating into, as well as a source folder for original

files. Place a copy of the Ventura file for translation in each of these target language directories in VP

subfolders. In this way, you retain a copy of each source and target file.

To retain copies of each file we suggest the following structure:

C A source language folder with a subfolder for VP files and another subfolder for TXT files.

C A target language folder with a subfolder for VP files and another subfolder for TXT files.


1 Place the files to be translated in the source VP folder.

2 Place a copy of the same files in the target VP folder.

3 Export the source files from the source VP folder to your source TXT folder.

4 We recommend that you copy the files in your source TXT folder into your target TXT

folder as it makes it less likely that you overwrite the source TXT files by mistake.

5 Either add the TXT files to a Synergy project to be translated or translate them directly


TXT folder.

6 Open the copy of the source files you placed in the target VP folder earlier, import the

translated files from the target TXT folder and save.



Trans la t ion7


7-

NOTED

For documents with many frames, decide whether it makes more sense to link the frames toeach other or to export them to separate files.

TRANSLATION

once you have created TXT versions of your files, you can either add the files to Synergy for

translation or translate them using Translator's Workbench and TagEditor.

NOTED

If you add files to Synergy, you will not need to carry out steps 2, 3 and 4 below. This is becausefiles are automatically converted to bilingual TradosTag (TTX) format when projects are createdin Synergy, files can be verified directly in Synergy and clean-up happens automatically when

files are finalized in Synergy.

The following steps offer a high level view of the translation process for Ventura files.

1 Export your file to your source TXT folder, and then place a copy of it in your target TXT folder.

2 Translate the file in the target TXT folder using TagEditor, saving the file in bilingual

TradosTag (TTX) format during translation.





bilingual data from the translated file and to convert the file back to TXT format. If



5 Then save the file to your target TXT folder.

6 Open the copy of the source file you previously placed in your target VP folder in

Ventura. Import the file back from your target TXT folder, and save.

This section explains how to import translated files back into Ventura.

Importing Ventura Text

1 Open the copy of the source file you previously placed in your target VP subfolder.

2 Place the cursor at the point at which you want the imported text to appear.

3 Select Import text from the File menu in Ventura. The Import text dialog box appears.

Select your translated TXT file in your target TXT subfolder, select the Insert at cursor

checkbox, and click OK. The translated text appears in the file.

4 Remove the source language text.

5 Paste translated text from the ancillary file into the Ventura document.

6 Perform DTP tidy up: adjust callout text, pagination, tables, update cross-references

and regenerate the TOC and index.


The Tags toolbar in TagEditor allows you to quickly and easily insert tags and special characters intotarget segments.

NOTED

For more information on the Tags toolbar in TagEditor, see the Translator’s Workbench Guide and TagEditor Help.

The following table displays a list of all tags appearing in tagged text from Ventura version 5 or later.

Tag Description Category Notes

<$! (ANY TEXT)> Hidden text Placeholder

<$&(ANY TEXT)> Picture anchor Structural tag

<$=(ANY TEXT)> Formula Placeholder

<$[(ANY TEXT)> Character tag Emphasis

<$](ANY TEXT)> Character tag Emphasis

7-

<(ANY TAG)*> or

<(ANY TAG)255>

Return to default Emphasis Appears a lot in

Ventura Publisher 7.

For example, adouble underline

applied to some

characters in a

normal sentence

might appear thus:

The <=>printer<U*>

is a nice man.

Where the <U*> is a

return to the default

underlining style.

<< and >> Less than and Greater

than characters

Placeholders Ventura 8 does not

export < and >

characters correctly,

therefore marking up

files containing these

characters may not

be successful.

ABOVE() Table formatting Structural tag in Tables only

ALIGN() Table formatting Structural tag in Tables only

BELOW() Table formatting Structural tag in Tables only

BOX() Table formatting Structural tag in Tables only

CLIPLASTCELLSKEW Table formatting Structural tag in Tables only

COLUMNS() Table formatting Structural tag in Tables only

COLWIDTHS() Table formatting Structural tag in Tables only

DIMENSION() Table formatting Structural tag in Tables onlyHEADERS() Table formatting Structural tag in Tables only

HGRID() Table formatting Structural tag in Tables only

HGUTTER() Table formatting Structural tag in Tables only

INDENT() Table formatting Structural tag in Tables only

KEEP() Table formatting Structural tag in Tables only

Tag Description Category Notes



Chapte

WORD AND RTF HELP FILES

Section 5 of the File Formats Reference Guide explains how to

work with Microsoft formats.

This chapter explains the following aspects of translating

Microsoft Word and RTF help files:

C Word document translation workflow

C Preparing Microsoft Word documents for translation,translation situations and tips for post-translationproduction

CRTF help file translation workflow

C Preparing RTF help files for translation, translationsituations and tips for post-translation production

NOTED

If you are working with Synergy, this chapter is onlyrelevant if you are using Word as a translation editor,rather than TagEditor. If you want information aboutsetting filter settings for the Microsoft Word filter, or usingWord 2007 documents, see Chapter 9 .

8



Overv i ew8


OVERVIEW

You can translate Microsoft Word and RTF files directly with a minimum of preparation using

Translator’s Workbench and Microsoft Word. This chapter describes the Microsoft Word and RTF

translation process. It contains information about specific issues that arise during the preparation,translation and post-production of these file types. You can also opt to work with your Word files in

TagEditor using the TTX workflow described in Chapter 9, Translating Word Files in TagEditor .

Key Term Definition


C DOC file – Microsoft Word documents can have a DOC extension or an RTF (Rich Text

Format) extension.

C RTF help file – RTF-based Windows help files that contain the features and formatting that arerequired for online help. Special features include custom footnotes and hyperlink text.Translator’s Workbench facilitates the translation of these features.

C Footnotes – used in printed documents to explain, comment on, or provide references for textin a document. For example, you might use footnotes for detailed comments. Footnotesappear at the end of each page in a document.

C Track changes – a feature in Microsoft Word that allows you to mark changes in the currentdocument and keep track of each change by reviewer name.



Work ing w i th Mic roso f t Word Docu ments8


WORKING WITH MICROSOFT WORD DOCUMENTS

This section contains information on features that are specific to Word documents, the preparation

of Word documents for translation and tips for post-translation production.

NOTED

RTF help files and the special features they have are described later on in this chapter. For moreinformation, see Working with RTF Help Files on page 8-15 .

RTF Workflow

When using Translator’s Workbench with Word to translate documents, files are converted to the

RTF format. We refer to the Microsoft Word translation workflow as the RTF workflow. When using

TagEditor to translate Word documents, you use the TTX workflow. See Chapter 9, Translating Word Files in TagEditor for more information.

Translation of a Microsoft Word document involves the following stages:

1 Create a folder structure for your translation project. An orderly folder structure helps you to

keep track of all your source and target files.

2 Prepare your Word documents for translation.

3 In Translator’s Workbench, activate any translation project and filter settings that are

required.


using the Analyse and Translate batch tools.

5 Translate your Word documents in Word using Translator’s Workbench.

6 After translation, clean up the translated files and update the translation memory

using the Clean Up command in Translator’s Workbench. Keep an unclean copy of the

bilingual files for reference.

7Open the translated Word documents in Word for further processing.

NOTED

For more information about translating files in Word and the clean up feature in Translator’sWorkbench, see the Translator’s Workbench User Guide.



P repara t ion o f Mic roso f t Word F i l e s8


1 Check Strip Unused Fonts and/or Strip Unused Styles in the Tools tab of the Translation

Memory Options dialog box.

2 Run the Clean Up function on the files you wish to translate. This strips all unused

styles and/or fonts from your documents.

NOTED

Consult the originator of the document before changing any style sheets.

Using the Bookmark Handler Macros

The Bookmark Handler tool helps maintain cross-reference bookmarks during the translation

process. Translator's Workbench moves bookmarks to the end of the paragraph when opening

segments with Open/Get causing cross-references based on bookmarks to contain the entire

paragraph text instead of the bookmark text. If you use the PrepareBookmarks and

RestoreBookmarks macros, the hidden cross-references are preserved.

Adding the Bookmark Handler Template

To add the Bookmark Handler template to Microsoft Word:

1 In Microsoft Word, choose Tools > Templates and Add-ins.

2 Click Add and select the file Bookmark Handler.dot from the

C:\Program Files\SDL International\T2007[_FL]\TT\Templates folder. Click OK to add

the template.

The template should be selected in the Global Templates and Add-ins list.

3 Click OK to close the Templates and Add-ins dialog box.





8-

The Bookmark Handler macro icon appears in the Microsoft Word toolbar.

Running the Bookmark Handler Macros

Before translating the file you need to run the PrepareBookmarks macro. The macro converts the

bookmarks into tags. It also creates a new folder called Bookmark Handler. In the folder is a copy

of the source file with the prefix prep. For example, if you have a file in the folder C:\MyDocuments

called sample.doc , you will see a new folder C:\MyDocuments\Bookmark Handler containing a file

called prepsample.doc .

Use the newly created file to translate the text. Because the cross-references are converted to tags,

you may see an error message during translation: Error! Reference source not found. The referencefields are still looking for the bookmarks, but cannot recognize the tags. To make sure the reference

field is still pointing to the bookmark, press Alt+F9 to view the field code and verify it is correct. Once

the RestoreBookmarks macro is run, the reference fields will see the bookmarks and display the

correct text.

NOTED

Reference fields are treated as placeables. See “Fields” on page 8-13 for more information.

After you finish localizing the document, you need to run the CleanUp task on the file. Run the

RestoreBookmarks macro on the cleaned file. The macro creates a new file with the rest prefixin the Bookmark Handler folder.

Markup Options

There are two options you can use to create tags when running the PrepareBookmarks macro;

Internal and External.

If you choose Internal, the tags use the style tw4winInternal. these tags are treated as part of a text

segment and can be moved within the segment to make translation easier.

When you choose External, the tags use the style tw4winExternal. The tag is treated as separate fromthe text segment and appears outside the segment during translation.

To run the Bookmark Handler macros:

C Click the Bookmark Handler macro icon in the Microsoft Word toolbar.





The BookMark Handler dialog box appears:

To run the PrepareBookmarks macro:

1 Choose a Markup type: Internal or External

2 Click Prepare Bookmarks to run the macro and create the new file and folder.

To edit the file:

1 In Word, open the file with the prep prefix. The file can be found in the Bookmark Handler

folder in the source file directory.

2 Translate and save the file.

3 In Translator’s Workbench, choose Tools > Cleanup and clean up the translated file.

To run the RestoreBookmarks macro:

1 Open the cleaned file in Word

2 Run the RestoreBookmarks macro. A file with the rest prefix is created. Verify that

all cross-references in the file are correct.

TIPE

Cross-reference bookmarks in headers and footers and cross-references that refer to text inanother document are not processed by the Bookmark Handler macros. Make sure you verifythat all cross-reference bookmarks are functioning correctly in the restored file. You may need togo back to the source file and copy information over to fully restore all links.



Trans la t ion o f Mic roso f t Word F i l e s8


TIPE

If you embed several index entries in a sentence, each one has to be placed and translatedindividually. In contrast to this, leading index entries are treated as independent segments byTranslator’s Workbench. Each one is opened and translated separately. This facilitates

translation and increases the possibility of leveraging translations from the translation memory.

Footnotes

Footnotes are not treated as single segments in Word. Instead, as soon as you place a footnote as a

subsegment in the target field using [Alt] + the subsegment number, Translator's Workbench opens

a temporary document TW4Win Footnote.doc. You translate the footnote in this document

using the full Workbench functionality. After confirming the last segment in the footnote, you

return to the main segment in your document and continue translating as usual.

To translate a segment containing footnotes:

1 When you open a segment containing footnotes, Translator's Workbench automatically

assigns a subsegment number to each footnote in the source field, using segment delimiters.

The subsegment numbers assigned to the footnotes always start from 1. For example, if a

segment contains two footnotes, their subsegment numbers are 1 and 2. However, the first

footnote in the subsegment may actually be the 15th footnote in the document. This sentence

is displayed as follows:

You can now start translating the segment. We recommend that you translate the main

sentence first and then the footnotes. However, you can also start translating the footnotes

without entering any text into the main segment or you can translate the footnotes in a

different order. When translating the footnotes, ignore the absolute numbering of the

footnotes and only look at the subsegment marks Translator's Workbench has assigned to the

footnotes. To start translating any footnote, press [Alt] + the subsegment number. For





8-1

Word’s Footnote Pane

You can re-open a translated segment at any time in Word’s footnote pane, by selecting Footnotes

on the View menu in Word. Translator’s Workbench opens the corresponding footnote document,

TW4Win Footnote.doc, to allow you to edit your translation.

WARNINGF

After you finish translating in the TW4Win Footnote.doc, never close it using the Close command on Word's File menu. Instead, press [Alt] + [0] to return to the main document.Translator's Workbench automatically closes the document and places the translated footnotewhere it belongs in the main document.

Tips for Working with Footnotes

C Never delete a footnote that you have already placed inside the target segment. It is notpossible to replace the footnote because the corresponding source segment footnote hasalready been replaced by the fn code.

C Translate all footnotes inside a segment, so that each fn code in the source has acorresponding footnote in the target. If large parts of text in a footnote are left untranslated,use the Copy Source command inside the TW4Win Footnote.doc to copy the source textto the target segment as required.

Hyperlinks

Translator’s Workbench treats hyperlinks as placeables:

Fields

Translator's Workbench treats fields as placeables. When Translator's Workbench is in use, we

recommend that you work with the field codes visible on screen. To set this, select Options from the

Tools menu in Word, click the View tab and select Field Codes.



Trans la t ion o f RTF He lp F i l e s8


Jumps and Popups

When sentences include jumps and popups, you translate the double underlined text (for a jump) or

the single underlined text (for a popup) and then place the corresponding hidden text correctly in the

translation. To facilitate this task, Translator’s Workbench recognizes the hidden text as a placeable.

In the example above, Translator’s Workbench recognizes the hidden text following the jump and

popup as placeables. Position the cursor in the target field and type the translation for the sentence,

making sure to replicate the underlined text in the target segment.

TIPE

Use Word’s Format Painter to replicate source text formatting in the target segment.For more information on the Format Painter, see the Word Help.Press[Ctrl]+[Shift]+[C] to copy the formatting of the selected text.Press [Ctrl]+[Shift]+[V] to paste the copied formatting to the selected text.

To place the hidden text for the jump in the target field, click Get Current Placeable . The hidden

text is placed in the target field at the cursor position. Note that the hidden text is still selected. Pressthe right arrow key [→] to move to the end of the selection and continue to enter your translation

(you may have to press [Ctrl]+[Space] to switch off hidden text and apply the default paragraph font

to the text you are typing). To place the next jump or popup placeable, click Get Next Placeable .

If the hidden text parts of jumps and popups are formatted using a character style, Translator’s

Workbench does not recognize them as placeables. In this case, you need to define the character style

applied to the hidden text as an internal non-translatable character style in the setup of the

translation memory.

NOTE

D Press [Ctrl]+[Space] to apply the document default font when using the English version of Word.For other versions of Word a different shortcut may apply.



P ost - t r ans la t ion P rodu c t ion fo r RTF He lp F i l e s8


POST-TRANSLATION PRODUCTION FOR RTF HELPFILES

Once you have finished translating and cleaning up your translated RTF help files, they are ready for

final DTP and proofing.

Some typical tasks in post-translation production include:

C After clean up, check the documents for errors.

C Reapply the document template.

C Ensure that hyperlinks are accurate and work correctly.

C Make sure graphics are correctly placed and display correctly.

NOTED

If at this stage you choose to update any text, remember to run the Clean Up command inTranslator’s Workbench to update the translation memory.

CONCLUSION


Task Checked?Prepare Microsoft Word and RTF help files for translation ✔

Translate Microsoft Word and RTF help files completely including

features such as footnotes and index entries

✔

Finalize translated Microsoft Word and RTF help files so that text and

graphics display correctly and clearly.

✔



Se lec t ing a Work f low fo r Word F i l e s9


9-

TTX Workflow

Translation of a Microsoft Word document using TagEditor and Translator’s Workbench involves

the following stages:

1 Create a folder structure for your translation project. An orderly folder structure helps you tokeep track of all your source and target files.

2 Prepare your Word documents for translation.

3 Test the Word documents by performing a round trip from Word to TTX and back toWord in TagEditor.

4 In Translator’s Workbench, activate any translation project and filter settings that arerequired. Set the translation memory option for using the TTX workflow.

5

Analyse and pre-translate the documents for translation in Translator’s Workbench,using the Analyse and Translate batch tools.

6 Translate your Word documents using TagEditor.

7 Verify the tag content of target files using the verification plug-ins in TagEditor.

8 Save the target files in TradosTag (TTX) bilingual format, using the Save Bilingual As command in TagEditor.

9 After translation, clean up the translated files and update the translation memoryusing the Clean Up command in Translator’s Workbench. You can also use the SaveTarget As command in TagEditor to perform the same task.

10 Open the translated Word documents in Word post translation production steps andfor further processing.

NOTED

C Word counts using Translator’s Workbench with Word may be different from word countsusing TagEditor due to differences in how each workflow tags and processes the text. Sincethe text considered translatable by TagEditor differs from the text considered translatable byTranslator’s Workbench with Word, segment and word counts may vary.





9-

C Tracked Changes – Tracked changes must not be present in the Word documents to betranslated with TagEditor. If your Word documents contain tracked changes, TagEditordisplays a warning message. Consult the originator of the document about accepting orrejecting revision marks. Then, deactivate the feature in each Word document beforetranslating it.

C Hidden Text – Any text that is hidden in the Word document displays as a tag in TagEditor.Make any text you want to translate visible before opening the Word document in TagEditor.

C Subdocuments – Subdocuments are treated as a separate file. The main document keeps thesubdocument structure preserved.

C Fast Save – Deactivate the Fast Save option in Word, then save the document beforelocalization. This makes sure that the document structure is refreshed before localization.

9-1

If you need a font not provided with the filter you can:

1 Open the original Word document,

2 Apply the font you want to map to to some text in the document and save the file.

3 Reopen the document and change the font back to the original font used.

You can modify the Word filter file to include specific font mappings. In the case of conflicting rules

for an element, the first rule listed is applied. Font mapping settings are case sensitive.

The example below shows how you can use font mapping tags to configure the filter:

<FontMappingRules><FontMappingRule>

BatangBatangChe

Dotum<FontType>FarEast</FontType><LanguageAndRegion>de-DE</LanguageAndRegion><ApplyFont>Tahoma</ApplyFont>

</FontMappingRule><FontMappingRule>

<AllFonts /><AllFontTypes /><AllLanguageAndRegions /><ApplyFont>Arial Unicode MS</ApplyFont>

</FontMappingRule></FontMappingRules>

In the example the Batang, BatangChe, and Dotum fonts of the font type FarEast are being mappedto the Tahoma font. All other fonts will be mapped to Arial Unicode MS.





The table below lists some common Word features that use field codes and the value for the type

attribute.

TIPE

Cross-references are also known as bookmark references.

Hyperlinks

Hyperlinks are listed after the paragraph where the field codes are inserted. The hyperlink uses

placeholders tags in the segment and the URL is translated in the following paragraphs. A

translatable content tag pair is used to mark the URL.

Feature Attribute Value

Cross-references 0x3

Index Entries 0x4

Hyperlinks 0x58

Table of Contents 0xd

Index 0x8

Numeric Field 0x36

Macro Button 0x33

Hyperlink 0x58





9-2

Inserted Text

The following features can all be inserted into a Word document. In TagEditor, inserted text is

treated as a separate segment and each inserted item has a tag.

The following list shows the most common inserted text types:

C Footnotes

C Endnotes

C Comments

C Text boxes

Footnotes and EndnotesFootnotes and endnotes have a reference tag put in place to mark the location of the footnote or

endnote. The translatable text is in the following paragraph, which is wrapped by a footnote or

endnote tag pair.

Non-translatable Footnotes and Endnotes

Footnotes and endnotes can be translatable or not. For example the A footnotes in RTF Helpfiles are not to be translated. Using the SDL Trados Filter Settings you can set A footnotes to benon-translatable.





RTF Help Translation Workflow

Translation of an RTF help file involves the following stages:

1

Create a folder structure for your translation project. An orderly folder structure helps you tokeep track of all your source and target files.

2 Save your RTF help files as *.doc for translation in TagEditor.


required.

4 Translate your RTF help files in TagEditor.

NOTED

C Text in $ and K footnotes is available for translation. The $ and K footnote referencecharacters are protected against accidental deletion and are treated as internal tags.

C Text in other footnotes such as *, +, @, A are protected against translation and are notpresented for translation.

C Graphic references enclosed in curly braces e.g. {bmp c:\temp\mygraphic.bmp} are treatedas internal tags by default. You can however unprotect these internal tags in order to editthe name of the graphic if necessary. To turn all tag protection off, clear the Protect tags check box in the Tools>Options>Protection dialog box.

5 After translation, clean up the translated files and update the translation memory by

running the Clean Up command in Translator’s Workbench. Keep an unclean copy of the bilingual files for reference.

6 Open the translated RTF help files in Word for further processing.

NOTED

For more information about translating files in Word and the clean up feature in Translator’sWorkbench, see the Translator’s Workbench User Guide.



Conc lu s ion9


9-2

CONCLUSION


Task Checked?

Prepare Microsoft Word files for translation in TagEditor ✔

Translate Microsoft Word files completely including features such as

footnotes and index entries in TagEditor

✔

Finalize translated Microsoft Word files so that text and graphics

display correctly and clearly.

✔

Translate RTF Help files using TagEditor ✔



Conc lu s ion9




Overv i ew10



Translation of a PowerPoint document involves the following stages:

1


2 Prepare your PowerPoint documents for translation. For more information, see

“Preparation” on page 9-5.


required.

4 In Translator’s Workbench, analyse and pre-translate the files for translation using the

Analyse and Translate batch tools. During pre-translation, files are converted to

TradosTag.

5 Translate your PowerPoint documents in the TagEditor editing environment. Any files

that have not already been converted to TradosTag are converted during translation.

6 Verify the tag content of the target files using the Generic Tag Verifier plug-in in

TagEditor.

7 Save the target files in TradosTag format using the Save Bilingual As command in

TagEditor or clean the target files using the Clean Up command in Translator’s

Workbench. The clean up process converts each file back to its original format and

restores the original PowerPoint extension (PPT, PPS or POT). Note that the sourcefiles need to be present in their original location.

8 Open the translated documents in PowerPoint and carry out final DTP and proofing.


C For more information about translation and verification in the TagEditor editingenvironment, see the Translator’s Workbench User Guide.

C For more information about analysis, pre-translation and clean up in Translator’sWorkbench, see the Translator’s Workbench User Guide.



P repara t ion10


10-

Using the Filter Settings Application for the PowerPoint Filters

To modify some of the most commonly changed settings in the PowerPoint filter settings files, use

the SDL Trados Filter Settings. You can modify filter settings for the PowerPoint 2000-2003 filter

or for the PowerPoint 2007 filter, depending on which version of PowerPoint your files are from. Animproved PowerPoint filter is available in SDL Trados 2007 which substantially improves the speed

of conversion of PowerPoint documents.

PowerPoint 2000-2003 Filter

The settings you can modify using the SDL Trados Filter Settings for the PowerPoint 2000-2003

filter are:

C Hyperlink and comment processing

C Display formatting and font mapping

C Font adaptation

C Order of slides and shapes

C Segmentation


Trans la t ion10


10-1

PowerPoint Formatting Tags and Tag Display during Translation

In the TradosTag document, all PowerPoint formatting tags are represented as <cf></cf> tag pairs.

The formatting instructions themselves are given as <cf> tag attributes.

TagEditor allows you to choose whether tag text is displayed fully, partially or not at all during

translation. When tag text is displayed in full, the attribute that characterizes each formatting tag is

visible. For example, the tag pair for bold formatting is displayed as <cf bold = “on”></cf>. When

tag text is only partially displayed, the attributes are hidden and all formatting tags are displayed as

generic <cf> tag pairs. In this case, the tag pair for bold formatting is displayed as <cf></cf>.

C To view tag text in full and make tag attributes visible, select Tag Text > Complete from the

View menu or click the appropriate button – on the TagEditor toolbar.

C To hide tag attributes and display generic <cf> tag pairs only, select Tag Text > Partial from the

View menu or click the appropriate button – – on the TagEditor toolbar.

C To hide all tag text and view tag placeholders only, Tag Text > None from the View menu or

click the appropriate button – – on the TagEditor toolbar.

Inserting Tags during Translation

During translation with TagEditor, you can insert tags in your target text using the buttons that are

available on the Tags toolbar. Alternatively, you can copy and paste tags from elsewhere in your

document.

NOTED

If you wish to insert tags in a target segment, make sure that internal tag protection is switchedoff in TagEditor. To turn internal tag protection off, select External tags only on the Protection tab of the Options dialog box (Tools menu).

The Tags toolbar makes a number of frequently used PowerPoint formatting tags available; settings

are predefined and cannot be customized. The tool tip for each button displays information about

the corresponding tag or tag pair.

Use the Tags toolbar to insert tags as follows:

C Tag pairs – in the target segment, select the word or words around which you wish to place thetag pair and then click the appropriate button on the toolbar. TagEditor inserts the tag pairaround the selected target text.

C Stand-alone tag – in the target segment, place the cursor wherever you want the new tag to be inserted and then click the appropriate button on the toolbar. TagEditor insertsthe tag at the cursor position.



Chapte

MICROSOFT EXCEL DOCUMENTS

Microsoft Excel files created in Excel 2000-2003 and Excel

2007 can be translated using TagEditor. This chapter explains

the following aspects of translating Microsoft Excel documents:

C Excel document translation workflow

C Preparing Excel documents for translation

C Excel features during translation

C Post-translation production tips

C Filter Settings application

NOTED

If you are working with SDL Trados Synergy, only the partof this chapter about using the Filter Settings applicationfor the Excel filters (pages 11-7 to 11-9) is relevant to you.

11



Overv i ew11


OVERVIEW

This chapter outlines the translation process that applies to Microsoft Excel documents. It explains

how to prepare Excel documents for translation and shows you to how to handle Excel-specific

features during translation.

Both Translator’s Workbench and TagEditor provide direct support using a filter for the following

Excel document formats:

C XLS and XLSX – Excel workbook

C XLT and XLTX – Excel template.

Requirements

To process Excel documents in Translator’s Workbench or TagEditor, you must have Microsoft Excel

installed on the local computer. Excel 2000, Excel XP (2002), Excel 2003 and Excel 2007 are

supported.

The following considerations apply:

C We recommend that you use the most recent available version of Excel in order to avoid anyloss of data due to backward compatibility issues.

C We recommend that you use the same version of Excel for all tasks involving the same set of

files.

File Size Limitations

When translating Excel files, the files may grow to approximately twice their size because the original

text is stored in the file with the translated text until the clean up stage. If your machine specification

is not adequate or the translation memory is large, the response time of the translation memory is

affected. Keep files to a reasonable size. We recommend that Excel files that have the following

characteristics should be split into smaller files before being sent for translation:

CFile size is greater than 5MB

C Files have more than 15 worksheets

C Files contain mostly text rather than standard spreadsheet information

C Files contain many graphic images.



Overv i ew11


11-

To split your files:

1 In Excel, select the sheet you want to copy and from the Edit menu choose Copy. Open a newworksheet and from the Edit menu choose Paste.

2 Save the sheet with a different name ,for example, Spreadsheet1.xls so that youcan put your spreadsheet back together after you have completed your translationwork.

Key Term Definition

C Workbook – an Excel document.

C Worksheet – a sheet on which data is listed and analysed. Each Excel document consists of oneor more worksheets. A worksheet consists of cells that are organized into columns and rows.

C Spreadsheet – another term for worksheet.

C Chart – an Excel object that provides a graphic representation of worksheet data. A chart maybe embedded on the same worksheet as its source data; or displayed on a separate sheet, calleda chart sheet.

C Data types – Excel documents typically contain different types of data including text, formulasand numeric data. Most of the text in an Excel document qualifies as translatable content;formulas and numeric data do not qualify as translatable content.

C Translatable text – The Excel filter differentiates between translatable and non-translatable

text. Any text that is stored in a cell or text object is considered to be translatable. This text isautomatically extracted during conversion to TradosTag and presented for translation in theTradosTag document.

C Text object – refers to an object in Excel that contains translatable text. These include textboxes, AutoShapes, WordArt drawing objects, organization charts, charts and shapes that areused on Excel forms such as buttons, labels, group boxes and check boxes.

C Non-translatable text – any text that is stored in a Clip Art, external file, camera or scannerpicture is considered to be non-translatable. This text must be manually extracted andtranslated in a separate file.

C Grouped object – a grouped object occurs where one or more items in your presentation havebeen combined so that you can work with them as if they were one single object. The Excelfilter makes translatable text that is stored in grouped objects available for translation.

C Drawing object – refers to an object in Excel that is created using one of the tools on theDrawing toolbar. Some drawing objects, including text boxes, AutoShapes or WordArtdrawing objects, may contain translatable text.

Overv i ew11



Translation of an Excel document involves the following stages:

1


2 Prepare your Excel documents for translation. For more information, see Preparation on page 11-5

3 In Translator’s Workbench, activate any translation project and filter settings that arerequired.

4 In Translator’s Workbench, analyse and pre-translate the files for translation using theAnalyse and Translate batch tools. During pre-translation, files are converted toTradosTag.

5 Translate your Excel documents in the TagEditor editing environment. Any files thathave not already been converted to TradosTag are converted during translation.

NOTED

Do not translate any Excel sheet names, or you will have problems when creating the targetfiles. To avoid translating Excel sheet names, do not translate any text inside the <name> ...</name> external tags.

6 Verify the tag content of the target files using the Generic Tag Verifier plug-in inTagEditor.

7 Save the target files in TradosTag format using the Save Bilingual As command inTagEditor.

8 Clean the target files using the Clean Up command in Translator’s Workbench. Theclean up process converts each file back to its original format and restores the originalExcel extension (XLS or XLT). Note that the source files need to be present in theiroriginal location.

9 Open the translated documents in Excel and carry out final DTP and proofing.


C For more information about translation and verification in the TagEditor editingenvironment, see the Translator’s Workbench User Guide.

C For more information about analysis, pre-translation and clean up in Translator’sWorkbench, see the Translator’s Workbench User Guide.



P repara t ion11


11-

PREPARATION

This section explains how to prepare your Excel documents for conversion to TradosTag and

translation. It outlines the characteristics and limitations of the conversion process.

Handling Macros in Excel Documents

Many Excel documents contain macros that are used to automate frequently-used and complex tasks.

A macro virus is a type of computer virus that is stored in a macro. When you open an infected Excel

document, the macro virus can become active and be transmitted to your computer. When you open

an Excel document that contains a legitimate macro, the macro can become active, generating

message boxes that interrupt the progress of automated batch processes in Translator’s Workbench.

For this reason, you should take certain steps to disable macros before processing your Excel

documents with SDL Trados. Macros can be disabled in different ways, depending on the version of Microsoft Excel that you are using.

C Excel 2002, Excel 2003 – all macros are automatically disabled before processing with SDLTrados. No manual intervention is required.

C Excel 2000 – before you start processing, set the security level for macro virus protection inExcel 2000 to high. For more information, see Microsoft Excel Help. When the security level isset to high, unsigned macros or macros that are not from a trusted source are automaticallydisabled before processing.

TIP

EWhen the security level is set to high and you open a file that contains a macro in Translator’sWorkbench or TagEditor, Excel (2000) appears briefly on your screen. You can ignore it andcontinue working as normal.

About the Conversion Process

During translation with Translator’s Workbench and TagEditor, Excel documents are converted to

TradosTag using a dedicated Excel filter. During the conversion process, most of the content in your

documents is made available for translation and formatting instructions are effectively transferred

from the source to the target document. However, before you start, it is important to be aware of

certain characteristics and limitations in the process. These are outlined below.

C The time required to convert a given document to or from TradosTag depends on the amountof translatable content rather than on the file size. If the document contains a large amount of translatable content, conversion may take some time. During conversion, refer to the statusbar messages and progress indicators in Translator’s Workbench and TagEditor forinformation about conversion status.



P repara t ion11


Modifying the Excel Filter Settings File

During conversion to and from TradosTag, the Excel filter processes content according to

instructions that are outlined in the Excel filter settings file. The name of this file is

Excel_2_0_0_0.xml (for the Excel 2000-2003 filter) or Excel2007_1_0_0_0.xml (for theExcel 2007 filter )and it is installed by default to

C:\Documents and Settings\All Users\Application Data\SDL International\Filters .




information.

The settings in the filter settings file determine which elements of the Excel document will be

converted, and how. The default settings are suitable for most conversion tasks, however, in certain

situations, you may wish to modify one or more of the default settings. For example, by default, theExcel filter does not process any comments that occur in your Excel document. If you wish to

translate comments, you can modify the relevant setting in the filter settings file so that they are

automatically processed and presented for translation in the TradosTag document.

By default, you modify settings in the SDL Trados Filter Settings application, as outlined above. You

may also wish to change settings manually by opening the XML file directly in an appropriate editor.

NOTED

C We recommend that only advanced XML users modify the Excel filter settings file. Before

making any changes, create a backup of the original file.

C For more information about modifying the Excel filter settings file, contact SDL Consultancy.

C If you need to finish your current projects using the older version of the filterExcel_1_0_0_0.xml, you can find this inC:\Documents and Settings\All Users\Application Data\SDL International\Filters .

Trans la t ion11


Working with Bi-directional Languages

If you are translating to or from a directional language, the following considerations apply:

C In Microsoft Excel, when working with source and target files, use the options that areavailable with the Page Setup command to display data in the appropriate right-to-leftdirection.

C In Translator’s Workbench, make sure that the language direction of the translation memoryyou are using is appropriate. This will enable Translator’s Workbench to interpret and presentbi-directional language data correctly.

C During forward and backward conversion, the Excel filter automatically reads and presentstext and text objects in the appropriate direction.

Document Display in TagEditorTagEditor uses a semi-WYSIWYG display for all file types, including Excel documents. During

translation, font color, font size and other document formatting properties may be adapted to suit

the TagEditor environment. All original formatting is automatically stored in the target file during

backward conversion; no manual intervention is required.

Line Breaks, Paragraph Breaks and Segmentation

During conversion, the Excel filter generally interprets a paragraph break in the Excel document as

a line break. In the TradosTag document, a line break is represented as a tag. Note that the tag affects document display in TagEditor and target file formatting, but does not affect

segmentation. As a result, a piece of text that includes one or more tags may still be interpreted

as a single segment by Translator’s Workbench.


For more information about segmentation rules during translation with Translator’sWorkbench, see the online help for Translator’s Workbench.

After you open the document for translation in TagEditor and before you start translating, you may

find it useful to check formatting and segmentation. If necessary, you can modify formatting and

segmentation as follows:

C To introduce a segment break, place your cursor in the text at the appropriate position andpress [Enter]. As well as introducing a segment break, pressing the [Enter] key causes the lineto break in TagEditor, however, this has no effect on target file formatting.

C To introduce a paragraph break, use the 9 button – – on the Tags toolbar in TagEditor.Pressing the 9 button inserts a tag in the document for translation. The tag affectsdocument display in TagEditor and target file formatting, but does not affect segmentation.

Trans la t ion11


11-1

Bulleted Lists

The Excel filter interprets each item in a bulleted list as a separate line and segment. As usual in the

TradosTag document, a line break is represented as a tag.

Excel Formatting Tags and Tag Display during Translation

In the TradosTag document, all Excel formatting tags are represented as <cf></cf> tag pairs. The

formatting instructions themselves are given as <cf> tag attributes.

TagEditor allows you to choose whether tag text is displayed fully, partially or not at all during

translation. When tag text is displayed in full, the attribute that characterizes each formatting tag is

visible. For example, the tag pair for bold formatting is displayed as <cf bold = “on”></cf>. When

tag text is only partially displayed, the attributes are hidden and all formatting tags are displayed as

generic <cf> tag pairs. In this case, the tag pair for bold formatting is displayed as <cf></cf>.

C To view tag text in full and make tag attributes visible, select Tag Text > Complete from the

View menu or click the appropriate button – on the TagEditor toolbar.

C To hide tag attributes and display generic <cf> tag pairs only, select Tag Text > Partial from the

View menu or click the appropriate button – – on the TagEditor toolbar.

C To hide all tag text and view tag placeholders only, Tag Text > None from the View menu or

click the appropriate button – – on the TagEditor toolbar.

Inserting Tags during Translation

During translation with TagEditor, you can insert tags in your target text using the buttons that are

available on the Tags toolbar. Alternatively, you can copy and paste tags from elsewhere in your

document.

NOTED

If you wish to insert tags in a target segment, make sure that internal tag protection is switchedoff in TagEditor. To turn internal tag protection off, select External tags only on the Protection

tab of the Options dialog box (Tools menu).

The Tags toolbar makes a number of frequently used Excel formatting tags available; settings are

predefined and cannot be customized. The tool tip for each button displays information about the

corresponding tag or tag pair.

Use the Tags toolbar to insert tags as follows:

Trans la t ion11


C Tag pairs – in the target segment, select the word or words around which you wish to place thetag pair and then click the appropriate button on the toolbar. TagEditor inserts the tag pairaround the selected target text.

C Stand-alone tag – in the target segment, place the cursor wherever you want the new

 tag to be inserted and then click the appropriate button on the toolbar. TagEditor insertsthe tag at the cursor position.

NOTED

C You can also use the keyboard shortcuts that are associated with each button on the Tagstoolbar to insert tags in the target segment. The tool tip for each button displays thecorresponding keyboard shortcut.

C For more information about the tags that are available on the Tags toolbar for Exceldocuments, see the online help for TagEditor.

Use the copy and paste method to insert tags that are not available on the Tags toolbar.

Quality Assurance

Follow these guidelines to ensure highest quality content in your target files:

C Use the tag protection features in TagEditor to protect the tag content of your file.

C Use the segment level verification settings to have TagEditor verify tag content in thebackground as you work.

C Use the Generic Tag Verifier plug-in to verify tag content at document level frequently duringtranslation.

C Use the spelling checker plug-ins to check spelling as you work.

C Use the Preview tabs in TagEditor to preview individual slides as temporary documents inExcel.

NOTED

For more information about each of these tasks, see the online help for TagEditor or theTranslator’s Workbench User Guide.

After Translation

When translation, editing and tag verification are complete, the bilingual target files are ready for

clean up. The clean up process removes source language data and segment delimiting tags, thus

allowing the TradosTag target file to be converted back to its original format. There are two methods

of cleaning up your translated files. The method you choose depends on whether you have used

Translator’s Workbench throughout for translation and editing.



Trans la t ion11


11-1

Using the Excel Verifier Plug-in

Run the Excel Verifier before choosing Save Target As in TagEditor or running Clean Up in

Translator’s Workbench. The Excel Verifier checks Excel documents for blank worksheet names,

duplicate worksheet names, worksheet names that contain more than 31 characters, and worksheetnames that contain invalid characters such as *, [], !,:,?,\, or /.

Using the Save Target As Command in TagEditor

The Save Target As command in TagEditor cleans the translated file independently of Translator’s

Workbench and does not update the translation memory. This method of clean up is suitable if you

have used Translator's Workbench to translate and edit the document at all times, keeping the

translation memory up to date with the latest bilingual data. In the Save Target As dialog box, select

the original file type (Microsoft Excel Documents (*.xls, *.xlt)) from the Save as type drop-down list. As

the document is being saved and converted back to its original format, TagEditor removes all source

segments and segment delimiters, leaving only a ‘clean’ target language version.

Using the Clean Up Command in Translator’s Workbench

If you have made changes to the target segments without using Translator's Workbench, these

changes have not yet been added to the current translation memory.

There are several reasons why Translator's Workbench may not be active at all times during the

document editing stage:

C You may have corrected typing errors without first re-opening the translation unit and savingthe revised translation in the translation memory afterwards.

C You may have used the Replace command to make global text changes.

In this case, use the Clean Up command in Translator’s Workbench to remove source language data

from the translated file and to update the translation memory at the same time. Follow these steps:

1 In TagEditor, use the Save Bilingual As command (File menu) to save the translated file asTradosTag (TTX) and close it.

2 Select Clean Up from the Tools menu in Translator’s Workbench to clean up a singlefile or a batch of files together. Select Update TM in the Clean Up Files dialog box toupdate the translation memory in accordance with any changes you made to thetranslated files outside Workbench.

As well as removing source language data and updating the translation memory, the clean up process

converts each file back to its original format and restores the original Excel extension (*.xls,

*.xlt). Note that the source files need to be present in their original location.



Conc lu s ion11


11-1

CONCLUSION


Task Checked?

Prepare Excel documents for translation. ✔

Translate Excel documents using TagEditor and Translator’s

Workbench.

✔

Finalize target files so that all data displays correctly in Excel. ✔



Chapte

TRANSLATING PROGRAMMING

FILES

This chapter discusses how to localize executable files such as

EXE, DLL, OCX, and LNG files using filter plug-ins to open and

translate files directly in TagEditor. Other file types covered in

this chapter include RC, DLG, and Java .properties files.

NOTED

If you are working with SDL Trados Synergy, only the partof this chapter about using the Filter Settings applicationfor the Window RC files filter (pages 12-9 to 12-11) and theJava Resource files filter (pages 12-18 to 12-19) are relevantto you.

12



Loca l i z ing Windows32 B inar y F i l e s12


LOCALIZING WINDOWS32 BINARY FILES

The Windows32 Binary Filter allows you to open and translate Windows32 (Win32) binary files

(*.exe, *.dll, *.ocx) directly in TagEditor. Using the filter, you can directly process Win32 binary files

across all the other applications, such as Translator's Workbench for analysis, pre-translation, andclean-up and WinAlign for alignment of existing Win32 binary files.

NOTED

The Windows32 Binary Filter supports *.exe, *.dll, *.ocx, and .lng files developed in MicrosoftVisual Studio. However, Visual Basic executables and .NET assemblies cannot be localized withthis filter.


Translation of a Windows32 binary file involves the following steps:


keep track of all your source and target translation files.

2 In Translator’s Workbench, activate any translation projects and filter settings that are

required.

3 Analyze and pre-translate the files for translation in Translator’s Workbench using the

Analyse and Translate batch tools.

4 Translate your EXE, DLL, OCX, and LNG files in TagEditor.

5 Preview the Menu and Dialog box text in bilingual or source language format as you

translate.

6 Verify the tag content of target files using the Win32 Binary Verifier verification plug-

in.

7 Save the target files in TradosTag (TTX) bilingual format, using the Save Bilingual As

command in TagEditor.


9 Launch the translated EXE, DLL, OCX, and LNG files to test them in your build

environment.

NOTED


12-

Preparation

The Windows32 Binary Filter treats control characters such as line breaks, ampersands, percent

signs and plus signs as tags. You can prepare your translation memory before starting a new job in

SDL Trados 2007 by exporting the translation memory from Translator’s Workbench, editing thefile in a text editor such as Notepad, and importing the modified translation memory back into

Translator’s Workbench.

Convert the characters to a tag by using the code string:

{\cs6\f1\cf6\lang1024 <characters>} where <characters> is the control character

you want to convert.

The following table shows examples of some of the common characters that can be converted:

Translation

Win32 binary files can be translated in TagEditor just like any other tagged file. The Windows32

Binary Filter first presents all menu strings for translation, then the dialog box strings, and finally

all other strings, such as message strings.

C Menu items often have an ampersand (&) placeable at the beginning or in the middle of the

string. In the Menu item string below, the word File is preceded with an ampersand, which

is the shortcut indicator for the shortcut character F. In the target segment, you need to

position the ampersand tag to act as a shortcut indicator in front of the letter that is the

shortcut character in the target language, in this example, the letter D.

Control Character Conversion Code

+ {\cs6\f1\cf6\lang1024 +}

& {\cs6\f1\cf6\lang1024 &}

\n {\cs6\f1\cf6\lang1024 \n}

%s {\cs6\f1\cf6\lang1024 %s}

%d {\cs6\f1\cf6\lang1024 %d}





C Menu item strings can be followed by a shortcut key combination. These keyboard shortcuts

allow the user of the application to directly access functions by pressing a particular keyboard

combination, for example Ctrl+O.

C Shortcut key combinations can consist of a simple key, such as F8, or they can be comprised

of a key name that is preceded by a so-called modifier such as Ctrl, Shift, or Alt and an

internal "+" tag . An example of a shortcut key with a modifier is Alt+F8. The modifier

usually needs to be translated, for example the English Ctrl is translated into German as

Strg. The original shortcut key character needs to be replaced with the corresponding target

language character.

C Binary files can also contain dialog boxes. Dialog boxes can contain a number of control

elements such as buttons, drop-down lists, text fields or labels. The binary filter presents these

string elements for translation as well. Control element strings can also have shortcut key

indicators, which must be placed in front of the corresponding shortcut character of the targetlanguage.

C Binary files usually contain strings that are not associated with either a menu or a dialog box.

These can be message strings, which are shown to the user when a certain condition is met,

such as "Login failed." In TagEditor you will find these strings after the menu and dialog

strings. These strings are enclosed in string tags.





C At the end of the binary file you can find version information if applicable. This is the

information you see when you right-click the EXE, DLL, OCX, or LNG file in Windows

Explorer and choose to view the version information.

After Translation

1 When you have finished translating the file, verify the tag content using the SDL Trados

Win32Binary Verifier in TagEditor. Successful verification ensures that the syntax of tags in thetranslated file is correct and guarantees backward conversion.


bilingual data from the translated file and to convert the file back to the Win3dows2

Binary format.

3 Save the file to your target folder.

Previewing File OutputDuring or after translation you can preview the source and target-language menus and dialogs in

WYSIWYG mode. To do this, place your cursor somewhere within the menu or dialog tags of the

content you want to preview and select View > Preview Mode in TagEditor. You can choose among

Bilingual Preview, Source, or Target.

NOTED

Message strings cannot be previewed. For example, if you try to access the Preview Mode whileyour cursor is placed within a pair of string tags somewhere outside of a menu or dialogelement, a message is displayed stating that the string cannot be previewed.

When you preview a menu or a dialog, an external preview application will open, containing the

menu or dialog to preview.

NOTED

A preview just represents a token menu or dialog. It does not implement any functionality anddialog control elements cannot be resized in the preview.





12-


After finishing your translation, run the SDL Trados Win32Binary Verifier to check the translated

file for potential problems. Problems can include duplicate shortcut key assignments where the

same keyboard shortcut has been assigned to two different menu items within the same menu,strings that exceed the maximum length of 256 characters, and so on.

1 Select Tools > Plug-ins. In the Plug-ins dialog box, make sure that SDL Trados Win32Binary

Verifier is selected.

2 Close the Plug-ins dialog box and select Tools > Verify or press F8 to start the

verification.

Any potential problems are reported in the TagEditor message pane. Double-click a message

to jump to the corresponding string and correct the problem.

NOTED

Even if problems are reported during verification, it does not mean that your target file isinvalid. For example, if your translation contains duplicate shortcut key assignments, the target-





language application will still run. However, it is recommended that you correct such problemsto ensure optimum usability of the target-language application.

Cleaning Up Translated FilesThere are two methods for cleaning up translated files: Save Target As and Clean Up. The method

you choose depends on whether you have used Translator’s Workbench throughout for translation

and editing.

Saving Translated File as Target

After translation and verification you can save your bilingual TTX file as a target file by selecting

File > Save Target As in TagEditor. Select a name for your target file. Make sure that when saving the

target file, the source file is still present in its original location. Otherwise an error message displaysindicating where the source file is expected to be.

Clean Up

Use Clean Up in Translator's Workbench to update the translation memory with any changes made

and to generate the target files. Note that the source files need to be present in their original location.



Loca l i z ing Resou rce F i l e s12


12-

LOCALIZING RESOURCE FILES

The RC Filter allows you to add files directly to SDL Trados Synergy or to open and translate resource

files directly in TagEditor. Using the filter, you can directly process resource files across all SDL

Trados applications, such as Synergy (or Translator's Workbench if you are not using Synergy) for

analysis, pre-translation, and clean-up and WinAlign for alignment of existing resource files. The RC

Filter recognizes the .rc and .dlg file formats.

Windows RC files traditionally contain text used in the user interface and DLG files contain scripts

used for dialog resources and are linked to executables such as EXE or DLL files. One project can

have multiple resource files.

Resource files generally contain the text used for dialog boxes, menus, bitmaps, icons, and so on.

Some resources in a resource file such as bitmaps and icons may not need to be translated. Check

with the originator of the resource file.

NOTED

Microsoft .NET resource files (RESX) are treated as a special type of XML file. You can translatethese files using the resx.ini tag settings file. See Chapter 2, HTML, XML, and SGML Files for more information.





Using the Filter Settings Application for the Windows RC Files Filter

You can use the RC filter settings to determine if the filter should perform a check of the RC file

header or check for the occurrences of multiple language resources before opening or processing a

file. If the checks are enabled the filter behaves more strictly when opening an RC file. If you disablethese settings, the filter does not perform the checks.





Settings application opens..

2 Click Windows RC files and select an option. Follow the directions shown for each

setting to make changes.



TIPE






12-1

Modifying the RC Filter Settings File

During conversion to and from TradosTag, the RC filter processes content according to instructions

that are outlined in the RC Filter Settings s file. The name of this file is RCFilter_1_0_0_0.xml

and it is installed by default toC:\Documents and Settings\All Users\Application Data\SDL International\Filters .




information.

The settings in the filter settings file determine which elements of the RC document will be treated

during translation. By default, you modify settings in the SDL Trados Filter Settings application, as

outlined above. You may also wish to change settings manually by opening the XML file directly in

an appropriate editor.

NOTED

C We recommend that only advanced XML users modify the RC filter settings file. Beforemaking any changes, create a backup of the original file.

C For more information about modifying the RC filter settings file, contact SDL Consultancy.


Translation of a resource file involves the following steps:




required.

3 Analyse and pre-translate the files for translation in Translator’s Workbench using the


4 Translate your resource files in TagEditor.

5 Preview the Menu and Dialog box text in bilingual or source language format as you

translate.

6 Verify the tag content of target files using the RC File Verifier plug-in.



9 Open the translated resource files in your build environment for testing.

NOTE

D For more information about translating files in TagEditor and the clean up feature inTranslator’s Workbench, see the Translator’s Workbench User Guide.

Preparation

If you previously used SDL Trados translation tools to localize the RC files, your translation

memories will have a difference in the matching rates because RC files are now directly translated

in TagEditor instead of through a T-Window.

The RC Filter treats control characters such as line breaks, ampersands, percent signs and plus signsas tags. You can prepare your translation memory before starting a new job in SDL Trados 2007 by

exporting the translation memory from Translator’s Workbench, editing the file in a text editor such

as Notepad, and importing the modified translation memory back into Translator’s Workbench.

Convert the characters to a tag by using the code string:

{\cs6\f1\cf6\lang1024 <characters>} where <characters> is the control character

you want to convert.

The following table shows examples of some of the common characters that can be converted:

Translation

Resource files can be translated in TagEditor just like any other tagged file. The RC Filter first

presents the menu item strings, then the dialog box strings, and finally all other strings, such as

message strings. Resource files can be divided up so one file can only contain menu items strings,

another dialog box strings, and so on.

Control Character Conversion Code

+ {\cs6\f1\cf6\lang1024 +}

& {\cs6\f1\cf6\lang1024 &}

\n {\cs6\f1\cf6\lang1024 \n}

%s {\cs6\f1\cf6\lang1024 %s}

%d {\cs6\f1\cf6\lang1024 %d}





C Resource files can contain strings that are not associated with either a menu or a dialog box.

These can be message strings, which are shown to the user when a certain condition is met,

such as "Login failed." In TagEditor you will find these strings after the menu and dialog

strings. These strings are enclosed in string tags.

C Strings can contain special (non-printable) control characters, such as \n, which indicates a

line break or \r, which indicates a carriage return. Most control characters are tags, however,

tabs appear as part of the text. Control characters are shown as internal tags, which need to be

inserted at the corresponding position in the target segment. Strings can also contain variable

placeholders such as %d or %s, shown in TagEditor as internal tags. Variable placeholders start

with a percent sign % and are followed by one or more characters or numbers.

In the example below, the placeholder %d is used as a placeholder for the current pagenumber, which is inserted dynamically during runtime of the application. Make sure you

insert these placeholders at the corresponding position of the target segment without

changing the order in which they occur in the source segment.





12-1

However, you can change the order of numbered placeholders such as %1, %2, %3, in the

target segment.

C At the end of the resource file you can find version information, if applicable.

After Translation

1 When you have finished translating the file, verify the tag content using the SDL Trados RC

File Verifier in TagEditor or SDL Trados Synergy. Successful verification ensures that the

syntax of tags in the translated file is correct and guarantees backward conversion and

compilation in Visual Studio.


bilingual data from the translated file and to convert the file back to the resource file

format.

NOTED

You can also save the file to the target format in TagEditor. See Cleaning Up Translated Files on page 12-17 for more information.

3 Save the file to your target folder.

Previewing File Output

During or after translation you can preview the source and target-language menus and dialogs inWYSIWYG mode. To do this, place your cursor somewhere within the menu or dialog tags of the

content you want to preview and select View > Preview Mode in TagEditor. You can choose among

Bilingual Preview, Source, or Target.

NOTED

Message strings cannot be previewed. For example, if you try to access the Preview Mode whileyour cursor is placed within a pair of string tags somewhere outside of a menu or dialogelement, a message is displayed stating that the string cannot be previewed.





When you preview a menu or a dialog, an external preview application will open, containing the

menu or dialog to preview.

NOTED

A preview just represents a token menu or dialog. It does not implement any functionality anddialog control elements cannot be resized in the preview.


After finishing your translation, run the SDL Trados RC File Verifier to check the translated file for

potential problems. Problems can include duplicate shortcut key assignments where the same

keyboard shortcut has been assigned to two different menu items within the same menu, strings that

exceed the maximum length of 255 characters, and so on.

1 Select Tools > Plug-ins. In the Plug-ins dialog box, make sure that SDL Trados RC File Verifier

is selected.

2 Close the Plug-ins dialog box and select Tools > Verify or press F8 to start the

verification.

Any potential problems are reported in the TagEditor message pane. Double-click a messageto jump to the corresponding string and correct the problem.





12-1

NOTED

Even if problems are reported during verification, it does not mean that your target file isinvalid. For example, if your translation contains duplicate shortcut key assignments, the target-language application will still run. However, it is recommended that you correct such problemsto ensure optimum usability of the target-language application.

Cleaning Up Translated Files

There are two methods for cleaning up translated files: Save Target As and Clean Up. The method

you choose depends on whether you have used Translator’s Workbench throughout for translation

and editing.

Saving Translated File as Target

After translation and verification you can save your bilingual TTX file as a target file by selectingFile > Save Target As in TagEditor. Select a name for your target file. Make sure that when saving the

target file, the source file is still present in its original location. Otherwise an error message displays

indicating where the source file is expected to be.

Clean Up

Use Clean Up in Translator's Workbench to update the translation memory with any changes made

and to generate the target files. Note that the source files need to be present in their original location.



Loca l i z ing Java .p rope r t i es F i l e s12


LOCALIZING JAVA .PROPERTIES FILES

The Java Resource Files Filter allows you to add files directly to SDL Trados Synergy or to open and

translate java properties files directly in TagEditor. Using the filter, you can directly process Java

properties files across all SDL Trados applications, such as Synergy (or Translator's Workbench if you are not using Synergy) for analysis, pre-translation, and clean-up and WinAlign for alignment

of existing properties files. The Java Properties Filter recognizes the .properties file format.

Using the Filter Settings Application for the Java Properties Filter

You can use the Filter Settings application to modify some of the settings for Java Properties files:

C Comments

C Delimiters

C Empty values and verification

C Tags

C Entities






12-1





2 Click Java Resource files and select an option. Follow the directions shown for each

setting to make changes.



TIPE

If you do not want to save the changes, and you have not clicked Save, clicking Exit will close

the application without saving.

Modifying the Java Properties Filter Settings File

During conversion to and from TradosTag, the Java Properties filter processes content according to

instructions that are outlined in the Java Properties filter settings file. The name of this file is

JavaResourceFilter_1_0_0_0.xml and it is installed by default to



want to see this folder and any subfolders. Also, if you want to make any changes to files in thisfolder, you must have read/write access to this folder. Consult your IT department for more

information.

The settings in the filter settings file determine which elements of the Java document will be

processed. The default settings are suitable for most conversion tasks, however, in certain situations,

you may wish to modify one or more of the default settings. You generally modify settings in the SDL

Trados Filter Settings application, as outlined above. You may also wish to change settings manually

by opening the XML file directly in an appropriate editor.

NOTED

C We recommend that only advanced XML users modify the Java Properties filter settings file.Before making any changes, create a backup of the original file.

C For more information about modifying the Java Properties filter settings file, contact SDLConsultancy.






Translation of a Java properties file involves the following steps:




required.



4 Open your Java properties files in TagEditor. Your file will look similar to this

5 Translate your Java properties files in TagEditor.





12-2

6 You can preview your file in bilingual or source language format as you translate.

7 Placing your cursor over the resource tag will enable you to check what the resource is.




10 Open the translated resource files in your build environment for testing.

NOTED




Def in ing Java V i r tu a l Mach ine S i ze f i l t e r se t t ings12


DEFINING JAVA VIRTUAL MACHINE SIZE FILTERSETTINGS

When you are working with RC files or java .properties files, you may receive a

java.lang.OutofMemory error when you attempt use the Save Target As command in

TagEditor. This error occurs when the Heap Size of the Java virtual machine is set too low. If you

increase the minimum/maximum amount of available Java memory, this error will not occur.

You can increase the minimum/maximum amount of available Java memory using the Java Virtual

Machine Size filter settings, which you define in the Filter Settings application:




2 Click Java Virtual Machine Size to display the Java Virtual Machine Size Filter Settings

page.

The filter automatically checks for the total amount of available RAM and adjusts the figures

in the Minimum Java Memory and Minimum Java Memory drop-down lists accordingly.

3 To change the minimum and maximum amount of Java memory, select the Change

Java virtual machine size checkbox and adjust the values in the Minimum Java Memory

and Minimum Java Memory drop-down lists.

Click Save to save your changes and click Exit to close the application.



Chapte

TRANSLATING SDLX FILES

This chapter discusses how to edit ITD files coming from

SDLX in TagEditor.

NOTED

SDLX 2005 SP1 must be installed before you can useTagEditor to translate SDLX ITD files.

13



Abou t Work ing w i th SDLX Docu ments13


ABOUT WORKING WITH SDLX DOCUMENTS

SDLX ITD Files are the bilingual files created during translation when you are using SDLX. SDLX

documents have a file extension of .itd.

ITD files can be edited or reviewed in TagEditor, and you can leverage from your Translator's

Workbench translation memory but the analysis and clean up function must take place in SDLX

2005 SP1.

They are translated in the same way as other file types but there are some differences:

C ITD files are automatically formatted into translation units (TUs); only the target segment text

can be edited

C ITD specific options are available from the SDLX menu and the SDLX toolbar

C ITD files cannot be saved as TTX files

C ITD files cannot be opened in any other SDL Trados application (including Translator's

Workbench)

C ITD files should be returned to SDLX for translation memory updating and export to target

format.

Translation Memory

When translating ITD files you use Translator's Workbench for translation memory functions. If

you wish to use an SDLX translation memory, it must be exported to SDL Trados format and then

opened in Translator's Workbench. To do this open the ITD files in SDLX and use the File List to

Trados function which is available from the Export to format option on the TM menu in SDLX Edit

and SDLX Maintain. Alternatively, you could use the Export to TMX option on the TM menu in

SDLX Edit or SDLX Maintain.

However, you could use an SDL Trados translation memory (TM) when you are translating the file

as the SDLX project manager can update the SDLX TM when the translation has been completed

and the file returned to them.

SDLX Menu

The SDLX menu is located on the Edit menu. It contains options for confirming and unconfirming

segments and for navigating the ITD by moving from one unconfirmed segment to the next. The

SDLX menu options are only available when you are working on an ITD file.

13-

SDLX Toolbar

The SDLX toolbar is automatically enabled when you are working on an ITD file. It contains options

for confirming segments and navigating the ITD file.

The SDLX toolbar contains three options:

C Confirmed - toggles the confirmed status for the current segment on/off

C Previous Unconfirmed - moving up the document from the current segment, go to the

next unconfirmed segment

C Next Unconfirmed - moving down the document from the current segment, go to the

next unconfirmed segment.

TagEditor Toolbar

Only three tags may be inserted into ITD segments: , and . Other tag options are

disabled when working on ITD files.





Comments

You can add document and segment level comments and read comments added to the ITD file in

SDLX. For more information on Comments refer to the TagEditor help.

Confirming Segments

Segments are automatically confirmed when you close them using the Set/Close command.

Alternatively you can place the cursor anywhere in the TU and:

C Click the Confirmed button on the SDLX toolbar, or

C

Press CTRL/Enter, or

C Select Edit>SDLX>Confirmed Translation from the menu bar (a check mark here means that

the segment is currently confirmed).

The confirmed status can be toggled on and off using the same commands.





13-

To confirm all segments select Edit>SDLX>Confirm All Translations from the menu bar. This

command cannot be undone.

SDLX>Confirm Translation

Sets the status of the current TU to confirmed. Selecting again toggles the confirmed status on/off.

If the option is preceded by a check mark, the segment is currently confirmed.

This option is used on a closed TU.

The keyboard shortcut for this option is Ctrl+Enter. You can also confirm/unconfirm the TU by

clicking the Confirmed button on the SDLX toolbar.

SDLX> Confirm All Translations

Sets the status of all TUs to confirmed. The confirm all status cannot be toggled on/off by selecting

this option again.





SDLX> Go To Next Unconfirmed Translation

Moving down the document from the current segment, go to the next segment which has not been

confirmed.

The keyboard shortcut for this option is F5.

SDLX> Go To Previous Unconfirmed Translation

Moving up the document from the current segment, go to the next segment which has not been

confirmed.

The keyboard shortcut for this option is Ctrl+F5.

SDLX> Open/Get Next Unconfirmed

Opens the next unconfirmed segment, searches for potential matches in the translation memory and

transfers the translation, if any, to your document.

Use this button to start translation mode for SDLX ITD files.

The keyboard shortcut for this option is Ctrl+F5.

SDLX> Set/Close Next Unconfirmed Open/Get

Closes the currently open translation unit, saves it in the translation memory, opens the next

segment and transfers the translation, if any, to your document.

Use this button to confirm a translation and move on to the next segment when translating SDLX

ITD files.

The keyboard shortcut for this option is Alt+Ctrl+Enter.

Cleaning up SDLX Files

Any batch processing including analysis and clean up of SDLX ITD files must be carried out in SDLX

2005 SP1 or higher.



Chapte

TRANSLATING GENERIC

DELIMITED TEXT FILES

This chapter discusses how to edit Generic Delimited Text files,

that is files that are delimited by a marker such as a tab or a

colon.

NOTED

In order to use the SDL Generic Delimited Filter Settingsyou must have SDLX 2005 SP1 (Lite version or better)installed. SDLX 2007 is always installed alongside SDLTrados 2007.

14



Gener i c De l imi ted Tex t F i l e s14


GENERIC DELIMITED TEXT FILES

You can localize ASCII text files which are delimited using a specified delimiter such as semi-colon

or tab.

You can use the SDL Trados Filter Settings application to determine how your generic delimited text

files should be processed.

Using the Filter Settings Application for the SDL Generic Delimited Filter

You can use the SDL Generic Delimited files filter Settings to determine which file types can be

processed using this filter.

NOTED

In order to use the SDL Generic Delimited files filter settings you must have SDLX 2005 SP1(Lite version or better) installed.







Gener i c De l imi ted Tex t F i l e s14


NOTED

C We recommend that only advanced XML users modify the SDL Generic Delimited filtersettings file. Before making any changes, create a backup of the original file.

C

For more information about modifying the SDL Generic Delimited filter settings file, contactSDL Consultancy.


Translation of your delimited file involves the following steps:




required.



4 Translate your text files in TagEditor.


command in TagEditor. Select a name for your target file. Make sure that when saving

the target file, the source file is still present in its original location. Otherwise an error

message displays indicating where the source file is expected to be.


NOTED




Chapte

TRANSLATING OPENOFFICE

AND STAROFFICE FILES

SDL Trados 2007 supports the translation of OpenOffice and

StarOffice files.

Open Office and StarOffice files are similar to each other and

are handled in the same way by SDL Trados 2007.

NOTED

If you are working with SDL Trados Synergy, this chapteris not relevant to you, as you can add OpenOffice filesdirectly to Synergy projects.

15



Overv i ew15


OVERVIEW

Supported Versions

SDL Trados 2007 supports files from OpenOffice 1.1.5, OpenOffice 2 and StarOffice 8. OpenOffice

or StarOffice do not need to be installed in order to translate files but in order to see what your files

look like once they have been translated you must have the OpenOffice or StarOffice application.

Supported File Types

The following StarOffice and Open Office file types are supported by SDL Trados.

OpenOffice

C ODT for word processing

C ODS for spreadsheets

C ODP for presentations

StarOffice

C SXW for word processing

C SXC for spreadsheets

C SXI for presentations

The SDL OpenOffice Filter Settings File

During conversion to and from TradosTag, SDL Trados processes content according to instructions

that are outlined in the SDL OpenOffice filter settings file. The name of this file is

OpenOfficeFilter_1_0_0_0.xml and it is installed by default to





information.



Overv i ew15


15-

The settings in the filter settings file determine which elements of the text file will be treated during

translation. By default, you modify settings in the SDL Trados Filter Settings application, as outlined

above. You may also wish to change settings manually by opening the XML file directly in an

appropriate editor.

NOTED

C We recommend that only advanced XML users modify the SDL OpenOffice filter settingsfile. Before making any changes, create a backup of the original file.

C For more information about modifying the SDL OpenOffice filter settings file, contact SDLConsultancy.


Translation of your OpenOffice file involves the following steps:




required.



4 Translate your text files in TagEditor.


command in TagEditor. Select a name for your target file. Make sure that when saving

the target file, the source file is still present in its original location. Otherwise an error

message displays indicating where the source file is expected to be.


NOTED


Previewing OpenOffice and StarOffice Files

In order to preview your OpenOffice or StarOffice files you must have the OpenOffice or StarOffice

application installed on your computer.



Overv i ew15


Defining Java Virtual Machine Size filter settings

When you are working with OpenOffice files, you may receive a java.lang.OutofMemory error

when you attempt use the Save Target As command in TagEditor. This error occurs when the Heap

Size of the Java virtual machine is set too low. If you increase the minimum/maximum amount of available Java memory, this error will not occur.

You can increase the minimum/maximum amount of available Java memory using the Java Virtual

Machine Size filter settings, which you define in the Filter Settings application:




2 Click Java Virtual Machine Size to display the Java Virtual Machine Size Filter Settings

page.

The filter automatically checks for the total amount of available RAM and adjusts the figuresin the Minimum Java Memory and Minimum Java Memory drop-down lists accordingly.

3 To change the minimum and maximum amount of Java memory, select the Change

Java virtual machine size checkbox and adjust the values in the Minimum Java Memory

and Minimum Java Memory drop-down lists.

Click Save to save your changes and click Exit to close the application.



Chapte

TRANSLATING TEXT-BASED

FILES

This chapter discusses how to prepare text files for translation

using the Regular Expression text file filter. Sections include:

C Overview

C Using the Filter Settings Application for the Regular

Expressions Filter

C Modifying the Regular Expression Settings File

16



Overv i ew16


OVERVIEW

The Regular Expression text files filter allows you to add text files directly to SDL Trados Synergy or

to open and translate text files directly in TagEditor. Using the filter, you can directly process text files

across all SDL Trados applications, such as Synergy, TagEditor, Translator’s Workbench andWinAlign.

Text files often contain text for translation or localization in a pre-defined structure. Using the

Regular Expression text files filter allows this structure to be retained during the translation process.

Using the Filter Settings Application for the Regular ExpressionsFilter

You can use the Regular Expressions text files filter settings to to define external patterns describingthe structure of your text files or to define internal patterns specifing the text blocks that should be

converted to internal tags during translation. You can also specify the source and target encoding for

your files or use the built-in default codepage detection feature.


NOTED

The regular expressions in this filter follow the implementation in the Microsoft .NETFramework version 2.0.



Overv i ew16


16-





2 Click Regular Expressions text files.

3 If you want to specify the source encoding for your files, select an option from the

Source encoding drop-down list.

NOTED

If you want to use the built-in default codepage detection feature, leave the default selection,_Default (code-paged detection)_, selected here.

4

If you want to specify the target encoding for your files, select an option from theTarget encoding drop-down list.

5 If you want to use external patterns to define the structure of your text files, click

External patterns under Regular Expression text files in the left-hand pane.

C In the Opening pattern and Closing pattern text boxes, enter opening and closing patterns

to define the start and end point of external tags. Any text in external tags should be

skipped and not exposed for translation. Click Add to add the external tag setting to the list.

C To delete an external tag setting, select it in the list and click Del.



Overv i ew16


6 If you want to use internal patterns to define which text should be converted to internal

tags, click Internal patterns under Regular Expression text files in the left-hand pane.

C In the Internal tag pattern text box, enter the interal pattern you want to use to convert

something into an internal tag. Click Add to add the internal tag setting to the list.

C To delete an internal tag setting, select it in the list and click Delete.



TIPE




Overv i ew16


16-

Modifying the Regular Expression Settings File

During conversion to and from TradosTag, the Regular Expression filter processes content

according to instructions that are outlined in the Refular Expression Filter Settings file. The name

of this file is RegExFileFilter_1_0_0_0.xml and it is installed by default toC:\Documents and Settings\All Users\Application Data\SDL International\Filters .




information.

The settings in the filter settings file determine which elements of the text file will be treated during

translation. By default, you modify settings in the SDL Trados Filter Settings application, as outlined

above. You may also wish to change settings manually by opening the XML file directly in an

appropriate editor.



Overv i ew16




Append

SUPPORTED LANGUAGES

This appendix covers supported languages and locales for SDL

Trados Synergy .

A



Su ppor ted Langu ages and Loca les A


A-

Byelorussian Default 1059

Catalan Default 1027Chinese Hong Kong 3076

Chinese PRC 2052

Chinese Singapore 4100

Chinese Taiwan 1028

Croatian Croatia 1050

Czech Czech Republic 1029

Danish Denmark 1030

Divehi (Maldives)

Dutch Belgium 2067

Dutch Netherlands 1043

English Australia 3081

English Bellize 10249

English Canada 4105

English Caribbean 9225

English Ireland 6153

English Jamaica 8201

English New Zealand 5129

English South Africa 7177

English Trinidad 11273

English United Kingdom 2057

English United States 1033

Estonian Estonia 1061

Faeroese Faeroe Island 1080

Farsi Iran 1065

Finnish Finland 1035

Language SubLanguage ID



Su ppor ted Langu ages and Loca lesA

A-4FILE FORMATS REFERENCE GUIDE

French Belgium 2060

French Canada 3084French France 1036

French Luxembourg 5132

French Switzerland 4108

Gaelic Ireland 1084

Gaelic Scotland 3132

Georgian (Georgia)

German Austria 3079

German Germany 1031

German Liechtenstein 5127

German Luxembourg 4103

German Switzerland 2055

Greek Greece 1032

Gujarati (India)

Hebrew Israel 1037

Hindi (India)

Hungarian Hungary 1038

Icelandic Iceland 1039

Indonesian Indonesia 1057

Italian Italy 1040

Italian Switzerland 2064

Japanese Japan 1041

Kannada (India)

Kazakh

Konkani (India)

Korean Korea 1042






A-

Latvian-Lettish Latvia 1062

Lithuanian Lithuania 1063Macedonian Macedonia 1071

Malay Malaysia 1086

Malayalam

Marathi (India)

Mongolian

Northern Sotho

Norwegian Bokmal 1044

Norwegian Nynorsk 2086

Polish Poland 1045

Portuguese Brazil 1046

Portuguese Portugal 2070

Punjabi (Gurmukhi - India)

Quechua (all variants)

Romanian Romania 1048

Russian Russia 1049

Sanskrit (India)

Serbian-Cyrillic Yugoslavia 3098

Serbian Yugoslavia 2074

Slovak Slovakia 1051

Slovenian Slovenia 1060

Spanish Argentina 11274

Spanish Bolivia 16394

Spanish Chile 13322

Spanish Colombia 9226

Spanish Costa Rica 5130






Spanish Dominican Republic 7178

Spanish Ecuador 12298Spanish El Salvador 17418

Spanish Guatemala 4106

Spanish Honduras 18442

Spanish Mexico 2058

Spanish Modern Sort 3082

Spanish Nicaragua 19466

Spanish Panama 6154

Spanish Paraguay 15370

Spanish Peru 10250

Spanish Puerto Rico 23562

Spanish Spain 1034

Spanish Uruguay 14346

Spanish Venezuela 8202

Swedish Finland 2077

Swedish Sweden 1053

Syriac (Syria)

Tagalog Philippines 1124

Tamil (India)

Tatar

Telugu (India)

Thai Thailand 1054

Tswana

Turkish Turkey 1055

Ukrainian Ukraine 1058

Urdu Pakistan 1056






A-

Two-letter Language Codes from ISO 639

Uzbek (Cyrillic),

Uzbek (Latin)Vietnamese Vietnam 1066

Welsh Wales 2108

Afrikaans AF

Albanian SQ

Arabic AR

Armenian HY

Azeri (Cyrillic) AZ-LT

Azeri (Latin) AZ-CY

Basque EU

Bengali BNBulgarian BG

Byelorussian BE

Catalan CA

Chinese ZH

Croatian SH-HR

Czech CS

Danish DA

Dutch NL

English EN

Estonian ET

Faeroese FO






Farsi FA

Finnish FI

French FR

Gaelic GA

Georgian KA

German DE

Greek EL

Gujarati GU

Hebrew HE

Hindi HI

Hungarian HU

Icelandic IS

Indonesian ID

Irish = Gaelic (Ireland)

Italian IT

Japanese JA

Kampuchean KA

Kannada KN

Kazakh KK

Konkani KOK

Korean KO

Kazakh

Laothian

KK

LO

Latvian, Lettish LV

Lithuanian LT

Macedonian MK

Malay

(Brunei Darussalam)

MS-BN





A-

Malay

(Malaysia)

MS-MY

Malayalam MAL

Maltese MT

Maori MI

Marathi MR

Mongolian MN

Northern Sotho NSO

Norwegian NO

Polish PL

Portuguese PT

Punjabi PA

Quechua QU

Rhaeto-Romance RM

Romanian RO

Russian RU

Sami SE

Sanskrit SA

Scots Gaelic = Gaelic (Scotland)

Serbian SH-YU

Slovak SK

Slovenian SL

Sotho ST

Spanish ES

Syriac SYR

Swahili SW

Swedish SV

Tagalog TL





Two-letter Country Codes From ISO 3166

Tamil TA

Tatar TT

Telugu TE

Thai TH

Tsonga TS

Tswana TN

Turkish TR

Ukrainian UK

Urdu UR

Uzbek UZ

Vietnamese VI

Welsh Gaelic = Gaelic (Wales)

Xhosa XH

Zulu ZU

Algeria DZ

Argentina AR

Australia AU

Austria AT

Azerbaijan AZ

Bahrain BH

Belgium BE

Bolivia BO

Brazil BR

Canada CA

Caribbean CB





A-1

Chile CL

China CN

Colombia CO

Costa Rica CR

Croatia (Hrvatska) HR

Dominican Republic DO

Ecuador EC

Egypt EG

El Salvador SV

Finland FI

France FR

Germany DE

Guatemala GT

Honduras HN

Hongkong HK

Indonesia

Iraq

ID

IQ

Ireland IE

Israel IL

Italy IT

Jamaica JM

Johab JH

Jordan JO

Korea KR

Kuwait KW

Lebanon LB

Libyan Arab Jamahriya LY

Liechtenstein LI





Luxembourg LU

Malaysia MY

Malta MT

Mexico MX

Modern EM

Moldova MD

Morocco MA

Netherlands NL

New Zealand NZ

Nicaragua NI

Norway (Bokmal) NO

Norway (Nynorsk) NY

Oman OM

Panama PA

Paraguay PY

Peru PE

Philippines PH

Portugal PT

Puerto Rico PR

Qatar QA

Reunion RE

Romania RO

Russia RU

Saudi Arabia SA

Scotland CT

Singapore SG

South Africa ZA

Spain ES





A-1

Sweden SE

Switzerland CH

Syrian Arab Republic SY

Taiwan TW

Trinidad TT

Tunisia TN

United Arab Emirates AE

United Kingdom GB

United States US

Uruguay UY

Venezuela VE

Vietnam VN

Wales WA

Yemen YE




Glossary-

A

Access rightsThe rights of a user or group of users to

access, read, or write to, a translation

memory. Access rights for file-based

translation memories are defined in

Translator’s Workbench; access rights for

server-based translation memories aredefined in Server Manager.

AlignmentProcess of building a translation memory

from previously translated material.

WinAlign is the alignment tool.

AnalysisFeature in Translator’s Workbench that

allows you to assess the number of

translation matches in a document for

translation by comparing the document to

an existing translation memory.

Ancil lary f i leTradosTag, RTF or text-only file that is

generated during the conversion of

MIF/IASCII documents to STF using the

S-Taggers. The ancillary file contains shared

text that cannot be accessed in the STF file

but requires translation.

ANSIANSI (American National Standards

Institute) a character set used by Windows. It

is a collection of special characters and

associated codes adopted by the ANSI

standards organization. The ANSI character

set includes many foreign characters, special

punctuation, and business symbols.

ASCIIASCII (American Standard Code for

Information Interchange) is a character set

which represents English characters as

numbers, with each letter assigned a

number from 0 to 127. For example, the

ASCII code for uppercase M is 77. Most

computers use ASCII codes to represent

text, which makes it possible to transfer data

from one computer to another.

AttributeAn unordered set of key-value bindings for

an element in an SGML, HTML, or XML

document tree.

B

Batch processingThe practice of processing multiple files at

one time. The Analyse, Translate and Clean

Up utilities in Translator’s Workbench can

be used to process files individually or in

batches. For this reason, they are known as

batch tools.

GLOSSARY



G

Glossary-2FILE FORMATS REFERENCE GUIDE

Bi-directionalRefers to those languages that have a right-

to-left reading order, visual appearance and

alignment. Arabic and Hebrew are bi-

directional languages.

Book f i leUsed by FrameMaker and Interleaf to

assemble any number of documents into a

unified document with continuous page,

figure, and list numbering. A book file

allows you to graphically see and manage the

organization of documents within it. This

organization can include generating files

like table of contents and an index, andassigning page numbering.

C

Cal loutCaption that appears beside a graphic,

explaining items in the graphic.

Catalog f i leInterleaf allows you to set up the styles for a

document or set of documents in one file

which can then be imported into all

following documents. A catalog is a type of

style sheet.

CAT fi leFile created by S-Tagger for Interleaf from

catalog files.

Character setA character set is a defined list of characters

recognized by computer hardware and

software. Each character is represented by a

number.

See also ANSI, ASCII.

Character sty leFont attribute (typeface, size, bold, italic) that

can be given a character style and applied to

individual or sets of characters.

In Interleaf, character style formatting can

be applied through the use of inline

components.

Clean upFeature in Translator’s Workbench that

removes source segments from translated

documents. The source segments have been

stored in the translated document during the

translation process. The clean up feature

also allows you to update the translation

memory in accordance with the latest

changes in the target files.

Client computerComputer in a network that hosts a front-

end application, which accesses a server to

obtain data (information, files, application

data). The client interface (GUI) is the point

at which the user interacts with the system.

Client/serverComputer system architecture in which

clients request a service and a server provides

that service. The SDL Trados translation

solution can be deployed as a client/server

system in a multi-user environment.

CMP fi leFile generated by the S-Tagger verification

feature. It details all errors, alerts andwarnings about tag changes in the target file.

Also known as the verifier report.

G


Glossary-

ConcordanceFeature in Translator’s Workbench that

allows you to search the translation memory

for text fragments during interactive

translation. The Concordance tab in theTranslation Memory Options dialog box in

Translator’s Workbench defines the

parameters for concordance searching.

Customize veri f icationSettings that allow you to suppress certain

alerts and warnings during the verification

process. These settings are available in the

S-Taggers and in the S-Tag Verifier plug-in

in TagEditor. When you select to suppressmessages relating to a particular tag, any

alerts or warnings referring to that tag are

suppressed in the verifier report or Message

pane.

D

Database server

The back end in a client/server installation of the SDL Trados translation solution. This is

where all server-based translation memories

are stored.

DBCSDouble-byte Character Set. DBCS languages

such as Japanese, Korean and Chinese

require special DBCS fonts.

Demo modeCertain SDL Trados applications can be used

in demonstration mode when the necessary

license information is not available. When

an application is running in demo mode, file

size limitations and feature restrictions may

apply.

DTDDocument Type Definition. An ASCII file

that defines the structure, elements and

conventions to which an SGML, XML or

HTML document must conform. The DTDfile is separate from the document it defines.

An example of a widely used DTD is the

HTML 4.0 DTD; all HTML 4.0 documents

are based on this DTD.

DTPDesktop Publishing.

E

ElementA type of node in an SGML, HTML, or XML

document tree. An SGML element is

typically represented by a start tag ("")

and an end tag (""). The start tag can

contain attributes. Both the start tag and end

tag for an element typically contain the "tag

name" for that element. In XML, an element

is always represented either by an explicitstart tag and end tag, or by an empty element

tag.

Excel f i l terSDL Trados filter component that converts

Excel documents (XLS, XLT) to and from

TradosTag (TTX). The Workbench batch

tools and the TagEditor editing environment

provide direct support for Excel documents

by automatically converting them to

TradosTag.

Extended charactersAccented letters and symbols which do not

appear in the standard ASCII character set,

for example, ‘à’ or ‘é’.



G


External tagTag type used in tagged text files to store

structural information. Paragraph styles,

anchored frames and tables are usually

represented as external tags. During thetranslation process, external tags are treated

differently to internal tags.

F

Font Mapper for FrameMakerFont Mapper for FrameMaker facilitates

changing the fonts in FrameMaker MIF

documents translated into or from Asianlanguages. Font Mapper for FrameMaker

maps, or replaces, the fonts in the original

document with fonts that you specify.

Font Mapper for Interleaf Font Mapper for Interleaf facilitates

changing the fonts in Interleaf ASCII

documents translated into or from Japanese.

It maps, or replaces, the fonts in the original

document with fonts that you specify.

FrameMakerFrameMaker is a powerful desktop

publishing and book-building package from

Adobe. It runs on several platforms; UNIX,

Macintosh and Windows.

See also S-Tagger for FrameMaker.

Fuzzy match

One of five match types identified byTranslator’s Workbench. A fuzzy match

indicates that a similar, but not identical,

match to the source segment has been found

in the translation memory.

H

Hard return

Manual line break or a non-breakingcarriage return. When you want a new

paragraph to begin, but do not want to incur

paragraph attributes or the end of previous

paragraph attributes, you insert a hard

return.

Hard returns are also known as forced

returns in FrameMaker.

HTMLHypertext Markup Language. HTML is the

authoring language used to create

documents on the World Wide Web. HTML

is similar to SGML, although it is not a strict

subset. HTML defines the structure and

layout of a Web document by using a variety

of tags and attributes.

I

IASCIIInterleaf ASCII. IASCII is a text file format

which allows you to exchange information

between Interleaf and other applications. All

formatting, file and page layout is retained in

the IASCII file.

InDesignDesktop publishing package from Adobe.

SDL Trados supports tagged text files fromInDesign 2.0 or later.

See also Story Collectors.



G


Glossary-

Index markerIndex entries are stored in index markers.

The cursor is placed at the point in the text

where you want an index entry to be

referenced to and the text is typed into theindex marker. In STF files, index markers

are moved to the ends of the paragraphs they

were originally contained in.

Interleaf A desktop publishing package from

BroadVision, which has some similar

features to FrameMaker. The STF produced

from Interleaf files is similar to the STF

produced from FrameMaker files. Interleaf runs on several platforms; UNIX, DOS and

Windows.

See also S-Tagger for Interleaf.

Internal tagTag type used in tagged text files to store

formatting commands that do not affect the

overall structure of the file. Character styles,

variables special characters, and non-

breaking spaces are represented as internal

tags. During the translation process, internal

tags are treated differently to external tags.

L

LANLocal area network. A computer network that

spans a relatively small area. LAN computers

are usually linked to each other via Ethernet

connections. The SDL Trados translation

solution can be deployed as a client/server

system on a LAN.

See also WAN.

License f i leFile that contains information about your

SDL Trados license. In order to run SDL

Trados software in comprehensive mode on

your computer, you must provide thenecessary license information by locating

the relevant license file or attaching a dongle

to the parallel or USB port.

See also Demo mode.

M

MiddlewareIn a client/server architecture, the

middleware sits between the client

components and the back-end database

server. The main purpose of the middleware

is to facilitate successful communication

between the database server and its clients.

TM Server acts as the middleware in a

client/server implementation of the SDL

Trados translation solution.

See also TM Server.

MIFMaker Interchange Format, a text format

used by FrameMaker which allows you to

exchange information between FrameMaker

and other applications. All formatting and

page layout information is retained in the

MIF document.

Modif ier keyThe modifier keys are [Ctrl], [Alt] and [Shift]

or a combination of the three. When pressed

with the correct hotkey, they allow access to

a menu item or dialog box control.



G


MultiTermSDL terminology management system.

MultiTerm exists as a client/server system

(MultiTerm 2007) and as a desktop

application (MultiTerm Workstation). Themain user interface for both versions of the

system is called MultiTerm. Both versions of

the MultiTerm system are integrated with

Translator’s Workbench to provide term

recognition during translation.

See also Term recognition.

MultiTerm ExtractSDL terminology application for extracting

terms from documents. MultiTerm Extract

extracts terms and presents them in an easy-

to-use interface for validation and export.

Terminology data can be exported directly

from MultiTerm Extract to local and remote

MultiTerm termbases.

MultiTerm 2007Client/server version of the SDL

terminology management system. In

MultiTerm 2007, termbase data can be

stored locally or, in a multi-user setup, on a

network database server. The main client

interface for MultiTerm 2007 is called

MultiTerm.

O

ORG fi leFile containing structural information forthe conversion of STF files to original format

using the S-Taggers. The S-Taggers produce

an ORG file for each MIF/IASCII file that is

converted to STF. The ORG file is used to

convert the translated STF file back to its

original MIF/IASCII format.

P

Page breakIn Interleaf and FrameMaker, you can set up

a component/paragraph style so that it

always starts at the top of a page or always

stays with the following paragraph. Most

documents will contain some

components/paragraph styles whose

pagination attributes are overridden, for

example, when a forced page break has to be

inserted.

PageMakerDesktop publishing package from Adobe.

SDL Trados supports tagged text files from

PageMaker version 6.5 or later.


Paragraph StyleUsed with FrameMaker, paragraph style

properties, such as indents, line spacing, tab

stops, font attributes (typeface, size or color),

pagination, hyphenation and word spacing,are all assigned within the Paragraph

Designer.

In Interleaf, paragraph styles are known as

components and the style properties are

assigned within the component’s master

property sheet.

PlaceablePart of a segment that has been identified as

a non-text item in Translator’s Workbench,

for example a number or a hyperlink.

Placeables do not require translation but

must be placed in the correct location in the

target segment.



G


Glossary-

PowerPoint f i l terSDL Trados filter component that converts

PowerPoint documents (PPT, PPS, POT) to

and from TradosTag (TTX). The Workbench

batch tools and the TagEditor editingenvironment provide direct support for

PowerPoint documents by automatically

converting them to TradosTag.

Pre-translationProcess of pre-translating multiple files

using the Translate command in

Translator’s Workbench to extract data from

a particular translation memory.

Translator’s Workbench automaticallyinserts matches from the translation

memory into the document for translation.

Public entity setA standardized set of character entities.

Typically, a character entity represents a

special character not available in the ASCII

character set. For example, the public entity

set ISO Added Latin 1 contains

representations for all umlaut and accentedcharacters, as used in Western European

alphabets.

Q

QuarkXPressDesktop publishing package from Quark.


QuarkXPress version 4.1 or later.


R

RC f i l terA filter used to convert resource files into the

TTX format.

Read-onlyInterleaf allows you to apply a read-only

property to any component or

subcomponent. Components with read-only

properties assigned to them cannot be editedin any way in the Interleaf file. S-Tagger for

Interleaf allows you to choose whether or not

these components are to be treated as

translatable text.

Repeti t ion matchOne of five match types identified by

Translator’s Workbench. A repetition match

is defined as any match that occurs more

than once in a document for translation. Thefirst time a segment occurs in a document, it

is counted as a 100% match, a fuzzy match

or a no match. The next time the same

segment occurs, it is counted as a repetition

match.

RTFRich Text Format. This is an interchange file

format invented by Microsoft.

See also Workbench RTF.

S

Server computerA computer on which server software is

installed.

SGMLStandard Generalized Markup Language, alanguage used for designing tagged text

formats.

Shift - J ISA standard for Japanese character encoding,

used mainly under Windows and

Macintosh.



G


Smart quotesCurly left and right quotation marks instead

of straight quotation marks. Smart quotes

can have different formats, depending on the

language they are used in; for example,German smart quotes are different to

English smart quotes.

Special charactersSymbols like ‘®’, ‘™’, ‘©’, as well as accented

characters such as á and ì. Special characters

and symbols must be inserted into the STF

file using the Alt keyboard sequence. They

may not be inserted using the Insert Symbol

command in Microsoft Word for Windows.

S-Tagger for FrameMakerSDL Trados conversion solution for

FrameMaker. S-Tagger for FrameMaker

converts MIF files to STF. All FrameMaker

page layouts and character formatting are

preserved during translation. S-Tagger for

FrameMaker supports MIF files from all

platforms supported by FrameMaker and

from FrameMaker versions 4.0 or later.

S-Tagger for Interleaf SDL Trados conversion solution for

Interleaf. S-Tagger for Interleaf converts

Interleaf ASCII files to STF. All Interleaf

page layouts and character formatting are

preserved during translation. S-Tagger for

Interleaf supports IASCII files from all

Interleaf platforms and from Interleaf

version 5.2 or later.

S-TagsBrief coded statements in STF files that

represent formatting in FrameMaker and

Interleaf documents. S-Tags are divided into

external tags and internal tags.

STF f i leFile produced when you convert

MIF/IASCII files to STF using the

S-Taggers. Formatting from the

FrameMaker/Interleaf documents isrepresented by brief coded statements

(S-Tags). STF files are translated using

Translator’s Workbench in the TagEditor or

Microsoft Word editing environments.

STF f i le formatWhen using the S-Taggers to convert

FrameMaker (MIF) and Interleaf (IASCII)

files to STF, you choose the file format of the

STF files. They can be saved in TTX(TradosTag), RTF (Rich Text Format) or as

ANSI text.

Story Col lectorsSDL Trados provides Story Collectors for the

most widely-used desktop publishing (DTP)

packages – InDesign, QuarkXPress and

PageMaker. Each Story Collector facilitates

the export of tagged text from DTP files and

the subsequent re-import of text aftertranslation.

Stopword ListA language specific list that contains articles,

pronouns, prepositions, conjunctions and

some frequent adjectives and adverbs. These

words are disregarded as potential term

candidates. MultiTerm Extract ships with

stopword lists for the major languages. You

can customize existing stopword list or add

your own.



G


Glossary-

T

TagEditor

SDL Trados translation editor for tagged textformats including HTML, SGML, XML, STF

(Workbench RTF and TradosTag); DTP file

formats including InDesign, QuarkXPress,

PageMaker and Ventura; and Microsoft

formats including PowerPoint and Excel.

TagEditor also includes the Tag Settings

Manager, tag verification and spelling

checker plug-ins.

Tag Settings Fi leDocument that contains information

necessary for processing documents that

conform to a particular DTD. For example,

SDL Trados requires a tag settings file to

process and format HTML, SGML, and XML

documents for translation purposes. tag

settings files (also known as initialization

files) have the extension *.ini.

Tag Settings ManagerThe Tag Settings Manager is used to managethe tag settings files that are available on

your file system. The Tag Settings Manager

provides access to the Tag Settings Wizard

where you can create and edit tag settings

files. You can access both the manager and

the wizard from TagEditor, WinAlign,

Translator’s Workbench and LM Studio.

TeamWorks Manager

TeamWorks Manager is an administrativetool for the TeamWorks system that is used

to configure server components and define

system-wide settings. TeamWorks Manager

can run independently or it can be hosted

within the SDL Trados Server Manager.

Term recognit ionFeature in Translator’s Workbench that

makes use of the interface between

Translator’s Workbench and MultiTerm.

When you activate term recognition, termsstored in the selected MultiTerm termbase

are automatically suggested to you during

translation.

TermbaseDatabase used to store terminology and

related information.

TM Anywhere

In a client/server implementation of the SDLTrados translation solution, TM Anywhere

is a web server application that enables

TM Server to communicate with

Translator’s Workbench using an Internet

connection.

TM ServerMiddleware component in a client/server

implementation of the SDL Trados

translation solution. TM Server is

responsible for all communication between

the server-based translation memory and

clients of the system, including Translator’s

Workbench and SDL Trados Server

Manager. Translator’s Workbench can

communicate with TM Server using an

intranet or an Internet connection. The

Internet connection type is only available if

TM Anywhere is installed as part of the

system.

SDL GXTGlobalization management system for

enterprise translations integrating best

practice workflow with the proven ability of

the SDL Trados desktop translation solution.



G


Server ManagerServer Manager is the administration client

for a client/server implementation of the

SDL Trados translation solution. It

comprises two separate modules: TMManager and User Manager.

TM Manager is used to configure TM Server

and related components, to create server-

based translation memories, and to import

and export translation memory data. User

Manager is required for user management

and the definition of access rights within the

TM Server and – where applicable –

TeamWorks systems.

See also TM Server.

SDL TeamWorksSDL TeamWorks is a scalable, highly flexible

translation solution. It facilitates translation

project workflow management in a

distributed environment. It allows you to

manage all your translation projects, people,

resources and files efficiently and flexibly.

The main client interface for theTeamWorks system is called TeamWorks.

TM ServerTM Server is a client/server implementation

of the SDL Trados translation solution. It

allows you to create server-based translation

memories where all data is stored on a

remote database server in your network

environment. This contrasts with file-based

translation memories, where data is storedin a group of files on your system.

TradosTagAn XML-based file format for representing

tagged text and bilingual data. TradosTag

(TTX) provides a standard method for

processing XML, HTML, SGML, PPT, XLSand DTP file formats and replaces BIF as the

file format for bilingual documents in SDL

Trados 2006.

TradosTag is one of the STF file format

options that you can select in the S-Taggers.

Translation memoryDatabase of segment or sentence pairs. Each

source language segment is paired with its

corresponding target language segment.

Translator’s WorkbenchTranslation memory database and

management system with document

analysis, pre-translation and clean up

features. Translator's Workbench can be

used in conjunction with a variety of editing

environments including Microsoft Word

and TagEditor. Translator's Workbench is

also integrated with the MultiTerm

terminology management system for the

purposes of term recognition during

translation.

TTXSee also TradosTag.

T-Windows for Cl ipboardEditor for translating Clipboard files.



G


Glossary-1

V

Val idation

In TagEditor, validation refers to the processof validating an XML document after

translation using the XML Validator plug-in.

VenturaDesktop publishing package from Corel.


Ventura version 5 or later.

Veri f icationRefers to the comparison of tags in the target

file with tags in the source file. During and

after translation, translators should verify

that they have placed all the tags in the

translated files in the correct sequence and

position.

All tagged text files can be verified using the

verification plug-ins in TagEditor. In

addition, STF files can be verified using the

verification feature in the S-Taggers.

Verification plug-inSDL Trados verification plug-ins provide

advanced tag verification functionality for

whole documents that have been translated

in TagEditor. Verification plug-ins include

the Generic Tag Verifier, the XML Validator

and the S-Tag Verifier.

W

WAN

Wide area network. A computer networkthat spans a relatively large geographical

area. Typically, a WAN consists of two or

more local-area networks (LANs). The

largest WAN in existence is the Internet.

See also LAN.

WarningMessage which is generated during tag

verification in TagEditor or the S-Taggers.

Certain warnings may be suppressed during

the verification process by customizing the

verifier report. Warnings identify changes in

tags which do not affect the structure of the

file, only the formatting of the text within the

file. Warnings do not prevent backward

conversion of the target file but should be

checked in order to avoid undesirable effects

in the finished document.

WinAlignSDL Trados visual alignment tool that allows

you to create translation memory import

files from previously translated source and

target texts. WinAlign also includes the Tag

Settings Manager.

Workbench RTFWorkbench RTF documents (also referred to

as tagged RTF documents) are files that

comply with the Translator’s Workbenchstandard for tagged RTF. These files contain

tags that have been marked up with the

tw4winExternal and tw4winInternal tag styles.

Workbench RTF is one of the STF file format

options that you can select in the S-Taggers.



G


X

XML

Extensible Markup Language. XML is asimple, very flexible text format subset of

SGML.

See also SGML.

XML Val idatorSDL Trados plug-in that allows you to

validate XML documents that have been

translated in TagEditor.

XPathA W3c standard that forms a set of syntax

rules for defining the parts of an XML

document. XPath is designed to be used by

XSLT, XPointer and other XML parsing

software. For more information, see

http://www.w3.org/TR/xpath.

http://www.w3.org/TR/xpath











I-

■AAdobe FrameMaker

see FrameMaker

Adobe InDesign

see InDesign

Adobe PageMaker

see PageMaker

Application Programming Interface (API)

QuarkXPress 5-2

■BBatch functions

InDesign

exporting stories 6-20

importing stories 6-22

setting the story order 6-18

QuarkXPress




bilingual target files

cleaning up

IASCII files 3-7

InDesign files 6-16

MIF files 3-7

ML files 2-33

PageMaker files 4-10

PowerPoint files 10-15

QuarkXPress files 5-12

RoboHelp files 8-25

RTF files 9-24

Ventura files 7-5

Word files 8-4, 9-3

Bookmark Handler macros 8-6

adding template 8-6

running 8-7

browsers 2-17, 2-18

■Ccharacter entities

converting 2-16

Clean Up command

Translator’s Workbench 2-34

comparing the TTX workflow to the RTF workflow 9-2

conditional markup language tags 2-23

conditional ML 2-23

conditional ML tags 2-23

Context TM 3-5

Cross-reference, PageMaker 4-12

■DDirectory structure

InDesign 6-11

PageMaker 4-6

QuarkXPress 5-7

DLG files 12-9

DLL files 12-2

Document layersPageMaker 4-13

Document type definition (DTD) 2-5

DTDtutorial on Tag Settings Wizard 2-8–2-18

■EExcel

filter 11-2

handling macros 11-5

preparing files 11-5

EXE files 12-2

executable files

EXE,DLL, OCX, and LNG files 12-2

Exporting stories

from InDesign 6-15

from PageMaker 4-9

INDEX



I

I-2FILE FORMATS REFERENCE GUIDE

from QuarkXPress 5-11

from Ventura 7-4

■FFile organization

InDesign 6-11

PageMaker 4-6

QuarkXPress 5-7

filter

Excel 11-2

Folder structure

InDesign 6-11

PageMaker 4-6

QuarkXPress 5-7

Font MappersFrameMaker 3-3

Interleaf 3-3

FONT tags 2-15

footnotes

in RTF Help files 8-17–8-19

translating in Word 8-10

FrameMaker

preparing MIF files for conversion 3-5

translating 3-6

using Font Mappers 3-3

■GGeneric Delimited Text files 14-2

Generic Tag Verifier 2-33

Graphics

replacing references with placeables 8-20–8-21

■HHTML

previewing within TagEditor 2-17, 2-18

HTML files

translating 2-31

■IIASCII files 3-3

cleaning up bilingual target files 3-7Importing stories

InDesign 6-17

PageMaker 4-11

QuarkXPress 5-13

InDesign

cleaning up bilingual target files 6-16

directory structure 6-11

story order 6-12

Index entry, PageMaker 4-12

Inline graphicsInDesign 6-7

PageMaker 4-13

QuarkXPress 5-7

Installation

Story Collector for InDesign 6-8

Story Collector for PageMaker 4-4

Story Collector for QuarkXPress 5-5

Interleaf

preparing IASCII files for conversion 3-5

translating 3-6

using Font Mappers 3-3

Internet browsers 2-17, 2-18

Internet Explorer 2-17, 2-18

■JJapanese PageMaker version 6.5 and 7

character support 4-14

Java properties files 12-18

jumps 8-24

■LLNG files 12-2

Local overrides in Word 8-5

localizing 12-18

localizing resource files using SDL Trados 12-9, 16-2



I


I-

■MMacros

handling macros in Excel files 11-5macros

Bookmark Handler 8-6

Bookmark Handler template 8-6

PrepareBookmarks 8-6

RestoreBookmarks 8-6

Master page, PageMaker

exporting 4-13

META tags 2-15

Microsoft Excel

see Excel

Microsoft PowerPoint

see PowerPoint

Microsoft Wordsee Word

MIF files 3-3


ML files 2-5

ASCX 2-2

ASP, 2-2

ASP.NET 2-2

ASPX 2-2


DTD 2-3

format 2-2

HTML 2-2, 2-3INC 2-2

JSP 2-2

PHP 2-2

preparation 2-5

Save Target As 2-33

SGML 2-2, 2-3

tag settings 2-3, 2-5

translating 2-4, 2-31

XML 2-2, 2-3

MultiDoc Pro from Citec 2-17

Multiple files

InDesign 6-18

QuarkXPress 5-14

■NNetscape Navigator/Communicator 2-17, 2-18

■OOCX files 12-2

OpeningStory Collector for InDesign 6-12



opening QuarkXpress files using SDLXtract. 5-4

■PPageMaker


creating a folder structure 4-6

cross-references 4-12


exporting master pages 4-13


index entry 4-12

installing Story Collector 4-4

Japanese version 6.5 and 7character support 4-14

exporting and importing 4-14

preparing files 4-5

preparing PageMaker 7 files 4-5

tag error 4-13

translation process 4-10

troubleshooting 4-12

Paragraph style, Word

local overrides 8-5

Placeables

graphics references as 8-20–8-21

internal character styles for Help files 8-20

Plug-in




popups 8-24

PowerPoint

cleaning up bilingual target files 10-15filter 10-5

translating files 10-11–10-14

understanding the conversion process 10-5

PrepareBookmarks macro 8-6

previewing ML files in an external viewer 2-17



I

I-4FILE FORMATS REFERENCE GUIDE

■Q QuarkXPress

batch export 5-15, 6-20batch functions 5-14



inline graphics 5-7

multiple page spreads 5-10, 6-15

preparing files 5-7

Story Collector 5-2

story order 5-9

story order for multiple files 5-14

■RRC files 12-9

RC Filter 12-9, 12-18

Replace command

Translator’s Workbench 2-34

Resource files 12-9, 16-2

resource files

RC andDLG files 12-9, 12-18

RestoreBookmarks macro 8-6

RoboHelp files


translating 8-25

RTF Files

Windows help files 8-15

RTF Help files

character styles for non-translatable text 8-20


context ID 8-17

custom footnotes 8-16

describing 8-15

footnotes 8-23

footnotes in Word 8-17–8-19

graphics references as placeables 8-20

hidden text 8-16, 8-17

jumps 8-16, 8-17, 8-24

paragraph styles 8-17

popups 8-16, 8-17, 8-24

preparing files for translation 8-17–8-21

segmentation rules 8-18

spell-checking and proofreading 8-25

translating 8-23

tw4winJump and tw4winPopup styles 8-17

■SSave Bilingual As command

Translator’s Workbench 2-34Save Target As

ML files 2-33

SDL Generic Delimited Filter 14-2, 15-2

SDL Trados RC File Verifier 12-16

SDL Trados Win32Binary Verifier 12-7

SDLX files 13-1

Segmentation rulestranslation memory

setting options for help files 8-18

Translator’s Workbenchadding new 8-18

changing, for keyword translation 8-18SGML

previewing in external browser 2-17

Tag Settings Wizard in TagEditor 2-8–2-18

SGML files

translating 2-31

Source directory

INDD 6-20

ISC 6-20

P65/PMD 4-9

QSC 5-11

QXD 5-11

TXT 4-9

spell-checking and proofreading 8-25

S-Taggers

defining 3-3

for FrameMaker 3-2

for Interleaf 3-2

installing 3-2

preparing FrameMaker files for conversion 3-5

preparing Interleaf files for conversion 3-5

using 3-3

STF files 3-3

Stories

exporting from InDesign 6-15

multiple files 6-20exporting from PageMaker 4-9

exporting from QuarkXPress 5-11

multiple files 5-15

importing from InDesign 6-17

multiple files 6-22

importing into PageMaker 4-11

importing into QuarkXPress 5-13

multiple files 5-17

Story Collector for InDesign

accessing help 6-9



I

batch functions 6-18

creating a folder structure 6-11

describing 6-6


exporting stories from multiple files 6-20

importing multiple files 6-22


installing 6-8

opening 6-12

preparing files 6-10

sample files 6-9

setting story order 6-12

story order for multiple files 6-18

tag reference 6-24–6-50

translating 6-16

Story Collector for PageMaker

describing 4-2

exporting 4-9

importing translated text 4-11

installing 4-4

opening 4-7

preparing files 4-5

preparing PageMaker 7 files 4-5



troubleshooting 4-12

verifying the tagged text output 4-9


installing 5-5

Japanese version 4.1 5-6

opening 5-8

setting up a folder structure 5-7


Story order 5-9, 6-13

Custom 5-9, 6-13

Left-right 5-9, 6-13

PageMaker 4-2

setting for multiple files in InDesign 6-18

setting for multiple files in QuarkXPress 5-14

setting in InDesign 6-12

setting in QuarkXPress 5-9

Top-down 5-9, 6-13

supported browsers 2-17, 2-18

Supported Languages and Locales A-2

Unicode-only A-7

■TTag Settings

tutorial on Tag Settings Wizard 2-8–2-18Tag settings file

.NET RESX files 2-6

default DITA settings 2-6

default HTML settings 2-6

default SVG settings 2-6

default XLIFF settings 2-6

default XSL settings 2-6

tag settings file

creating 2-8

editing 2-19

managing 2-7

overview 2-5

Tag Settings Manageropening 2-7

Tag Settings Properties 2-19

Tag Settings Wizard

tutorial 2-8–2-18

TagEditor

Internet browsers 2-17, 2-18

previewing files in an external application 2-17

Tag Settings Wizard 2-8–2-18

translation guidelines 2-31

Tagged text files

verifying 2-33

Textimporting into Ventura 7-6

TRADOStagdescription 1-5

file components 1-7

PowerPoint

converting from 10-5

translating 13-1

FrameMaker files 3-6

HTML files 2-31

Interleaf files 3-6

Microsoft Word files 8-9, 9-16

ML files 2-31

PowerPoint files 10-11–10-14RTF Help files 8-23

SGML files 2-31


Ventura files 7-5

XML files 2-31

translating Word files in TagEditor 9-1

translation memorysegmentation rules 8-18

setting options for help files 8-18