SDL Trados 2007 Suite - File Formats Reference Guide

(1)

File Formats

Reference

Guide

(2)

COPYRIGHT

FILE FORMATS REFERENCE GUIDE

All trademarks are the property of their respective owners. The names of other companies and products mentioned herein may be the trademarks of their respective owners. Unless stated to the contrary, no association with any other company or product is intended or should be inferred.

Although SDL takes all reasonable measures to provide accurate and comprehensive information about the product, this guide is provided “as is” without warranty, either express or implied. This guide accompanies SDL Trados 2007. May 2008

(3)

FILE FORMATS REFERENCE GUIDE iii

Chapter 1 Introduction

About this Guide . . . 1-2 Audience Profile . . . 1-2 Related Documentation . . . 1-2 Accessing Documentation . . . 1-3 Key Term Definition . . . 1-3 Supported File Formats . . . 1-5 TradosTag Bilingual File Format . . . 1-5 Conclusion . . . 1-7

Chapter 2 HTML, XML, and SGML Files

Overview . . . 2-2 Supported ML File Formats . . . 2-2 Key Term Definition . . . 2-3 Translation Workflow . . . 2-4 Preparation . . . 2-5 What is a DTD? . . . 2-5 Managing Tag Settings . . . 2-7 Tutorial: Tag Settings Wizard . . . 2-8 Editing Tag Settings . . . 2-19 Using Conditional ML Tags in Tag Settings Files . . . 2-23 Translation . . . 2-31 Translating Files Using Conditional ML Tags . . . 2-32 Verifying Translated Files . . . 2-33 Cleaning Up Translated Files . . . 2-33 Post-translation Production . . . 2-34 Conclusion . . . 2-35

(4)

Chapter 3 FrameMaker and Interleaf/QuickSilver Files

Overview . . . 3-2 Key Term Definition . . . 3-2 Translation Workflow . . . 3-4 Preparation and Conversion . . . 3-5 The STF File Formats . . . 3-5 Translation . . . 3-6 Post-translation Production . . . 3-7 Conclusion . . . 3-8

Chapter 4 PageMaker Files

Overview . . . 4-2 Key Term Definition . . . 4-3 Translation Workflow . . . 4-3 Installing Story Collector for PageMaker . . . 4-4 Preparation and Export . . . 4-5 Creating a Folder Structure . . . 4-6 Opening Story Collector for PageMaker . . . 4-7 Setting the Story Order . . . 4-7 Exporting Stories . . . 4-9 Translation . . . 4-10 Post-translation Production . . . 4-11 Importing Translated Stories . . . 4-11 Troubleshooting . . . 4-12 Tips for Export . . . 4-12 Tips for Import . . . 4-13 Tips for Japanese PageMaker 6.5 and 7 . . . 4-14 Tag Reference Material . . . 4-14 Story Collector for PageMaker Tags . . . 4-14 Tags in PageMaker Tagged Text Files . . . 4-15 Conclusion . . . 4-22

(5)

FILE FORMATS REFERENCE GUIDE v

Chapter 5 QuarkXPress Files

Overview . . . 5-2 Using QuarkXPress 7.x . . . 5-2 How Story Collector for QuarkXPress Works . . . 5-2 XTG files . . . 5-4 Key Term Definition . . . 5-4 Translation Workflow . . . 5-5 Installing Story Collector for QuarkXPress . . . 5-5 Preparation and Export . . . 5-7 Creating a Folder Structure . . . 5-7 Opening Story Collector for QuarkXPress . . . 5-8 Setting the Story Order . . . 5-9 Exporting Stories . . . 5-11 Translation . . . 5-12 Post-translation Production . . . 5-13 Importing Translated Stories . . . 5-13 Batch Functions in Story Collector for QuarkXPress . . . 5-14 Setting the Story Order . . . 5-14 Exporting Stories . . . 5-15 Importing Stories . . . 5-17 Tag Reference Material . . . 5-19 Story Collector for QuarkXPress Tags . . . 5-19 Tags in QuarkXPress Tagged Text Files . . . 5-19 Conclusion . . . 5-26

Chapter 6 InDesign Files

