sdl trados 2006 - file formats reference guide

8/7/2019 SDL Trados 2006 - File Formats Reference Guide

http://slidepdf.com/reader/full/sdl-trados-2006-file-formats-reference-guide 1/318

File Formats

Reference Guide

File Formats

Reference Guide



COPYRIGHT

FILE FORMATS REFERENCE GUIDE

Copyright © 2006 SDL International.

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

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.

To access the latest documentation for this andother products, see the downloads page at SDLCustomer Center or www.translationzone.com.

This guide accompanies SDL Trados 2006.

February 2006




i

Chapter 1 Introduction

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

Supported File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

TRADOStag bilingual file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Chapter 2 HTML, XML, and SGML Files

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

Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4What is a DTD? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Managing Tag Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Tutorial: Tag Settings Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Editing Tag Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Using Conditional ML Tags in Tag Settings Files . . . . . . . . . . . . . . . . . . 2-22

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

Post-translation Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34

TABLE OF CONTENTS


http://slidepdf.com/reader/full/sdl-trados-2006-file-formats-reference-guide 4/318ivFILE FORMATS REFERENCE GUIDE

Chapter 3 FrameMaker and Interleaf Files

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Key Term Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Translation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Preparation and Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

The STF file formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6


Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Chapter 4 PageMaker Files

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Key Term Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Translation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Installing Story Collector for PageMaker . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Preparation and Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Creating a Folder Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Opening Story Collector for PageMaker . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Setting the Story Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Exporting Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Post-translation Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Importing Translated Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11Tips for Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11Tips for Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12Tips for Japanese PageMaker 6.5 and 7 . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Tag Reference Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14Story Collector for PageMaker Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14Tags in PageMaker Tagged Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21




Chapter 5 QuarkXPress Files

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2XTG files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Key Term Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Translation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Installing Story Collector for QuarkXPress . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Preparation and Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Creating a Folder Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Opening Story Collector for QuarkXPress . . . . . . . . . . . . . . . . . . . . . . . . 5-7Setting the Story Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Exporting Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Post-Translation Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12Importing Translated Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

Batch Functions in Story Collector for QuarkXPress . . . . . . . . . . . . . . . . . . . . . . 5-13Setting the Story Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13Exporting Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Importing Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Tag Reference Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18Story Collector for QuarkXPress Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18Tags in QuarkXPress Tagged Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25

Chapter 6 InDesign Files

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Key Term Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Translation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4Installing Story Collector for InDesign . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Preparation and Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Creating a Folder Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6Opening Story Collector for InDesign . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

Setting the Story Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7Exporting Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

Post-translation Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11Importing Translated Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12

Batch Functions in Story Collector for InDesign . . . . . . . . . . . . . . . . . . . . . . . . . 6-13Setting the Story Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13


http://slidepdf.com/reader/full/sdl-trados-2006-file-formats-reference-guide 6/318viFILE FORMATS REFERENCE GUIDE

Exporting Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14Importing Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16

Tag Reference Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18Story Collector for InDesign Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18

Tags in InDesign Tagged Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18

Translating InDesign CS 2 files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-45

Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-49

Chapter 7 Ventura Files

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Key Term Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Translation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Preparation and Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Creating a Folder Structure organization . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Preparing the Text in Ventura Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4Exporting Ventura Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

Post-translation Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Importing Ventura Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

Tag Reference Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

Chapter 8 Word and RTF Help Files

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2Key Term Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Selecting a Workflow for Word Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Working with Microsoft Word Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4RTF Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

Preparation of Microsoft Word Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5Using the Bookmark Handler macros . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6


http://slidepdf.com/reader/full/sdl-trados-2006-file-formats-reference-guide 8/318viiiFILE FORMATS REFERENCE GUIDE

Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9PowerPoint Documents during Translation . . . . . . . . . . . . . . . . . . . . . . . 10-9After Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12


Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14

Chapter 11 Microsoft Excel Documents

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2Key Term Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3Translation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4

Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5

Handling Macros in Excel Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5About the Conversion Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5

Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9Excel Documents during Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9After Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12


Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14

Chapter 12 Translating Programming Files

Localizing Windows32 Binary Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3Previewing File Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6Verifying Translated Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7Cleaning Up Translated Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8

Localizing Resource Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12Previewing File Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15Verifying Translated Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16Cleaning Up Translated Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17

Localizing Java .properties files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18




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

Supported Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2Supported File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2The SDL OpenOffice Filter Settings File . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2

Translation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3Previewing OpenOffice and StarOffice files . . . . . . . . . . . . . . . . . . . . . . . 15-3

Glossary

Index


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



Chapte

INTRODUCTION

Chapter 1, Section 1, of the File Formats Reference Guide

introduces the 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 2006. 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-4

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

The following user guides contain information that is relevant to the file formats described in this

guide:

C S-Tagger User Guide – contains detailed and comprehensive information on how to manage

FrameMaker and Interleaf files throughout the translation process. It also includes details on

the Font Mappers for FrameMaker and Interleaf. These applications facilitate the font changes

necessary when translating Asian language files, including Indian languages.

C Translator’s Workbench User Guid e – describes in detail how to work with Translator’s

Workbench, and the Translator’s Workbench editing environments. It also outlines the

Translator’s Workbench terminology recognition feature which allows you to access termbase

data while translating.

FOR MORE INFORMATIONV

For a complete list of user guides, see the Getting Started Guide for the product you purchased.

Sample Files

Sample files are included as part of your SDL Trados installation. These files are installed by default

to the following location:

C:\Program Files\SDL International\T2006_FL]\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.



Abou t th i s Gu ide1


1-

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

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.



Su ppor ted F i l e Formats1


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

C DTP formats – FrameMaker and FrameMaker + SGML tagged text format (MIF), 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 documetns – ITD.

C Java Properties files.

C SDL Generic Delimited files.

C OpenOffice and StarOffice files.

C FrameMaker and Interleaf files.

NOTED

For more detailed information on FrameMaker and Interleaf files, see the S-Tagger Guide.

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 b i l i ngu a l f i l e fo rmat1


1-

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

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

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.


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



Conc lu s ion1


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.



Chapte

HTML, XML, AND SGML FILES

Chapter 2, Section 2, of the File Formats Reference Guide

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 theTag Settings Wizard

C Post-translation production tips

2



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.

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 ActiveServer Pages (ASP), Active Server.NET (ASP.NET), ASP.NET (ASPX and ASCX), Java ServerPages (JSP), Include files (INC) and PHP: Hypertext Preprocessor (PHP) files.

C SGML documents (SGM, SGML).

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

NOTED

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.

Key Term Definition

The following terms occur frequently in this chapter:

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 XML – 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.



Overv i ew2


2-

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.

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

Translation Workflow

Translation of an HTML, XML, and SGML 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 Prepare the necessary tag settings file(s). For more information, see “Tutorial: Tag

Settings Wizard” on page 2-7.

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

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

publishing environment for further processing.



P repara t ion2


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.

NOTED

All the information on tag settings in this guide relates to management of tag settings fileswhen using Translator’s Workbench, TagEditor or WinAlign as stand-alone applications.WinAlign does not display external tags, but uses the tag settings file to parse the tag content.

What is a DTD?

The structure of HTML, XML, and SGML documents are 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 aparticular 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 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-7.

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, TagEditor uses 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 TagEditor on how to handle HTML, SGML or XML

elements, such as tags and character entities.



P repara t ion2


2-

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 Translator’s Workbench, TagEditor, or WinAlign.

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 theHTML 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 havethe root element XLIFF.

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

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

Built-in tag settings files are stored in the Workbench/TagEditor installation folder (by default

C:\Program Files\SDL International\T2006[_FL]\TT\. You can create copies of and modify

these files as required.

NOTED

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

Using Tag Settings Files

Tag settings files are required for the following processes:

C Alignment of ML files in WinAlign.

C Analysis and pre-translation of ML files in Translator’s Workbench.

C Translation and verification of ML files in TagEditor.



P repara t ion2


Managing Tag Settings

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

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

To access the Tag Settings Manager:

1 Launch TagEditor from the Start menu on your computer.

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 Tag

Settings” on page 2-18.



P repara t ion2


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 fromTranslator’s Workbench or WinAlign. For more information, see the 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:\Program Files\SDL International\T2006[_FL]\Samples\TagEditor\SGML\:

C The document type definition (DTD), in this case the file Letter.dtd. This DTD defines rulesfor writing letters in SGML. In normal circumstances, you may have to contact the originatorof 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. Thistutorial uses the SGML file, but you can use the XML file to work through it. Letter.xml islocated inC:\Program Files\SDL International\T2006[_FL]\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 displays.

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



P repara t ion2


2 This opens the Tag Settings Wizard – Step 1 of 6 page, in which you specify the general

tag settings, as follows:

C Specify the Settings name you want to use (in our example, Sample Letter). This will bethe 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.



P repara t ion2


2-

3 This opens the Tag Settings Wizard – Step 2 of 6 page. Click Import and specify the file

you want to import (in this example, Letter.dtd).

C You can review the definitions for each tag in the file you are importing. Click thecheckmark next to any definition you do not want to import. The checkmark converts to anX. In this example, all definitions are accepted. Click OK to close the Import TagDefinitions dialog box.



P repara t ion2


4 This opens the Tag Settings Wizard – Step 3 of 6 page. Step 3 allows 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

Accept the default settings and click Next.



P repara t ion2


2-1

5 The Tag Settings Wizard – Step 4 of 6 page opens allowing you to 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 IMGtag in HTML).

C Assign special formatting properties to text between specific tags (for example, headingsor 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-22 .

C Select one or more root elements.


For more information on tag formatting and classification, see the Tag Settings Help. Inaddition, look at the predefined HTML settings file (HTML4.ini) to see the tag formatting andclassification settings that SDL Trados has defined for HTML documents.



P repara t ion2


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

7 On the Tag Settings Wizard – Step 4 of 6 page, 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-translatableplaceholder tags.

In the Script Translation group box, define the strings within <SCRIPT> tags in HTML

documents that TagEditor presents for translation:

C Select Allow translation of all strings if you want to present all strings between quotationmarks for translation.

C Select Allow translation of L_strings only to present text contained within L _variables fortranslation.

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



P repara t ion2


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. Thisis 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 <FONT> tags and treats line

breaks.

C Select the Disable formatting for <FONT> 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 breaksin the file(s) you wish to translate.


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.

Click OK in the Advanced Settings dialog box to accept the default settings and click Next in

the wizard to proceed to the Tag Settings Wizard – Step 5 of 6 page.



P repara t ion2


2-1

8 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 theampersand and semicolon delimiters.

For example, the entity “>” (> ‘greater than’ symbol) is displayed as in TagEditor. If you

are editing an existing tag settings file, the relevant public entity sets in the Entity sets list are

selected for conversion by default. These default conversion settings ensure that all character

entities are handled properly by TagEditor. We recommend that you do not make major

changes to the default conversion settings. Generally, this should only be done by

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 and to proceed to the Tag Settings Wizard – Step 6 of 6

dialog box.



P repara t ion2


9 Step 6 allows you to 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 specifyan external viewer, such as Netscape Communicator. 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 5.x, Firefox 1.x, or Netscape Navigator7.x or later) for previewing HTML files. Older browsers may not be fully supported.

C Use any current SGML browser for previewing SGML files.

C Use a recent browser (for example, Internet Explorer 5.x, Firefox 1.x, or Netscape Navigator7.x or later) for previewing XML files. The XML files may display as code. Older browsersmay not be fully supported.

C Before returning from the external application to TagEditor, close the file in the externalapplication to avoid potential conflicts with the open file in TagEditor.



P repara t ion2


2-1

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

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

10 When you are satisfied with your tag settings, click Finish in the Tag Settings Wizard –

Step 6 of 6 dialog box. 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

typically appears as follows (additional format mappings are used in this example):



P repara t ion2


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 steps (1-6) in the Tag Settings Wizard. For

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

Defining Tag Settings to Handle Script Translation

Through the Advanced Settings 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 marksto be available for translation.

C Allow translation of strings identified as localizable: Use this option if you want only thosestrings 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 stringwhatsoever to be available for translation.

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.



P repara t ion2


2-1

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.valuefirstname=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


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

VBSript

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

<script type="text/vbscript">

alert("Hello, World!")</script>

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.

<script type="text/vbscript">

dim L_HelloMessageL_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.

NOTED

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

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

C Do not allow translation of any strings in scripts

Choose Allow translation of L_ strings only

5 Click OK to save the settings.



P repara t ion2


Using Conditional ML Tags in Tag Settings Files

You can specify which tags are translatable or not translatable using the Element 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 shouldbe translated and which content should be ignored.


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

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.



P repara t ion2


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


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 or the Tag Settings Wizard. See Tutorial: Tag Settings Wizard on page 2-7 for more information.

2 Click the Elements tab.

http://www.w3.org/TR/xpath




P repara t ion2


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


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

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


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>



P repara t ion2


2-2

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

C Longer expressions override short ones, with every element and attribute counting as oneexpression. 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 lengthyelement definitions as this can be a sign of poorly written XML and should be fixed by theauthor.

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.

<PARA translate="N">

This text will stay in the source language.

<PARA translate="Y">This text is translated to the target language.

</PARA>

<PARA translate="Y" color="Blue">

This text is both translated and colored blue.

</PARA>

More text staying in the source language.

</PARA>

GrandParent/Parent

[@attr3=”value3”]/

Element[@attr1=”value5”]

Parent/child relations

combined with attribute

conditions to form complexexpressions.

<GrandParent>

…

<Parent attr3=”value3”>…

<Element attr1=”value5”>

…

</Element>

…

</Parent>

…

</GrandParent>

XPath Format Description XML equivalent



P repara t ion2


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 nestedPARA

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



P repara t ion2


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

Once translated, your XML file looks like the following:



Trans la t ion2


TRANSLATION

Translate your HTML, XML and SGML files using Translator’s Workbench and TagEditor. During

translation, the files are converted to TRADOStag bilingual format 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 thebackground as you work.

C Use the verification plug-ins 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 TRADOStag Viewer plug-in to preview or print any TRADOStag files as you work.



Trans la t ion2


2-3

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-22 for details.

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.

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

C Use the Generic Tag Verifier plug-in in TagEditor to verify the tag content of each of the abovefile 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.



Trans la t ion2



For more information about verifying the tag content of translated HTML, SGML and XMLdocuments, see the Translator’s Workbench 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 TagEditorThe 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.



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


2-3

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


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



Chapte

FRAMEMAKER AND INTERLEAF

FILES

This chapter explains explains how to work with FrameMaker

and Interleaf files.

Sections include:

C FrameMaker and Interleaf translation workflow

C Preparing FrameMaker and Interleaf files using the

S-Taggers

C Translating FrameMaker and Interleaf files

C Converting translated files back to original format usingthe S-Taggers

C General post-production tasks

3



Overv i ew3


OVERVIEW

This chapter gives a high level view of working with FrameMaker and Interleaf file formats.

To translate FrameMaker and Interleaf files, you need to convert the text in the files to a format thatis easily translated. The S-Taggers facilitate this conversion. See the S-Tagger User Guide for

comprehensive information on the S-Taggers.

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.

Installing the S-Taggers

The S-Taggers are installed as part of your SDL Trados package. The default installation location for

these files depends on the path used for the product installation.

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.

S-Tagger for Interleaf supports IASCII and catalog files saved from Interleaf 5.2 or later. Interleaf 7whichi is included as part of the QuickSilver XML application suite is 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.

C ILDOC – Interleaf 7 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 function as

master style sheets. The author of the original Interleaf 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 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. It is a tagged text format that is compatible with

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

Interleaf documents is represented by brief coded statements (S-Tags). You can decide which

C CAT file – a file created by S-Tagger from Interleaf 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 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 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 backwardconversion 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.



Overv i ew3



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

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

2 Prepare your FrameMaker or Interleaf files for translation.

3 Save your FrameMaker files as MIF or your Interleaf 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.


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

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

FM/ILDOC format. You can now carry out the final DTP work, such as generating theindex 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 S-Tagger User Guide or the onlinehelp for the Font Mappers for more information.

C See the S-Tagger User Guide for comprehensive information on each stage of theFrameMaker and Interleaf translation process.

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.



P repara t ion and Conve rs ion3


3-

PREPARATION AND CONVERSION

You may need to prepare your FrameMaker and Interleaf file(s) before using the S-Taggers to

convert the files to STF. The extent of your preparation will depend on the formatting of your

document and the source and target languages of your translation.

Using the S-Taggers, you can choose to create an STF file in TXT, RTF or TTX format. This choice

governs your choice of editing environments and whether or not you can process files with Context

TM.

The STF file formats

You have three choices for the format of the STF file. You make your choice in the Settings tab in the

S-Tagger:

TRADOStag (TTX). Select this to create TTX files suitable for translation directly in TagEditor. The

STF files have the extension .rtf.ttx. TRADOStag is an XML-based file format for representing both

DTP tagged text output and bilingual data. In TTX format, the S-Tags will be marked with formatting