Translating InDesign CS2/CS3 files . . . 6-2 Translating InDesign Files . . . 6-6 Overview . . . 6-6 Key Term Definition . . . 6-7 Translation Workflow . . . 6-8 Installing Story Collector for InDesign . . . 6-8 Preparation and Export . . . 6-10

Creating a Folder Structure . . . 6-11 Opening Story Collector for InDesign . . . 6-12 Setting the Story Order . . . 6-12 Exporting Stories . . . 6-15 Translation . . . 6-16

(6)

Post-translation Production . . . 6-17 Importing Translated Stories . . . 6-17 Batch Functions in Story Collector for InDesign . . . 6-18 Setting the Story Order . . . 6-18 Exporting Stories . . . 6-20 Importing Stories . . . 6-22 Tag Reference Material . . . 6-24 Story Collector for InDesign Tags . . . 6-24 Tags in InDesign Tagged Text Files . . . 6-24 Defining Java Virtual Machine Size filter settings . . . 6-51 Conclusion . . . 6-52

Chapter 7 Ventura Files

Overview . . . 7-2 Key Term Definition . . . 7-2 Translation Workflow . . . 7-2 Preparation and Export . . . 7-3 Creating a Folder Structure Organization . . . 7-3 Preparing the Text in Ventura Files . . . 7-4 Exporting Ventura Text . . . 7-4 Translation . . . 7-5 Post-translation Production . . . 7-6 Importing Ventura Text . . . 7-6 Tag Reference Material . . . 7-6 Conclusion . . . 7-11

Chapter 8 Word and RTF Help Files

Overview . . . 8-2 Key Term Definition . . . 8-2 Selecting a Workflow for Word Files . . . 8-3 Working with Microsoft Word Documents . . . 8-4 RTF Workflow . . . 8-4

(7)

FILE FORMATS REFERENCE GUIDE vii

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-23 Translating 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-2 TTX Workflow . . . 9-3 Preparation of Microsoft Word Files . . . 9-4 About the Conversion Process . . . 9-4 Setting the TTX Workflow Translation Memory Option . . . 9-5 Testing the TTX Workflow . . . 9-6 Word Document Preparation Tips . . . 9-6 Modifying the Word Filter Settings File . . . 9-11 Translation of Microsoft Word Files . . . 9-16

Understanding Tags . . . 9-16 Field Codes . . . 9-17 Headers and Footers . . . 9-20 Inserted Text . . . 9-21 Non-translatable Footnotes and Endnotes . . . 9-21 Tables . . . 9-23 RTF Help Translation Workflow . . . 9-24 Post-translation Production for Word Files . . . 9-25 Conclusion . . . 9-27

Chapter 10 Microsoft PowerPoint Documents

Overview . . . 10-2 Requirements . . . 10-2 Key Term Definition . . . 10-2 Translation Workflow . . . 10-4 Preparation . . . 10-5 About the Conversion Process . . . 10-5 Translation . . . 10-11

(8)

PowerPoint Documents during Translation . . . 10-11 After Translation . . . 10-14 Post-translation Production . . . 10-16 Conclusion . . . 10-16

Chapter 11 Microsoft Excel Documents

Overview . . . 11-2 Requirements . . . 11-2 Key Term Definition . . . 11-3 Translation Workflow . . . 11-4 Preparation . . . 11-5 Handling Macros in Excel Documents . . . 11-5 About the Conversion Process . . . 11-5 Translation . . . 11-11

Excel Documents during Translation . . . 11-11 After Translation . . . 11-14 Post-translation Production . . . 11-16 Conclusion . . . 11-17

Chapter 12 Translating Programming Files

Localizing Windows32 Binary Files . . . 12-2 Preparation . . . 12-3 Translation . . . 12-3 Previewing File Output . . . 12-6 Verifying Translated Files . . . 12-7 Cleaning Up Translated Files . . . 12-8 Localizing Resource Files . . . 12-9 Preparation . . . 12-12 Translation . . . 12-12 Previewing File Output . . . 12-15 Verifying Translated Files . . . 12-16 Cleaning Up Translated Files . . . 12-17 Localizing Java .properties Files . . . 12-18 Defining Java Virtual Machine Size filter settings . . . 12-22

(9)

FILE FORMATS REFERENCE GUIDE ix

Chapter 13 Translating SDLX Files

About Working with SDLX Documents . . . 13-2 Translation Memory . . . 13-2 SDLX Menu . . . 13-2 SDLX Toolbar . . . 13-3 TagEditor Toolbar . . . 13-3 Comments . . . 13-4 Confirming Segments . . . 13-4 SDLX>Confirm Translation . . . 13-5 SDLX> Confirm All Translations . . . 13-5 SDLX> Go To Next Unconfirmed Translation . . . 13-6 SDLX> Go To Previous Unconfirmed Translation . . . 13-6 SDLX> Open/Get Next Unconfirmed . . . 13-6 SDLX> Set/Close Next Unconfirmed Open/Get . . . 13-6 Cleaning 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-2 Supported Versions . . . 15-2 Supported File Types . . . 15-2 The SDL OpenOffice Filter Settings File . . . 15-2 Translation Workflow . . . 15-3 Previewing OpenOffice and StarOffice Files . . . 15-3 Defining Java Virtual Machine Size filter settings . . . 15-4

Chapter 16 Translating Text-based Files

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

Glossary

(10)

(11)

Chapter

I N T R O D U C T I O N

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

(12)

A b o u t t h i s G u i d e

1 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 during translation 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-post-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. Any chapters 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.

₁

FILE FORMATS REFERENCE GUIDE 1-3

Accessing Documentation

The full set of SDL Trados 2007 guides is available in PDF format: C in the Doc subfolder of your SDL Trados 2007 installation folder

C from Start > Programs > SDL International > SDL Trados 2007 > Documentation after installation of the software

C Some guides are also available from the Start view in SDL Trados Synergy. NOTE

D

Online Help is also available with each of the SDL Trados applications.

Sample Files

Sample files are included as part of your SDL Trados installation. These files are installed by default to the following location:

C:\Documents and Settings\All Users\Documents\SDL Trados\Samples.

In this guide, we use these sample files to demonstrate features that provide specific support for particular file formats. We recommend that you use the sample files to work your way through procedures and examples on your own computer.

Key Term Definition

This guide contains file format-specific information in the context of the translation process. Throughout this guide, we use the following key terms to describe the different stages in the translation process:

C Preparation – refers to any tasks or conversion carried out on source files to make them more easily translatable; for example, setting the story order for PageMaker, QuarkXPress and InDesign files, or removing comments from Microsoft Word files.

C Conversion – refers to converting files from one format to another. There is forward conversion and backward conversion.

C Forward conversion is the conversion of source files to an easily translatable file format: for example, converting ILDOC files to STF using the S-Tagger for Interleaf/QuickSilver. Forward conversion sometimes involves exporting text from source files.

C Backward conversion is the conversion of translated files back into their original format: for example, converting STF to MIF using the S-Tagger for FrameMaker. Backward conversion sometimes involves importing translated text into source files.

(14)

1

C Translation – refers to the process of changing source language text into target language text. C Post-translation production – refers to any tasks or conversion carried out on translated files to

to finalize them, for example, positioning inline graphics in InDesign and QuarkXPress files, repagination, or final DTP tasks.

C Workflow – used in this guide in the generic sense, that is, a linear sequence of related steps that accomplish a task, for example, the translation workflow consists of preparation, translation and post-translation production steps.

C File format – refers to a format for encoding information in a file. Each type of file has a different format, for example, DOC, RTF, FM, QXD.

C Bilingual file format – refers to files that contain both source and target language text as well as text segmentation delimiting marks, for example, TradosTag.

(15)

S u p p o r t e d F i l e F o r m a t s

₁

SUPPORTED FILE FORMATS

The file formats described in this guide are:

C Tagged text formats – HTM, HTML, JSP, ASP, ASPX, ASCX, INC, PHP, SGML, XML and XSL, including standardized XML formats, such as DITA, SVG, RESX etc.

C DTP formats – FrameMaker and FrameMaker + SGML tagged text format (MIF), InDesign Exchange XML format (INX), Interleaf and QuickSilver tagged text format (IASCII), Ventura tagged text format (TXT), PageMaker tagged text format (TXT), QuarkXPress tagged text format (QSC), and InDesign tagged text format (ISC).