suitable for use with Translator's Workbench.

Rich text format (RTF) is the default file format. The STF files have the extension .rtf and can be

opened in any word processor that supports RTF. Note that TagEditor accepts RTF files, but converts

them to TTX format while you are working on them.

For this option, you must also select the page size for the RTF files:

A4 is the standard page size for Europe and Asia.

Letter is the American standard.

In RTF format, the S-Tags will be marked with formatting suitable for use with Translator's

Workbench. Internal and external tags are assigned tw4winInternal and tw4winExternal character

styles.

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 arevery 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 communication

with document management or machine translation systems and is not recommended for

interactive translation.



Trans la t ion3


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/Interleaf files for translation

C Save your FrameMaker/Interleaf files as MIF/IASCII

C Select your conversion settings in the S-Taggers

C Convert your MIF/IASCII files to STF format.

NOTED

All of these tasks are explained in detail in the S-Tagger User Guide.

TRANSLATION

Translate your FrameMaker and Interleaf files using Translator's Workbench and TagEditor. The

following steps offer a high level view of the translation process for FrameMaker and Interleaf 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.

4 Verify the tag content of the target files using the verification plug-ins in TagEditor.

NOTED

Alternatively, you can use the S-Taggers to verify batch files. See the S-Tagger User Guide formore details.





3-

5 Save the target files in TRADOStag (TTX) bilingual format, using the Save Bilingual As

command in TagEditor. We recommend that files remain in bilingual format after

translation while editing, review and tag verification are still in progress.

6

Clean up the translated files using theClean Up

command in Translator’s Workbench.Use the Update TM option to ensure that the translation memory is updated in

accordance with the latest changes in the translated files. Keep an unclean copy of the

bilingual files for reference.

7 Convert the translated file back to MIF/IASCII format using the S-Taggers.

8 Open the translated FrameMaker/Interleaf documents for post-translation production.

NOTED

C For more information about translating files in TagEditor and the clean up feature in

Translator’s Workbench, see the Translator’s Workbench User Guide.


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

ready for final DTP and proofing.


CCheck line breaks, page breaks and pagination.

C Ensure that cross references are accurate and work correctly.

C Make sure graphics are correctly placed and that call out text has been translated and displays

fully.

C Check that headers and footers have been translated and display correctly.

C Generate the table of contents and the index.

NOTE

D If 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 ion3


CONCLUSION

Now that you have completed this chapter you should understand the FrameMaker/Interleaf

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

Section 4 of the File Formats Reference Guide

explains how to work with the following DTP file formats:

PageMaker, QuarkXPress, InDesign and Ventura.

Chapter 4 deals with the following aspects of translating the

PageMaker DTP file format:

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


OVERVIEW

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

translated.

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

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

spent on preparatory and post-translation work.

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.

Story Collector for PageMaker works with PageMaker 6.5 and PageMaker 7. It converts files in P65

and PMD format to a TXT format that can be easily translated using Translator's Workbench and

TagEditor.

How Story Collector for PageMaker Works

Story Collector for PageMaker is a PageMaker plug-in. This means that it uses the Application

Programming Interface (API) provided by PageMaker to add extra functionality to PageMaker itself.

Once you have placed the Story Collector.add file in the Plugins folder of the Adobe

PageMaker program folder, you can launch Story Collector via the Utilities menu and the Plug-ins

submenu in PageMaker.

Story Collector has three basic functions which are presented in the Trados Story Collector dialog

box. These are the story order, export and import functions.

C Story Order: Before exporting stories from your PageMaker document, you can determine theorder in which they appear in the export file. This means that stories are presented fortranslation 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 taggedtext export file. After exporting all stories to this file, you open the file for translation inTagEditor. The file is translated in the normal way, using Translator’s Workbench.