C Microsoft Office formats – Microsoft Word, Microsoft RTF, Microsoft PowerPoint and Microsoft Excel.

C SDL Trados formats – TradosTag and Workbench RTF. C Windows executable files – EXE, DLL, OCX, and LNG. C Windows resource files – RC and DLG.

C SDLX translation documents – ITD. C Java Properties files.

C SDL Generic Delimited files. C OpenOffice and StarOffice files. C Generic text files.

C XLIFF files.

TRADOSTAG BILINGUAL FILE FORMAT

TradosTag provides a standard method of describing tagged text formats and bilingual data for translation purposes. During conversion to TradosTag, translatable text and formatting information are extracted from the native file format and presented in an abstracted file format called TradosTag. During translation, the TradosTag file stores all the necessary bilingual data, including source and target language data and segment delimiting marks. After translation the TradosTag file is merged with the native file to create a translated document.

TradosTag files are XML-compliant and consist of well-formed XML documents that can be processed without explicit reference to a Document Type Definition (DTD).

(16)

T r a d o s T a g B i l i n g u a l F i l e F o r m a t

1 Converting to TradosTag

Tagged text formats that are automatically converted to TradosTag during pre-translation and translation include XML, HTML, SGML, PowerPoint, Excel, Word, and DTP file formats such as InDesign, QuarkXPress, PageMaker and Ventura. FrameMaker and Interleaf/QuickSilver documents can be converted directly to TradosTag or Workbench RTF using the S-Tagger conversion tools. The resulting STF files can be processed in either format; in addition, STF files in Workbench RTF format can be converted to TradosTag during pre-translation in Translator’s Workbench. Word documents (DOC, RTF) cannot be converted to TradosTag.

NOTE

D

If you are using SDL Trados Synergy, your files are automatically converted to TradosTag for you.

Why TradosTag?

Creating one file format for all tagged text formats has several advantages:

C The learning curve for translators is greatly reduced allowing them to focus on translation without having to worry about how the native applications work.

C The translation process is standardized as the same translation process applies to all tagged text formats.

C The prospect of cross-format leveraging increases as the translation memory stores similar tags for different formats.

C TradosTag is Unicode-based and therefore supports all languages supported by Translator’s Workbench.

C TradosTag the standard for all tagged text formats. FOR MORE INFORMATION

V

The TradosTag Application Programming Interface (API) facilitates third party customization, including filter creation for custom file formats not currently supported by SDL Trados. For more details about the TradosTag API, contact SDL Consultancy at your local SDL office.

(17)

C o n c l u s i o n

₁

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.

(18)

C o n c l u s i o n

1

(19)

Chapter

H T M L , X M L , A N D S G M L F I L E S

This chapter explains how to work with ML files. Sections include:

C HTML, XML and SGML translation workflow C Preparing HTML, XML, SGML files for translation C Creating and editing tag settings files with the

Tag Settings Wizard

C Post-translation production tips NOTE

D

If you are working with SDL Trados Synergy, only the part of this chapter about creating and editing tag settings and translating ML files (pages 2-4 to 2-32) is relevant to you.

(20)

O v e r v i e w

2 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.

NOTE

D

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

Supported ML File Formats

SDL 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 Active Server Pages (ASP), Active Server.NET (ASP.NET), ASP.NET (ASPX and ASCX), Java Server Pages (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 supported as long as the file includes the XML declaration, <?xml version='1.0'...?>, and the extension does 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 tag settings file. See Predefined Tag Settings on page 2-6 for more information about using INI files.

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.

(21)

O v e r v i e w

₂

Key Term Definition

The following terms occur frequently in this chapter:

C XML – Extensible Markup Language. XML is a metalanguage, which enables a general availability and interchange of information that is structured according to its content. Both DTD and schema-based XML formats are supported.

C SGML – Standard Generalized Markup Language. SGML is a powerful metalanguage for defining and standardizing the structure of documents. It also describes a grammar which you 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 it can be published on the Internet and viewed with a browser. Its most distinguishing feature is the hypertext, which means pages can be linked to anything else on the Internet.

C DTD – 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 to which a document must conform. A DTD is separate from the HTML, SGML, or XML document itself.

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

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

(22)

O v e r v i e w

2 Translation Workflow

Translation of HTML, XML, and SGML files 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 the necessary tag settings file(s). For more information, see “Tutorial: Tag Settings Wizard” on page 2-8.

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

4 Analyse and pre-translate the files for translation in Translator’s Workbench, using the Analyse and Translate batch tools.

5 Translate your HTML, XML, and SGML files in TagEditor.

6 Verify the tag content of target files using the verification plug-ins in TagEditor. 7 Save the target files in TradosTag (TTX) bilingual format, using the Save Bilingual As

command in TagEditor.

8 Clean up the translated files using the Clean Up command in Translator’s Workbench. 9 Open the translated HTML, XML, and SGML files in your browser, editing, or

(23)

P r e p a r a t i o n

₂

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.

(24)

2

NOTE

D

The Tag Settings Manager is shared by Synergy, Translator’s Workbench, TagEditor and WinAlign. The changes that you make to the Tag Settings Manager list from one of these applications will affect the list as viewed from the other applications.

Predefined Tag Settings

SDL Trados ships with a series of built-in files that contain predefined tag settings for certain document types. These files are as follows:

C HTML4.ini – suitable for processing all HTML/ASP documents that are based on the

HTML 4.0 DTD and have the root element HTML.

C XSL.ini – suitable for processing XSL documents that have the root element xsl:stylesheet. XSL is a particular type of XML.

C RESX.ini – suitable for processing .NET RESX files that have the root element RESX.

C XLIFF.ini – suitable for processing XML Localization Interchange File Format files that have

the root element XLIFF.

C DITA.ini – suitable for processing Darwin Information Typing Architecture XML files that have the root element DITA.

C SVG.ini – suitable for processing Scalable Vector Graphics XML files.

C Flash MX 2004.ini – suitable for processing Flash MX 2004 files.

C Visio.ini – suitable for processing Visio files.

Built-in tag settings files are stored in the following location by default

C:\Documents and Settings\All Users\Application Data\SDL International\Filters. You can create copies of and modify these files as required.

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.

Using Tag Settings Files

(25)

₂

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. NOTE

D

Although TagEditor is used to describe the steps below, the Tag Settings Manager is equally accessible 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 launch TagEditor.

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 using the 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 ships with software) using the Tag Settings Wizard. For more information, see “Editing Tag Settings” on page 2-19.

(26)

2 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 from Synergy, 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 defines

rules for writing letters in SGML. In normal circumstances, you may have to contact the originator of the DTD to obtain a copy.

C A sample letter written in SGML that makes use of this DTD, Letter.sgm. NOTE

D

There is also a sample letter written in XML that makes use of this DTD, Letter.xml. This tutorial uses the SGML file, but you can use the XML file to work through it. Letter.xml is located in

C:\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.

(27)

₂

Review the text on the first page of the wizard and click Next.

2 The Settings Name and Type page is displayed. On this page, you specify the general tag settings.

C Specify the Settings name you want to use (in our example, Sample Letter). This will be the descriptive name used to identify the INI file. It is displayed under Descriptive Name in the Tag Settings Manager.

C Select the type of settings you want to create. You can choose one of the following options: C New Settings for XML

C New Settings for SGML/HTML C Base on predefined HTML 4.0 settings C Base on predefined XSL settings

For this example, select New Settings for SGML/HTML. C Click Next.

(28)

2

3 The Import Tag Definitions page is displayed. On this page you specify the tag definition file you want to import.

C Click Import and specify the file you want to import (in this example, Letter.dtd). the

(29)

₂

C You can review the definitions for each tag in the file you are importing. Click the checkmark next to any definition you do not want to import. The checkmark converts to an X. In this example, all definitions are accepted.

C Click OK to close the Import Tag Definitions dialog box.

4 The Default Plain Text Formatting page is displayed. On this page you to specify how plain text should be displayed.

The default properties for plain text are: C Font: Arial

C Size: 10 point C Effects: none C Colour: black

(30)

2

5 The Elements and Attributes page is displayed. On this page you configure the elements and attributes.

This is the key step in the Tag Settings Wizard. It enables you to perform one or more of the following tasks:

C Classify tags as external, internal, or a placeholder. C Classify tags as always translatable or non-translatable.