C Importing Stories: After translation, you clean up the translated files and save the file to TXTformat. You then import the translated stories into a copy of the original PageMaker file usingStory Collector.



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.



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\T2006[_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:\Program Files\SDL International\T2006[_FL]\Samples\Story Collector for

PageMaker, where xxx corresponds to the name of the software you are using. 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-

PREPARATION AND EXPORT

You may need to prepare your PageMaker file(s) before using Story Collector 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 a folder structure for your PageMaker translation project

C set the story order of the stories in the PageMaker file so that they are presented for translationin a logical sequence

C export the stories in the PageMaker file to a text file.

For more detailed information about preparing PageMaker files for export and translation, see

“Troubleshooting” on page 4-11.

NOTED

PageMaker files work with European languages and Japanese.

Working with PageMaker 7

Adobe PageMaker 7 has several new features that may involve additional preparatory steps:

C Data merge – allows you to create direct mail publications by using a Comma Separated Value(CSV) file as a source for the data to be merged. Commonly this CSV file would be used tostore name and address information to be merged into a PageMaker template. If a storycontaining data merge information is imported after translation into PageMaker the datamerge tags become ordinary text. The best way to work with a PageMaker publication thatcontains data merge information is to place the data merge text on a separate layer inPageMaker and hide this layer before exporting all the stories using the Story Collector forPageMaker. When you import the translated text, you can make the hidden layer visible again.

C Place PDF – allows you to copy pages from an Adobe PDF (Portable Document Format) fileinto a PageMaker publication. The text in these cannot be translated as it behaves like agraphic file in the PageMaker publication. If the text from a placed PDF needs to be translated

the source document it originated in must be translated and the page from that placed in thePageMaker publication.

C Native support for Adobe Photoshop and Illustrator files – allows you to add layeredPhotoshop and Illustrator files to a PageMaker publication. These behave like other graphicformats in PageMaker.





C Hyperlinks – allow documents saved as HTML or Adobe PDF to have links to another place inthe document or to a website. This link information is not exported by PageMaker whenstories are exported by the Story Collector. The links will need to be re-created whentranslation is complete.

Creating a Folder Structure

As this process produces a PageMaker (P65 or PMD) and a TXT file for each language, it is vital to

set up a folder structure for the project. Otherwise files may be lost or misplaced.

NOTED

Pagemaker 6.5 files have a P65 extension and PageMaker 7 files have a PMD extension.

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

C A source language folder with a subfolder for P65/PMD files and another subfolder for theTXT files.

C A target language folder with a subfolder for copies of the P65/PMD files and anothersubfolder for the TXT files.

To keep a copy of each file and file version:

1 Place the files to be translated in the source P65/PMD folder.

2 Set the story order of the files in the source P65/PMD folder, and save them.

3 Place a copy of the same files in the target P65/PMD folder.

4 Export the source files from the source P65/PMD folder to your source TXT folder.

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

6 Translate the TXT files in the target TXT folder using Translator's Workbench and

TagEditor, and save the translated files in your target TXT folder.

7

Open the copy of the source files you placed in the target P65/PMD folder earlier,import the translated files from the target TXT folder.


PageMaker file and save.





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.





To select the story order for the tagged text export files:

1 Click Story Order in the Trados Story Collector dialog box. The Story Order dialog box appears.

The Story List shows you the first few words or characters of each story on the page. You can

change the order in which they appear in the tagged text file by selecting a story and clicking

the Up or Down button. The story ordering process automatically starts on the page which is

currently open in the PageMaker file. If you wish to start at the beginning of the document,

click the Previous Page button until you reach the first page.

2 When each story on the page has been correctly positioned in the Story List, click on

the Next Page or Previous Page buttons to access other parts of your document and

rearrange the story order.

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

return to the Trados Story Collector dialog box.

NOTED

Even if you are working with double page spreads in PageMaker, you can only rearrange thestory order within a single page.





4-

Exporting Stories

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

1In the Trados Story Collector dialog box, click Export to open the Select Export File dialog box.

2 In the Select Export File dialog box, specify your source TXT folder and a name for the

extended tagged text file. Click Save. All stories are collected and placed in a TXT file in

the location you have specified.



4 The progress and results of the export operation are displayed in the Results window of

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

window to a results file by clicking Save Results. The Save Results As dialog box isdisplayed where you can specify the location and name of the results file.

5 After export, save the original PageMaker file to ensure that the correct story

positioning information is retained.

6 Copy the original PageMaker file you just saved from the source P65/PMD folder into

the target P65/PMD folder.

WARNINGF

You must save the PageMaker file after export to ensure that the correct story positioning

information is retained. This information is necessary for importing stories back into thePageMaker file in the correct order after translation.

Verifying Tagged Text Output before Translation

After export, we recommend that you verify the tagged text output from Story Collector by importing

a copy of the export file back into the original PageMaker file before translation. This allows you to

minimize the possibility of errors occurring later in the project and is particularly important if you

are working with Japanese PageMaker 6.5 or 7.

WARNINGFIt is important to run the verification test using a copy of the original tagged text output fromStory Collector. We recommend that you do not open or make any changes to the originaltagged text file. This eliminates the possibility of file corruption.



Trans la t ion4


TRANSLATION

Translate your PageMaker files using Translator's Workbench and TagEditor. 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 bilingual

TRADOStag (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.


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

Importing Translated Stories1 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.



Trou b leshoot ing4


4-1

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 stories

in your target TXT folder.

4

ClickOpen

. Story Collector imports the translated stories back into the PageMaker filein 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.


PageMaker file.

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

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.



Trou b leshoot ing4


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.

Inline Graphics

If your PageMaker file contains inline graphics, these will not be exported to the tagged text file. As

a result, all inline graphics will be absent from the target file after import, but they can be cut and

pasted from the source file.

Master Pages

C PageMaker does not support the export of text from text boxes on a master page. Use textframes rather than text boxes for all text on the master pages.

C PageMaker does not support the export of page number tags from the left and right masterpages. Page number tags can easily be cut and pasted from the source to the target file.

Tips for Import

The following tips should help you import stories into PageMaker.

Document Layers

If your PageMaker file has layers, make sure that all layers containing stories with text for import are

visible before import begins. Import will fail if you try to reimport text to a story that is on a layer that

has been hidden since export.



Trou b leshoot ing4


4-1

PM Tags Error

If an error message similar to the one below appears as you import the translated file intoPageMaker, this means that there is an error in the tags in the translated file.

To locate the error:

C Examine the imported text and locate the text: ERROR[Basic syntax error]. Theincorrect tag is noted here.

C Locate the corresponding text in the translated file, fix the tag error and re-import the file.

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 importtranslated 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 thetranslated text file back into the PageMaker file. This ensures that tags containing Japanesecharacters are correctly interpreted during import.

CIf 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 Re fe rence Mate r i a l4


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 normal

PageMaker tags. Each Story Collector tag will appear on a separate line.

This table lists the Story Collector tags.

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

Tag Description

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

<$storystart> Beginning of story

(might contain a single text block)

<$storyend> End of story

<$stname "name"> Story name





4-1

General Tags

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

<\!/> 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!





Character Attribute Tags

Tag Type Category

<font "font name"> Font Emphasis

<size ####> Size Emphasis

<f"font name"> Font Emphasis

<s####> Size Emphasis

<ccolor "color name"> color Emphasis

<horizontal ###> Horizontal scale Emphasis

<h###> Horizontal scale Emphasis

<kern ###> Manual pair kerning Miscellaneous

<k###> Manual pair kerning Miscellaneous

<letterspace ###> Kerning Emphasis

<l###> Kerning Emphasis

<p> Plain text Emphasis

<b> Bold Emphasis

<i> Italic Emphasis

<o> Outline Emphasis

< ~> Shadow Emphasis

<u> Underline Emphasis

<x> Strikethrough Emphasis

<+> Superscript Emphasis

<-> Subscript Emphasis

<call> All caps Emphasis

<ca> All caps Emphasis

<csmall> Small caps Emphasis

<cs> Small caps Emphasis

<creverse> Reverse Emphasis

Note: Not used in PM 6.5





Structural Tags

Paragraph Tags

Tag Type Category

<PMTags# ###> Version and codepage spec StructuralThe version documented here is

1.0, code page can be "mac" or

"win".

<c-colortable ("name")

# ####)>

Custom color definition Structural

<c-c...> Custom color definition Structural

<#define_###_

="macro text">

Macro definition Structural

Note: May contain text to be

localized.

<@ ###=definition> Paragraph style definition Structural

Tag Type Category

gbabove ### # ###

### ### "Color"### #>

Rule above Structural

<gbbelow ...> Rule below Structural

<@-next "###"> Set next paragraph style Structural

<@ ###:> Apply paragraph style Structural

<@-parent "###"> Set base on paragraph style Structural

<@-p "###"> Set base on paragraph style Structural

<gleft ###> Left indent Structural

<gl###> Left indent Structural

<gright ###> Right indent Structural

<gr###> Right indent Structural

<gfirst ###> First line indent Structural

<gf###> First line indent Structural





4-1

<gtab(<###>

<align#>

<"leader">)>

Tab definition Structural

<gt(<###> <align#>

<"leader">)>

Tab definition Structural

<galignment # Paragraph alignment Structural

<ga#> Paragraph alignment Structural

<ggrid ###> Leading grid Structural

<gg###> Leading grid Structural

<g& "dictionary

name">

Language Structural

<g+before ### Space before Structural

<g+b###> Space before Structural

<g+after ###> Space after Structural

<g+a###> Space after Structural

g% ###> Autoleading percentage Structural

<g2> Manual + dictionary hyphenation Structural

<g3> Manual + algorithm hyphenation Structural

<gmethod #> Leading method Structural

<gm#> Leading method Structural

<gwordspace ###

### ###

Word spacing Structural

<gw ### ### ###> Word spacing Structural

<gspace ### ###

###>

Letter spacing Structural

<gs ### ### ###> Letter spacing Structural

<gpairs ###> Pair kerning above Structural

<gp###> Pair kerning above Structural

Tag Type Category





<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


4-2

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



Conc lu s ion4




Chapte

QUARKXPRESS FILES


QuarkXPress DTP file type:

C QuarkXPress translation workflow

C Preparing and exporting QuarkXPress files for

translation using Story Collector for QuarkXPress

C Translating QuarkXPress files

C Importing translated files back into QuarkXPress using

Story Collector for QuarkXPress

5



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.

TIPE

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

and QXT format to a text format (QSC) that can be easily 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.

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

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-

XTG files

In SDL Trados 2006 TagEditor can also open XTG files created with SDLXtract. SDLXtract is a

standalone application, available from SDL, that exports Mac-based Quark documents into XTG text

files, which can then be opened in SDL Edit or TagEditor.

Key Term Definition


C QXD – QuarkXPress files have a QXD extension.

C QXT – QuarkXPress files have a QXT extension.

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

C Export file – a tagged text file in QSC format containing untranslated text. This file is produced

when you export stories from a QuarkXPress file.

C Import file – a tagged text file in QSC format containing translated text. You import this file

into a copy of the source QuarkXPress file overwriting the source language text contained in it.

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 QuarkXPress relies on the QuarkXPress

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

from QuarkXPress documents. Inline frames, however, cannot be manipulated via the API,which is why Story Collector cannot export or re-import them.

NOTED

QuarkXPress places inline frames at the start of the translated file when you import yourtranslated file back into QuarkXPress. Use your source QXD files as a reference to move theseinline frames back into their original position.



Overv i ew5



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

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

Installing Story Collector for QuarkXPressStory Collector for QuarkXPress 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\T2006[_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

C 6.0_E

If you have a version later than 6.0, use the files in the 6.0_E folder. Before you install the Story

Collector XTension, make sure that QuarkXPress 4.1, 5.x, or 6.x is installed on your system and is

not running.



Overv i ew5


5-

To install the Story Collector XTension:

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

folder in the QuarkXPress installation folder.

C Story CollectorQ.xnt

C Story Collector GUI.dll

C Story Collector Kernel.dll

C Story Collector Common.dll

C Story CollectorQ1033.hlp

C Story CollectorQ1033.cnt

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

access Story Collector functionality.

NOTED

C If you use Story Collector for QuarkXPress 4.1 for Japanese, move Enhance Preview.xnt intothe XTension Disabled folder before starting QuarkXPress.

C For Story Collector for QuarkXPress 4.1 for Japanese, the files to be copied to theQuarkXPress XTension folder are: EA_Common.dll, EA_Story Collector Gui.dll, EA_StoryCollector Kernel.dll, and EA_Story CollectorQ.axt

Online HelpStory 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 QuarkXPress file (sample.qxd) to work with the Story Collector for

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

C:\Program Files\SDL International\T2006[_FL]\Samples\Story Collector

for QuarkXPress. You should use the sample file to work through the Story Collector processexample that follows in this chapter.






You may need to prepare your QuarkXPress file(s) before using Story Collector 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 a folder structure for your QuarkXPress translation project

C Set the story order of the stories in the QuarkXPress file so that they are presented for

translation in a logical sequence

C Export the stories in the QuarkXPress file to a text file.

NOTEDC If you want to process multiple files at the same time, the procedure for setting the story

order and exporting are slightly different. For more details, See “Batch Functions in StoryCollector for QuarkXPress” on page 5-13.

C QuarkXPress files work with European languages and Japanese.

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.


As this process produces a QXD (QuarkXPress Document) and QSC (QuarkXPress Story Collector)

file for each language, it is vital to set up a folder structure for the project. Otherwise files may be lost

or misplaced.

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

original files. Place a copy of the QuarkXPress file for translation in each target language folder. In

this way, you retain a copy of each source and target file.


C A source language folder with a subfolder for QXD files and another subfolder for QSC files.

C A target language folder with a subfolder for QXD files and another subfolder for QSC files.





5-

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 Translate the files in the target QSC folder using Translator's Workbench and

TagEditor, and 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.






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 theTop-Down order

orLeft-Right order

radio buttons in theStory

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





5-

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.





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


5-1

TRANSLATION

Translate your QuarkXPress files using Translator's Workbench and TagEditor. 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 bilingual






bilingual data from the translated file and to convert the file back to QSC format. If necessary, you can also use the Clean Up command to update the translation memory


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.

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.



P ost -Trans la t ion P rodu c t ion5



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

Importing Translated Stories

To import the translated stories back into the QuarkXPress file:

1 Open the copy of the original QuarkXPress file that you placed in the target QXD subfolder

earlier.

2 Choose Import from the Trados menu in QuarkXPress. The Select Import File dialog

box is displayed.

3 Select the import file from the target QSC subfolder.

4 Click Open, a series of progress bars appear and Story Collector for QuarkXPressimports the translated stories. The Import Results dialog box opens. It tells you if theimport has been successful and how many stories have been imported.

5 Click OK to finish the import process, or click Save As to save the import results to alog 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 Collectorfor QuarkXPress saves it under the name and in the location you specified.

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

8 From the File menu, select Save. The Save dialog box is displayed.

9 Click Save.




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


5-1

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.

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





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.





5-1

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.





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.


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.





5-1

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.




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.






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

as the tags that QuarkXPress itself introduces.

Story Collector for QuarkXPress Tags

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

QuarkXPress includes some of its own tags. Story Collector tags use the ‘$’ symbol to differentiate

them from the normal QuarkXPress tags. Each Story Collector tag will appear on a separate line.

This table lists the Story Collector tags.

Tags in QuarkXPress Tagged Text Files

Tags in QuarkXPress tagged text files have the following characteristics:

C They cannot be nested, i.e. you never have one tag inside another.

C Tags start with < and end with >, except for paragraph tags that start with @ and end with

colon (:) or equals sign (=).

C Paragraphs are separated by line breaks.

Tag Description

<$XPExtTags 1.0 win> Extended QuarkXPress tags file signature

<$STORY NAME = "name "

LOCATION = "Location">

Story name and location

<$storystart> Beginning of story

(Might contain a single text block)

</story> End of story





5-1

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

<XO> Start of XPress index

marker

Structural Applies to version 4.1

and higher

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





Special Character Tags

<XI,"…"> Single level XPress index

marker

Structural Applies to version 4.1

and higher

Note: The Index Palettemust be displayed in

QuarkXPress (select

Show Index from the

View menu) to export

index markers as fully

expanded XPress tags.

Tag Type Category

<\n> Soft return Placeholder

<\d> Discretionary return Placeholder

<\-> Hyphen Placeholder

<\i> Indent here Placeholder

<\t> Right indent tab Placeholder

<\s> Standard space Placeholder

<\!s> Non-breaking space Placeholder

<\f> Figure space Placeholder

<\!f> Non-breaking figure space Placeholder

<\p> Punctuation space Placeholder

<\!p> Non-breaking punctuation Space Placeholder

<\q> Flex space (1/4-Em space) Placeholder

<\!q> Non-breaking 1/4-Em space Placeholder

<\m> Breaking Em dash Placeholder

<\!m> Non-breaking Em dash Placeholder

<\h> Discretionary hyphen Placeholder

Tag Type Category Comment





5-2

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 # character

must 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





Character Formatting Tags

Tag Type Category

<P> Plain text Emphasis

<B> Bold on/off Emphasis

<I> Italic on/off Emphasis

<O> Outline on/off Emphasis

<S> Shadow on/off Emphasis

<U> 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





5-2

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





Paragraph Formatting Tags

Tag Type Category

<*L> Left align paragraph Structural

<*C> Center align paragraph Structural

<*R> Right align paragraph Structural

<*J> Justify paragraph Structural

<*F> Force-justify paragraph Structural

<*t(##.#,#,"

character">

Set tab stops Structural

<*p(##.#,##.#,##.#,##.#,##.#,g/G)>

Set paragraph formats Structural

<*h"specification name"> Hyphenation & justification Structural

<*ra(##,#,"color

name",#,##,##,##)>

Paragraph rule above Structural

<*rb(##,#,"color

name",#,##,##,##)>

Paragraph rule below Structural

<*d(character count, line

count)>

Drop cap Structural

<*kn1> Keep with next Structural

<*kn0> Don't keep with next Structural

<*kt(A)> Keep together, all Structural

<*kt(x,y)> Keep together, line x to y Structural

@Stylesheetname:

text

Apply style sheet to text Structural

Note: Stylesheetname is a user

defined name. "text" is any text.@$:text Normal style sheet Structural

@:text No style Structural



Conc lu s ion5


5-2

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




Know how to use the Story Collector batch functions. ✔




Conc lu s ion5




Chapte

INDESIGN FILES


InDesign files. Files from earlier versions of InDesign

(InDesign 2 and InDesign CS) have to be prepared for

translation using the Story Collector for InDesign. Files from

the most recent version of InDesign (CS2) can be exported to

the InDesign Interchange Format (INX) and opened directly in

TagEditor.

C InDesign translation workflow

C Preparing and exporting InDesign files for translation

using Story Collector for InDesign

C Translating InDesign files

C Importing translated files back into InDesign using Story

Collector for InDesign

C Translating InDesign CS2 INX files

6



Overv i ew6


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



Overv i ew6


6-

Key Term Definition


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.

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.





6-

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 InDesignthat ships with SDL Trados. This sample file is installed to

C:\Program Files\SDL International\T2006[_FL]\Samples\Story Collector for

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

follows in this chapter.


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

your preparation will depend on the formatting of your document and the source and targetlanguages of your translation.

You should:

C create a folder structure for your InDesign translation project

C set the story order of the stories in the InDesign file so that they are presented for translation

in a logical sequence

C export the stories in the InDesign file to a text file.





NOTED

C If you want to process multiple files at the same time, the procedure for setting the storyorder and exporting are slightly different. For more details, see “Batch Functions in StoryCollector for InDesign” on page 7-13.

C Story Collector for InDesign does not export stories in hidden layers. If you wish hiddenlayers, text frames or stories to be included in the export file for translation, remove thehidden attribute before export and re-apply it manually in the translated InDesign file afterimport.

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


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.


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 Translate the files in the target ISC folder using Translator's Workbench and TagEditor,

and save the translated files in your target ISC folder.

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

the translated files from the target ISC folder.

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





6-

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.





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. InDesign displays the page behind the InDesign dialog box and

highlights the story you selected.

NOTEDC InDesign does not display the master page or master page stories when you select a master

page story in the Story Order dialog box.

C Story Collector for InDesign displays a table as a generic (<Table>) story in the Story Order dialog box in InDesign 2.0. Story Collector for InDesign displays the story text in InDesignCS.

3 You may change the story order by clicking on a story in the Story List box, and use the

arrows to the left of the Story List box to reorder them. This will activate the Custom

order button in the Story Order box. Alternatively, you may set the story order for all

pages by clicking on Top-down order or Left-right order in the Story Order box.

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

C Left-right order: Story Collector for InDesign 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.





6-

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 InDesign document behind thedialog box. However InDesign does not display the master page or master page stories whenyou select a master page story in the Story Order dialog 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.





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


6-1


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 yourtarget ISC folder.

NOTED

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

TRANSLATION

Translate your InDesign files using Translator's Workbench and TagEditor. 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





4 After verification, use the Clean Up command in Translator’s Workbench to removebilingual data from the translated file and to convert the file back to ISC format. If

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


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.

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


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





Importing Translated Stories

To import the translated stories back into the InDesign file:

1Open the copy of the original InDesign file that you placed in the target INDD folder earlier.

2 Choose Import from the Trados menu in InDesign. The Import dialog box is displayed.

3 Select the import file from the target ISC folder.

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

the correct sequence.

5 Click Open, a series of progress bars appear and Story Collector for InDesign importsthe translated stories. The Import Results dialog box opens. It tells you if the importhas been successful and how many stories have been imported.

6 Click OK to finish the import process, or click Save As to save the import results to alog file. The Save Log File dialog box opens.

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.



NOTED




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


4 Click OK to confirm the settings.

NOTED

The Settings dialog box allows you to include stories left on the pasteboard. These are placed

after 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 in the Settings dialog box. Select your

source ISC folder. You must set a default folder before you can export multiple files. The Batch

Export button in the Batch Export dialog box remains grayed out until you select an export

folder.

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





6-1


4 Browse to your source INDD 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 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.




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.





Importing Stories

To import multiple files at the same time:

1Select a default batch import folder for the batch files in the Settings dialog box. Select yourtarget ISC folder. 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 InDesign, select Batch Import. The Batch Import dialog box

is displayed.


4 Browse to your target INDD 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.





6-1

5 In the Batch Import dialog box, your target ISC 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 theBatch Import

dialog box, clickImport

to run the import operation, theBatch

Import progress bar is displayed and Story Collector for InDesign overwrites the copy

of the original source file(s) in the target INDD 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 export process is finished.

Story Collector for InDesign overwrites existing files of the same name in the target INDD folder.

Therefore each target INDD file has the same name as its corresponding source INDD file, but is

located in the target folder.

NOTED







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-1

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.





Character Tags

Character 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 a

text 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."

Paragraph style

applied

<ParaStyle:Paragraph style name> <ParaStyle:Heading 1>The tag

<ParaStyle:> starts a new

paragraph with no paragraph style.You can use the abbreviation

<pStyle>.

Character style

definition

<DefineCharStyle>Char style name=

<char attr1><char attr2>...>A character

style definition includes character

attributes as well as <Nextstyle:style

name>.

<DefineCharStyle:Emphasis=<Next

style:Emphasis><cTypeface:Italic>

>The character style definition

includes a list of all styles defined

in the Character Styles palette and

used in the text.

Character styleapplied

<CharStyle:Character style name> <CharStyle:Emphasis>The tag<CharStyle:> ends the character

style definition.

Stroke style table <StrokeStyleTable:=<StrokeName1:

StrokeStyleType (DASH or STRIPE):

Dash/stripe values>

<StrokeName2>...>

Dash syntax:

<Dash name:DASH:LineCap(0,1,2):

AdjustDashOrGaps:segment lengthslist separated

by commas>

Stripe syntax:

<Strip name:STRIPE:segmentlengths

list separated by commas>

<StrokeStyleTable:=<StrokeStyle1:

DASH:0:

AdjustDashes:3.810811,5.675676,11.

432432,3.081081>

<StrokeStyle2:STRIPE:0.130000,0.

470000,0.220000,0.1800

00><StrokeStyle3:DASH:1:Adjust-Gaps:0.000000,6.000000,0.0000

00,18.000000>>

Here StrokeStyle1 is a custom

dash, StrokeStyle2 is a

custom stripe; and StrokeStyle3 is a

dotted dash.

Attribute Format Example and Notes





6-2

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.

C To return an attribute to its default state, type the attribute name followed by a colon (:). For

example, to return to the default leading value, type <cLeading:>

Attribute Tag NameTag

Abbr.

Examples and Notes

Alternate glyph cAlternateGlyph:Integer cag <cAlternateGlyph:3>Alternate glyphs

for multiple master fonts such as

Tekton Pro MM appear in the Insert

Character dialog box in InDesign. In

this example, 3 represents the third.

Auto pair kerning cAutoPairKern:String capk <cAutoPairKern:Optical>This tag can

include Optical or Metrics (default).

Baseline shift cBaselineShift:Real cbs <cBaselineShift:3>This value can be

between -5000 and 5000 points.

Case cCase:Enum ccase <cCase:Small Caps>Valid values

include Small Caps, All Caps, Caps To

Small Caps, or Normal (default).

Caps To Small Caps is an Open-Type

font attribute.

Character

alignment

cHang:Enum ch <cHang:Top>Valid values include

EmTop, EmCenter (default),

EmBottom, Baseline, ICFTop, and

ICFBottom.

Character skew cSkew:Real csk <cSkew:-25>The value represents the

percentage of character skew from 85

to -85 degrees.

Color: color tint cColorTint:Real cct <cColorTint:80>Specify a tint

percentage.





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

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.


Abbr.Examples and Notes





6-2

Font: family cFont:String cf <cFont:Adobe Garamond>Specify

only the family name. To complete thefont information,also use <cSize>

and <cTypeface>.

Font: point size cSize:Real cs <cSize:18>Specify a point size

between 0.1 and 1296.

Font: typeface cTypeface:String ct <cTypeface:Italic>The values for this

tag depend on which font is used. For

example, Times New Roman uses

Regular while Helvetica uses Plain.

ILG shift cILGShift:Real cilgs <cILGShift:200>Specify a value

between -8640 and 8640.

Kerning cKerning:Real ct <cKerning:50>Kerning cKerning:Real

ct <cKerning:50>Kerning

cKerning:Real ct

<cKerning:50>Kerning cKerning:Real

ct <cKerning:50>

Language cLanguage:String clang <cLanguage:Portuguese: Brazilian>To

use a valid string, type the name of the language as it appears in the

Character palette.

Leading cLeading:Real cl <cLeading:18>This tag lets you

specify a leading value between 0 and

5000. To use default auto leading,

leave value empty (<cLeading:>).

Ligatures cLigatures:Boolean clig <cLigatures:1>1=on (default), 0=off

No break cNoBreak:Boolean cnb <cNoBreak:1>1=on, 0=off (default)

Next break

character

cNextXChars:Enum cnxs <cNextXChars:Column>Valid values

include NoForcedBreak (default),

ColumnBreak,PageBreak, BoxBreak,

OddPageBreak, and EvenPageBreak.

Old style figures cOldStyleFigures:Boolean cosf <cOldStyleFigures:1>

1=on, 0=off (default)







6-2

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>


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>







6-2

C To return an attribute to its default state, type the attribute name followed by a colon (:). For

example, to return to the default leading value, type <cLeading:>.

Attribute Tag Name

Tag

Abbr. Examples and Notes

Align to baseline grid pAlignToGrid:Boolean patg <pAlignToGrid:1>1=on, 0=off

(default).

Alignment of text in

paragraph

pTextAlignment:Enum pta <pTextAlignment:Center> Valid

values include Left, Right, Center, and

Justify. Left is the default value.

Alignment of last line

in paragraph

pLastLineAlignment:Enum plla <pLastLineAlignment:Center>Valid



Alignment of

paragraph body (not

including the last line)

pBodyAlignment:Enum pba <pBodyAlignment:Center> Valid



Balance ragged lines pBalanceLines:Boolean pbl <pBalanceLines:1> 1=on, 0=off

(default)

Drop cap: number of

characters

pDropCapCharacters:Intege

r

pdcc <pDropCapCharacters:1>Drop cap:

number of characters

pDropCapCharacters:Integer pdcc

<pDropCapCharacters:1>

Drop cap: number of

lines

pDropCapLines:Integer pdcl <pDropCapLines:3>

First line indent pFirstLineIndent:Real pfli <pFirstLineIndent:6>

Glyph scaling: desired pDesiredGlyphScale:Real pdgs <pDesiredGlyphScale:1.0>Specify a

value between -0.5 (-50%) and 2.0

(200%). The default value is 1.0

(100%).

Glyph scaling:

maximum

pMaxGlyphScale:Real pmaxgs <pMaxGlyphScale:1.2>The value 1.0

equals 100%.Specify a value between

-0.5 (-50%) and the desired glyph

scaling value.The default value is 0.





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: numberof characters in

shortest word allowed

to be hyphenated

PshortestWordHyphenated:Integer pswh <pShortestWordHyphenated:3>Thisrange 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-2

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


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


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







Nested styles pNestedStyles:Enum pnstyles <pNestedStyles:Character Style

1\,Words\,1\1;CharacterStyle2\,Forced Line Break\,1\,0\;>

Page or columns

break before

paragraph

pBreakBefore:Enum pbb <pBreakBefore:Column Break> This

tag can include Page, Column, or

None.

Paragraph rule above

color

pRuleAboveColor:String prac <pRuleAboveColor:Black>This value

indicates the color for the rule (line)

above the paragraph.This string value

must be a color name (not an

unnamed color definition).


gap color

pRuleAboveGap

Color:String

pragc <pRuleAboveGapColor:Blue>


tint

pRuleAboveTint:Real prat <pRuleAboveTint:80>This value

indicates the tint for the rule (line)

above the paragraph.The value must

be between 0 and 100.


gap tint

pRuleAboveGapTint:Real pragt <pRuleAboveGapTint:80>


gap

overprint

pRuleAboveGap

Overprint:Boolean

prago <pRuleAboveGapOverprint:1>



stroke type

pRuleAboveStroke

Type:Enum

prastype <pRuleAboveStrokeType:ThickThin>


is turned on

pRuleAboveOn:Boolean prao <pRuleAboveOn:1>1=on, 0=off

(default)

Paragraph rule aboveleft indent pRuleAboveLeftIndent:Real prali <pRuleAboveLeftIndent:3>This valueindicates the left indent from the

frame edge or text edge, depending

on the paragraph rule mode.







6-3


mode

pRuleAboveMode:Enum pram <pRuleAboveMode:Text>This value

indicates whether the paragraph rulestarts at the width of the column

(frame) or width of the first line of

text in the paragraph. Valid values

include Text and Column. Column is

the default.


offset

pRuleAboveOffset:Real prao <pRuleAboveOffset:3>This value

indicates the offset from the baseline

to the paragraph rule above.

Paragraph rule aboveright indent

pRuleAboveRightIndent:Real

prari <pRuleAboveRightIndent:3>Thisvalue indicates the right indent from

the frame edge or text edge,

depending on paragraph rule mode.


stroke

pRuleAboveStroke:Real pras <pRuleAboveStroke:2>This value

indicates the line weight for the

paragraph. Specify a value between 0

and 1000.

Paragraph rule below

color

pRuleBelowColor:String prbc <pRuleBelowColor:Black>This value

indicates the color for the rule (line)below the paragraph.This string value

must be a color name (not an

unnamed color definition).


gap color

pRuleBelowGap

Color:String

prbgc <pRuleBelowGapColor:Blue>


tint

pRuleAboveTint:Real prbt <pRuleAboveTint:80>This value

indicates the tint for the rule (line)

below the paragraph.The value must

be between 0 and 100.


gap tint

pRuleBelowGap

Tint:Real

prbgt <pRuleBelowGapTint:80>


gap

overprint

pRuleBelowGap

Overprint:Boolean

prbgo <pRuleBelowGapOverprint:1>









stroke type

pRuleBelowStroke

Type:Enum

prb

stype

<pRuleBelowStrokeType:ThickThin>


is turned on

pRuleBelowOn:Boolean prbo <pRuleBelowOn:1>1=on, 0=off

(default)


left indent

pRuleBelowLeftIndent:Real prbli <pRuleBelowLeftIndent:3>This value

indicates the left indent from the

frame edgeor text edge, depending

on paragraph rule mode.


mode

pRuleBelowMode:Enum prbm <pRuleBelowMode:Text>This value

indicates whether the paragraph rulestarts at the width of the column

(frame) or width of the first line of

text in the paragraph. Valid values

include Text and Column. Column is

the default.


offset

pRuleBelowOffset:Real prbo <pRuleBelowOffset:3>This value

indicates the offset from the baseline

to the paragraph rule below.

Paragraph rule belowright indent pRuleBelowRightIndent:Real prbri <pRuleBelowRightIndent:3>Thisvalue indicates the right indent from

the frame edgeor text edge,

depending on paragraph rule mode.


stroke

pRuleBelowStroke:Real prbs <pRuleBelowStroke:2>This value

indicates the line weight for the

paragraph rule below the paragraph.

Right indent pRightIndent:Real pri <pRightIndent:6>

Rotate roman pRotateRoman:Boolean prr <pRotateRoman:1>This value

determines whether all half-width textin the paragraph is rotated counter-

clockwise to stand upright in vertical

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

Space after paragraph pSpaceAfter:Real psa <pSpaceAfter:4>

Space before

paragraph

pSpaceBefore:Real psb < pSpaceBefore:4>







6-3

Tab ruler settings pTabRuler::x value,tab

type,align on,default, leader

ptr <pTabRuler:48,Center,.,0,;96,Char,x,0

,*;144,Left,.,0,;>A semi-colon (;)indicates the start of a new tab

setting. The x value determines the

distance from the left edge of the text

frame or inset. Tab type includes

Left,Center,Right,and Char (also

called a decimal tab). Align on

determines the character on which a

decimal tab (Char) will align. Default

is a boolean value (0 or 1) that

indicates whether the tab is a defaulttab setting. Leader is a character or

string of characters (such as periods

or hyphens) you want to use as a tab

leader.

Text composition

engine

pTextComposer:String ptc <pTextComposer:Adobe Single-Line

Composer> Specify any composer

available, including the Paragraph

Composer (default) and the Single-

line Composer.

Word spacing: align

single word

pSingleWord

Alignment:Enum

pswa <pSingleWordAlignment:Left>

Word spacing: desired pDesiredWordSpace:Real pdws <pDesiredWordSpace:1.2>Specify a

value between 0 and 10 (1000%). The

default value is 1.0 (100%).

Word spacing:

maximum

pMaxWordSpace:Real pmaws <pMaxWordSpace:1.2>The value 1.0

equals 100%. The default value is

133% (1.3). Specify a value between 0

and 10 (1000%) not less thanDesired value.

Word spacing:

minimum

pMinWordSpace:Real pmiws <pMinWordSpace:0.9>The value 1.0

equals 100%. The default value is 0.8

(80%).Specify a value between 0 and

10 (1000%) not greater than Desired

value.







Table Tags

The following are the tags that InDesign uses for tables.

Attribute Tag Name Tag Abbr. Examples and Notes

Table start TableStart:Real Real tStart <tStart:54>Table start

TableStart:Real

Table end TableEnd tEnd <tEnd>

Row start RowStart rStart <rStart>

Row end RowEnd rEnd <rEnd>

Cell start CellStart:Real Real cStart <cStart:11>Cell start CellStart:Real

Cell end CellEnd cEnd <cEnd>

Column start ColStart

Start headers tStartHeadersOn: Real tshon <tStartHeadersOn:2> Possible

values are 0, 1, 2

0 = Repeat header on every text

column

1 = Repeat header once per frame

2 = Repeat header once per page

Start footers tStartFootersOn:Real tsfon <StartFoodersOn:1>Possible values are 0, 1, 2

0 = Repeat footer on every text

column

1 = Repeat footer once per frame

2 = Repeat footer once per page

Skip first header tSkipFirstHeader:Boolean tsfh <tSkipFirstHeader:1>


Skip first footer tSkipFirstFooter:Boolean tsff <tSkipFirstFooter:1>


Cell: bottom inset tCellAttrBottomInset:Real tcabi <tCellAttrBottomInset:9>

Cell: bottom stroke

color

tCellBottomStrokeColor:

Definition

tcbsc <tCellBottomStrokeColor:Blue>Cel

l: bottom stroke color

tCellBottomStrokeColor:Defi nition

tcbsc

<tCellBottomStrokeColor:Blue>





6-3

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>






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>


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

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>






6-3

Row: stroke

pattern(second

color)

tRowStrokePatSecondColor:

Enum

trspscl <tRowStrokePatSecondColor:

ThinThick>

Row: stroke pattern

(second type)

TRowStrokePatternSecond

Type:Enum

trspst <tRowStrokePatternSecondType:T

hinThick>

Row: stroke pattern

first weight

TRowStrokePatternFirst

Weight:Real

trspfw <tRowStrokePatternFirst

Weight:9>

Row:stroke pattern

second weight

TRowStrokePatternSecond

Weight:Real

trspsw <tRowStrokePatternSecond

Weight:9>

Row:stroke type tRowStrokeType:Enum trst <tRowStrokeType:ThickThin>

Table: column end

pattern (start value)

TTablerColFillPatternEnd

Value:Real

trcfpev <tTablerColFillPatternEndValue:1>

Table: column fill

pattern (first count)

TTableColFillPatternFirst

Count:Real

tcfpfc <tTableColFillPatternFirst

Count:2>

Table: column fill

pattern (second

count)

TTableColFillPatternSecond

Count:Real

tcfpsc <tTableColFillPatternSecond

Count:2>

Table: column fill


tTableColFillPatternStartValue:R

eal

tcfpsv <tTableColFillPatternStartValue:1>

Table: column

stroke color

tColStrokeColor:Definition tcsc <tColStrokeColor:Blue>

Table: column

strokepattern (first

count)

TTableColStrokePattern

FirstCount:Real

tcspfc <tTableColStrokePattern

FirstCount:2>

Table: column

strokepattern

(second count)

TTableColStrokePattern

SecondCount:Real

tcspsc <tTableColStrokePatternSecond

Count:2>

Table: column

strokeweight

tColStrokeWeight:Real tcsw <tColStrokeWeight:3>

Table: fill pattern

priority

tTableFillPatternPriority:Real tfpp <tTableFillPatternPriority:1>

Table: outer bottom

stroke tint

tOuterBottomStrokeTint:Real tobst <tOuterBottomStrokeTint:70>






Table: outer bottom

stroke weight

tOuterBottomStrokeWeight:

Real

tobsw <tOuterBottomStrokeWeight:3>

Table: outer left

stroke tint

tOuterLeftStrokeTint:Real tolst <tOuterLeftStrokeTint:70>

Table: outer left

stroke weight

tOuterLeftStrokeWeight:Real tolsw <tOuterLeftStrokeWeight:3>

Table: outer right

stroke tint

tOuterRightStrokeTint:Real torst <tOuterRightStrokeTint:70>

Table: outer right

stroke weight

tOuterRightStrokeWeight:Real torsw <tOuterRightStrokeWeight:3>

Table: outer top

stroke tint

tOuterTopStrokeTint:Real totst <tOuterTopStrokeTint:70>

Table: outer top

stroke weight

tOuterTopStrokeWeight:Real totsw <tOuterTopStrokeWeight:3>

Table: row end


TTableRowFillPatternEndValue:

Real

trfpev <tTableRowFillPatternEnd

Value:1>

Table: row fill


TTableRowFillPatternFirst

Count:Real

trfpfc <tTableRowFillPatternFirst

Count:2>

Table: row fill

pattern(second

count)

TTableRowFillPatternSecond

Count:Real

trfpsc <tTableRowFillPatternSecond

Count:2>

Table: row fill


TTableRowFillPatternStart

Value:Real

trfpsv <tTableRowFillPatternStart

Value:1>

Table: row keeps tRowKeeps:Real trk <tRowKeeps:3>

Table: row stroke

color

tRowStrokeColor:Definition trsc <tRowStrokeColor:Blue>

Table: row stroke


TTableRowStrokePatternFirst

Count:Real

trspfc <tTableRowStrokePatternFirst

Count:2>

Table: row stroke

pattern (second

count)

TTableRowStrokePattern

SecondCount: Real

trspsc <tTableRowStrokePatternSecondC

ount:2>






6-4

Table: row stroke

weight

tRowStrokeWeight:Real trsw <tRowStrokeWeight:3>

Table: stroke

drawing order

tStrokeOrder:Real tso <tStrokeOrder:3>

Possible values are 0-3:

0 - Best Join

1 - Row Strokes in Front

2 - Column Strokes in Front

3 - InDesign 2.0 Compatability

Table: spacing after tAfterSpace:Real tas <tAfterSpace:9>

Table: spacing

before

tBeforeSpace:Real tbs <tBeforeSpace:9>






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>





6-4

Hyperlink border

highlight

BrdrHilight:Boolean brdrh <BrdrHilight:1>

Hyperlink border

style

BrdrStyle:Enum brdrs <BrdrStyle:1>

Hyperlink border

color

BrdrColor:Real brdrc <BrdrColor:Blue>

Index entry IndexEntry Idx <IndexEntryType:IndexPageEntry>

<IndexEntryStyleUid:0><IndexEntr

yRangeType:

kCurrentPage><IndexEntryDisplay

String:simple pageindex>>

Index entry type IndexEntryType IdxEnType <IndexEntryType:IndexPageEntry>

Index entry range

type

IdexEntryRangeType IdxEnRng-

Type

<IndexEntryRangeType:kForNextN

Paragraphs>

Index entry style IndexEntryStyle IdxEnStyle <IndexEntryStyle:MyStyle>

Index entry next

style

InexEntryNextStyle IdxEnNxt-

Style

<IndexEntryNextStyle:MyStyle>

Index entry numberof

paragraph or page

IndexEntryNumParOrPage

IdexEn-NumPgOr-

Par

<IndexEntryNumParOrPage:30>

Index entry display

string

IndexEntryDisplay

String

IdxEnDispStr <IndexEntryDisplayString:simple

page index>

Index entry sorting

string

IndexEntrySortString IdxEnSortStr <IndexEntrySortString:An index>

Index cross-

reference entrytype

IndexXRefEntryType IdxXrEnType <IndexXRefEntryType:kSeeHerein>

Index cross-

reference entry

custom string

IndexXRefEntryCustomStri

ng

IdxXrEn-

CusStr

<IndexXRefEntryCustomString:abc

>






Special Character Tags

Special Character Value

Auto Page Numbering <0xE0018>

Section Marker <0xE0019>

Bullet Character <0x2022>

Copyright Symbol <0x00A9>

Degree Symbol <0x00B0>

Ellipsis <0x2026>

Paragraph Symbol <0x00B6>

Registered Trademark

Symbol

<0x00AE>

Section symbol <0x00A7>

Trademark Symbol <0x2122>

Em Dash <0x2014>

Em Space <0x2003>

En Dash <0x2013>

En Space <0x2002>

Flush Space <0x2001>

Hair Space <0x200A>

Nonbreaking space <0x00A0>

Thin space <0x2009>

Discretionary hyphen <0x00AD>

Nonbreaking hyphen <0x2011>

Double left quotation mark <0x201C>

Double right quotation

mark

<0x201D>

Single left quotation mark <0x2018>

Single right quotation mark <0x2019>



Trans la t ing InDes ign CS 2 f i l e s6


6-4

TRANSLATING INDESIGN CS 2 FILES

TagEditor can support InDesign CS2 files which are exported directly from InDesign CS2 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 rather references to

the graphics.

WARNINGF

Although InDesign CS files could be exported to InDesign Interchange Format, INX files fromthis version of InDesign CS are not supported by TagEditor.

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 Filter

You can use the InDesign CS2 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 formatting

C Use font mapping

C Make destinations of external locations translatable

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 2006 > Filters > Filter Settings. The

Filter Settings application opens.

2 Click InDesign CS2 filter settings and select an option. Follow the directions shown for

each setting to make changes.

3 Click Apply to save your changes.

4 Click Exit to close the application.





6-4

TIPE

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

Modifying the InDesign CS2 Filter Settings File

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

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

IndesignFilter_1_0_0_0.xml and it is installed by default to C:\Program Files\SDL

International\T2006[_FL]\TT\.

The settings in the filter settings file determine which elements of the InDesign CS2 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.

NOTED

C We recommend that only advanced XML users modify the InDesign CS2 filter settings file.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 Interchange format files

You can open files which have an .inx extension in TagEditor.

1 From the Start menu, open SDL Trados 2006> TagEditor.

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

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

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





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 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 files. In

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

Select InDesign CS2 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.



Conc lu s ion6


6-4

CONCLUSION


Task Checked?

Set a logical story order in an InDesign file. ✔

Prepare InDesign files for translation. ✔




Know how to use the Story Collector batch functions. ✔


Know that InDesign CS 2 files can be opened directly in TagEditor ✔



Conc lu s ion6




Chapte

VENTURA FILES


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



Overv i ew7


OVERVIEW

Use Ventura’s internal export functionality to produce a TXT file that can be easily translated. This

TXT export format converts easily to TRADOStag in TagEditor, the translating environment for

Translator’s Workbench. You simply open the Ventura TXT export format file in TagEditor to

convert it to TRADOStag.


To find out more about TRADOStag, See TRADOStag bilingual file format on page 1-4

SDL Trados supports TXT export files from Ventura 5 and higher. If you have Ventura 10, you can

also export the files to HTML and use the ML Format guidelines in Chapter 2. The Ventura filter

supports codepage 1252 only (Windows Western Latin 1 ANSI).

Key Term Definition


C VP – Ventura files have a VP extension

C TXT – a tagged text format that is produced by Ventura’s internal export functionality.

C Export file – a tagged text file (TXT) containing untranslated text. This file is produced by

Ventura’s internal export functionality.

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

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


Translation of a Ventura file involves the following stages:

1 Prepare your Ventura source files for translation.

2 Create a folder structure.

3 Export all stories from the Ventura file to a text file (TXT).


5 Import the file back into Ventura.





7-


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.


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.



5 Translate the files in the target TXT folder using Translator's Workbench and TagEditor,

and save the translated files in your target 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.





Preparing the Text in Ventura Files

You should carry out the following preparation on Ventura files:

CTag all text frames.

C Place callout text in frames and tag all frames.

C Anchor all graphics or free form frames.

C Automatically generate variables, auto-numbered lists, cross-references, headers and footers.

C Open the files in Word. If there are page breaking tags, delete them using Word’s search and

replace function.

C Create an ancillary file for text which is not exported to the tagged text format (callout text, text

in headers and footers and frame text). After translation incorporate the ancillary file into thetranslated Ventura file.

C Use hyphenation, and remove manually inserted page breaks. The translation might become

significantly longer than the original.

NOTED

If your document was written with an English version of your DTP package, use an Englishversion for file preparation; if it was written with a Japanese version, use a Japanese version,and so on. This is important because style names might be different in foreign language

versions.

Exporting Ventura Text

To export text:

1 Click into the chapter and choose the Export Text command from the File menu. The Export

Text dialog box appears. Specify ANSI text (TXT) in the Save As Type combo box, and do not

check the Export Without Corel Ventura Markup check box.

2 Create one export file for each chapter. Try to assign meaningful file names to theexport files, so you can easily import them back into the right locations after

translation.

3 We recommend that you copy the export file in your source TXT folder into your target

TXT folder as it makes it less likely that you overwrite the source TXT file by mistake.



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

Translate your Ventura files using Translator's Workbench and TagEditor. 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






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


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





<P(ANY NUMBER)> Point size Emphasis

<R> Soft Return Placeholder<SA> Small caps Emphasis

<U> Underline Emphasis

<V> Subscript Placeholder

<W[1-9]> TrueType font weights Emphasis

<X> Strikethrough Emphasis

@ (ANY TEXT) = Format for all

paragraph tags.

Structural tag The @ character has

to be the firstcharacter in the line

at the beginning of

the paragraph

<(ANY TAG)*> or

<(ANY TAG)255>

Return to default Emphasis Appears a lot in

Ventura Publisher 7.

For example, a

double underline

applied to some

characters in a

normal sentencemight 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

Tag Description Category Notes





7-

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 only

HEADERS() 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

L0() Table formatting Structural tag in Tables only




LEFTCOLSKEW() Table formatting Structural tag in Tables only

ROWHEIGHT Table formatting Structural tag in Tables only

RULE() Table formatting Structural tag in Tables only

SKEWLEFTCOLTEXT Table formatting Structural tag in Tables only

SKIPFIRSTCELLSKEW Table formatting Structural tag in Tables only

TOPROWSKEW() Table formatting Structural tag in Tables only

TOPROWSKEWTEXT() Table formatting Structural tag in Tables only

VERSION() Specify table definition

and formatting

Structural tag Not used before

Ventura version 7

VGRID() Table formatting Structural tag in Tables only

VGUTTER() Table formatting Structural tag in Tables only

VJBOT() Table formatting Structural tag in Tables only




Conc lu s ion7


CONCLUSION


VJTOP() Table formatting Structural tag in Tables only

WIDTH() Table formatting Structural tag in Tables only

Task Checked?

Prepare Ventura files for translation. ✔

Export text for translation. ✔

Import translated text. ✔






Chapte

WORD AND RTF HELP FILES

Section 5 of the File Formats Reference Guide explains how to

work with Microsoft formats.

Chapter 8 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

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.



Se lec t ing a Work f low fo r Word F i l e s8


8-

SELECTING A WORKFLOW FOR WORD FILES

There are two ways you can translate a Word document. You can use Translator’s Workbench with

Word. When using Translator’s Workbench with Word to translate documents, all files are converted

to Rich Text Format (RTF). We refer to the Microsoft Word translation workflow as the RTF

workflow.

You can also use TagEditor to open and translate a Word document as described in Chapter 9,

Translating Word Files in TagEditor . When using TagEditor to translate Word documents, the files

are converted to the TRADOStag (TTX) format. The TTX format is XML-based and uses tags to

preserve document structure and formatting. We refer to the TagEditor translation workflow as the

TTX workflow. To compare the RTF workflow in this chapter to the TTX workflow, see TTX

Workflow on page 9-3 .

Translate Word files using the TTX workflow when you want to do the following:

C Run the Context TM process on the file before translating the remaining content.

C Translate files from multiple file formats such a Word, Excel, and HTML using the sameeditor. The translation memory can be shared since all the documents are tagged formats andno RTF formatting is stored in the translation unit.

C Take advantage of font handling capabilities for complex script languages, such as Arabic,Hebrew, Thai, Vietnamese, and Indic family, or East Asian languages, such Chinese, Japanese,and Korean.

If you start a Word translation project using the TTX workflow, complete it in the same workflow.Do not switch between using the RTF workflow and the TTX workflow since TTX workflow TUs are

different from RTF workflow TUs and your translation reuse rate may be affected.



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


8-

PREPARATION OF MICROSOFT WORD FILES

You may need to prepare your Word document(s) before translating them using Translator’s

Workbench. The extent of your preparation will depend on the formatting of your document and the

source and target languages of your translation.

Some issues you should consider when authoring Word documents that will be translated:

C File size – when translating using Translator's Workbench, files grow to approximately twicetheir size because the original text is stored in the file with the translated text until the clean upstage. If your machine specification is not adequate or the translation memory is large, theresponse time of the translation memory is affected. Keep files to a reasonable size.

C Graphics – graphics should always be linked rather than embedded. If graphics areembedded, the file size is much larger than it is when they are linked. Request the art files from

the originator of the document.

C Styles – Translator's Workbench automatically applies the paragraph style of the sourcesentence to the target sentence. However, if the base paragraph style has been changedmanually (local override), this change may not be applied to the target sentence. Each time thisoccurs, the translators have to apply the style manually. As a rule, styles should only bemodified using the Style command in Word, rather than changing individual styles manually.

C Cross-references – Use the template, Bookmark Handler.dot to prepare documentscontaining hidden cross-references and to restore the cross-references after the translationprocess. The template contains the two macros: PrepareBookmarks andRestoreBookmarks. For more information on the template and how to use it, see “Using

the Bookmark Handler macros” on page 8-6.

C Tracked Changes – tracked changes must not be present in the Word documents to betranslated with Translator’s Workbench. If your Word documents contain tracked changes,Translator’s Workbench displays a warning message. Consult the originator of the documentabout accepting or rejecting revision marks. Then, deactivate the feature in each Worddocument before translating it.

C Comments – Translator’s Workbench does not support comments during interactivetranslation or clean up. Remove all comments before translation. You can do this with a singleFind and Replace run on the files, replacing comments with nothing. For more information,see the Word Help.

C Unused styles and fonts – every Word document has a style sheet and a font table. Thesecontain all the paragraph styles, character styles and fonts defined in the Word document.Often style sheets contain many styles that are not used. Similarly, the font table can containmany unused fonts. Removing the unused styles may help optimize the response timebetween Translator’s Workbench and Word. Translator's Workbench allows you to strip outany unused styles and fonts from a document, or series of documents before translation, asfollows:





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\T2006[_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


8-

TRANSLATION OF MICROSOFT WORD FILES

Below are some of the common features of Word documents and how Translator’s Workbench

handles them. For more examples of basic translation situations in Word, see the Translator’s

Workbench User Guide.

Index Entries

Translator's Workbench treats index entries (“XE” fields) embedded in sentences as subsegments

(segments within segments). They are opened separately within a translation unit and are stored

separately in the translation memory. For example, the following text occurs in your document for

translation:

When opening this sentence for translation using the Open/Get function, Translator’s Workbench

searches the translation memory for a match and places segment delimiters around the text for

translation. The index entry is treated as a subsegment. It is surrounded by its own delimiters and

allocated its own number, as shown below:

Where there is more than one subsegment, each one is allocated a separate number. For example,

where a segment contains two index entries, the first is treated as subsegment number 1 and the

second as subsegment number 2.

To translate sentences with index entries:

1 Enter the translation for the main segment in the target field.

2 Position your cursor where you want to insert the index entry in the translated target

segment. Press [Alt] + [1]. Translator’s Workbench inserts an empty index (XE) entryand places the subsegment delimiters around it. The cursor is positioned between the

quotes. You can now enter the translation for the index entry.

3 If there are more index entries, press [Alt] + [2] to insert the second one, [Alt] + [3] to

insert the third, and so on.

4 Once you have completed translating both the main segment and all index entries,

click Set/Close Next Open/Get to continue translating.





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





NOTED

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.

5 Continue translating the main segment or the other footnotes in the main document.Repeat steps 1 to 4 for all other footnotes contained in the main segment.

Translator's Workbench supports a maximum of 19 subsegments (footnotes or index entries) per

main segment. To place subsegments 1 to 9, press [Alt]+[1] to [Alt]+[9]. To place subsegments 10 to

19, press [Alt]+[Shift]+[0] to [Alt]+[Shift]+[9].

Footnotes after Translation

After you translate a footnote and return to the main document, the footnote number in the source

language disappears. The superscript contains the code fn instead of an absolute footnote number.The absolute numbers have changed, both in the source and in the target fields. The numbering now

begins or continues from the first untranslated footnote in the source segment until the last

translated footnote in the target segment.

For example, in the following screenshot, the first footnote has already been translated (as indicated

by the fn code). The other two footnotes have not yet been translated. Absolute numbering

continues from the previous paragraph, ignores the translated footnote with the fn code and goes to

the first untranslated footnote in the source segment (absolute footnote number 5, subsegment

number 2). It then continues with the translated footnote in the target segment (absolute footnote

number 7, subsegment number 1).

This numbering system indicates which footnotes have already been translated and are in the

translation memory. When you finish translating, your target segment should contain the same

number of footnotes as the source. Each source footnote is assigned an fn code.





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.



P ost - t r ans la t ion P rodu c t ion fo r Word F i l e s8


Colored Text

If you plan to use Translator's Workbench Translated Text Colours option, check first if it clashes

with the use of color in the source documents.

Non-translatable Text

You can instruct Translator’s Workbench to ignore text in paragraph or character styles that does not

require translation. Use the Non-translatable Text tab in the Setup dialog box in Translator’s

Workbench to identify character styles that do not require translation; use the Non-translatable

Paragraphs command in Translator’s Workbench to specify the names of paragraph styles that do

not require translation. For more information, see the Translator’s Workbench online help.

Spell-checking and ProofreadingWhen you spell-check, you want Word to check the translated segments only. You should turn off

hidden text (or apply the no proofing attribute to all hidden text using Word’s Replace command) for

the spell-checking stage. Also, if you want to proof a hard copy, you only want to print your translated

text, not the source. Ensure that hidden text is not specified as one of the printing characters.

This section presents a list of guidelines for post-translation production on Microsoft Word

documents. Not all of these steps may apply to your document(s).

POST-TRANSLATION PRODUCTION FOR WORD FILES


documents. Not all of these steps may apply to your document(s).


C After clean up, check the documents for errors.

C Reapply the document template.

C Place the translated artwork, and check that call out text has been translated and displays fully.

C Check line breaks, page breaks and pagination.

C Ensure that cross-references are accurate and work correctly. The Bookmark Handler.dot template allows you to restore cross-references.

C Check that headers and footers have been translated and display correctly.

C Regenerate the table of contents and index files.



Work ing w i th RTF He lp F i l e s8


8-1

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.

WORKING WITH RTF HELP FILES

This section describes some of the characteristics of RTF-based Windows help files, outlines how to

prepare the files for translation and provides some guidelines for post-translation production. There

are two ways you can translate RTF-based help files. You can use can use Translator’s Workbench

with Word.

You can also use TagEditor to open and translate an RTF help file document. When using TagEditor

to translate RTF help documents, the files are converted to the TRADOStag (TTX) format. The TTX

format is XML-based and uses tags to preserve document structure and formatting.

Translate RTF help files using the TTX workflow when you want to do the following:


C Translate files from multiple file formats such a Word, Excel, and HTML using the sameeditor. The translation memory can be shared since all the documents are tagged formats andno RTF formatting is stored in the translation unit. This is an important plus when you havelegacy help files.

C Take advantage of font handling capabilities for complex script languages, such as Arabic,

Hebrew, Thai, Vietnamese, and Indic family, or East Asian languages, such Chinese, Japanese,and Korean.

If you start a translation project using the TagEditor, complete it in TagEditor. Do not switch between

using the Translator’s Workbench and Word and TagEditor for the same set of files as your

translation reuse rate may be affected. For more information on translating RTF help files in

TagEditor see Chapter 9,

Characteristics of RTF Help Files

Online help files for translation are usually in RTF (Rich Text Format) format. In most cases, thesefiles are created either directly in Word and/or using a help authoring tool, such as RoboHelp.

RTF help files usually contain the following elements:

C Custom footnotes, for example, $, # , K and +.

C The $ footnote denotes the topic title.

C The # footnote is used to identify help pages with a unique ID.



Work ing w i th RTF He lp F i l e s8


C The K footnotes refer to the keywords found in the help index.

C The + footnote indicates browse sequences that allow the user to browse through topicssequentially in the compiled help file.

$ and K footnotes require translation, while # and + footnotes do not.

C Formatted text, for example, double or single underlined text. Such formatting indicates a linkto a related topic, such as a jump or popup (hypertext function). The double or singleunderlined text of a jump or popup requires translation.

C Hidden text, which normally follows immediately after double or single underlined text. It is

used to link help topics with related topics (jumps or popups). Hidden text is never translated,

but it must be correctly linked to its corresponding double or single underlined text.

Translator’s Workbench facilitates the translation of these specific features in RTF help files.

Jumps and popups ( double- or single-underlined text followed by hidden text are recognised fortranslation. The jump or popup text which is typically a reference to a help topic is translatable. The

hidden text which is typically the unique help context ID is treated as an internal tag and therefore

is not made available for translation.

To keep the formatting use the Copy Source command and overtype rather than entering text directly

into the yellow editing area.



P repara t ion o f RTF He lp F i l e s8


8-1

PREPARATION OF RTF HELP FILES

RTF help files share many features found in Word documents. For more information, see

“Preparation of Microsoft Word Files” on page 9-5. Common issues include:

C size of files

C revision marks/tracked changes

C comments

C unused styles and fonts

In addition, you should consider the following points for file setup of RTF-based Windows help files:

C Jumps and popups – Never apply a paragraph style containing the double underline property

where there is also hidden text in the paragraph. This leads to problems for Translator'sWorkbench in recognizing the context ID as a placeable. The context ID should be formattedas hidden only.

NOTED

When you translate RTF-based Windows help files using Translator's Workbench, the reservedstyles tw4winJump and tw4winPopup are applied to jumps and popups, respectively. This doesnot affect the functionality of the help file in any way.

C Footnotes – Footnotes are one of the key characteristics of RTF-based Windows help files. Themethod used by Translator's Workbench to handle footnotes varies according to the version of

Word being used to translate the help files, as described below.

C All documents in RTF format should be converted to .doc before translatio. You must to thisbefore your translate the files in TagEditor.

Custom Help Footnotes

During translation in the Word editing environment, Translator's Workbench creates a temporary

document called TW4WinFootnote.doc in which you translate footnotes.

In addition, for keyword footnotes, Translator's Workbench can treat each phrase occurring between

semicolons as a separate segment. This increases the likelihood of the same segment occurring

again and facilitates the translation process. To activate this option, do the following:

C Modify the existing semicolon Skip Rule in your translation memory.

C Add a new segmentation rule for the semicolon to the existing End Rules.





Follow these steps to change the semicolon Skip Rule:

1 Open the translation memory in which you want to change the segmentation rules in

exclusive mode. Select Setup on the File menu. The Setup dialog box opens.

2 Click the Segmentation Rules tab. Check Skip Rules to display the semicolon rule. In

the Trailing Whitespaces box, change the value to 1. Translator's Workbench now

interprets the semicolon as a skip character only if it is followed by at least one

character space.

Follow these steps to add a new End Rule for the semicolon:

1 In the Segmentation Rules tab, check End Rules. The set of End Rules that has been defined for

the current translation memory is displayed.

2 Click Add to add a new rule to the existing ones. Enter a name for the new rule, for

example, Semicolon in Keyword FNs.

3 From the Stop Character drop-down list, select the semicolon (";"). Change the Trailing

Whitespaces value to zero. Translator's Workbench now interprets the semicolon as a

stop character if it is not followed by at least one character space. This is typically the

case in keyword footnotes in online help files.





Turning Graphics References into Placeables

You can exclude graphics references, for example {bmc sample.bmp}, from the translation process by

creating and applying a custom character style to them in Word. Then you can select the custom style

as a non-translatable style in Translator’s Workbench.

To create custom character style to graphics references:

1 In Word 2002 or 2003, select Styles and Formatting on the Format menu. The Styles and

Formatting dialog box appears. Click New Style and the New Style dialog box opens.

In Word 2000, select Styles on the Format menu. The Styles and Formatting dialog box

appears. Click New and the New Style dialog box opens.

2 Under Name, assign a name to the new style, for example, graphicrefs. Under

Style type, select Character. Accept the default Default Paragraph Font under Style based on (Based on in Word 2000). Activate the Add to template option. If you wish,

select Font on the Format shortcut menu and assign a color to the new style, for

example, dark blue. This distinguishes graphic references from the rest of the text in

the RTF file. Click OK to confirm the new character style definition.

NOTED

If you plan to use Translator's Workbench Translated Text colours option, check first if it clasheswith the use of color in the source documents.





8-2

After creating the custom character style, you must apply it to all graphic references. Follow these

steps:

1 In Word use the Find and Replace dialog box to apply the custom character style:

C In the Find what input field, type \{bm*\}. Check Use Wildcards (you may have to clickMore to display this option). This search criterion finds all occurrences of graphicsreferences. For more information on wildcard searching, see the Word online help.

C In the Replace with box, type ^&. This means that the text in the Find what field will bereplaced by itself and the graphics reference text will remain exactly as is.

C With the cursor still in the Replace with box, click Format. Select Style and select thecustom style from the Replace With Style list. Click OK to confirm.

2 Apply the new custom style to all graphics references using your preferred method of

replacement.


For details on how to apply a non-translatable character style to the custom character style, seethe Translator’s Workbench User Guide.





After you apply the non-translatable style, it appears in Translator’s Workbench as follows:



Trans la t ion o f RTF He lp F i l e s8


8-2

TRANSLATION OF RTF HELP FILES

The tips about the translation of Word documents also apply to RTF-based Windows help files. The

following RTF help file features, and how Translator’s Workbench treats them, is explained in this

section:

C Footnotes

C Jumps and popups

C Spell-checking and proofreading

Footnotes

The following example describes Word footnotes. Translator's Workbench always treats keyword

and title footnotes as separate segments in Word. When the cursor is positioned beside a footnote

symbol (such as $) and Open/Get is clicked, Translator's Workbench opens a temporary

document (TW4Win Footnote.doc) for translating the text inside the $ footnote.

Enter the translation in the target field and then click Set/Close Next Open/Get to return to the

main document or to move on to the next footnote symbol.





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





8-2

Spell-checking and Proofreading

When you spell-check, you want Word to check the translated segments only. You should turn off

hidden text (or apply the no proofing attribute to all hidden text using Word’s Replace command) for

the spell-checking stage. Also, if you want to proof a hard copy, you only want to print your translatedtext, not the source. Ensure that hidden text is not specified as one of the printing characters.

Translating RoboHelp Files

If you are translating RoboHelp DOC or RTF files using Translator's Workbench while the

RoboHelp toolbar is active, there may be some conflicts between the two toolbar macro sets. The

following procedure is recommended for RoboHelp files:

1 Open the file for translation in Word.

2 Detach the RoboHelp template (robohelp.dot). Select Templates and Add-ins on

the Tools menu. If you do not specify a new template, Word automatically applies the

default template normal.dot.

3 Translate the file in Word using Translator's Workbench.

4 Clean up the translated file using the Clean Up command in Translator’s Workbench.

Keep an unclean copy of the bilingual files for reference.

5 After cleaning up the translated file, re-apply the RoboHelp template.

6 Compile the help system in RoboHelp.

7 If you need to implement any changes in the translated file, implement them in the

segmented bilingual files and run the Clean Up command again.

8 Repeat steps 4-7 as necessary.



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.


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.

NOTED

Switch off protection for particullar reference type.

This is only possible before forward conversion (opening a file).

> You would need to edit Word_1_0_0_0.xml, by deleting or commenting out

> following:

> <NonTranslatableText>

> <NonTranslatableTextStart>{bmc</NonTranslatableTextStart>

> <NonTranslatableTextEnd>}</NonTranslatableTextEnd>

> </NonTranslatableText>

NOTED

> Also settigs manager could be used for that.



Conc lu s ion8


8-2

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.

✔



Conc lu s ion8




Chapte

TRANSLATING WORD FILES IN

TAGEDITOR

Word files created in Word 2000, Word XP (2002), and Word

2003 can be translated using TagEditor as an alternative to

using the RTF workflow as described in chapter 8. This chapter

explains the following aspects of translating Microsoft Word

files in TagEditor:

C Comparing the RTF workflow with the TTX workflow forWord documents

C TTX translation workflow

C Preparing Microsoft Word documents for translation,

translation situations and tips for post-translationproduction

C The Filter Settings application which is designed to allowyou change settings in the Word filter

9





SELECTING A WORKFLOW FOR WORD FILES

There are two ways you can translate a Word document. You can use Translator’s Workbench with

Word as described in Chapter 8, Word and RTF Help Files . When using Translator’s Workbench

with Word to translate documents, all files are converted to Rich Text Format (RTF). We refer to the

Microsoft Word translation workflow as the RTF workflow.

When using TagEditor to translate Word documents, the files are converted to the TRADOStag

(TTX) format. The TTX format is XML-based and uses tags to preserve document structure and

formatting. We refer to the TagEditor translation workflow as the TTX workflow. To compare the

TTX workflow in this chapter to the RTF workflow, see RTF Workflow on page 8-4 .

Translate Word files using the TTX workflow when you want to do the following:


C Translate files from multiple file formats such a Word, Excel, and HTML using the sameeditor. The translation memory can be shared since all the documents are tagged formats andno RTF formatting is stored in the translation unit.

C Take advantage of font handling capabilities for complex script languages, such as Arabic,Hebrew, Thai, Vietnamese, and Indic family, or East Asian languages, such Chinese, Japanese,and Korean.

If you start a Word translation project using the TTX workflow, complete it in the same workflow.

Do not switch between using the RTF workflow and the TTX workflow since TTX workflow TUs are

different from RTF workflow TUs and your translation reuse rate may be affected.





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.

5Analyse 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.

C The workflow in TagEditor supports Word 2000, XP and 2003, but is optimized for use with

Word XP and 2003 files.





9-

Setting the TTX Workflow Translation Memory Option

Before translating Word documents in TagEditor, you need to configure the translation memory to

use the TTX workflow in Translator’s Workbench.

To set the TTX workflow option:

1 Launch Translator’s Workbench from the Start menu on your computer.

2 Select Options > Translation Memory Options.

3 Select the Tools tab.

4 Select the option TRADOStag XML Workflow for Word .doc files and click OK.





Testing the TTX Workflow

We recommend that you test the TTX workflow using a copy of the Word document you want to

translate. To test the workflow in TagEditor:

1 Update all the fields in a document by selecting Ctrl+A in Word to choose the entire document,then press F9 to update all the fields. Save the Word document and exit Word.

2 Open the Word document in TagEditor.

3 Save the Word document as a bilingual file and translate one of the segments.

4 Save the bilingual file as a target file and open the target file in Word.

If the file has a problem opening in Word, try troubleshooting the file by reviewing the issues listed

here. If the file will not make a complete round trip through the TTX workflow, you can use

Translator’s Workbench with Word for your translation but you will not be able to use Context TMor other TTX workflow benefits.

Word Document Preparation Tips

Some issues you should consider when authoring Word documents that will be translated:

C File Permissions – When using TagEditor to translate a Word document, make sure thepermission settings for the file is set to Unrestricted Access in Word 2003.

C Shared Workspaces – When using TagEditor to translate a Word document, make sure thereare no shared workspaces active for the file. This feature is only available in Word 2003.

C Protected Documents – Protected documents should be unprotected before localization.Consult the originator of the document to get an unprotected copy of the file before opening itin TagEditor.

C File Versioning – Word documents with multiple versions cannot be opened in TagEditor.Save the file to a new name and delete the versions in Word before translating the file usingTagEditor.

C Frames – If you are working with a document that uses frames, save a copy of the document

without frames before opening it in TagEditor.

C Drop Caps – When a document uses Drop Caps, the initial letter is tagged as a separateparagraph by TagEditor. You can select Format > Drop Cap > None in Word to turn off thefeature before opening the document in TagEditor to keep the word as one paragraph. Notethe type of Drop Cap used so you can return the formatting to its original state during post-translation processing of the Word document.





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.





Using the Filter Settings application for the Word Filter

To modify some of the most commonly changed settings in the Word filter settings file, use the SDL

Trados Filter Settings. The settings you can modify using the SDL Trados Filter Settings are:

C Order of text boxes

C Line breaks

C Asian and Complex Script fonts

C Non-translatable styles

C Non-translatiable footnotes and endnotes

C Non-translatable texts

C Display formatting and font-mapping

C Font adaptation









9-

2 Click Word filter settings and select an option. Follow the directions shown for each

setting to make changes.



TIPE


Modifying the Word Filter Settings File

During conversion to and from TRADOStag, the Word filter processes content according to

instructions that are outlined in the Word filter settings file. The name of this file isWord_1_0_0_0.xml and it is installed by default to:

C:\Program Files\SDL International\T2006[_FL]\TT\.

The settings in Filter Settings determine which elements of the Word 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.

NOTED

C We recommend that only advanced XML users modify the Word filter settings file. Before

making any changes, create a backup of the original file.

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

Fonts

Complex script and Asian language fonts may display differently than Latin fonts due to how Word

handles these fonts. The following table lists where font changes may be made, either in TagEditor

or by manually changing the font mapping. settings in the Word filter.

Direction Applies To Description

Asian - Latin

Latin - Asian

Complex Script - Latin

Latin - Complex Script

Formatting applied

directly to

characters

When writing to particular language, users can

exchange one font for another. See section about font

mapping below.





Font Mapping for Asian and Complex Script Characters

Font mapping works only for fonts applied directly to characters. These fonts are identified through

usage of the cf tag, which represents character formatting. Fonts used in font mapping must already

be present in the Word file. The following fonts are included with the Word filter and will be added

to the TTX file if not already present.

C Arial Unicode MS

C SimSun

C PMingLiU

C MS Mincho

C Mangal

C Tahoma

C Code 2000

Complex Script - Latin

Latin - Complex Script

Plain Styles only

(paragraph and

character)

The direction of text will be changed automatically for

all paragraphs and styles. When previewing partially

translated documents the direction of both thetranslated and non-translated text may be the same -

depending on the target language.

Direction Applies To Description





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>

<Font>Batang</Font><Font>BatangChe</Font>

<Font>Dotum</Font><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 the Tahoma font. All other fonts will be mapped to Arial Unicode MS.





The following table lists the XML elements and provides a description:

NOTED

You can contact your local SDL Business Consultancy for assistance with setting up fontmapping rules.

Element Description

FontMappingRules Contains one or more FontMappingRule elements

FontMappingRule This is a rule to be applied to the font name. Contains: one or

more Font or AllFonts tags, one or more FontType or

AllFontTypes tags, one or more LanguageAndRegion or

AllLanguagesAndRegions tags, and one ApplyFont tag.

Font Font name to which FontMappingRule applies. There can be

one or more font names in a rule.

AllFonts Rule applies to all fonts. If there are more specific rules to beapplied (with explicit names) they should go first in the list.

FontType FontType to which FontMappingRule applies. There can be

one or more font types in a rule. Available font types: Latin,

ComplexScripts, Asian

AllFontTypes Rule applies to all fonts types. If there are more specific rules

to be applied (with explicit names) they should go first in the

list.

LanguageAndRegion Language and region of the text/font to be displayed orwritten back. This is a .NET format. Example "de-DE" -

german (germany). There can be one or more such tags. See

Appendix A, Supported Languages for a complete list of

language and region codes.

AllLanguagesAndRegions Rule applies to all languages and regions. If there are more

specific rules to be applied (with explicit names) they should

go first in the list.

ApplyFont Font name to be applied. If font name, language, and region

are the same like in the rule font name is changed to name set

in this tag.





9-1

Non-translatable text

You can define particular text to be non-translatable.

Non-translatable styles

You can add styles that you do not want to be translated.

Display formatting

You can choose how you want to see display formatting information or not.

Font adaptation

You can choose to modify fonts in Word files so that they are easier to read in TagEditor.





9-1

When you see a forward slash (/) before a tag name, such as /paragraph it indicates the end of the

area where the tag is applied. When the slash appears after the tag name, such as field/, it indicates

that the tag begins and ends in that location.

Field Codes

Many of the features in Word are represented as field codes. In TagEditor, these field codes are

typically represented by a placeholder tag in the main segment and are translated in a separate

paragraph. Each field code type is represented by a paragraph tag such as <fieldinfotype="0x3">. The following example shows how TagEditor displays a cross-reference:

A translatable content tag pair is used when part of the field code can be localized.

field Marks a field such as an index entry, a number,

or macro button. See Field Codes on page 9-15

for a list of fields.

footnote

endnote

comment

textbox

Marks the beginning of the tags related to the

corresponding type of text. Usually, there a

paragraph tag immediately after this tag. The

translatable text is enclosed in the paragraph

tag.

text Contains text that cannot be translated in

TagEditor. This text can be manually translated in

post-production.

Tag Description





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-1

Index entries

Index entries are listed after the paragraph where the index entry field codes are inserted. The index

entries use placeholders tags in the segment and the index entry content is translated in the

following paragraphs marked by a translatable content tag pair. If you have multiple index entries ina paragraph, the index entry text is listed in the order of placement.

TIPE

C When translating index entries, place the "field" tag in the appropriatelocation in the translation.

C Translate the index entries in the order of placement after the paragraph.Refer to the translated paragraph to help make the connection between theplaced field tag and the translated content.





Headers and Footers

TagEditor treats headers and footers as segments. Regardless of where the header and footer text

were placed in the Word document, the header and footer text is found at the beginning of the file

in TagEditor. Empty tags may appear even if there is no header or footer text.

TIPE

Selecting View > Header and Footer while your document is open in Word can cause empty tagsto appear in the TTX file.

Each type of header and footer has a separate tag.

The header and footer tag types include:

C HeaderForEvenPages

C HeaderForOddPages

C HeaderForFirstPageOfSection

C FooterForEvenPages

C FooterForOddPages

C FooterForFirstPageOfSection

C FootnoteSeparator

C FootnoteContinuationSeparator

C FootnoteContinuationNotice

C EndnoteSeparator

C EndnoteContinuationSeparator

C EndnoteContinuationNotice

Each tag type corresponds to the appropriate Word header or footer style.





9-1

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.





Comments

Comments have a reference tag put in place to mark the location of the comment. The reference tag

includes the initials and the comment number. The translatable text is in the following paragraph,

which is wrapped by a comment tag pair. When you have multiple comments, you can refer to thereference tag to make the connection between the translated paragraph and the comment tag.

Text boxes

Text boxes are listed after the paragraph where the text box field codes are inserted. The translatable

text is in the following paragraph, which is wrapped by a textbox tag pair.





9-2

Tables

Tables are broken out into table, row, and cell tags. A paragraph tag is associated with each item of

translatable text.

NOTED

Tables created in Word 2000 in a Complex Script and translated to a Latin-based language areordered right to left when saved to a target file in TagEditor. Save the file in Word XP (2002) orWord 2003 before opening in TagEditor to order the text left to right.





RTF Help Translation Workflow

Translation of an RTF help file involves the following stages:

1Create 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.



P ost - t r ans la t ion P rodu c t ion fo r Word F i l e s9


9-2

POST-TRANSLATION PRODUCTION FOR WORD FILES


documents. Not all of these steps may apply to your documents.


C After clean up, checking the documents for errors.

C Reapplying the document template.

C Regenerating the table of contents, table of figures, table of authorities, and index. To updateall the fields in a document, press Ctrl+A in Word to select the entire document, then press F9 to update all the fields.

C Placing the translated artwork and checking that call out text has been translated and displays

fully.

C In Word 2000, make sure tables display the contents in the desired text direction: left to rightif translating from Complex Script to Latin, and right to left if translating from Latin toComplex Script,

C Reapplying any Drop Cap styles removed before translating the text.

C Checking line breaks, page breaks and pagination.

C Ensuring that cross-references are accurate and work correctly.

C Checking that headers and footers have been translated and display correctly.

C For some Complex Script or Asian languages, you may need to manually set the font orchange a font style for proper text viewing. Changing the font in the style definition for theNormal style typically updates the font for most, if not all, other styles. We recommend editingthe style definitions whenever possible.

C Borders and Shading information may not be present in the final translated document. Makesure you keep a copy of the source file so you can re-apply the formatting after translation.

NOTED

If at this stage you choose to update any text, remember to open the Word document inTagEditor and run the Clean Up command in Translator’s Workbench to update the translationmemory. You cannot switch from the TTX workflow to the RTF workflow for this step.



Conc lu s ion9


CONCLUSION


Task Checked?

Prepare Microsoft Word files for translationin 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 ✔



Chapte

MICROSOFT POWERPOINT

DOCUMENTS

This chapter explains the following aspects of translating

Microsoft PowerPoint documents:

C PowerPoint document translation workflow

C Preparing PowerPoint documents for translation

C PowerPoint features during translation


C Filter Settings application

10



Overv i ew10


OVERVIEW

This chapter outlines the translation process that applies to Microsoft PowerPoint documents. It

explains how to prepare PowerPoint documents for translation and shows you to how to handle

PowerPoint-specific features during translation.

Both Translator’s Workbench and TagEditor provide direct support for the following PowerPoint

document formats:

C PPT – PowerPoint presentation

C PPS – PowerPoint show

C POT – PowerPoint design template.

FOR MORE INFORMATION

V C For more information about the TagEditor editing environment, see theTranslator’s Workbench User Guide.

Requirements

To process PowerPoint documents in Translator’s Workbench or TagEditor, you must have

Microsoft PowerPoint installed on the local computer. PowerPoint 2000, PowerPoint XP (2002) and

PowerPoint 2003 are supported.

The following considerations apply:

C We recommend that you use the most recent available version of PowerPoint in order to avoidany loss of data due to backward compatibility issues.

C We recommend that you use the same version of PowerPoint for all tasks involving the sameset of files.

Key Term Definition

C Presentation – a PowerPoint document.

C Slide – the equivalent of a body page in a presentation. Each presentation consists of 1 or moreslides. Each slide may contain translatable content which is stored in text objects.

C Title slide – a slide that contains the title of the presentation, or subsection of the presentation.Each title slide may contain translatable content which is stored in text objects.

C Notes page – each slide in the presentation may have a corresponding notes page. Each notespage may contain translatable content which is stored in text objects.



Overv i ew10


10-

C Handout – printed version of a presentation, featuring slide content only. Handouts do notcontain any new translatable content.

C Master page – the equivalent of a template for a group of slides or pages in the presentation.PowerPoint uses separate master pages for slides, title slides, notes pages and handouts. The

master page allows you to define text formatting, layout and any common content such asheader and footer elements for the relevant group of slides or pages. Header and footerelements qualify as translatable content; master pages may also contain other translatablecontent that is stored in text objects.

C Placeholders – master page elements that are used to define and represent the characteristicsof text, headers and footers. For instance, you can use the text placeholders on a slide master todefine the characteristics of your master text; you can use the footer placeholders to define thecharacteristics of footer elements such as the date, time and slide number.

C Translatable text – The SDL Trados PowerPoint filter differentiates between translatable andnon-translatable text. Any text that is stored in a text object is considered to be translatable.This text is automatically extracted during conversion to TRADOStag and presented fortranslation in the TRADOStag document.

C Text object – refers to an object in PowerPoint that contains translatable text. These includeinclude text boxes, AutoShapes, WordArt drawing objects, organization charts, tables, headers,and footers.

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 SDLTrados PowerPoint filter makes translatable text that is stored in grouped objects available fortranslation.

C Drawing object – refers to an object in PowerPoint 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 ew10



Translation of a PowerPoint document involves the following stages:


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-

PREPARATION

This section explains how to prepare your PowerPoint documents for conversion to TRADOStag and

translation. It outlines the characteristics and limitations of the conversion process.

About the Conversion Process

During translation with Translator’s Workbench and TagEditor, PowerPoint documents are

converted to TRADOStag using a dedicated PowerPoint 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 theamount of translatable content rather than on the file size. If the document contains a largeamount of translatable content, conversion may take some time. During conversion, refer tothe status bar messages and progress indicators in Translator’s Workbench and TagEditor forinformation about conversion status.

C The PowerPoint filter does not process placeholder text on master pages (for example, Click toedit Master text style on the slide master). As a result, this text is not presented for translation inthe TRADOStag document. If you wish to translate placeholder text, it must be extractedmanually and presented for translation in a separate file.

C The PowerPoint filter does not process text that is stored in Clip Art, external file, camera orscanner pictures. As a result, this text is not presented for translation in the TRADOStagdocument. If you wish to translate text that is stored in such pictures, it must be extractedmanually and presented for translation in a separate file.

C By default, the PowerPoint filter does not process comments. As a result, they are notpresented for translation in the TRADOStag document. If you wish to translate comments,you can modify the relevant setting in the PowerPoint filter settings file. For moreinformation, see Modifying the PowerPoint Filter Settings File on page 10-8 Alternatively, youcan extract comments manually and translate them in a separate file.

C The PowerPoint filter differentiates between automatically updated footer elements (slide

number, date and time) that are inserted directly onto a slide, and those that are inserted usingplaceholders on the slide master. In both cases, the elements are presented for translation inthe TRADOStag document. However, those that are inserted directly onto a slide lose anyspecial formatting on backward conversion and will no longer be updated automatically.Where necessary, they must be recreated manually in the target file.



P repara t ion10


C By default, the PowerPoint processes hyperlinks and presents them for translation in theTRADOStag document. However, hyperlink processing is time-consuming and may slowdown conversion. If required, you can modify the relevant setting in the PowerPoint filtersettings file so that hyperlinks are no longer processed. For more information, see Modifying the PowerPoint Filter Settings File on page 10-8

C The PowerPoint filter does not support more than one level of nesting in hyperlinks.Hyperlinks that feature more than one level of nesting will be lost during conversion andmust be recreated manually in the target file.

C The PowerPoint filter does not process sound data. As a result, sound data must be reinsertedmanually in the target file.



P repara t ion10


10-

Using the Filter Settings application for the PowerPoint Filter

To modify some of the most commonly changed settings in the PowerPoint filter settings file use

the SDL Trados Filter Settings application:

C Hyperlink and comment processing

C Display formatting and font mapping

C Font adaptation

C Order of slides and shapes

C Segmentation



1 Select Start > Programs > SDL International > SDL Trados 2006 > Filters > Filter Settings. TheFilter Settings application opens.

2 Click PowerPoint filter settings and select an option. Follow the directions shown for

each setting to make changes.





P repara t ion10


TIPE


Modifying the PowerPoint Filter Settings File

During conversion to and from TRADOStag, the PowerPoint filter processes content according to

instructions that are outlined in the PowerPoint filter settings file. The name of this file is

PowerPoint_1_0_0_0.xml and it is installed by default to C:\Program Files\SDL


The settings in the filter settings file determine which elements of the PowerPoint 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, the

PowerPoint filter does not process any comments that occur in your PowerPoint document. If youwish 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.

NOTED

C We recommend that only advanced XML users modify the PowerPoint filtersettings file. Before making any changes, create a backup of the original file.

C For more information about modifying the PowerPoint filter settings file, contactSDL Consultancy at your local SDL office. Contact details for the local offices are available atwww.sdl.com or www.translationzone.com.



Trans la t ion10


10-

TRANSLATION

Translate your Microsoft PowerPoint documents using Translator's Workbench and TagEditor. If

you have pre-translated your files, they are already converted to TRADOStag. Otherwise, the files are

still in PowerPoint document format. In either case, files for translation can be opened directly in

TagEditor.

PowerPoint Documents during Translation

This section explains the characteristics of PowerPoint documents during translation in the

TagEditor editing environment.

Translation Sequence – Slides and MastersA PowerPoint document may consist of slides, slide masters, title masters, notes pages, a notes

master, handouts and a handout master. In the TRADOStag document, content from each of these

items is presented for translation in the following default order:

C slide master(s)

C title master(s)

C notes master

C handout master

C ancillary slide

C each slide, presented in turn along with its corresponding notes page.

The ancillary slide is a temporary slide that is created during conversion to hold the content that is

common to the header and footer elements on notes and handout masters. During backward

conversion, this content is automatically reinserted in the notes and handout masters.

Translation Sequence – Text Objects and Text

The PowerPoint filter processes content from all text objects found in a PowerPoint document. Text

and text objects are read and presented for translation in the following default order:

C Western languages – from top-left to bottom-right by row.

C DBCS languages – from top-left to bottom-right by row.

C Bi-directional languages – from top-right to bottom-left by row.



Trans la t ion10


C Grouped objects and tables are read and presented as flat structures, using the language-specific orders specified above.

C Objects in diagrams are read and presented in the order in which they were created.

Document Display in TagEditor

TagEditor uses a semi-WYSIWYG display for all file types, including PowerPoint 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 PowerPoint filter generally interprets a paragraph break in the PowerPointdocument as a line break. In the TRADOStag document, a line break is represented as a <br/> tag.

Note that the <br/> 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 <br/> 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 mayfind 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 0 button – – on the Tags toolbar in TagEditor.Pressing the 0 button inserts a <br/> tag in the document for translation. The <br/> tag affectsdocument display in TagEditor and target file formatting, but does not affect segmentation.

Bulleted Lists

The PowerPoint 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 <br/> tag.



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 <br/> tag – in the target segment, place the cursor wherever you want the new<br/> tag to be inserted and then click the appropriate button on the toolbar. TagEditor insertsthe <br/> tag at the cursor position.



Trans la t ion10


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 PowerPointdocuments, 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 Generic Tag Verifier plug-in to verify tag content at document level frequently duringtranslation.


C Use the Preview tabs in TagEditor to preview individual slides as temporary documents inPowerPoint.

NOTEDFor more information about each of these tasks, see the online help for TagEditor or theTranslator’s Workbench User Guide.

After Translation



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 haveused Translator’s Workbench throughout for translation and editing.



Trans la t ion10


10-1

Using the Save Target As Command in TagEditor

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


have used Translator's Workbench to translate and edit the document at all times, keeping thetranslation memory up to date with the latest bilingual data. In the Save Target As dialog box, select

the original file type (Microsoft PowerPoint Documents (*.ppt, *.pps, *.pot)) 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.



changes have not yet been added to the current translation memory.





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 as

TRADOStag (TTX) and close it.

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

file or a batch of files together. Select Update TM in the Clean Up Files dialog box to

update the translation memory in accordance with any changes you made to the

translated 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 PowerPoint extension (*.ppt,

*.pps, *.pot). Note that the source files need to be present in their original location.

NOTED

For more information about the clean up feature in Translator’s Workbench,see the Translator’s Workbench User Guide.






Once you have finished translating and cleaning up your PowerPoint documents, they are ready for

final DTP and proofing. For the post-translation phase of production, we recommend that you use

the same version of PowerPoint that you used to prepare files for translation.

Where necessary, carry out the following post-translation tasks:

C Reinsert any text that was manually extracted and translated in a separate file. This mayinclude placeholder text on master pages, text that is stored in pictures and comments.

C Check all header and footer elements. The auto-numbering properties of footer elements(slide number, date and time) that were inserted directly onto a slide in the source file are lostduring backward conversion. These footer elements must be recreated in the target file.

C Check all hyperlinks. Hyperlinks that featured more than one level of nesting in the source fileare lost during the conversion process. These hyperlinks must be recreated in the target file.

C Check that all text displays correctly, especially text that is stored in AutoShapes, WordArtdrawing objects, organizational charts and tables.

C If the target file is in a bi-directional language, check the display of all text and carry out DTPwhere necessary.

C Use the Print Preview command on the File menu in PowerPoint to review each slide and thenmake any adjustments that are necessary.

CONCLUSION


Task Checked?

Prepare PowerPoint documents for translation. ✔

Translate PowerPoint documents using TagEditor and Translator’s

Workbench.

✔

Finalize target files so that text and graphic elements display correctly

in PowerPoint.

✔



Chapte

MICROSOFT EXCEL DOCUMENTS

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 Filter Settings application

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 – Excel workbook

C XLT – 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) and Excel 2003 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:

C File 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:


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.

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 theamount of translatable content rather than on the file size. If the document contains a largeamount of translatable content, conversion may take some time. During conversion, refer tothe status bar messages and progress indicators in Translator’s Workbench and TagEditor forinformation about conversion status.



P repara t ion11


C The Excel filter does not process protected or hidden content. As a result, this type of contentis not presented for translation in the TRADOStag document. Before processing, check thesettings in each Excel document to make sure that hidden or protected content is madeavailable for processing. Conversely, if your Excel document contains content that you wish toexclude from translation, you can hide this content before processing.

C By default, the Excel filter does not process comments. As a result, they are not presented fortranslation in the TRADOStag document. If you wish to translate comments, you can modifythe relevant setting in the Excel filter settings file. For more information, see Modifying the Excel Filter Settings File on page 11-8 Alternatively, you can extract comments manually andtranslate them in a separate file.

C The Excel filter differentiates between hyperlinks that are created using the Hyperlink menucommand in Excel and those that are created using a hyperlink function. Only thosehyperlinks that were created using the Hyperlink menu command are presented fortranslation in the TRADOStag document. Hyperlinks that are created using a hyperlinkfunction must be extracted manually and presented for translation in a separate file.

C The Excel filter does not process text that is stored in Clip Art, external file, camera or scannerpictures. As a result, this text is not presented for translation in the TRADOStag document. If you wish to translate text that is stored in such pictures, it must be extracted manually andpresented for translation in a separate file.

C The Excel filter does not process pivot tables, pivot charts or their data sources. As a result, thetext that these objects contain is not presented for translation in the TRADOStag document.Where necessary, the text must be extracted manually and presented for translation in aseparate file.

C The Excel filter does not process cell names or cell labels. As a result, this type of text is notpresented for translation in the TRADOStag document. Where necessary, this text must beextracted manually and presented for translation in a separate file.

C The Excel filter does not support subscript, superscript or double-underline formatting in textboxes, AutoShapes, comments and buttons. As a result, this type of formatting is lost duringconversion. Where necessary, you must reapply this type of formatting manually in the targetfile.



P repara t ion11


11-

Using the Filter Settings application for the Excel Filter

You can use the Excel Filter Settings to modify some of the most following commonly changed

settings:

C Content and macro processing

C Display formatting and font mapping

C Font adaptation

C Text exceeding the length limit

C Segmentation

C Order of sheets and shapes





2 Click Excel filter settings and select an option. Follow the directions shown for each





P repara t ion11



TIPE

If you do not want to save the changes, and you have not clicked Apply, clicking Exit will close

the application without saving.

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 and it is installed by default to C:\Program Files\SDL


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 certainsituations, you may wish to modify one or more of the default settings. For example, by default, the

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

NOTED

C We recommend that only advanced XML users modify the Excel filter settings file. Beforemaking 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 as shipped with TRADOS 6.5, you can find it in C:\ProgramFiles\TRADOS\xxx\TT\FF60 where xxx corresponds to the name of the software youare using.



Trans la t ion11


11-

TRANSLATION

Translate your Microsoft Excel documents using Translator's Workbench and TagEditor. If you have

pre-translated your files, they are already converted to TRADOStag. Otherwise, the files are still in

Excel document format. In either case, files for translation can be opened directly in TagEditor.

Excel Documents during Translation

This section explains the characteristics of Excel documents during translation in the TagEditor

editing environment.

Translation Sequence – Worksheets and Chart Sheets

An Excel document may consist of one or more worksheets and chart sheets. By default, the Excel

filter follows the order in which sheets are arranged in the source file and presents content from each

sheet in this order in the TRADOStag document.

Translation Sequence – Text Objects and Text

The Excel filter processes content from all text objects found in a Excel document. Text and text

objects are read and presented for translation in the following default order:

CWestern languages – from top-left to bottom-right by row.

C DBCS languages – from top-left to bottom-right by row.

C Bi-directional languages – from top-right to bottom-left by row.

C Grouped objects and tables are read and presented as flat structures, using the language-specific orders specified above.

C Objects in diagrams are read and presented in the order in which they were created.

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.



Trans la t ion11


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 presents

text and text objects in the appropriate direction.

Document Display in TagEditor

TagEditor 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 <br/> tag. Note that the

<br/> 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 <br/> tags may still be interpreted

as a single segment by Translator’s Workbench.


For more information about segmentation rules during translation with Translator’s

Workbench, 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 <br/> tag in the document for translation. The <br/> tag affectsdocument display in TagEditor and target file formatting, but does not affect segmentation.

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 <br/> tag.



Trans la t ion11


11-1

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:

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 <br/> tag – in the target segment, place the cursor wherever you want the new<br/> tag to be inserted and then click the appropriate button on the toolbar. TagEditor insertsthe <br/> tag at the cursor position.



Trans la t ion11


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 Generic Tag Verifier plug-in to verify tag content at document level frequently duringtranslation.


C Use the Preview tabs in TagEditor to preview individual slides as temporary documents inExcel.

NOTEDFor more information about each of these tasks, see the online help for TagEditor or theTranslator’s Workbench User Guide.

After Translation



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 haveused 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


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.



changes have not yet been added to the current translation memory.





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.





NOTED

For more information about the clean up feature in Translator’s Workbench,see the Translator’s Workbench User Guide.


Once you have finished translating and cleaning up your Excel documents, they are ready for final

DTP and proofing. For the purposes of post-translation phase of production, we recommend that

you use the same version of Excel that you used to prepare files for translation.

NOTED

Before opening target files in Excel, check that the system locale settings on the local computerare compatible with the target language. This will enable Excel to present numeric data in thetarget file(s) correctly.

Where necessary, carry out the following post-translation tasks:

C If your target file is in a bi-directional language, use the options that are available with thePage Setup command in Excel to display data in the appropriate right-to-left direction.Afterwards, check the display of all text and carry out DTP where necessary.

C Reinsert any text that was manually extracted and translated in a separate file, for example,text that is stored in pictures, pivot tables, pivot charts, cell names and cell labels.

C Check all hyperlinks. Hyperlinks that were originally created using the hyperlink functionrather than the Hyperlink menu command will have been translated separately and must berecreated in the target file.

C Check that all text displays correctly, especially text that is stored in AutoShapes, WordArtdrawing objects, organizational charts and tables.

C Reapply subscript, superscript or double-underline formatting in text boxes, AutoShapes,comments and buttons.

C Use the Print Preview command on the File menu in Excel to review each worksheet and chartsheet and then make any necessary adjustments.

CONCLUSION


Task Checked?

Prepare Excel documents for translation. ✔



Conc lu s ion11


11-1

Translate Excel documents using TagEditor and Translator’s

Workbench.

✔

Finalize target files so that all data displays correctly in Excel. ✔

Task Checked?



Conc lu s ion11




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.

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, and

clean-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


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

If you previously used SDL Trados translation tools to localize the Windows32 binary files, your

translation memories will have a difference in the matching rates because Windows32 binary files

are now directly translated in TagEditor instead of through a T-Window.

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 2006 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

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 thestring. 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 open and translate resource files directly in TagEditor. Using the filter,

you can directly process resource files across all SDL Trados applications, such as Translator's

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

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









2 Click RC filter settings and select an option. Follow the directions shown for each




TIPE


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 file. The name of this file is

RCFilter_1_0_0_0.xml and it is installed by default to C:\Program Files\SDL


The settings in the filter settings file determine which elements of the RC document will be treated

during translation.





12-1

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.

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

7 Save the target files in TRADOSTag (TTX) bilingual format, using the Save BilingualAs command in TagEditor.


9 Open the translated resource files in your build environment for testing.

NOTED


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 signs

as tags. You can prepare your translation memory before starting a new job in SDL Trados 2006 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.

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 Close is preceded with an ampersand, which

is the shortcut indicator for the shortcut character C. 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 S.

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}





12-1

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 F4, 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 Shift+F4. The modifier usually

needs to be translated, for example the English Shift is translated into German as

Umschalt. The original shortcut key character needs to be replaced with the corresponding

target language character.

C Resource files often contain the strings for dialog boxes. Dialog boxes can contain a number of

control elements such as buttons, drop-down lists, text fields or labels. The 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 thetarget language.





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. 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 Properties Filter allows you to open and translate java properties files directly in TagEditor.

You no longer have to use the T-Window for Resources to translated Java properties files. Using the

filter, you can directly process Java properties files across all SDL Trados applications, such as

Translator's Workbench 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









4 Open your Java properties files in TagEditor. Your file will look similar to this

5 Translate your Java properties files in TagEditor.

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.


As command in TagEditor.





12-2


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



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.





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.



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 2006 is available on the SDL Trados 2006CD.

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 Filter Settings to determine which file types can be

processed using this filter.

NOTED

In order to use the SDL Generic Delimited Filter Settings you must have SDLX 2005 SP1 (Liteversion or better) installed.




2 Click SDL Generic Delimited filter settings and select Filter option. Follow the

directions shown for each setting to make changes.





14-



TIP

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

Modifying the SDL Generic Delimited Filter Settings File

During conversion to and from TRADOStag, the SDL Trados processes content according to

instructions that are outlined in the SDL Generic Delimited filter settings file. The name of this file

is SdlGdfFilter1_0_0_0.xml and it is installed by default to C:\Program Files\SDL


The settings in the filter settings file determine which elements of the text file will be treated during

translation.

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.


As 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

For more information about translating files in TagEditor and the clean up feature in

Translator’s Workbench, see the Translator’s Workbench User Guide.



Chapte

TRANSLATING OPENOFFICE

AND STAROFFICE FILES

SDL Trados 2006 supports the translation of OpenOffice and

StarOffice filetypes.

OpenOffice.org and StarOffice offer word processer,

spreadsheet, presentation and vector drawing components

Open Office and StarOffice files are similar to each other and

are handled in the same way by SDL Trados 2006.

15



15


Supported Versions

SDL Trados 2006 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 toC:\Program Files\SDL


The settings in the filter settings file determine which elements of the text file will be treated during

translation.



15


15-

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.

CFor more information about modifying the SDL OpenOffice filter settings file, contact SDLConsultancy.


Translation of your OpenOffice file involves the following steps:



2 In Translator’s Workbench, activate any translation projects and filter settings that arerequired.



4 Translate your text files in TagEditor.


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



15




Append

SUPPORTED LANGUAGES

This appendix covers supported languages and locales for SDL

Trados 2006.

A



Su ppor ted Langu ages and Loca lesA

A-2FILE FORMATS REFERENCE GUIDE

SUPPORTED LANGUAGES AND LOCALES

Translator’s Workbench supports the widest array of languages in the translation software industry

including Eastern and Western European, bi-directional, and Asian languages.

The following table identifies the languages and locales supported by Translator’s Workbench as

source and target languages...

Language SubLanguage ID

Afrikaans Default 1078

Albanian Albania 1053

Arabic Algeria 5121

Arabic Bahrain 15361

Arabic Egypt 3073

Arabic Iraq 2049

Arabic Jordan 11265

Arabic Kuwait 13313

Arabic Lebanon 12289

Arabic Libya 4097

Arabic Morocco 6145

Arabic Oman 8193

Arabic Qatar 16385

Arabic Saudi Arabia 1025

Arabic Syria 10241

Arabic Tunisia 7169

Arabic UAE 14337

Arabic Yemen 9217

Armenian

Basque Default 1069

Bengali

Bulgarian Default 1026



Su ppor ted Langu ages and Loca les A


A-

Byelorussian Default 1059

Catalan Default 1027

Chinese 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






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






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 processing

The practice of processing multiple files atone 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.

Context TMContext TM refers to the use of previously

translated documents as a type of translation

memory that allows segment matches to be

checked for context as well as content. The

Context TM process compares updatedsource files to old bilingual documents

rather than a translation memory. Segment

matches, known as Context TM units (XUs,)

are checked for context and extracted from

the old bilingual documents and transferred

to the updated source files. This results in a

new set of bilingual documents that have the

extension *.ttx. Use the Context TM

Wizard to run the Context TM process

interactively. Context TM is also available asan automated process in SDL GXT.

Context TM MatchOne of five match types identified by

Translator’s Workbench during analysis.

Context TM matches indicate that the

analyzed document contains Context TM

Units (XUs) or segment matches from a

previous version of the bilingual document

as opposed to a translation memory.

Context TM UnitsContext TM units (XUs) are translation units

that appear in your bilingual document after

running the Context TM Wizard. Context

TM units represent segment matches thatcome from the previous version of the

bilingual document rather than the

translation memory. Because the Context

TM process includes a check for context, XU

segment matches represent those parts of

your document that typically need no further

translation or editing.

Customize veri f ication

Settings that allow you to suppress certainalerts 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 suppress

messages relating to a particular tag, any

alerts or warnings referring to that tag are

suppressed in the verifier report or Message

pane.

D

Database serverThe 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.



G


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, filesize 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 DTD

file is separate from the document it defines.

An example of a widely used DTD is theHTML 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 ("<p>")

and an end tag ("</p>"). 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 explicit

start 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 environmentprovide 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 ‘é’.

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 the

translation 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 Asian

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



G


Glossary-

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 matchOne of five match types identified by

Translator’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 returnManual line break or a non-breaking

carriage 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 varietyof tags and attributes.

I

IASCII

Interleaf ASCII. IASCII is a text file formatwhich 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 from

InDesign 2.0 or later.

See also Story Collectors.

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 the

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



G


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 computersare 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 the

necessary license information by locating

the relevant license file or attaching a dongle

to the parallel or USB port.

See also Demo mode, Dongle.

M

Middleware

In a client/server architecture, themiddleware 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 key

The 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


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 TagEditorediting environment 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.

See also Story Collectors.

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


Glossary-

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


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

See also SDL TeamWorks.

TeamWorks ManagerTeamWorks Manager is an administrative

tool 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


Glossary-1

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.

V

Val idationIn TagEditor, validation refers to the process

of validating an XML document after

translation using the XML Validator plug-in.



G


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


Glossary-1

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.











G





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-14

importing stories 6-16

setting the story order 6-13

QuarkXPress




bilingual target files

cleaning up

IASCII files 3-7

InDesign files 6-11

MIF files 3-7

ML files 2-32

PageMaker files 4-10

PowerPoint files 10-13

QuarkXPress files 5-11

RoboHelp files 8-25

RTF files 9-22

Ventura files 7-5

Word files 8-4, 9-3

Bookmark Handler macros 8-6

adding template 8-6

running 8-7

browsers 2-16

■Ccharacter entities

converting 2-15

Clean Up command

Translator’s Workbench 2-33

comparing the TTX workflow to the RTF workflow 9-2

conditional markup language tags 2-22

conditional ML 2-22

conditional ML tags 2-22

Context TM 3-5

Cross-reference, PageMaker 4-12

■DDirectory structure

InDesign 6-6

PageMaker 4-6

QuarkXPress 5-6

DLG files 12-9

DLL files 12-2

Document layers

PageMaker 4-12

Document type definition (DTD) 2-4

DTD

tutorial on Tag Settings Wizard 2-7–2-17

■EExcel

filter 11-2

handling macros 11-5

preparing files 11-5

EXE files 12-2

executable filesEXE,DLL, OCX, and LNG files 12-2

Exporting storiesfrom InDesign 6-10

from PageMaker 4-9

INDEX



I

I-2FILE FORMATS REFERENCE GUIDE

from QuarkXPress 5-10

from Ventura 7-4

■FFile organization

InDesign 6-6

PageMaker 4-6

QuarkXPress 5-6

filter

Excel 11-2

Folder structure

InDesign 6-6

PageMaker 4-6

QuarkXPress 5-6

Font MappersFrameMaker 3-3

Interleaf 3-3

FONT tags 2-14

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-31

Graphics

replacing references with placeables 8-20–8-21

■HHTML

previewing within TagEditor 2-16

HTML files

translating 2-30

■IIASCII files 3-3

cleaning up bilingual target files 3-7

Importing stories

InDesign 6-12

PageMaker 4-10

QuarkXPress 5-12

InDesigncleaning up bilingual target files 6-11

directory structure 6-6

story order 6-7

Index entry, PageMaker 4-11

Inline graphics

InDesign 6-3

PageMaker 4-12

QuarkXPress 5-6

Installation

Story Collector for InDesign 6-4

Story Collector for PageMaker 4-4

Story Collector for QuarkXPress 5-4

Interleaf

preparing IASCII files for conversion 3-5

translating 3-6

using Font Mappers 3-3

Internet browsers 2-16

Internet Explorer 2-16

■JJapanese PageMaker version 6.5 and 7

character support 4-13

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

■MMacros

handling macros in Excel files 11-5

macros

Bookmark Handler 8-6



I


I-

Bookmark Handler template 8-6

PrepareBookmarks 8-6

RestoreBookmarks 8-6

Master page, PageMakerexporting 4-12

META tags 2-14Microsoft Excel

see Excel

Microsoft PowerPointsee PowerPoint

Microsoft Wordsee Word

MIF files 3-3


ML files 2-4

ASCX 2-2

ASP, 2-2

ASP.NET 2-2ASPX 2-2


DTD 2-3

format 2-2

HTML 2-2, 2-3

INC 2-2

JSP 2-2

PHP 2-2

preparation 2-4

Save Target As 2-32

SGML 2-2

tag settings 2-3, 2-4

translating 2-3, 2-30

XML 2-2

MultiDoc Pro from Citec 2-16

Multiple files

InDesign 6-13

QuarkXPress 5-13

■NNetscape Navigator/Communicator 2-16

■OOCX files 12-2

Opening




opening QuarkXpress files using SDLXtract. 5-3

■PPageMaker

cleaning up bilingual target files 4-10creating a folder structure 4-6

cross-references 4-12


exporting master pages 4-12


index entry 4-11

installing Story Collector 4-4

Japanese version 6.5 and 7

character support 4-13

exporting and importing 4-13

preparing files 4-5

preparing PageMaker 7 files 4-5

tag error 4-13

translation process 4-10

troubleshooting 4-11

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

PowerPointcleaning up bilingual target files 10-13

filter 10-5

translating files 10-9–10-12

understanding the conversion process 10-5

PrepareBookmarks macro 8-6

previewing ML files in an external viewer 2-16

■Q

QuarkXPressbatch export 5-14, 6-14

batch functions 5-13



inline graphics 5-6

multiple page spreads 5-9, 6-10

preparing files 5-6

Story Collector 5-2

story order 5-8

story order for multiple files 5-13



I

I-4FILE FORMATS REFERENCE GUIDE

translating files 5-11

■RRC files 12-9

RC Filter 12-9, 12-18

Replace command


Resource files 12-9

resource files

RC andDLG files 12-9, 12-18

RestoreBookmarks macro 8-6

RoboHelp files


translating 8-25

RTF FilesWindows 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


Save Target As

ML files 2-32

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 rules

translation memory

setting options for help files 8-18

Translator’s Workbench

adding new 8-18

changing, for keyword translation 8-18

SGML

previewing in external browser 2-16Tag Settings Wizard in TagEditor 2-7–2-17

SGML files

translating 2-30

Source directory

INDD 6-15

ISC 6-14

P65/PMD 4-9

QSC 5-10

QXD 5-10

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-10

multiple files 6-14

exporting from PageMaker 4-9

exporting from QuarkXPress 5-10

multiple files 5-14

importing from InDesign 6-12

multiple files 6-16

importing into PageMaker 4-10

importing into QuarkXPress 5-12

multiple files 5-16

Story Collector for InDesign

accessing help 6-5

batch functions 6-13

creating a folder structure 6-6

describing 6-2


exporting stories from multiple files 6-14

importing multiple files 6-16


installing 6-4

opening 6-7

preparing files 6-5

sample files 6-5

setting story order 6-7

story order for multiple files 6-13

tag reference 6-18–6-44

translating 6-11

Story Collector for PageMaker



I


I-

describing 4-2

exporting 4-9

importing translated text 4-10

installing 4-4

opening 4-7

preparing files 4-5

preparing PageMaker 7 files 4-5



translating 4-10

troubleshooting 4-11

verifying the tagged text output 4-9


installing 5-4

Japanese version 4.1 5-5

opening 5-7

setting up a folder structure 5-6


translating 5-11

Story order 5-8, 6-8

Custom 5-8, 6-8

Left-right 5-8, 6-8

PageMaker 4-2

setting for multiple files in InDesign 6-13

setting for multiple files in QuarkXPress 5-13

setting in InDesign 6-7

setting in QuarkXPress 5-8

Top-down 5-8, 6-8

supported browsers 2-16

Supported Languages and Locales A-2

Unicode-only A-7

■TTag Settings

tutorial on Tag Settings Wizard 2-7–2-17

Tag settings file

.NET RESX files 2-5

default DITA settings 2-5

default HTML settings 2-5

default SVG settings 2-5

default XLIFF settings2-5

default XSL settings 2-5

tag settings file

creating 2-7

editing 2-18

managing 2-6

overview 2-4

Tag Settings Manager

opening 2-6

Tag Settings Properties 2-18

Tag Settings Wizard

tutorial 2-7–2-17

TagEditor

Internet browsers 2-16

previewing files in an external application 2-16

Tag Settings Wizard 2-7–2-17

translation guidelines 2-30Tagged text files

verifying 2-31

Text

importing into Ventura 7-5

TRADOStag

description 1-4

file components 1-6

PowerPoint

converting from 10-5

translating 13-1

FrameMaker files 3-6

HTML files 2-30

Interleaf files 3-6

Microsoft Word files 8-9, 9-14

ML files 2-30

PowerPoint files 10-9–10-12

RTF Help files 8-23

SGML files 2-30




Ventura files 7-5

XML files 2-30

translating Word files in TagEditor 9-1

translation memory

segmentation rules 8-18

setting options for help files 8-18

Translator’s WorkbenchClean Up command

Update TM 2-33

Replace command 2-33

Save Bilingual As command 2-33

segmentation rules

adding new 8-18

changing, for keyword translation 8-18

using the Clean Up command 2-33

Troubleshooting, PageMaker 4-11

TTXsee TRADOStag

TTX workflow 9-2, 9-3

tw4winInternal style 8-20, 8-22

tw4winJump and tw4winPopup styles 8-17

■U