C Define translatable attributes within tags (for example, the ALT attribute within the IMG tag in HTML).

C Assign special formatting properties to text between specific tags (for example, headings or emphasized text).

C Add or remove tags from the list of elements.

C Add conditions to determine when text is translatable. See Using Conditional ML Tags in Tag Settings Files on page 2-23.

C Select one or more root elements. FOR MORE INFORMATION

(31)

₂

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 Element

Properties dialog box. Click the Formatting tab.

C Select Bold and click OK to confirm. The new text formatting is displayed in the preview pane of the wizard. Repeat this procedure for each tag whose formatting properties you want 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.

(32)

2

7 Click Advanced to open the Advanced Settings dialog box.

Here you specify advanced tag settings.

In the Treat unrecognised elements as group box, define how TagEditor treats tags that have not yet been added to the Elements tab:

C Select External to format all undefined tags as external tags. This is the default setting. C Select Internal to format all undefined tags as internal tags.

C Select Placeholder if you want all undefined tags to be treated as non-translatable placeholder tags.

In the Script translation group box, define the strings within <SCRIPT> tags in HTML documents that TagEditor presents for translation:

(33)

₂

C Select Do not allow translation of any strings in scripts to protect all text within strings from 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 to change 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 change the 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 Trados environment which rely on the charset value to remain unchanged during translation. In the Display Options group box, define how TagEditor displays <FONT> tags and treats line breaks.

C Select the Disable formatting for <FONT> tags option when translating into Asian languages. 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 using DBCS 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.

V

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 case sensitivity is only be possible at the time settings are created. This option allows you to check 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 the XML document):

C Select Change source language to target language if you always want the xml:lang attribute to 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 be changed 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.

(34)

2

In the Unicode UTF-8 byte order mark (BOM) group box, specify whether or not you want to apply the Unicode UTF-8 byte order mark:

C Select Preserve; don’t add if not originally present if you do not want to add the byte order mark.

C Select Preserve; add if not orginally present for UTF-8 encoded file if you want to add the byte order.

C Select Remove if present if you want to remove the byte order.

Click OK in the Advanced Settings dialog box to accept the default settings and then click Next. 8 The Conversion of Character Entities page is displayed. On this page, you can specify which

SGML/XML/HTML character entities should be converted to real characters and which should be left untouched. When you select a public entity set from the Entity sets list, the corresponding list of entities appears in the Character entities pane. By default, TagEditor converts all entities from the selected public entity set to real characters. Unconverted entities are formatted as internal tags, using the SGML markup with the ampersand and semicolon delimiters.

(35)

₂

SGML/XML/HTML experts. If you are creating a new tag settings file, select the public entity sets that correspond to the file format of your document. For more information about character entity conversion for different file formats, see the Tag Settings Manager Help. For the SGML-based tag settings file used in this tutorial (Letter.ini), select Added Latin 1 in the list of sets. Click Next to confirm.

9 The Previewing page is displayed. On this page, you specify the application to use to preview files translated in TagEditor.

Internet Explorer 5.0 or higher is the default internal browser. Here, internal means that TagEditor does not have to launch Internet Explorer in an external window; instead, it opens a special window within the main TagEditor application window. If you wish to use another browser to view your HTML files, you can specify an external viewer, such as Firefox. In the case of SGML files, as in our example, you may wish to use an external viewer.

To set this up, click External and use the Browse button to locate the application on your system.

When you are translating files in TagEditor, clicking the Preview tab launches the external application specified. The message, “In external preview mode” appears in the TagEditor application window. The following recommendations may be useful:

C Use a recent browser (for example, Internet Explorer 6.0 or Firefox 2.0) for previewing HTML files. Older browsers may not be fully supported.

(36)

2

C Use a recent browser (for example, Internet Explorer 6.0 or Firefox 2.0) for previewing XML files. The XML files may display as code. Older browsers may not be fully supported. C Before returning from the external application to TagEditor, close the file in the external

application to avoid potential conflicts with the open file in TagEditor.

C TagEditor only sends a temporary file to the external application. Do not modify it outside TagEditor, otherwise changes will be lost.

C When you return from the external application, the external preview mode is still active in TagEditor. To continue translating the file in TagEditor, switch back to Edit view.

10 When you are satisfied with your tag settings, click Finish. When you click Finish, the Save As dialog box appears. Enter a logical name and save the tag settings file with an *.ini extension.

You are returned to the Tag Settings Manager dialog box. The new tag settings file is available for selection.

11 Click OK to return to the main TagEditor window. You are now ready to translate the SGML file, Letter.sgm, using Translator’s Workbench and TagEditor.

After all tag settings have been defined as required, an SGML file based on the letter DTD

(37)

₂

Editing Tag Settings

To modify existing tag settings files, select the INI file you want to change and click Properties in the Tag Settings dialog box. The Tag Settings Properties dialog box is displayed.

Select the tab containing the properties you want to modify and make any changes that are required. Click OK to confirm. Each tab corresponds to one of the pages in the Tag Settings Wizard. For more information, see “Tutorial: Tag Settings Wizard” on page 2-8.

Defining Tag Settings to Handle Script Translation

Through the Advanced Settings dialog box which you can access by clicking Advanced in the Elements tab of the Tag Settings Manager, TagEditor offers three options for translation of strings within <SCRIPT> tags in HTML documents:

C Allow translation of all strings: Use this option if you want all strings within quotation marks to be available for translation.

C Allow translation of L-strings only: Use this option if you want only those strings that are identified as localizable strings to be available for translation.

C Do not allow translation of any strings in scripts: Use this option if you want no string whatsoever to be available for translation.

(38)

2

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.

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>

(39)

₂

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.

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.value firstname=x.myName.value submitOK="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>

(40)

2

VBSript

The example below contains one localizable string resource. It is highlighted in bold.

To identify this string resource as localizable:

1 Separate the localizable text from the script code by declaring it as a variable. 2 Prefix the variable name with "L_".

3 Use the variable in the script code.

dim L_HelloMessage

L_HelloMessage="Hello, World!"

alert(L_HelloMessage) </script>

Defining tag settings to allow for translation of L_ strings only

To modify a tag settings file:

1 In TagEditor, select Tools > Tag Settings. Make sure no documents are open.

2 In the Tag Settings Manager, select the tag settings file for your HTML documents and click Properties.

NOTE

D

If you are using the default tag settings file for HTML (html4.ini), select Predefined HTML Settings.

3 Click the Elements tab, and then click the Advanced button. 4 In the Advanced Settings dialog, options for Script translation are:

C Allow translation of all strings C Allow translation of L_ strings only

(41)

₂

Using Conditional ML Tags in Tag Settings Files

You can specify which tags are translatable or not translatable using the Element Properties dialog box, which is accessible by clicking Properties in the Tag Settings Manager and then clicking Properties on the Elements tab of the Tag Settings Properties dialog box. Tag settings support using conditional XML, HTML, or SGML tags. By creating conditions in the tag settings file that the ML file must meet, you can control which content in an ML file should be translated and which content should be ignored.

V

To learn more about creating or modifying tag settings files, see “Tutorial: Tag Settings Wizard” on page 2- 8.

Conditions can be based on attribute values or parent elements. Use the Element Content setting in the Element Properties dialog box to specify whether element content is always ignored or should always be translated. Click Conditions to further specify the conditions that must apply to make content translatable or not translatable.

(42)

2 XPath Expressions

You can add or edit complex XPath expressions by clicking Conditions in the General tab of the Element Properties dialog box. You can assign a parent element or create an attribute condition. TagEditor supports nested elements at the parent and grandparent level, elements with multiple attribute/value pairs, and elements with a single attribute/value pair.

Support for these options is based on a subset of the XPath standard. XPath is a set of syntax rules for defining the parts of an XML document.

V

To learn more about the XPath standard, see http://www.w3.org/TR/xpath.

When working with ML files, you can use an attribute in an element to specify whether the content should be translated. To create a condition:

1 Open the Tag Settings Manager and click Properties to open the Tag Settings Properties dialog box.

(43)

₂

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.

(44)

2

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. NOTE

D

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

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. NOTE

D

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

(45)

₂

7 When finished adding attribute conditions and parent elements, click OK to return to the Element Properties page. The condition is displayed in XPath format underneath the element name.

The following table lists the supported XPath options:

XPath Format Description XML equivalent

Element Plain element. <Element> …

</Element> Element[@attr="value1"] Element with an attribute

that has a value.

<Element attr="value1"> …

</Element> Element[@attr1="value2"]

[@attr2="value4"]

Element with two attributes that have values.

<Element attr1="value2" attr2="value4"> …

</Element> Parent/Element Element with a parent. <Parent>

… <Element> … </Element> … </Parent>

(46)

2

C Each definition in the table applies to the content of the element, not the parent or grandparent.

C Longer expressions override short ones, with every element and attribute counting as one expression. If you have element definitions of a/b/c and b/c[@attr1="value1"],

markup results will be unpredictable when the XML file contains an element definition of

a/b/c[@attr1="value1"] because there are two matching expressions with a length of

three. If you run into this problem, add a definition for a/b/c[@attr1="value1"]. Because this definition has four expressions it overrides the shorter definitions. C SDL Trados supports long expressions. An element definition can consist of

Document/Chapter/Section/Subsection/Subheading/Enumeration/ Item/Formatting[@NumericPrefix="no"][@Translatable="yes"]

[@Color="green"][@Visible="yes"]. However, we do not recommend using lengthy element definitions as this can be a sign of poorly written XML and should be fixed by the author.

The example below shows several uses of the supported XPath syntax rules. This example includes nested elements, an element with multiple attribute/value pairs, and an element with a single element/value pair.

This text will stay in the source language. <PARA translate="Y">

This text is translated to the target language. </PARA>

GrandParent/Parent [@attr3=”value3”]/ Element[@attr1=”value5”]

Parent/child relations combined with attribute conditions to form complex expressions. <GrandParent> … <Parent attr3=”value3”> … <Element attr1=”value5”> … </Element> … </Parent> … </GrandParent> XPath Format Description XML equivalent

(47)

₂

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 the

nontranslatable 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 Settings Manager using the Element Content settings as shown in the following example:

Element Option in tag settings file Result

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 to Always translatable in the General tab of the Element Properties

You can always translate content inside 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

(48)

2

When you view this section of the 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.

(49)

T r a n s l a t i o n

₂

TRANSLATION

Translate your HTML, XML and SGML files using Translator’s Workbench and TagEditor. If you are using Synergy, your files will have already been converted to TradosTag format during the project creation process and you can open them in TagEditor directly from Synergy. You can verify your files from within Synergy and clean-up happens automatically during the Finalization process in Synergy. If you are not using Synergy, your files are converted to TradosTag bilingual format during translation and remain in that format until the last translated file is cleaned up.

Follow these guidelines during translation in TagEditor:

C Use the tag protection features in TagEditor to protect the tag content of your file. C Use the Tags toolbar and the Insert Tag command to insert tags into your target file. C Use the Tags toolbar and the Insert Entity command to insert entities into your target file. C Use the segment level verification settings to have TagEditor verify tag content in the

background as you work.

C Use the verification plug-ins to verify tag content at document level frequently during translation.

NOTE

D

If you are using Synergy, you can define verification settings and verify files from within Synergy after translation.

C Use the spelling checker plug-ins to check spelling as you work.

(50)

2 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.

(51)

₂

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 is successful, the target file can then be converted back to its original format.

NOTE

D

If you are using Synergy, you can define verification settings and verify files from directly within 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 each of the above file types.

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

V

For more information about verifying the tag content of translated HTML, SGML and XML documents, 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 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 (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.

(52)

P o s t - t r a n s l a t i o n P r o d u c t i o n

2 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 saving the 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 as TradosTag (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. NOTE

D

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

(53)

C o n c l u s i o n

₂

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. ✔

(54)

C o n c l u s i o n

2

(55)

Chapter

F R A M E M A K E R A N D

I N T E R L E A F / Q U I C K S I L V E R

F I L E S

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 NOTE

D

If you are working with SDL Trados Synergy, this chapter is not relevant to you, as you can add MIF files directly to Synergy projects. For more information, see the Synergy

(56)

O v e r v i e w

3 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.

TIP

E

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.

C MIF – Maker 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.

(57)

O v e r v i e w

₃

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 is retained 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 correct sequence 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 verify the 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.