SDL Trados 2007 Suite - File Formats Reference Guide

File Formats Reference Guide

COPYRIGHT FILE FORMATS REFERENCE GUIDE Copyright © 2008 SDL plc. All rights reserved. No part of this documentation may be duplicated in whole or in part or reproduced in any form without the express written permission of SDL plc. All trademarks are the property of their respective owners. The names of other companies and products mentioned herein may be the trademarks of their respective owners. Unless stated to the contrary, no association with any other company or product is intended or should be inferred. Although SDL takes all reasonable measures to provide accurate and comprehensive information about the product, this guide is provided “as is” without warranty, either express or implied. This guide accompanies SDL Trados 2007. May 2008 DC-T27-FF-03-EN

TABLE OF CONTENTS Chapter 1

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

Chapter 2

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

FILE FORMATS REFERENCE GUIDE

iii

Chapter 3

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

Chapter 4

PageMaker Files Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key Term Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Translation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Story Collector for PageMaker . . . . . . . . . . . . . . . . . . . . . . . . .

4-2 4-3 4-3 4-4

Preparation and Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Folder Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening Story Collector for PageMaker . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Story Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-5 4-6 4-7 4-7 4-9

Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 Post-translation Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 Importing Translated Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tips for Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tips for Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tips for Japanese PageMaker 6.5 and 7 . . . . . . . . . . . . . . . . . . . . . . . . . .

4-12 4-12 4-13 4-14

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

iv

FILE FORMATS REFERENCE GUIDE

Chapter 5

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

Chapter 6

InDesign Files Translating InDesign CS2/CS3 files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Translating InDesign Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6 Key Term Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7 Translation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8 Installing Story Collector for InDesign . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8 Preparation and Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10 Creating a Folder Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11 Opening Story Collector for InDesign . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12 Setting the Story Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12 Exporting Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15 Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16

FILE FORMATS REFERENCE GUIDE

v

Post-translation Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17 Importing Translated Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17 Batch Functions in Story Collector for InDesign . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Story Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-18 6-18 6-20 6-22

Tag Reference Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24 Story Collector for InDesign Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24 Tags in InDesign Tagged Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24 Defining Java Virtual Machine Size filter settings . . . . . . . . . . . . . . . . . . . . . . . . 6-51 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52

Chapter 7

Ventura Files Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Key Term Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Translation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Preparation and Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Folder Structure Organization . . . . . . . . . . . . . . . . . . . . . . . . Preparing the Text in Ventura Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Ventura Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-3 7-3 7-4 7-4

Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Post-translation Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6 Importing Ventura Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6 Tag Reference Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11

Chapter 8

Word and RTF Help Files Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 Key Term Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 Selecting a Workflow for Word Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 Working with Microsoft Word Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 RTF Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 Preparation of Microsoft Word Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5 Using the Bookmark Handler Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

vi

FILE FORMATS REFERENCE GUIDE

Translation of Microsoft Word Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9 Post-translation Production for Word Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14 Working with RTF Help Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15 Preparation of RTF Help Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17 Translation of RTF Help Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23 Translating RoboHelp Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25 Post-translation Production for RTF Help Files . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26

Chapter 9

Translating Word Files in TagEditor Selecting a Workflow for Word Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 TTX Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3 Preparation of Microsoft Word Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 About the Conversion Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 Setting the TTX Workflow Translation Memory Option . . . . . . . . . . . . . 9-5 Testing the TTX Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6 Word Document Preparation Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6 Modifying the Word Filter Settings File . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11 Translation of Microsoft Word Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16 Understanding Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16 Field Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17 Headers and Footers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20 Inserted Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21 Non-translatable Footnotes and Endnotes . . . . . . . . . . . . . . . . . . . . . . . 9-21 Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23 RTF Help Translation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24 Post-translation Production for Word Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27

Chapter 10

Microsoft PowerPoint Documents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2 Key Term Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2 Translation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5 About the Conversion Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5 Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11 FILE FORMATS REFERENCE GUIDE

vii

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

Chapter 11

Microsoft Excel Documents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key Term Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Translation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11-2 11-2 11-3 11-4

Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5 Handling Macros in Excel Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5 About the Conversion Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5 Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11 Excel Documents during Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11 After Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14 Post-translation Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-16 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17

Chapter 12

Translating Programming Files Localizing Windows32 Binary Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Previewing File Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying Translated Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cleaning Up Translated Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12-2 12-3 12-3 12-6 12-7 12-8

Localizing Resource Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Previewing File Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying Translated Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cleaning Up Translated Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12-9 12-12 12-12 12-15 12-16 12-17

Localizing Java .properties Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18 Defining Java Virtual Machine Size filter settings . . . . . . . . . . . . . . . . . . . . . . . . 12-22

viii

FILE FORMATS REFERENCE GUIDE

Chapter 13

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

Chapter 14

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

Chapter 15

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

Chapter 16

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

Glossary Index

FILE FORMATS REFERENCE GUIDE

ix

x

FILE FORMATS REFERENCE GUIDE

INTRODUCTION

This chapter introduces the File Formats Reference Guide and some key concepts. Sections include: C

About this Guide

C

Key Term Definition

C

Supported File Formats

C

TradosTag Bilingual File Format

Chapter

1

1

About this Guide

ABOUT THIS GUIDE The File Formats Reference Guide contains file format specific information that is relevant to translation workflows when working with SDL Trados 2007. This guide deals with each file format individually: this means that you can quickly and easily access the information you need during translation and determine what to watch out for during translation of this file format. See Supported File Formats on page 1-5. If you are working with SDL Trados Synergy, the project creation and management tool in SDL Trados 2007, many sections of this guide will not be relevant to you, as Synergy allows you to add many file types directly without formatting the files and also performs many of the pre- and posttranslation steps for you, such as analysis, pre-translation and clean-up. You can also verify your files from within Synergy. All applications mentioned in this guide, such as the SDL Trados Filter Settings, Tag Settings Manager and Verification Plug-ins are also accessible via Synergy. However, you may still need to prepare your files for translation and/or set filter settings for your files. Any chapters or sections that are not relevant to you if you work using Synergy are marked with a note. For more information about Synergy, see the SDL Trados 2007 Synergy User Guide.

Audience Profile This guide is most useful to project managers, localization specialists or translators who are working with the file formats described in this guide.

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

SDL Trados Installation Guide – contains information for the installation and configuration of all the SDL Trados components, including Synergy, the translation tools and the server components.

C

SDL Trados Administrator Guide – contains information about the SDL Trados server components, including TM Server, Server Manager and Synergy Server.

C

SDL Trados Synergy User Guide – introduces the main concepts in SDL Trados Synergy, including project creation and the translation workflow in Synergy.

C

Translator’s Workbench User Guide – contains information about Translator’s Workbench and the TagEditor and Microsoft Word editing environments.

C

1-2

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

FILE FORMATS REFERENCE GUIDE

About this Guide

1

Accessing Documentation The full set of SDL Trados 2007 guides is available in PDF format: C

in the Doc subfolder of your SDL Trados 2007 installation folder

C

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

C

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

D

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

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

C:\Documents and Settings\All Users\Documents\SDL Trados\Samples. In this guide, we use these sample files to demonstrate features that provide specific support for particular file formats. We recommend that you use the sample files to work your way through procedures and examples on your own computer.

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

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

C

Conversion – refers to converting files from one format to another. There is forward conversion and backward conversion. C Forward conversion is the conversion of source files to an easily translatable file format: for example, converting ILDOC files to STF using the S-Tagger for Interleaf/QuickSilver. Forward conversion sometimes involves exporting text from source files. C Backward conversion is the conversion of translated files back into their original format: for example, converting STF to MIF using the S-Tagger for FrameMaker. Backward conversion sometimes involves importing translated text into source files. FILE FORMATS REFERENCE GUIDE

1-3

1

1-4

About this Guide

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.

FILE FORMATS REFERENCE GUIDE

Supported File Formats

1

SUPPORTED FILE FORMATS The file formats described in this guide are: C

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

C

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

C

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

C

SDL Trados formats – TradosTag and Workbench RTF.

C

Windows executable files – EXE, DLL, OCX, and LNG.

C

Windows resource files – RC and DLG.

C

SDLX translation documents – ITD.

C

Java Properties files.

C

SDL Generic Delimited files.

C

OpenOffice and StarOffice files.

C

Generic text files.

C

XLIFF files.

TRADOSTAG BILINGUAL FILE FORMAT TradosTag provides a standard method of describing tagged text formats and bilingual data for translation purposes. During conversion to TradosTag, translatable text and formatting information are extracted from the native file format and presented in an abstracted file format called TradosTag. During translation, the TradosTag file stores all the necessary bilingual data, including source and target language data and segment delimiting marks. After translation the TradosTag file is merged with the native file to create a translated document. TradosTag files are XML-compliant and consist of well-formed XML documents that can be processed without explicit reference to a Document Type Definition (DTD).

FILE FORMATS REFERENCE GUIDE

1-5

1

TradosTag Bilingual File Format

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

D

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

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

1-6

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.

V

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

FILE FORMATS REFERENCE GUIDE

Conclusion

1

TradosTag Files TradosTag files are composed of three sections: C

Front matter – contains tools settings, user settings and information that has been extracted from the native file format.

C

Body – contains the document text plus formatting tags.

C

Back matter – contains ancillary text. This is translatable text that is shared throughout the document, for example variable or cross-reference text. Not all TradosTag files have back matter. It depends on the format of the file before you converted it to TradosTag.

When you open a TradosTag file for translation in TagEditor, the body text and formatting information appears. The back matter section also appears as it requires translation. The front matter section is not visible in TagEditor.

CONCLUSION Now that you have read this chapter, you know where to find the information you need for the file format you are translating.

FILE FORMATS REFERENCE GUIDE

1-7

1

1-8

Conclusion

FILE FORMATS REFERENCE GUIDE

HTML, XML, AND SGML FILES

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

HTML, XML and SGML translation workflow

C

Preparing HTML, XML, SGML files for translation

C

Creating and editing tag settings files with the Tag Settings Wizard

C

Post-translation production tips

D

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

Chapter

2

2

Overview

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.

D

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

Supported ML File Formats SDL Trados provides explicit support for the following ML file formats: C

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

C

SGML documents (SGM, SGML).

C

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

C

XML documents (XML, XSL). XML files with unrecognized file extensions are also supported as long as the file includes the XML declaration, , and the extension does not conflict with file extensions for other supported file types.

C

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

The XML filter can support any language, but the file encoding must be in Unicode. The SGML/HTML filter supports any language that has language support installed on the computer.

D

2-2

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

FILE FORMATS REFERENCE GUIDE

Overview

2

Key Term Definition The following terms occur frequently in this chapter: C

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

C

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

C

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

C

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

C

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

C

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

FILE FORMATS REFERENCE GUIDE

2-3

2

Overview

Translation Workflow Translation of HTML, XML, and SGML files involves the following stages:

2-4

1

Create a folder structure for your translation project. An orderly folder structure helps you to keep track of all your source and target files.

2

Prepare the necessary tag settings file(s). For more information, see “Tutorial: Tag Settings Wizard” on page 2-8.

3

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

4

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

5

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

6

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

7

Save the target files in TradosTag (TTX) bilingual format, using the Save Bilingual As command in TagEditor.

8

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

9

Open the translated HTML, XML, and SGML files in your browser, editing, or publishing environment for further processing.

FILE FORMATS REFERENCE GUIDE

Preparation

2

PREPARATION In general, the ML files themselves need no preparation prior to translation. However, in order to process and format the files, a tag settings file is required.

What is a DTD? The structure of HTML, XML, and SGML documents is usually stored in a text file that is separate from the document itself. This file is called the document type definition (DTD). The DTD for a particular document type defines the structure, elements and conventions to which a document must conform. An example of a widely-used DTD is the HTML 4.0 DTD: all HTML 4.0 documents are based on this DTD. Many other standard DTDs have been designed, such as the book, article and serial DTDs included in ISO 12083. You can also develop your own DTD.

What is a Schema? An XML schema is a text file describing the structure of an XML document and is an alternative to DTD. It is also referred to as XML Schema Definition (XSD).You can use a predefined schema or create your own. Both DTD-based and schema-based XML files are supported. For both types of XML files you need to use the Tag Settings Wizard to set up a tag settings file, so that Synergy, Translator’s Workbench, TagEditor, or WinAlign can distinguish between, for example, structural and inline elements. For more information, see “Tutorial: Tag Settings Wizard” on page 2-8.

Tag Settings File A tag settings file contains information necessary for processing documents that conform to a particular DTD or schema. Tag settings files are also known as initialization files, and have the extension *.ini. SDL Trados requires a tag settings file to process and format HTML, SGML, or XML documents for translation purposes. For example, Synergy, TagEditor, Translator’s Workbench and WinAlign use the tag settings file to scan the document for translation and define whether tags are external (structural tags) or internal (formatting or other inline tags). The tag settings file also instructs the Trados applications on how to handle HTML, SGML or XML elements, such as tags and character entities. Use the Tag Settings Manager to manage the tag settings files on your system. Use the Tag Settings Wizard to create new or edit existing tag settings files. You can access both the Tag Settings Manager and the Tag Settings Wizard from Synergy, Translator’s Workbench, TagEditor, or WinAlign.

FILE FORMATS REFERENCE GUIDE

2-5

2

Preparation

D

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

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

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

HTML 4.0 DTD and have the root element HTML. C

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

C

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

C

XLIFF.ini – suitable for processing XML Localization Interchange File Format files that have the root element XLIFF.

C

DITA.ini – suitable for processing Darwin Information Typing Architecture XML files that

have the root element DITA. C

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

C

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

C

Visio.ini – suitable for processing Visio files.

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

C:\Documents and Settings\All Users\Application Data\SDL International\Filters. You can create copies of and modify these files as required. Note that the Application Data folder may be hidden and you will have to set it to be visible if you want to see this folder and any subfolders. Also, if you want to make any changes to files in this folder, you must have read/write access to this folder. Consult your IT department for more information.

Using Tag Settings Files Tag settings files are required for the following processes:

2-6

C

Alignment of ML files in WinAlign.

C

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

FILE FORMATS REFERENCE GUIDE

Preparation

C

Translation of ML files in TagEditor.

C

Verification of ML files in Synergy or TagEditor.

2

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

D

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

To access the Tag Settings Manager: 1

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

2

From the Tools menu in TagEditor, choose Tag Settings. The Tag Settings Manager dialog box is displayed:

Use the Tag Settings Manager dialog box to perform the following tasks: C Add new or existing tag settings files to the list. You can create a new tag settings file using the Tag Settings Wizard, as outlined in the tutorial below. C Remove existing tag settings files from the list. C Edit existing tag settings files (for example, the predefined HTML settings file that ships with software) using the Tag Settings Wizard. For more information, see “Editing Tag Settings” on page 2-19.

FILE FORMATS REFERENCE GUIDE

2-7

2

Preparation

Tutorial: Tag Settings Wizard This tutorial shows you how to use the Tag Settings Wizard to create a new tag settings file. We recommend that you work through the tutorial on your own computer. The tutorial is based on the wizard as seen from TagEditor. Minor differences are evident when accessing the wizard from Synergy, Translator’s Workbench or WinAlign. For more information, see the Synergy User Guide, Translator’s Workbench User Guide or the WinAlign User Guide. Before you start, make sure that you have access to the following files which are installed by default to C:\Documents and Settings\All Users\Documents\SDL Trados\Samples\TagEditor\SGML\: C

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

C

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

D

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

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

2-8

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

FILE FORMATS REFERENCE GUIDE

Preparation

2

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

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

C Specify the Settings name you want to use (in our example, Sample Letter). This will be the descriptive name used to identify the INI file. It is displayed under Descriptive Name in the Tag Settings Manager. C Select the type of settings you want to create. You can choose one of the following options: C

New Settings for XML

C

New Settings for SGML/HTML

C

Base on predefined HTML 4.0 settings

C

Base on predefined XSL settings

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

FILE FORMATS REFERENCE GUIDE

2-9

2

Preparation

3

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

C Click Import and specify the file you want to import (in this example, Letter.dtd). the Import Tag Definitions dialog box is displayed.

2-10

FILE FORMATS REFERENCE GUIDE

Preparation

2

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

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

The default properties for plain text are: C Font: Arial C Size: 10 point C Effects: none C Colour: black Accept the default settings and click Next.

FILE FORMATS REFERENCE GUIDE

2-11

2

Preparation

5

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

This is the key step in the Tag Settings Wizard. It enables you to perform one or more of the following tasks: C Classify tags as external, internal, or a placeholder. C Classify tags as always translatable or non-translatable. C Define translatable attributes within tags (for example, the ALT attribute within the IMG tag in HTML). C Assign special formatting properties to text between specific tags (for example, headings or emphasized text). C Add or remove tags from the list of elements. C Add conditions to determine when text is translatable. See Using Conditional ML Tags in Tag Settings Files on page 2-23. C Select one or more root elements.

V

2-12

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

FILE FORMATS REFERENCE GUIDE

Preparation

6

2

The Emphasis tag is a typical example of an internal tag for which you can define formatting. In this tutorial, we assign bold formatting to any text that appears between the opening and closing Emphasis tags as follows: C In the Elements list, select the Emphasis tag and click Properties. This opens the Element Properties dialog box. Click the Formatting tab. C Select Bold and click OK to confirm. The new text formatting is displayed in the preview pane of the wizard. Repeat this procedure for each tag whose formatting properties you want to change.

V

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

FILE FORMATS REFERENCE GUIDE

2-13

2

Preparation

7

Click Advanced to open the Advanced Settings dialog box.

Here you specify advanced tag settings. In the Treat unrecognised elements as group box, define how TagEditor treats tags that have not yet been added to the Elements tab: C Select External to format all undefined tags as external tags. This is the default setting. C Select Internal to format all undefined tags as internal tags. C Select Placeholder if you want all undefined tags to be treated as non-translatable placeholder tags. In the Script translation group box, define the strings within tags in HTML documents that TagEditor presents for translation: C Select Allow translation of all strings if you want to present all strings between quotation marks for translation. C Select Allow translation of L_strings only to present text contained within L _variables for translation.

2-14

FILE FORMATS REFERENCE GUIDE

Preparation

2

C Select Do not allow translation of any strings in scripts to protect all text within strings from translation. For more information about script translation, see Defining Tag Settings to Handle Script

Translation on page 2-19. In the tags group box, define how the charset value in the 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 tag if not present if you want TagEditor to change the charset value if it is present in the document. If no charset value is found, TagEditor adds it to the document. C Select Change charset value only if tag is present if you want TagEditor to change the charset value only if it was present in the source document. C Select Do not change charset value if you want TagEditor to ignore the charset value. This is only needed if the HTML document is processed by tools outside the SDL Trados environment which rely on the charset value to remain unchanged during translation. In the Display Options group box, define how TagEditor displays tags and treats line breaks. C Select the Disable formatting for tags option when translating into Asian languages. It disables the WYSIWYG effect for fonts in the TagEditor document window. As a result, single-byte fonts such as Arial are no longer interfering with translation using DBCS fonts such as MS Mincho and the Copy Source command. C Select the Keep all line breaks option if you need to keep the exact structure of line breaks in the file(s) you wish to translate.

V

FOR MORE INFORMATION See the Tag Settings Help for more information on line breaks. The XML Options group box indicates if the settings are case sensitive or not. C Element and Attribute names are case sensitive is always disabled, since setting case sensitivity is only be possible at the time settings are created. This option allows you to check if a certain tag settings file uses case sensitive tag names or not. In the xml:lang attribute values group box, specify the language to be used in the xml:lang attribute (this specifes the language used in the contents of any subsequent elements in the XML document): C Select Change source language to target language if you always want the xml:lang attribute to be changed from the source language to the target language. C Select Always change to target language if you always want the xml:lang attribute to be changed to the target language, regardless of what language the attribute specifies. C Select Do not change if you do not want to change the xml:lang attribute.

FILE FORMATS REFERENCE GUIDE

2-15

2

Preparation

In the Unicode UTF-8 byte order mark (BOM) group box, specify whether or not you want to apply the Unicode UTF-8 byte order mark: C Select Preserve; don’t add if not originally present if you do not want to add the byte order mark. C Select Preserve; add if not orginally present for UTF-8 encoded file if you want to add the byte order. C Select Remove if present if you want to remove the byte order. Click OK in the Advanced Settings dialog box to accept the default settings and then click Next. 8

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

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

2-16

FILE FORMATS REFERENCE GUIDE

Preparation

2

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

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

Internet Explorer 5.0 or higher is the default internal browser. Here, internal means that TagEditor does not have to launch Internet Explorer in an external window; instead, it opens a special window within the main TagEditor application window. If you wish to use another browser to view your HTML files, you can specify an external viewer, such as Firefox. In the case of SGML files, as in our example, you may wish to use an external viewer. To set this up, click External and use the Browse button to locate the application on your system. When you are translating files in TagEditor, clicking the Preview tab launches the external application specified. The message, “In external preview mode” appears in the TagEditor application window. The following recommendations may be useful: C Use a recent browser (for example, Internet Explorer 6.0 or Firefox 2.0) for previewing HTML files. Older browsers may not be fully supported. C Use any current SGML browser for previewing SGML files.

FILE FORMATS REFERENCE GUIDE

2-17

2

Preparation

C Use a recent browser (for example, Internet Explorer 6.0 or Firefox 2.0) for previewing XML files. The XML files may display as code. Older browsers may not be fully supported. C Before returning from the external application to TagEditor, close the file in the external application to avoid potential conflicts with the open file in TagEditor. C TagEditor only sends a temporary file to the external application. Do not modify it outside TagEditor, otherwise changes will be lost. C When you return from the external application, the external preview mode is still active in TagEditor. To continue translating the file in TagEditor, switch back to Edit view. 10

When you are satisfied with your tag settings, click Finish. When you click Finish, the Save As dialog box appears. Enter a logical name and save the tag settings file with an *.ini extension. You are returned to the Tag Settings Manager dialog box. The new tag settings file is available for selection.

11

Click OK to return to the main TagEditor window. You are now ready to translate the SGML file, Letter.sgm, using Translator’s Workbench and TagEditor. After all tag settings have been defined as required, an SGML file based on the letter DTD typically appears as follows (additional format mappings are used in this example):

2-18

FILE FORMATS REFERENCE GUIDE

Preparation

2

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

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

Defining Tag Settings to Handle Script Translation Through the Advanced Settings dialog box which you can access by clicking Advanced in the Elements tab of the Tag Settings Manager, TagEditor offers three options for translation of strings within tags in HTML documents: C

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

C

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

C

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

FILE FORMATS REFERENCE GUIDE

2-19

2

Preparation

Declaring Localizable Strings If you want to ensure that only localizable strings are accessible during translation you need to identify these strings. To allow SDL Trados to automatically identify the localizable strings, declare them as "L_" strings as shown in the examples below.

JavaScript The example below contains three localizable string resources. They are highlighted in bold. function validate() { x=document.myForm at=x.myEmail.value.indexOf("@") code=x.myCode.value firstname=x.myName.value submitOK="True" if (at==-1) { alert("Not a valid e-mail") submitOK="False" } if (code5) { 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 } }

2-20

FILE FORMATS REFERENCE GUIDE

Preparation

2

To identify these string resources as localizable: 1

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

2

Prefix the variable name with "L_".

3

Use the variable in the script code. var L_InvalidEmail="Not a valid e-mail" var L_WrongCode="Your code must be between 1 and 5" var L_NameTooLong="Your name must be less than 10 letters" function validate() { x=document.myForm at=x.myEmail.value.indexOf("@") code=x.myCode.value firstname=x.myName.value submitOK="True" if (at==-1) { alert(L_InvalidEmail) submitOK="False" } if (code5) { alert(L_WrongCode) submitOK="False" } if (firstname.length>10) { alert(L_NameTooLong) submitOK="False" } if (submitOK=="False") { return false } }

FILE FORMATS REFERENCE GUIDE

2-21

2

Preparation

VBSript The example below contains one localizable string resource. It is highlighted in bold. alert("Hello, World!")

To identify this string resource as localizable: 1

Separate the localizable text from the script code by declaring it as a variable.

2

Prefix the variable name with "L_".

3

Use the variable in the script code. dim L_HelloMessage L_HelloMessage="Hello, World!" alert(L_HelloMessage)

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.

D

NOTE

3

Click the Elements tab, and then click the Advanced button.

4

In the Advanced Settings dialog, options for Script translation are:

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

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

2-22

Click OK to save the settings.

FILE FORMATS REFERENCE GUIDE

Preparation

2

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

V

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

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

FILE FORMATS REFERENCE GUIDE

2-23

2

Preparation

XPath Expressions You can add or edit complex XPath expressions by clicking Conditions in the General tab of the Element Properties dialog box. You can assign a parent element or create an attribute condition. TagEditor supports nested elements at the parent and grandparent level, elements with multiple attribute/value pairs, and elements with a single attribute/value pair. Support for these options is based on a subset of the XPath standard. XPath is a set of syntax rules for defining the parts of an XML document.

V

FOR MORE INFORMATION 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:

2-24

1

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

2

Click the Elements tab.

FILE FORMATS REFERENCE GUIDE

Preparation

3

2

Click Add to add a new element.

Type the element into the Name field on the General tab. If the element already exists in the tag settings file, you can edit it by selecting the element in the Tag Settings Properties dialog box and clicking Properties. 4

Click Conditions. The Element Conditions dialog box opens.

5

Click Attribute to specify an attribute/value pair. The Attribute Condition dialog box opens.

FILE FORMATS REFERENCE GUIDE

2-25

2

Preparation

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.

D

NOTE

6

Click Parent Element to select parents and grandparents for the current element. The Select Element dialog box opens.

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

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.

D

2-26

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

FILE FORMATS REFERENCE GUIDE

Preparation

7

2

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[@attr="value1"]

Element with an attribute that has a value.

…

Element[@attr1="value2"] [@attr2="value4"]

Element with two attributes that have values.

…

Parent/Element

Element with a parent.

… … …

FILE FORMATS REFERENCE GUIDE

2-27

2

Preparation

XPath Format

Description

XML equivalent

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

Parent/child relations combined with attribute conditions to form complex expressions.

… … … … …

C Each definition in the table applies to the content of the element, not the parent or grandparent. C Longer expressions override short ones, with every element and attribute counting as one expression. If you have element definitions of a/b/c and b/c[@attr1="value1"], markup results will be unpredictable when the XML file contains an element definition of a/b/c[@attr1="value1"] because there are two matching expressions with a length of three. If you run into this problem, add a definition for a/b/c[@attr1="value1"]. Because this definition has four expressions it overrides the shorter definitions. C SDL Trados supports long expressions. An element definition can consist of Document/Chapter/Section/Subsection/Subheading/Enumeration/ Item/Formatting[@NumericPrefix="no"][@Translatable="yes"] [@Color="green"][@Visible="yes"]. However, we do not recommend using lengthy

element definitions as this can be a sign of poorly written XML and should be fixed by the author. The example below shows several uses of the supported XPath syntax rules. This example includes nested elements, an element with multiple attribute/value pairs, and an element with a single element/value pair. This text will stay in the source language. This text is translated to the target language. This text is both translated and colored blue. More text staying in the source language.

2-28

FILE FORMATS REFERENCE GUIDE

Preparation

2

A Content type setting of Normal for the PARA element makes the element translatable. Setting up an XPath for the attribute translate="N" defines an exception to make PARA elements untranslatable based on the attribute translate="N" when the Element Content option Not translatable is checked. Checking the Element Content option Always translatable for the nested PARA element with the attribute translate="Y" makes the element available again inside the nontranslatable elements. All the elements in this example use attributes with values. A single attribute value pair is demonstrated by the element. A multiple attribute/value pair is shown in the element.

Element Content Settings The Element Content setting for an element is used to determine if the content is translatable. For example, an element called PARA can be configured in the Tag Settings Wizard or Tag Settings Manager using the Element Content settings as shown in the following example:

Element

Option in tag settings file

Result

...

Set the Content type to Normal in the General tab of the Element Properties

You can translate content inside the tag

...

Set the Element Content to Always translatable in the General tab of the Element Properties

You can always translate content inside the tag, even when content is nested inside an element marked nontranslatable

...

Set the Element Content to Not translatable in the General tab of the Element Properties

You cannot translate content inside the tag

FILE FORMATS REFERENCE GUIDE

2-29

2

Preparation

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:

2-30

FILE FORMATS REFERENCE GUIDE

Translation

2

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

Use the tag protection features in TagEditor to protect the tag content of your file.

C

Use the Tags toolbar and the Insert Tag command to insert tags into your target file.

C

Use the Tags toolbar and the Insert Entity command to insert entities into your target file.

C

Use the segment level verification settings to have TagEditor verify tag content in the background as you work.

C

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

D

NOTE

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.

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

FILE FORMATS REFERENCE GUIDE

2-31

2

Translation

Translating Files Using Conditional ML Tags You may see files containing conditional ML elements. In the following example of a file in TagEditor, the text in the PARA translate="N" element is not available for translation, but the text in the PARA translate="Y" element is available.

Make sure you have the correct tag settings file before attempting to translate the documents. If one does not exist you may need to create one. See Using Conditional ML Tags in Tag Settings Files on page 2-23 for details.

2-32

FILE FORMATS REFERENCE GUIDE

Translation

2

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.

D

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

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

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

C

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

V

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

Cleaning Up Translated Files When translation, editing and tag verification are complete, the bilingual target files are ready for clean up. The clean up process removes source language data and segment delimiting tags, thus allowing the target file to be converted back to its original format. There are two methods of cleaning up your translated files. The method you choose depends on whether you have used Translator’s Workbench throughout for translation and editing.

Using the Save Target As Command in TagEditor The Save Target As command in TagEditor cleans the translated file independently of Translator’s Workbench and does not update the translation memory. This method of clean up is suitable if you have used Translator's Workbench to translate and edit the document at all times, keeping the translation memory up to date with the latest bilingual data. In the Save Target As dialog box, select the original file type (XML, HTML, SGML) from the Save as type drop-down list. As the document is being saved and converted back to its original format, TagEditor removes all source segments and segment delimiters, leaving only a ‘clean’ target language version.

FILE FORMATS REFERENCE GUIDE

2-33

2

Post-translation Production

Using the Clean Up Command in Translator’s Workbench If you have made changes to the target segments without using Translator's Workbench, these changes have not yet been made in the current translation memory. There are several reasons why Translator's Workbench may not be active at all times during the document editing stage: C

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

C

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

In this case, use the Clean Up command in Translator’s Workbench to remove the source language segments and to update the translation memory at the same time. Follow these steps: 1

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

2

Select Clean Up from the Tools menu in Translator’s Workbench to clean up the document. Select Update TM in the Clean Up Files dialog box to update the translation memory in accordance with any changes you made to the target language version outside Workbench.

POST-TRANSLATION PRODUCTION Once you have finished translating, verifying tags and cleaning up your translated files, they are ready for final DTP and proofing. Some typical tasks in post-translation production include:

2-34

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.

D

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

FILE FORMATS REFERENCE GUIDE

Conclusion

2

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.

✔

FILE FORMATS REFERENCE GUIDE

2-35

2

2-36

Conclusion

FILE FORMATS REFERENCE GUIDE

FRAMEMAKER AND INTERLEAF/QUICKSILVER FILES This chapter explains how to work with FrameMaker and Interleaf/QuickSilver files. Sections include: C

FrameMaker and Interleaf/QuickSilver translation workflow

C

Preparing FrameMaker and Interleaf/QuickSilver files using the S-Taggers

C

Translating FrameMaker and Interleaf/QuickSilver files

C

Converting translated files back to original format using the S-Taggers

C

General post-production tasks

D

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

Chapter

3

3

Overview

OVERVIEW This chapter gives a high level view of working with FrameMaker and Interleaf/QuickSilver file formats.To translate FrameMaker and Interleaf/QuickSilver files, you need to convert the text in the files to a format that is easily translated. The S-Taggers facilitate this conversion.

E

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

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

Installing the S-Taggers The S-Taggers are installed as part of your SDL Trados package. By default, the S-Taggers are installed to C:\Program Files\SDL International\T2007\TT.

Version Information S-Tagger for FrameMaker supports MIF files generated by FrameMaker version 4.0 or later, FrameBuilder, and FrameMaker+SGML 5.0 or later. It also supports Unicode-based MIF files generated by FrameMaker 8.0 or later. S-Tagger for Interleaf/QuickSilver supports IASCII and catalog files saved from Interleaf 5.2 or later. Interleaf 7 which is included as part of the QuickSilver XML application suite and QuickSilver 3.0 are also supported.

Key Term Definition The following key terms occur frequently in this chapter:

3-2

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 and QuickSilver files have an ILDOC extension. Older versions of Interleaf produce files with a DOC extension.

FILE FORMATS REFERENCE GUIDE

Overview

C

ILSTY – Interleaf 7 catalog files have an ILSTY extension. Catalog files in Interleaf/QuickSilver function as master style sheets. The author of the original Interleaf/QuickSilver files sets up components, shared components, page numbering, and headers and footers in the catalog and exports these components to other files in the Interleaf/QuickSilver book. Older versions of Interleaf produce files with a STY extension.

C

STF file – File produced when you convert MIF or IASCII files to STF using S-Tagger for FrameMaker or S-Tagger for Interleaf/QuickSilver. It is a tagged text format that is compatible with Translator’s Workbench and other SDL Trados tools. Formatting from the FrameMaker and Interleaf/QuickSilver documents is represented by brief coded statements (S-Tags).

C

CAT file – a file created by S-Tagger from Interleaf/QuickSilver catalog files when converting them to STF.

C

IASCII – Interleaf ASCII. IASCII is a text file format that allows you to exchange information between Interleaf/QuickSilver and other applications. All formatting, file and page layout is retained in the IASCII file.

C

S-Tags – Coded statements that the S-Taggers use to represent document formatting. These tags can be either external or internal.

C

Conversion – Refers to the conversion of MIF/IASCII files to STF format. It also refers to the conversion of the STF files back to their original file format (MIF/IASCII) after translation.

C

Verification – Refers to the comparison process where the tags in the target STF file are compared and verified against the tags in the source STF file. During and after translation, translators should verify that they have placed all the tags in the translated files in the correct sequence and position.

3

How the S-Taggers Work The S-Taggers are conversion utilities that convert FrameMaker MIF files and Interleaf/QuickSilver IASCII files into STF, which is the umbrella name for the tagged text formats that are compatible with Translator’s Workbench and TagEditor. STF files can be RTF, TXT or TTX files. You can translate these STF files using TagEditor or Microsoft Word. After translation, you can use the tag verification features in TagEditor and in the S-Taggers to verify the tag content of your target STF files. Successful verification guarantees successful backward conversion to MIF/IASCII. When your STF files have been verified, you can convert the STF files back to their original file format. The S-Taggers are used in conjunction with the Font Mappers, which specifies the fonts that you wish to map quickly and easily. This is necessary when working with Asian languages such as Japanese. There are two Font Mappers: Font Mapper for FrameMaker and Font Mapper for Interleaf/QuickSilver. FILE FORMATS REFERENCE GUIDE

3-3

3

Overview

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

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

2

Prepare your FrameMaker or Interleaf/QuickSilver files for translation.

3

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

4

Select your conversion settings in the S-Taggers.

5

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

6

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

7

Translate the STF files.

8

Verify the tag content of the target files.

9

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

10

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

11

Open the new MIF/IASCII files in FrameMaker or Interleaf/QuickSilver and save them in FM/ILDOC format. You can now carry out the final DTP work, such as generating the index and table of contents.

D

NOTE C If you are translating into an Asian language you need to map your fonts so that the translated documents can be opened and viewed. See the online help for the Font Mappers for more information. C For more information on translating files in TagEditor or Word and the batch features in Translator’s Workbench, see the Translator’s Workbench User Guide.

3-4

FILE FORMATS REFERENCE GUIDE

Preparation and Conversion

3

PREPARATION AND CONVERSION You may need to prepare your FrameMaker and Interleaf/QuickSilver file(s) before using the STaggers 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.

D

NOTE Context TM has largely been replaced by its successor, SDL PerfectMatch. This is only available in SDL Trados Synergy. However, if you are working outside the Synergy workflow, the Context TM Wizard application is still available in your installation folder.

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.

FILE FORMATS REFERENCE GUIDE

3-5

3

Translation

Text only (TXT) files have the extension .txt and can be opened in any text editor that supports ANSI text. The tags have no special formatting. If you are going to translate ANSI text files and the files are very large, you may not be able to edit them in Notepad or other small text editors. Always open and save the files as text only, without formatting. It is very important that you never open or save the files as MS-DOS text or in a DOS-based editor. ANSI text format is mainly used for communication with document management or machine translation systems and is not recommended for interactive translation.

D

NOTE C The default setting for this option is Rich text format (RTF). If you are using SDL GXT, you must change this setting to TradosTag (TTX). C When translating into Asian languages, you must choose Rich text format (RTF) or TradosTag (TTX) as the file format. C We recommend that you use the same STF file format setting for forward and backward conversion of files. C The option you choose for the STF file format is written to the registry and does not change until you manually change it.

You should: C

Create folder structure for your translation project

C

Prepare your FrameMaker or Interleaf/QuickSilver files for translation

C

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

C

Select your conversion settings in the S-Taggers

C

Convert your MIF/IASCII files to STF format.

TRANSLATION Translate your FrameMaker and Interleaf/QuickSilver files using Translator's Workbench and TagEditor. The following steps offer a high level view of the translation process for FrameMaker and Interleaf/QuickSilver files:

3-6

1

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

2

Analyse and pre-translate the documents for translation in Translator’s Workbench, 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.

FILE FORMATS REFERENCE GUIDE

Post-translation Production

4

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

D

NOTE

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 the Clean 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 or Interleaf/QuickSilver documents for posttranslation production.

D

NOTE

3

Alternatively, you can use the S-Taggers to verify batch files.

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.

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

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

D

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

FILE FORMATS REFERENCE GUIDE

3-7

3

Conclusion

CONCLUSION Now that you have completed this chapter you should understand the FrameMaker or Interleaf/QuickSilver translation process and know where to find detailed information on all tasks involved in this process:

3-8

Task

Checked?

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

✔

Prepare FrameMaker and Interleaf/QuickSilver files for translation

✔

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

✔

Clean up the translated files in Translator’s Workbench

✔

Finalize translated files

✔

FILE FORMATS REFERENCE GUIDE

PAGEMAKER FILES

This chapter explains how to work with the PageMaker DTP file format. Sections include: C

PageMaker translation workflow

C

Preparing and exporting PageMaker files for translation using Story Collector for PageMaker

C

Translating PageMaker files

C

Importing translated files back into PageMaker using Story Collector for PageMaker

Chapter

4

4

Overview

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.

E

TIP 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 added to SDL Trados Synergy projects and 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.

4-2

C

Story Order: Before exporting stories from your PageMaker 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 open the file for translation in TagEditor. 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 TXT format. You then import the translated stories into a copy of the original PageMaker file using Story Collector.

FILE FORMATS REFERENCE GUIDE

Overview

4

Key Term Definition The following key terms occur frequently in this chapter: C

P65 – 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 produced when you export stories from a PageMaker file.

C

Import file – a tagged text file in TXT format containing translated text. You import this file into 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 that stories be presented for translation in a logical sequence. Story Collector allows you to change the order of the stories without affecting the layout of your file.

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

D

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

FILE FORMATS REFERENCE GUIDE

4-3

4

Overview

Installing Story Collector for PageMaker Story Collector for PageMaker is included as part of your SDL Trados installation. These files are installed by default to the following location: C

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

Before you install the Story Collector plug-in, make sure that PageMaker is installed on your system and that it is not running. 1

Copy the following files from the default Story Collector installation folder to the Plugins folder in the Adobe PageMaker installation folder. The Plugins folder will normally be found in the C:\Program Files\Adobe\PageMaker 7.0\Rsrc\Lang\ folder, where Lang is the language of your installation. C Trados Story Collector.add C 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.

D

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

Online Help Story Collector installs a comprehensive help system into the Story Collector installation folder. To access help from within Story Collector, make sure you copy the HLP and CNT files into the PageMaker Plugins folder.

Sample File You can use the sample PageMaker 6.5 file (sample.p65) to work with the Story Collector for PageMaker that ships with SDL Trados. This sample file is installed to

C:\Documents and Settings\All Users\Documents\SDL Trados\Samples\Story Collector for PageMaker. You should use the sample file to work through the Story Collector process example that follows in this chapter.

4-4

FILE FORMATS REFERENCE GUIDE

Preparation and Export

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 translation in 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-12.

D

NOTE 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 to store name and address information to be merged into a PageMaker template. If a story containing data merge information is imported after translation into PageMaker the data merge tags become ordinary text. The best way to work with a PageMaker publication that contains data merge information is to place the data merge text on a separate layer in PageMaker and hide this layer before exporting all the stories using the Story Collector for PageMaker. 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) file into a PageMaker publication. The text in these cannot be translated as it behaves like a graphic 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 the PageMaker publication.

C

Native support for Adobe Photoshop and Illustrator files – allows you to add layered Photoshop and Illustrator files to a PageMaker publication. These behave like other graphic formats in PageMaker.

FILE FORMATS REFERENCE GUIDE

4-5

4

Preparation and Export

C

Hyperlinks – allow documents saved as HTML or Adobe PDF to have links to another place in the document or to a website. This link information is not exported by PageMaker when stories are exported by the Story Collector. The links will need to be re-created when translation 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.

D

NOTE 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 the TXT files.

C

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

To keep a copy of each file and file version:

4-6

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

Either add the TXT files to a Synergy project to be translated or translate them directly using Translator's Workbench and TagEditor. Save the translated files in your target 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.

8

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

FILE FORMATS REFERENCE GUIDE

Preparation and Export

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.

D

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

FILE FORMATS REFERENCE GUIDE

4-7

4

Preparation and Export

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

4-8

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.

D

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

FILE FORMATS REFERENCE GUIDE

Preparation and Export

4

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

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

3

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.

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

F

WARNING 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 the PageMaker 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.

F

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

FILE FORMATS REFERENCE GUIDE

4-9

4

Translation

TRANSLATION Once you have created TXT versions of your files, you can either add the files to Synergy for translation or translate them using Translator’s Workbench and TagEditor.

D

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

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

4-10

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.

D

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

FILE FORMATS REFERENCE GUIDE

Post-translation Production

4

POST-TRANSLATION PRODUCTION This section explains how to import translated files back into PageMaker.

Importing Translated Stories 1

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

2

Choose Trados Story Collector from the Plug-ins submenu in the Utilities menu. The Trados Story Collector dialog box is displayed.

3

In the Trados Story Collector dialog box, click Import to open the Select Import File dialog box. Use this dialog box to locate the file that now contains the translated stories in your target TXT folder.

4

Click Open. Story Collector imports the translated stories back into the PageMaker file in the correct sequence.

5

The progress and results of the import operation are displayed in the Results window of the Trados Story Collector dialog box. After import, you can save the contents of this window to a results file by clicking Save Results. The Save Results As dialog box is displayed where you can specify the location and name of the results file.

6

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

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

FILE FORMATS REFERENCE GUIDE

4-11

4

Troubleshooting

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, make sure that all index entries are contained within a body of text.

C

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

En space

Placeholder



Non-breaking En space

Placeholder



Thin space

Placeholder



Non-breaking thin space

Placeholder



Word space

Placeholder



Non-breaking space

Placeholder



Soft return

Placeholder



Discretionary hyphen

Placeholder



Non-breaking hyphen

Placeholder

FILE FORMATS REFERENCE GUIDE

4-15

4

4-16

Tag Reference Material

Tag

Type

Category



Non-breaking slash

Placeholder



Any character, encoded.

Placeholder

\<

The character <

Placeholder

\>

The character >

Placeholder



Inline graphics file

Placeholder



Index marker

Placeholder Note: Text within quotes needs to be localized!

FILE FORMATS REFERENCE GUIDE

Tag Reference Material

4

Character Attribute Tags Tag

Type

Category



Font

Emphasis



Size

Emphasis



Font

Emphasis



Size

Emphasis



color

Emphasis



Horizontal scale

Emphasis



Horizontal scale

Emphasis



Manual pair kerning

Miscellaneous



Manual pair kerning

Miscellaneous



Kerning

Emphasis



Kerning

Emphasis



Plain text

Emphasis



Bold

Emphasis



Italic

Emphasis



Outline

Emphasis

< ~>

Shadow

Emphasis



Underline

Emphasis



Strikethrough

Emphasis



Superscript

Emphasis



Subscript

Emphasis



All caps

Emphasis



All caps

Emphasis



Small caps

Emphasis



Small caps

Emphasis



Reverse

Emphasis Note: Not used in PM 6.5

FILE FORMATS REFERENCE GUIDE

4-17

4

4-18

Tag Reference Material

Tag

Type

Category



Reverse

Emphasis Note: Not used in PM 6.5



Baseline shift

Emphasis



Baseline shift

Emphasis



Leading

Emphasis



Leading

Emphasis



Line breaks allowed

Emphasis Note: t can be 1.



Line breaks not allowed

Emphasis Note: f can be 0.



Small caps size

Emphasis



Small caps size

Emphasis



Superscript/subscript size

Emphasis



Superscript/subscript size

Emphasis



Superscript position

Emphasis



Superscript position

Emphasis



No tracking

Emphasis



Very tight tracking

Emphasis



Very tight tracking

Emphasis



Tight tracking

Emphasis



Tight tracking

Emphasis



Normal tracking

Emphasis



Normal tracking

Emphasis



Loose tracking

Emphasis



Loose tracking

Emphasis



Very loose tracking

Emphasis



Very loose tracking

Emphasis

FILE FORMATS REFERENCE GUIDE

Tag Reference Material

4

Structural Tags Tag

Type

Category



Version and codepage spec

Structural The version documented here is 1.0, code page can be "mac" or "win".



Custom color definition

Structural



Custom color definition

Structural



Macro definition

Structural Note: May contain text to be localized.



Paragraph style definition

Structural

Paragraph Tags Tag

Type

Category

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

Rule above

Structural



Rule below

Structural



Set next paragraph style

Structural



Apply paragraph style

Structural



Set base on paragraph style

Structural



Set base on paragraph style

Structural



Left indent

Structural



Left indent

Structural



Right indent

Structural



Right indent

Structural



First line indent

Structural



First line indent

Structural FILE FORMATS REFERENCE GUIDE

4-19

4

4-20

Tag Reference Material

Tag

Type

Category



Tab definition

Structural



Tab definition

Structural

Drop Cap > None in Word to turn off the feature before opening the document in TagEditor to keep the word as one paragraph. Note the type of Drop Cap used so you can return the formatting to its original state during posttranslation processing of the Word document.

FILE FORMATS REFERENCE GUIDE

Preparation of Microsoft Word Files

C

Tracked Changes – Tracked changes must not be present in the Word documents to be translated with TagEditor. If your Word documents contain tracked changes, TagEditor displays a warning message. Consult the originator of the document about accepting or rejecting revision marks. Then, deactivate the feature in each Word document before translating 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 the subdocument structure preserved.

C

Fast Save – Deactivate the Fast Save option in Word, then save the document before localization. This makes sure that the document structure is refreshed before localization.

FILE FORMATS REFERENCE GUIDE

9

9-7

9

Preparation of Microsoft Word Files

Using the Filter Settings Application for the Word Filters To modify some of the most commonly changed settings in the Word filter settings files, use the SDL Trados Filter Settings. You can modify filter settings for the Word 2000-2003 filter (DOC format) or for the Word 2007 filter (DOCX format), depending on which version of Microsoft Word your files are from.

Word 2000-2003 Filter The settings you can modify using the SDL Trados Filter Settings for the Word 2000-2003 filter are:

9-8

C

Order of text boxes

C

Soft returns

C

Asian and Complex Script fonts

C

Non-translatable styles

C

Non-translatable footnotes and endnotes

C

Non-translatable texts

C

Display formatting and font-mapping

C

Font adaptation

C

Non accepted or rejected changes

FILE FORMATS REFERENCE GUIDE

Preparation of Microsoft Word Files

9

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

FILE FORMATS REFERENCE GUIDE

9-9

9

Preparation of Microsoft Word Files

Word 2007 Filter The settings you can modify using the SDL Trados Filter Settings for the Word 2007 filter are: C

Display formatting and font-mapping

C

Font adaptation

C

Non accepted or rejected changes

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

To run the Filter Settings application:

9-10

1

Select Start > Programs > SDL International > SDL Trados 2007 > Trados > Filters > Filter Settings. Alternatively, click the link in the Start view in SDL Trados Synergy. The Filter Settings application opens.

2

Click Word 2000-2003 or Word 2007, depending on the filter you want to modify and select an option. Follow the directions shown for each setting to make changes.

3

Click Save to save your changes.

4

Click Exit to close the application.

E

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

FILE FORMATS REFERENCE GUIDE

Preparation of Microsoft Word Files

9

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 is Word_1_0_0_0.xml (for the Word 2000-2003 filter) or Word2007_1_0_0_0.xml (for the Word 2007 filter) and it is installed by default to: C:\Documents and Settings\All Users\Application Data\SDL International\Filters. Note that the Application Data folder may be hidden and you will have to set it to be visible if you want to see this folder and any subfolders. Also, if you want to make any changes to files in this folder, you must have read/write access to this folder. Consult your IT department for more information. The settings in 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.

D

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

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.

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 the translated and non-translated text may be the same depending on the target language.

FILE FORMATS REFERENCE GUIDE

9-11

9

Preparation of Microsoft Word Files

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.

9-12

C

Arial Unicode MS

C

SimSun

C

PMingLiU

C

MS Mincho

C

Mangal

C

Tahoma

C

Code 2000

FILE FORMATS REFERENCE GUIDE

Preparation of Microsoft Word Files

9

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: Batang BatangChe Dotum FarEast de-DE Tahoma Arial Unicode MS

In the example the Batang, BatangChe, and Dotum fonts of the font type FarEast are being mapped to the Tahoma font. All other fonts will be mapped to Arial Unicode MS.

FILE FORMATS REFERENCE GUIDE

9-13

9

Preparation of Microsoft Word Files

The following table lists the XML elements and provides a description:

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 be applied (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 or written 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.

D

9-14

NOTE You can contact your local SDL Business Consultancy for assistance with setting up font mapping rules.

FILE FORMATS REFERENCE GUIDE

Preparation of Microsoft Word Files

9

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.

FILE FORMATS REFERENCE GUIDE

9-15

9

Translation of Microsoft Word Files

TRANSLATION OF MICROSOFT WORD FILES This section discusses some of the common features of Word documents and how TagEditor handles them.

Understanding Tags Word formatting styles are converted into XML-based tags. Tags use the format: Tag Name Attribute=”value”.

Some of these tags can have multiple attributes. The example below shows the paragraph tag which has multiple attributes and a cf tag with a single attribute.

This section explains how to understand what type of formatting the tags represent.

E

9-16

TIP Setting TagEditor to show the complete tag text can help to identify details of the tags.

Tag

Description

fieldinfo

Marks the beginning of a field code.

translatablecontent

Marks the text you can translate for hyperlinks, index entries, and other complex Word items.

footer header

Marks the beginning of a header or footer.

paragraph

Marks the beginning of a paragraph and includes style, font, and size information.

csf

Marks character style based formatting applied to text

cf

Marks character-based formatting applied to text.

FILE FORMATS REFERENCE GUIDE

Translation of Microsoft Word Files

Tag

Description

field

Marks a field such as an index entry, a number, or macro button. See Field Codes on page 9-17 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.

9

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

FILE FORMATS REFERENCE GUIDE

9-17

9

Translation of Microsoft Word Files

The table below lists some common Word features that use field codes and the value for the type attribute.

E

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

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

9-18

FILE FORMATS REFERENCE GUIDE

Translation of Microsoft Word Files

9

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 in a paragraph, the index entry text is listed in the order of placement.

E

TIP C When translating index entries, place the "field" tag in the appropriate location 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 the placed field tag and the translated content.

FILE FORMATS REFERENCE GUIDE

9-19

9

Translation of Microsoft Word Files

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.

E

TIP Selecting View > Header and Footer while your document is open in Word can cause empty tags to 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-20

FILE FORMATS REFERENCE GUIDE

Translation of Microsoft Word Files

9

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 Endnotes Footnotes 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 Help files are not to be translated. Using the SDL Trados Filter Settings you can set A footnotes to be non-translatable.

FILE FORMATS REFERENCE GUIDE

9-21

9

Translation of Microsoft Word Files

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 the reference 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-22

FILE FORMATS REFERENCE GUIDE

Translation of Microsoft Word Files

9

Tables Tables are broken out into table, row, and cell tags. A paragraph tag is associated with each item of translatable text.

D

NOTE Tables created in Word 2000 in a Complex Script and translated to a Latin-based language are ordered right to left when saved to a target file in TagEditor. Save the file in Word XP (2002), Word 2003 or Word 2007 before opening in TagEditor to order the text left to right.

FILE FORMATS REFERENCE GUIDE

9-23

9

Translation of Microsoft Word Files

RTF Help Translation Workflow Translation of an RTF help file involves the following stages: 1

Create a folder structure for your translation project. An orderly folder structure helps you to keep track of all your source and target files.

2

Save your RTF help files as *.doc for translation in TagEditor.

3

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

4

Translate your RTF help files in TagEditor.

D

NOTE C Text in $ and K footnotes is available for translation. The $ and K footnote reference characters 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 not presented for translation. C Graphic references enclosed in curly braces e.g. {bmp c:\temp\mygraphic.bmp} are treated as internal tags by default. You can however unprotect these internal tags in order to edit the 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.

9-24

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.

D

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

FILE FORMATS REFERENCE GUIDE

Post-translation Production for Word Files

9

POST-TRANSLATION PRODUCTION FOR WORD FILES This section presents a list of guidelines for post-translation production on Microsoft Word documents. Not all of these steps may apply to your documents. Some typical tasks in post-translation production include: 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 update all 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 right if translating from Complex Script to Latin, and right to left if translating from Latin to Complex 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 or change a font style for proper text viewing. Changing the font in the style definition for the Normal style typically updates the font for most, if not all, other styles. We recommend editing the style definitions whenever possible.

C

Borders and Shading information may not be present in the final translated document. Make sure you keep a copy of the source file so you can re-apply the formatting after translation.

D

NOTE If at this stage you choose to update any text, remember to open the Word document in TagEditor and run the Clean Up command in Translator’s Workbench to update the translation memory. You cannot switch from the TTX workflow to the RTF workflow for this step.

FILE FORMATS REFERENCE GUIDE

9-25

9

Post-translation Production for Word Files

Troubleshooting the Error Message "Error while writing breaks" in Word Documents Translated in TagEditor It may happen that you open a Word document (.doc) in TagEditor and translate it. When trying to save the translation using Save Target As, you get the error message Error while writing breaks and you are not able to create the translated document successfully. This may happen if the Word document contains one or more section breaks which are not preceded by a paragraph end mark. Section breaks without such paragraph marks are not supported by the Word-TradosTag (TTX) filter provided by TagEditor. To fix this problem: 1

Open your Word document in Word. Make all hidden characters visible so that you can see the section breaks and paragraph marks in the document.

2

Search for section breaks in the document.

E

TIP

3

Insert a paragraph mark before each section break that does not yet have such a mark directly in front of it. The document layout is not affected by adding such a paragraph mark. You don't need to insert such a mark in front of section breaks that already have such a mark.

4

Save the document and re-open it in TagEditor.

5

You should now be able to save the translated file in TagEditor successfully.

You can use the special search string ^b to search for section breaks.

We recommend that you always test the TradosTag (TTX) workflow using a copy of the Word document you want to translate. This way you can detect and fix any potential issues before translation starts. To test the workflow in TagEditor:

9-26

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.

2

Save the Word document and exit Word.

3

Open the Word document in TagEditor.

4

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

5

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

FILE FORMATS REFERENCE GUIDE

Conclusion

9

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

Checked?

Prepare Microsoft Word files for translation in TagEditor

✔

Translate Microsoft Word files completely including features such as footnotes and index entries in TagEditor

✔

Finalize translated Microsoft Word files so that text and graphics display correctly and clearly.

✔

Translate RTF Help files using TagEditor

✔

FILE FORMATS REFERENCE GUIDE

9-27

9

9-28

Conclusion

FILE FORMATS REFERENCE GUIDE

MICROSOFT POWERPOINT DOCUMENTS

Microsoft PowerPoint files created in PowerPoint 2000-2003 and PowerPoint 2007 can be translated using TagEditor. 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

Post-translation production tips

C

Filter Settings application

D

NOTE If you are working with SDL Trados Synergy, only the part of this chapter about using the Filter Settings application for the PowerPoint filters (pages 10-7 to 10-10) is relevant to you.

Chapter

10

10

Overview

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. SDL Trados Synergy, Translator’s Workbench and TagEditor provide direct support for the following PowerPoint document formats: C

PPT and PPTX – PowerPoint presentation

C

PPS and PPSX – PowerPoint show

C

POT and POTX – PowerPoint design template.

V

FOR MORE INFORMATION C For more information about the TagEditor editing environment, see the Translator’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), PowerPoint 2003 and PowerPoint 2007 are supported. The following considerations apply: C

We recommend that you use the most recent available version of PowerPoint in order to avoid any loss of data due to backward compatibility issues.

C

We recommend that you use the same version of PowerPoint for all tasks involving the same set of files.

Key Term Definition

10-2

C

Presentation – a PowerPoint document.

C

Slide – the equivalent of a body page in a presentation. Each presentation consists of 1 or more slides. 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 notes page may contain translatable content which is stored in text objects.

FILE FORMATS REFERENCE GUIDE

Overview

C

Handout – printed version of a presentation, featuring slide content only. Handouts do not contain 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 as header and footer elements for the relevant group of slides or pages. Header and footer elements qualify as translatable content; master pages may also contain other translatable content that is stored in text objects.

C

Placeholders – master page elements that are used to define and represent the characteristics of text, headers and footers. For instance, you can use the text placeholders on a slide master to define the characteristics of your master text; you can use the footer placeholders to define the characteristics of footer elements such as the date, time and slide number.

C

Translatable text – The SDL Trados PowerPoint filter differentiates between translatable and non-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 for translation in the TradosTag document.

C

Text object – refers to an object in PowerPoint that contains translatable text. These include include 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 scanner picture is considered to be non-translatable. This text must be manually extracted and translated in a separate file.

C

Grouped object – a grouped object occurs where one or more items in your presentation have been combined so that you can work with them as if they were one single object. The SDL Trados PowerPoint filter makes translatable text that is stored in grouped objects available for translation.

C

Drawing object – refers to an object in PowerPoint that is created using one of the tools on the Drawing toolbar. Some drawing objects, including text boxes, AutoShapes or WordArt drawing objects, may contain translatable text.

FILE FORMATS REFERENCE GUIDE

10

10-3

10

Overview

Translation Workflow Translation of a PowerPoint 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 PowerPoint documents for translation. For more information, see “Preparation” on page 9-5.

3

In Translator’s Workbench, activate any translation project and filter settings that are 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 source files need to be present in their original location.

8

Open the translated documents in PowerPoint and carry out final DTP and proofing.

V

FOR MORE INFORMATION C For more information about translation and verification in the TagEditor editing environment, see the Translator’s Workbench User Guide. C For more information about analysis, pre-translation and clean up in Translator’s Workbench, see the Translator’s Workbench User Guide.

10-4

FILE FORMATS REFERENCE GUIDE

Preparation

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. An improved PowerPoint filter is available in SDL Trados 2007 which substantially improves the speed of conversion of PowerPoint documents. During the conversion process, most of the content in your documents is made available for translation and formatting instructions are effectively transferred from the source to the target document. However, before you start, it is important to be aware of certain characteristics and limitations in the process. These are outlined below. C

The time required to convert a given document to or from TradosTag depends on the amount of translatable content rather than on the file size. If the document contains a large amount of translatable content, conversion may take some time. During conversion, refer to the status bar messages and progress indicators in Translator’s Workbench and TagEditor for information about conversion status.

C

The PowerPoint filter does not process placeholder text on master pages (for example, Click to edit Master text style on the slide master). As a result, this text is not presented for translation in the TradosTag document. If you wish to translate placeholder text, it must be extracted manually 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 or scanner pictures. 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 and presented for translation in a separate file.

C

By default, the PowerPoint filter does not process comments. As a result, they are not presented 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 more information, see Modifying the PowerPoint Filter Settings File on page 10-10. Alternatively, you can 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 using placeholders on the slide master. In both cases, the elements are presented for translation in the TradosTag document. However, those that are inserted directly onto a slide lose any special formatting on backward conversion and will no longer be updated automatically. Where necessary, they must be recreated manually in the target file.

FILE FORMATS REFERENCE GUIDE

10-5

10

10-6

Preparation

C

By default, the PowerPoint processes hyperlinks and presents them for translation in the TradosTag document. However, hyperlink processing is time-consuming and may slow down conversion. If required, you can modify the relevant setting in the PowerPoint filter settings file so that hyperlinks are no longer processed. For more information, see Modifying the PowerPoint Filter Settings File on page 10-10.

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 and must be recreated manually in the target file.

C

The PowerPoint filter does not process sound data. As a result, sound data must be reinserted manually in the target file.

FILE FORMATS REFERENCE GUIDE

Preparation

10

Using the Filter Settings Application for the PowerPoint Filters To modify some of the most commonly changed settings in the PowerPoint filter settings files, use the SDL Trados Filter Settings. You can modify filter settings for the PowerPoint 2000-2003 filter or for the PowerPoint 2007 filter, depending on which version of PowerPoint your files are from. An improved PowerPoint filter is available in SDL Trados 2007 which substantially improves the speed of conversion of PowerPoint documents.

PowerPoint 2000-2003 Filter The settings you can modify using the SDL Trados Filter Settings for the PowerPoint 2000-2003 filter are: C

Hyperlink and comment processing

C

Display formatting and font mapping

C

Font adaptation

C

Order of slides and shapes

C

Segmentation

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

FILE FORMATS REFERENCE GUIDE

10-7

10

Preparation

PowerPoint 2007 Filter The settings you can modify using the SDL Trados Filter Settings for the PowerPoint 2000-2003 filter are: C

Hyperlink and comment processing

C

Display formatting and font mapping

C

Font adaptation

C

Order of slides and shapes

C

Segmentation

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

10-8

FILE FORMATS REFERENCE GUIDE

Preparation

10

To run the Filter Settings application: 1

Select Start > Programs > SDL International > SDL Trados 2007 > Trados > Filters > Filter Settings. Alternatively, click the link in the Start view in SDL Trados Synergy. The Filter Settings application opens.

2

Click PowerPoint 2000-2003 or PowerPoint 2007, depending on the filter you want to modify and select an option. Follow the directions shown for each setting to make changes.

3

Click Save to save your changes.

4

Click Exit to close the application.

E

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

FILE FORMATS REFERENCE GUIDE

10-9

10

Preparation

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_2_0_0_0.xml (for the PowerPoint 2000-2003 filter) or PowerPoint2007_1_0_0_0.xml (for the PowerPoint 2007 filter ) and it is installed by default to C:\Documents and Settings\All Users\Application Data\SDL International\Filters. Note that the Application Data folder may be hidden and you will have to set it to be visible if you want to see this folder and any subfolders. Also, if you want to make any changes to files in this folder, you must have read/write access to this folder. Consult your IT department for more information.

D

NOTE An improved PowerPoint filter is available in SDL Trados 2007 which substantially improves the speed of conversion of PowerPoint documents.

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 you wish to translate comments, you can modify the relevant setting in the filter settings file so that they are automatically processed and presented for translation in the TradosTag document. By default, you modify settings in the SDL Trados Filter Settings application, as outlined above. You may also wish to change settings manually by opening the XML file directly in an appropriate editor.

D

NOTE C We recommend that only advanced XML users modify the PowerPoint filter settings file. Before making any changes, create a backup of the original file. C For more information about modifying the PowerPoint filter settings file, contact SDL Consultancy at your local SDL office. Contact details for the local offices are available at www.sdl.com or www.translationzone.com. C If you need to finish your current projects using the older version of the filter PowerPoint_1_0_0_0.xml, you can find this in

C:\Documents and Settings\All Users\Application Data\SDL International\Filters.

10-10

FILE FORMATS REFERENCE GUIDE

Translation

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

FILE FORMATS REFERENCE GUIDE

10-11

10

Translation

C

Grouped objects and tables are read and presented as flat structures, using the languagespecific 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 PowerPoint document as a line break. In the TradosTag document, a line break is represented as a tag. Note that the tag affects document display in TagEditor and target file formatting, but does not affect segmentation. As a result, a piece of text that includes one or more tags may still be interpreted as a single segment by Translator’s Workbench.

V

FOR MORE INFORMATION 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 and press [Enter]. As well as introducing a segment break, pressing the [Enter] key causes the line to 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 tag in the document for translation. The tag affects document 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 tag.

10-12

FILE FORMATS REFERENCE GUIDE

Translation

10

PowerPoint Formatting Tags and Tag Display during Translation In the TradosTag document, all PowerPoint formatting tags are represented as tag pairs. The formatting instructions themselves are given as 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 . When tag text is only partially displayed, the attributes are hidden and all formatting tags are displayed as generic tag pairs. In this case, the tag pair for bold formatting is displayed as . 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 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.

D

NOTE If you wish to insert tags in a target segment, make sure that internal tag protection is switched off 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 the tag pair and then click the appropriate button on the toolbar. TagEditor inserts the tag pair around the selected target text.

C

Stand-alone tag – in the target segment, place the cursor wherever you want the new tag to be inserted and then click the appropriate button on the toolbar. TagEditor inserts the tag at the cursor position.

FILE FORMATS REFERENCE GUIDE

10-13

10

Translation

D

NOTE C You can also use the keyboard shortcuts that are associated with each button on the Tags toolbar to insert tags in the target segment. The tool tip for each button displays the corresponding keyboard shortcut. C For more information about the tags that are available on the Tags toolbar for PowerPoint documents, see the online help for TagEditor.

Use the copy and paste method to insert tags that are not available on the Tags toolbar.

Quality Assurance Follow these guidelines to ensure highest quality content in your target files: C

Use the tag protection features in TagEditor to protect the tag content of your file.

C

Use the segment level verification settings to have TagEditor verify tag content in the background as you work.

C

Use the Generic Tag Verifier plug-in in Synergy or TagEditor to verify tag content at document level frequently during translation.

C

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

C

Use the Preview tabs in TagEditor to preview individual slides as temporary documents in PowerPoint.

D

NOTE For more information about each of these tasks, see the online help for TagEditor or the Translator’s Workbench User Guide.

After Translation When translation, editing and tag verification are complete, the bilingual target files are ready for clean up. The clean up process removes source language data and segment delimiting tags, thus allowing the TradosTag target file to be converted back to its original format. There are two methods of cleaning up your translated files. The method you choose depends on whether you have used Translator’s Workbench throughout for translation and editing.

10-14

FILE FORMATS REFERENCE GUIDE

Translation

10

Using the Save Target As Command in TagEditor The Save Target As command in TagEditor cleans the translated file independently of Translator’s Workbench and does not update the translation memory. This method of clean up is suitable if you have used Translator's Workbench to translate and edit the document at all times, keeping the translation memory up to date with the latest bilingual data. In the Save Target As dialog box, select the original file type (Microsoft 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.

Using the Clean Up Command in Translator’s Workbench If you have made changes to the target segments without using Translator's Workbench, these changes have not yet been added to the current translation memory. There are several reasons why Translator's Workbench may not be active at all times during the document editing stage: C

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

C

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

In this case, use the Clean Up command in Translator’s Workbench to remove 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, *.pptx, *.ppsx, *.potx). Note that the source files need to be present in their original location.

D

NOTE For more information about the clean up feature in Translator’s Workbench, see the Translator’s Workbench User Guide.

FILE FORMATS REFERENCE GUIDE

10-15

10

Post-translation Production

POST-TRANSLATION PRODUCTION 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 may include 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 lost during 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 file are 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, WordArt drawing 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 DTP where necessary.

C

Use the Print Preview command on the File menu in PowerPoint to review each slide and then make any adjustments that are necessary.

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

10-16

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.

✔

FILE FORMATS REFERENCE GUIDE

MICROSOFT EXCEL DOCUMENTS

Microsoft Excel files created in Excel 2000-2003 and Excel 2007 can be translated using TagEditor. This chapter explains the following aspects of translating Microsoft Excel documents: C

Excel document translation workflow

C

Preparing Excel documents for translation

C

Excel features during translation

C

Post-translation production tips

C

Filter Settings application

D

NOTE If you are working with SDL Trados Synergy, only the part of this chapter about using the Filter Settings application for the Excel filters (pages 11-7 to 11-9) is relevant to you.

Chapter

11

11

Overview

OVERVIEW This chapter outlines the translation process that applies to Microsoft Excel documents. It explains how to prepare Excel documents for translation and shows you to how to handle Excel-specific features during translation. Both Translator’s Workbench and TagEditor provide direct support using a filter for the following Excel document formats: C

XLS and XLSX – Excel workbook

C

XLT and XLTX – Excel template.

Requirements To process Excel documents in Translator’s Workbench or TagEditor, you must have Microsoft Excel installed on the local computer. Excel 2000, Excel XP (2002), Excel 2003 and Excel 2007 are supported. The following considerations apply: C

We recommend that you use the most recent available version of Excel in order to avoid any loss 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:

11-2

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.

FILE FORMATS REFERENCE GUIDE

Overview

11

To split your files: 1

In Excel, select the sheet you want to copy and from the Edit menu choose Copy. Open a new worksheet and from the Edit menu choose Paste.

2

Save the sheet with a different name ,for example, Spreadsheet1.xls so that you can put your spreadsheet back together after you have completed your translation work.

Key Term Definition C

Workbook – an Excel document.

C

Worksheet – a sheet on which data is listed and analysed. Each Excel document consists of one or 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 may be embedded on the same worksheet as its source data; or displayed on a separate sheet, called a chart sheet.

C

Data types – Excel documents typically contain different types of data including text, formulas and 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 is automatically extracted during conversion to TradosTag and presented for translation in the TradosTag document.

C

Text object – refers to an object in Excel that contains translatable text. These include text boxes, AutoShapes, WordArt drawing objects, organization charts, charts and shapes that are used 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 scanner picture is considered to be non-translatable. This text must be manually extracted and translated in a separate file.

C

Grouped object – a grouped object occurs where one or more items in your presentation have been combined so that you can work with them as if they were one single object. The Excel filter 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 the Drawing toolbar. Some drawing objects, including text boxes, AutoShapes or WordArt drawing objects, may contain translatable text.

FILE FORMATS REFERENCE GUIDE

11-3

11

Overview

Translation Workflow Translation of an Excel document involves the following stages: 1 2

Create a folder structure for your translation project. An orderly folder structure helps you to keep track of all your source and target files. 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 are 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 Excel documents in the TagEditor editing environment. Any files that have not already been converted to TradosTag are converted during translation.

D

NOTE

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.

8

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 Excel extension (XLS or XLT). Note that the source files need to be present in their original location.

9

Open the translated documents in Excel and carry out final DTP and proofing.

V

FOR MORE INFORMATION

Do not translate any Excel sheet names, or you will have problems when creating the target files. To avoid translating Excel sheet names, do not translate any text inside the ... external tags.

C For more information about translation and verification in the TagEditor editing environment, see the Translator’s Workbench User Guide. C For more information about analysis, pre-translation and clean up in Translator’s Workbench, see the Translator’s Workbench User Guide.

11-4

FILE FORMATS REFERENCE GUIDE

Preparation

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 SDL Trados. No manual intervention is required.

C

Excel 2000 – before you start processing, set the security level for macro virus protection in Excel 2000 to high. For more information, see Microsoft Excel Help. When the security level is set to high, unsigned macros or macros that are not from a trusted source are automatically disabled before processing.

E

TIP When the security level is set to high and you open a file that contains a macro in Translator’s Workbench or TagEditor, Excel (2000) appears briefly on your screen. You can ignore it and continue working as normal.

About the Conversion Process During translation with Translator’s Workbench and TagEditor, Excel documents are converted to TradosTag using a dedicated Excel filter. During the conversion process, most of the content in your documents is made available for translation and formatting instructions are effectively transferred from the source to the target document. However, before you start, it is important to be aware of certain characteristics and limitations in the process. These are outlined below. C

The time required to convert a given document to or from TradosTag depends on the amount of translatable content rather than on the file size. If the document contains a large amount of translatable content, conversion may take some time. During conversion, refer to the status bar messages and progress indicators in Translator’s Workbench and TagEditor for information about conversion status.

FILE FORMATS REFERENCE GUIDE

11-5

11

11-6

Preparation

C

The Excel filter does not process protected or hidden content. As a result, this type of content is not presented for translation in the TradosTag document. Before processing, check the settings in each Excel document to make sure that hidden or protected content is made available for processing. Conversely, if your Excel document contains content that you wish to exclude 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 for translation in the TradosTag document. If you wish to translate comments, you can modify the relevant setting in the Excel filter settings file. For more information, see Modifying the Excel Filter Settings File on page 11-10 Alternatively, you can extract comments manually and translate them in a separate file.

C

The Excel filter differentiates between hyperlinks that are created using the Hyperlink menu command in Excel and those that are created using a hyperlink function. Only those hyperlinks that were created using the Hyperlink menu command are presented for translation in the TradosTag document. Hyperlinks that are created using a hyperlink function 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 scanner pictures. 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 and presented for translation in a separate file.

C

The Excel filter does not process pivot tables, pivot charts or their data sources. As a result, the text 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 a separate file.

C

The Excel filter does not process cell names or cell labels. As a result, this type of text is not presented for translation in the TradosTag document. Where necessary, this text must be extracted manually and presented for translation in a separate file.

C

The Excel filter does not support subscript, superscript or double-underline formatting in text boxes, AutoShapes, comments and buttons. As a result, this type of formatting is lost during conversion. Where necessary, you must reapply this type of formatting manually in the target file.

FILE FORMATS REFERENCE GUIDE

Preparation

11

Using the Filter Settings Application for the Excel Filters To modify some of the most commonly changed settings in the Excel filter settings files, use the SDL Trados Filter Settings. You can modify filter settings for the Excel 2000-2003 filter or for the Excel 2007 filter, depending on which version of Excel your files are from.

Excel 2000-2003 Filter The settings you can modify using the SDL Trados Filter Settings for the Excel 2000-2003 filter are: 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

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

FILE FORMATS REFERENCE GUIDE

11-7

11

Preparation

Excel 2007 Filter The settings you can modify using the SDL Trados Filter Settings for the Excel 2007 filter are: 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

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

11-8

FILE FORMATS REFERENCE GUIDE

Preparation

11

To run the Filter Settings application: 1

Select Start > Programs > SDL International > SDL Trados 2007 > Trados > Filters > Filter Settings. Alternatively, click the link in the Start view in SDL Trados Synergy. The Filter Settings application opens.

2

Click Excel 2000-2003 or Excel 2007, depending on the filter you want to modify and select an option. Follow the directions shown for each setting to make changes.

3

Click Save to save your changes.

4

Click Exit to close the application.

E

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

FILE FORMATS REFERENCE GUIDE

11-9

11

Preparation

Modifying the Excel Filter Settings File During conversion to and from TradosTag, the Excel filter processes content according to instructions that are outlined in the Excel filter settings file. The name of this file is Excel_2_0_0_0.xml (for the Excel 2000-2003 filter) or Excel2007_1_0_0_0.xml (for the Excel 2007 filter )and it is installed by default to C:\Documents and Settings\All Users\Application Data\SDL International\Filters. Note that the Application Data folder may be hidden and you will have to set it to be visible if you want to see this folder and any subfolders. Also, if you want to make any changes to files in this folder, you must have read/write access to this folder. Consult your IT department for more information. The settings in the filter settings file determine which elements of the Excel document will be converted, and how. The default settings are suitable for most conversion tasks, however, in certain situations, you may wish to modify one or more of the default settings. For example, by default, 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. By default, you modify settings in the SDL Trados Filter Settings application, as outlined above. You may also wish to change settings manually by opening the XML file directly in an appropriate editor.

D

NOTE C We recommend that only advanced XML users modify the Excel filter settings file. Before making any changes, create a backup of the original file. C For more information about modifying the Excel filter settings file, contact SDL Consultancy. C If you need to finish your current projects using the older version of the filter Excel_1_0_0_0.xml, you can find this in

C:\Documents and Settings\All Users\Application Data\SDL International\Filters.

11-10

FILE FORMATS REFERENCE GUIDE

Translation

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

C

Grouped objects and tables are read and presented as flat structures, using the languagespecific orders specified above.

C

Objects in diagrams are read and presented in the order in which they were created.

D

NOTE If an Excel document that you are translating has external data or an external chart object, you must make sure that the name of this external sheet is not translated, otherwise you will get an error during backward conversion of the file. To ensure this does not happen, do not translate any text inside the ... external tags.

FILE FORMATS REFERENCE GUIDE

11-11

11

Translation

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 are available with the Page Setup command to display data in the appropriate right-to-left direction.

C

In Translator’s Workbench, make sure that the language direction of the translation memory you are using is appropriate. This will enable Translator’s Workbench to interpret and present bi-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 tag. Note that the tag affects document display in TagEditor and target file formatting, but does not affect segmentation. As a result, a piece of text that includes one or more tags may still be interpreted as a single segment by Translator’s Workbench.

V

FOR MORE INFORMATION 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:

11-12

C

To introduce a segment break, place your cursor in the text at the appropriate position and press [Enter]. As well as introducing a segment break, pressing the [Enter] key causes the line to break in TagEditor, however, this has no effect on target file formatting.

C

To introduce a paragraph break, use the 9 button – – on the Tags toolbar in TagEditor. Pressing the 9 button inserts a tag in the document for translation. The tag affects document display in TagEditor and target file formatting, but does not affect segmentation.

FILE FORMATS REFERENCE GUIDE

Translation

11

Bulleted Lists The Excel filter interprets each item in a bulleted list as a separate line and segment. As usual in the TradosTag document, a line break is represented as a tag.

Excel Formatting Tags and Tag Display during Translation In the TradosTag document, all Excel formatting tags are represented as tag pairs. The formatting instructions themselves are given as 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 . When tag text is only partially displayed, the attributes are hidden and all formatting tags are displayed as generic tag pairs. In this case, the tag pair for bold formatting is displayed as . 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 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.

D

NOTE If you wish to insert tags in a target segment, make sure that internal tag protection is switched off 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:

FILE FORMATS REFERENCE GUIDE

11-13

11

Translation

C

Tag pairs – in the target segment, select the word or words around which you wish to place the tag pair and then click the appropriate button on the toolbar. TagEditor inserts the tag pair around the selected target text.

C

Stand-alone tag – in the target segment, place the cursor wherever you want the new tag to be inserted and then click the appropriate button on the toolbar. TagEditor inserts the tag at the cursor position.

D

NOTE C You can also use the keyboard shortcuts that are associated with each button on the Tags toolbar to insert tags in the target segment. The tool tip for each button displays the corresponding keyboard shortcut. C For more information about the tags that are available on the Tags toolbar for Excel documents, see the online help for TagEditor.

Use the copy and paste method to insert tags that are not available on the Tags toolbar.

Quality Assurance Follow these guidelines to ensure highest quality content in your target files: C

Use the tag protection features in TagEditor to protect the tag content of your file.

C

Use the segment level verification settings to have TagEditor verify tag content in the background as you work.

C

Use the Generic Tag Verifier plug-in to verify tag content at document level frequently during translation.

C

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

C

Use the Preview tabs in TagEditor to preview individual slides as temporary documents in Excel.

D

NOTE For more information about each of these tasks, see the online help for TagEditor or the Translator’s Workbench User Guide.

After Translation When translation, editing and tag verification are complete, the bilingual target files are ready for clean up. The clean up process removes source language data and segment delimiting tags, thus allowing the TradosTag target file to be converted back to its original format. There are two methods of cleaning up your translated files. The method you choose depends on whether you have used Translator’s Workbench throughout for translation and editing. 11-14

FILE FORMATS REFERENCE GUIDE

Translation

11

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 worksheet names that contain invalid characters such as *, [], !,:,?,\, or /.

Using the Save Target As Command in TagEditor The Save Target As command in TagEditor cleans the translated file independently of Translator’s Workbench and does not update the translation memory. This method of clean up is suitable if you have used Translator's Workbench to translate and edit the document at all times, keeping the translation memory up to date with the latest bilingual data. In the Save Target As dialog box, select the original file type (Microsoft Excel Documents (*.xls, *.xlt)) from the Save as type drop-down list. As the document is being saved and converted back to its original format, TagEditor removes all source segments and segment delimiters, leaving only a ‘clean’ target language version.

Using the Clean Up Command in Translator’s Workbench If you have made changes to the target segments without using Translator's Workbench, these changes have not yet been added to the current translation memory. There are several reasons why Translator's Workbench may not be active at all times during the document editing stage: C

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

C

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

In this case, use the Clean Up command in Translator’s Workbench to remove 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 Excel extension (*.xls, *.xlt). Note that the source files need to be present in their original location.

FILE FORMATS REFERENCE GUIDE

11-15

11

Post-translation Production

D

NOTE For more information about the clean up feature in Translator’s Workbench, see the Translator’s Workbench User Guide.

POST-TRANSLATION PRODUCTION 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.

D

NOTE Before opening target files in Excel, check that the system locale settings on the local computer are compatible with the target language. This will enable Excel to present numeric data in the target file(s) correctly.

Where necessary, carry out the following post-translation tasks:

11-16

C

If your target file is in a bi-directional language, use the options that are available with the Page 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 function rather than the Hyperlink menu command will have been translated separately and must be recreated in the target file.

C

Check that all text displays correctly, especially text that is stored in AutoShapes, WordArt drawing 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 chart sheet and then make any necessary adjustments.

FILE FORMATS REFERENCE GUIDE

Conclusion

11

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

Checked?

Prepare Excel documents for translation.

✔

Translate Excel documents using TagEditor and Translator’s Workbench.

✔

Finalize target files so that all data displays correctly in Excel.

✔

FILE FORMATS REFERENCE GUIDE

11-17

11

11-18

Conclusion

FILE FORMATS REFERENCE GUIDE

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.

D

NOTE If you are working with SDL Trados Synergy, only the part of this chapter about using the Filter Settings application for the Window RC files filter (pages 12-9 to 12-11) and the Java Resource files filter (pages 12-18 to 12-19) are relevant to you.

Chapter

12

12

Localizing Windows32 Binary Files

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.

D

NOTE The Windows32 Binary Filter supports *.exe, *.dll, *.ocx, and .lng files developed in Microsoft Visual Studio. However, Visual Basic executables and .NET assemblies cannot be localized with this filter.

Translation Workflow Translation of a Windows32 binary file involves the following steps:

12-2

1

Create a folder structure for your translation project. An orderly folder structure helps you to keep track of all your source and target translation files.

2

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

3

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

4

Translate your EXE, DLL, OCX, and LNG files in TagEditor.

5

Preview the Menu and Dialog box text in bilingual or source language format as you translate.

6

Verify the tag content of target files using the Win32 Binary Verifier verification plugin.

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

Launch the translated EXE, DLL, OCX, and LNG files to test them in your build environment.

D

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

FILE FORMATS REFERENCE GUIDE

Localizing Windows32 Binary Files

12

Preparation The Windows32 Binary Filter treats control characters such as line breaks, ampersands, percent signs and plus signs as tags. You can prepare your translation memory before starting a new job in SDL Trados 2007 by exporting the translation memory from Translator’s Workbench, editing 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 } where is the control character you want to convert. The following table shows examples of some of the common characters that can be converted: 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}

Translation Win32 binary files can be translated in TagEditor just like any other tagged file. The Windows32 Binary Filter first presents all menu strings for translation, then the dialog box strings, and finally all other strings, such as message strings. C

Menu items often have an ampersand (&) placeable at the beginning or in the middle of the string. In the Menu item string below, the word File is preceded with an ampersand, which is the shortcut indicator for the shortcut character F. In the target segment, you need to position the ampersand tag to act as a shortcut indicator in front of the letter that is the shortcut character in the target language, in this example, the letter D.

FILE FORMATS REFERENCE GUIDE

12-3

12

12-4

Localizing Windows32 Binary Files

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

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.

FILE FORMATS REFERENCE GUIDE

Localizing Windows32 Binary Files

C

12

Strings can contain special (non-printable) control characters, such as "\n", which indicates a line break, "\t", which indicates a tab character, etc. 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 page number, 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.

However, you can change the order of numbered placeholders such as %1, %2, %3, in the target segment.

FILE FORMATS REFERENCE GUIDE

12-5

12

Localizing Windows32 Binary Files

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 the translated file is correct and guarantees backward conversion.

2

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 the Win3dows2 Binary format.

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

D

NOTE Message strings cannot be previewed. For example, if you try to access the Preview Mode while your cursor is placed within a pair of string tags somewhere outside of a menu or dialog element, 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.

D

12-6

NOTE A preview just represents a token menu or dialog. It does not implement any functionality and dialog control elements cannot be resized in the preview.

FILE FORMATS REFERENCE GUIDE

Localizing Windows32 Binary Files

12

Verifying Translated Files 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.

D

NOTE Even if problems are reported during verification, it does not mean that your target file is invalid. For example, if your translation contains duplicate shortcut key assignments, the target-

FILE FORMATS REFERENCE GUIDE

12-7

12

Localizing Windows32 Binary Files

language application will still run. However, it is recommended that you correct such problems to 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 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 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.

12-8

FILE FORMATS REFERENCE GUIDE

Localizing Resource Files

12

LOCALIZING RESOURCE FILES The RC Filter allows you to add files directly to SDL Trados Synergy or to open and translate resource files directly in TagEditor. Using the filter, you can directly process resource files across all SDL Trados applications, such as Synergy (or Translator's Workbench if you are not using Synergy) for analysis, pre-translation, and clean-up and WinAlign for alignment of existing resource files. The RC Filter recognizes the .rc and .dlg file formats. Windows RC files traditionally contain text used in the user interface and DLG files contain scripts used for dialog resources and are linked to executables such as EXE or DLL files. One project can have multiple resource files. Resource files generally contain the text used for dialog boxes, menus, bitmaps, icons, and so on. Some resources in a resource file such as bitmaps and icons may not need to be translated. Check with the originator of the resource file.

D

NOTE Microsoft .NET resource files (RESX) are treated as a special type of XML file. You can translate these files using the resx.ini tag settings file. See Chapter 2, HTML, XML, and SGML Files for more information.

FILE FORMATS REFERENCE GUIDE

12-9

12

Localizing Resource Files

Using the Filter Settings Application for the Windows RC Files Filter You can use the RC filter settings to determine if the filter should perform a check of the RC file header or check for the occurrences of multiple language resources before opening or processing a file. If the checks are enabled the filter behaves more strictly when opening an RC file. If you disable these settings, the filter does not perform the checks. You can also reset the filter settings back to the default values.

To run the Filter Settings application:

12-10

1

Select Start > Programs > SDL International > SDL Trados 2007 > Trados > Filters > Filter Settings. Alternatively, click the link in the Start view in SDL Trados Synergy. The Filter Settings application opens..

2

Click Windows RC files and select an option. Follow the directions shown for each setting to make changes.

3

Click Save to save your changes.

4

Click Exit to close the application.

E

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

FILE FORMATS REFERENCE GUIDE

Localizing Resource Files

12

Modifying the RC Filter Settings File During conversion to and from TradosTag, the RC filter processes content according to instructions that are outlined in the RC Filter Settings s file. The name of this file is RCFilter_1_0_0_0.xml and it is installed by default to C:\Documents and Settings\All Users\Application Data\SDL International\Filters. Note that the Application Data folder may be hidden and you will have to set it to be visible if you want to see this folder and any subfolders. Also, if you want to make any changes to files in this folder, you must have read/write access to this folder. Consult your IT department for more information. The settings in the filter settings file determine which elements of the RC document will be treated during translation. By default, you modify settings in the SDL Trados Filter Settings application, as outlined above. You may also wish to change settings manually by opening the XML file directly in an appropriate editor.

D

NOTE C We recommend that only advanced XML users modify the RC filter settings file. Before making any changes, create a backup of the original file. C For more information about modifying the RC filter settings file, contact SDL Consultancy.

Translation Workflow Translation of a resource file involves the following steps: 1

Create a folder structure for your translation project. An orderly folder structure helps you to 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

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

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 Bilingual As command in TagEditor.

FILE FORMATS REFERENCE GUIDE

12-11

12

Localizing Resource Files

8

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

9

Open the translated resource files in your build environment for testing.

D

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

Preparation If you previously used SDL Trados translation tools to localize the RC files, your translation memories will have a difference in the matching rates because RC files are now directly translated in TagEditor instead of through a T-Window. The RC Filter treats control characters such as line breaks, ampersands, percent signs and plus signs as tags. You can prepare your translation memory before starting a new job in SDL Trados 2007 by exporting the translation memory from Translator’s Workbench, editing 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 } where is the control character you want to convert. The following table shows examples of some of the common characters that can be converted: 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}

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.

12-12

FILE FORMATS REFERENCE GUIDE

Localizing Resource Files

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.

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 the target language.

FILE FORMATS REFERENCE GUIDE

12

12-13

12

Localizing Resource Files

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 page number, 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-14

FILE FORMATS REFERENCE GUIDE

Localizing Resource Files

12

However, you can change the order of numbered placeholders such as %1, %2, %3, in the target segment. C

At the end of the resource file you can find version information, if applicable.

After Translation 1

When you have finished translating the file, verify the tag content using the SDL Trados RC File Verifier in TagEditor or SDL Trados Synergy. Successful verification ensures that the syntax of tags in the translated file is correct and guarantees backward conversion and compilation in Visual Studio.

2

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 the resource file format.

D

NOTE

3

Save the file to your target folder.

You can also save the file to the target format in TagEditor. See Cleaning Up Translated Files on page 12-17 for more information.

Previewing File Output During 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.

D

NOTE Message strings cannot be previewed. For example, if you try to access the Preview Mode while your cursor is placed within a pair of string tags somewhere outside of a menu or dialog element, a message is displayed stating that the string cannot be previewed. FILE FORMATS REFERENCE GUIDE

12-15

12

Localizing Resource Files

When you preview a menu or a dialog, an external preview application will open, containing the menu or dialog to preview.

D

NOTE A preview just represents a token menu or dialog. It does not implement any functionality and dialog control elements cannot be resized in the preview.

Verifying Translated Files 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 message to jump to the corresponding string and correct the problem.

12-16

FILE FORMATS REFERENCE GUIDE

Localizing Resource Files

D

12

NOTE Even if problems are reported during verification, it does not mean that your target file is invalid. For example, if your translation contains duplicate shortcut key assignments, the targetlanguage application will still run. However, it is recommended that you correct such problems to 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 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 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.

FILE FORMATS REFERENCE GUIDE

12-17

12

Localizing Java .properties Files

LOCALIZING JAVA .PROPERTIES FILES The Java Resource Files Filter allows you to add files directly to SDL Trados Synergy or to open and translate java properties files directly in TagEditor. Using the filter, you can directly process Java properties files across all SDL Trados applications, such as Synergy (or Translator's Workbench if you are not using Synergy) for analysis, pre-translation, and clean-up and WinAlign for alignment of existing properties files. The Java Properties Filter recognizes the .properties file format.

Using the Filter Settings Application for the Java Properties Filter You can use the Filter Settings application to modify some of the settings for Java Properties files: C

Comments

C

Delimiters

C

Empty values and verification

C

Tags

C

Entities

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

12-18

FILE FORMATS REFERENCE GUIDE

Localizing Java .properties Files

12

To run the Filter Settings application: 1

Select Start > Programs > SDL International > SDL Trados 2007 > Trados > Filters > Filter Settings. Alternatively, click the link in the Start view in SDL Trados Synergy. The Filter Settings application opens.

2

Click Java Resource files and select an option. Follow the directions shown for each setting to make changes.

3

Click Save to save your changes.

4

Click Exit to close the application.

E

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

Modifying the Java Properties Filter Settings File During conversion to and from TradosTag, the Java Properties filter processes content according to instructions that are outlined in the Java Properties filter settings file. The name of this file is JavaResourceFilter_1_0_0_0.xml and it is installed by default to C:\Documents and Settings\All Users\Application Data\SDL International\Filters. Note that the Application Data folder may be hidden and you will have to set it to be visible if you want to see this folder and any subfolders. Also, if you want to make any changes to files in this folder, you must have read/write access to this folder. Consult your IT department for more information. The settings in the filter settings file determine which elements of the Java document will be processed. The default settings are suitable for most conversion tasks, however, in certain situations, you may wish to modify one or more of the default settings. You generally modify settings in the SDL Trados Filter Settings application, as outlined above. You may also wish to change settings manually by opening the XML file directly in an appropriate editor.

D

NOTE C We recommend that only advanced XML users modify the Java Properties filter settings file. Before making any changes, create a backup of the original file. C For more information about modifying the Java Properties filter settings file, contact SDL Consultancy.

FILE FORMATS REFERENCE GUIDE

12-19

12

Localizing Java .properties Files

Translation Workflow Translation of a Java properties file involves the following steps:

12-20

1

Create a folder structure for your translation project. An orderly folder structure helps you to 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

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

4

Open your Java properties files in TagEditor. Your file will look similar to this

5

Translate your Java properties files in TagEditor.

FILE FORMATS REFERENCE GUIDE

Localizing Java .properties Files

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.

8

Save the target files in TradosTag (TTX) bilingual format, using the Save Bilingual As command in TagEditor.

9

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

10

Open the translated resource files in your build environment for testing.

D

NOTE

12

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

FILE FORMATS REFERENCE GUIDE

12-21

12

Defining Java Virtual Machine Size filter settings

DEFINING JAVA VIRTUAL MACHINE SIZE FILTER SETTINGS When you are working with RC files or java .properties files, you may receive a java.lang.OutofMemory error when you attempt use the Save Target As command in TagEditor. This error occurs when the Heap Size of the Java virtual machine is set too low. If you increase the minimum/maximum amount of available Java memory, this error will not occur. You can increase the minimum/maximum amount of available Java memory using the Java Virtual Machine Size filter settings, which you define in the Filter Settings application: 1

Select Start > Programs > SDL International > SDL Trados 2007 > Trados > Filters > Filter Settings. Alternatively, click the link in the Start view in SDL Trados Synergy. The Filter Settings application opens.

2

Click Java Virtual Machine Size to display the Java Virtual Machine Size Filter Settings page.

The filter automatically checks for the total amount of available RAM and adjusts the figures in the Minimum Java Memory and Minimum Java Memory drop-down lists accordingly. 3

To change the minimum and maximum amount of Java memory, select the Change Java virtual machine size checkbox and adjust the values in the Minimum Java Memory and Minimum Java Memory drop-down lists.

Click Save to save your changes and click Exit to close the application. 12-22

FILE FORMATS REFERENCE GUIDE

TRANSLATING SDLX FILES

This chapter discusses how to edit ITD files coming from SDLX in TagEditor.

D

NOTE SDLX 2005 SP1 must be installed before you can use TagEditor to translate SDLX ITD files.

Chapter

13

13

About Working with SDLX Documents

ABOUT WORKING WITH SDLX DOCUMENTS SDLX ITD Files are the bilingual files created during translation when you are using SDLX. SDLX documents have a file extension of .itd. ITD files can be edited or reviewed in TagEditor, and you can leverage from your Translator's Workbench translation memory but the analysis and clean up function must take place in SDLX 2005 SP1. They are translated in the same way as other file types but there are some differences: C

ITD files are automatically formatted into translation units (TUs); only the target segment text can be edited

C

ITD specific options are available from the SDLX menu and the SDLX toolbar

C

ITD files cannot be saved as TTX files

C

ITD files cannot be opened in any other SDL Trados application (including Translator's Workbench)

C

ITD files should be returned to SDLX for translation memory updating and export to target format.

Translation Memory When translating ITD files you use Translator's Workbench for translation memory functions. If you wish to use an SDLX translation memory, it must be exported to SDL Trados format and then opened in Translator's Workbench. To do this open the ITD files in SDLX and use the File List to Trados function which is available from the Export to format option on the TM menu in SDLX Edit and SDLX Maintain. Alternatively, you could use the Export to TMX option on the TM menu in SDLX Edit or SDLX Maintain. However, you could use an SDL Trados translation memory (TM) when you are translating the file as the SDLX project manager can update the SDLX TM when the translation has been completed and the file returned to them.

SDLX Menu The SDLX menu is located on the Edit menu. It contains options for confirming and unconfirming segments and for navigating the ITD by moving from one unconfirmed segment to the next. The SDLX menu options are only available when you are working on an ITD file.

13-2

FILE FORMATS REFERENCE GUIDE

About Working with SDLX Documents

13

SDLX Toolbar The SDLX toolbar is automatically enabled when you are working on an ITD file. It contains options for confirming segments and navigating the ITD file. The SDLX toolbar contains three options:

C

Confirmed

C

Previous Unconfirmed - moving up the document from the current segment, go to the next unconfirmed segment

C

Next Unconfirmed - moving down the document from the current segment, go to the next unconfirmed segment.

- toggles the confirmed status for the current segment on/off

TagEditor Toolbar Only three tags may be inserted into ITD segments: , and . Other tag options are disabled when working on ITD files.

FILE FORMATS REFERENCE GUIDE

13-3

13

About Working with SDLX Documents

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

FILE FORMATS REFERENCE GUIDE

About Working with SDLX Documents

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.

FILE FORMATS REFERENCE GUIDE

13-5

13

About Working with SDLX Documents

SDLX> Go To Next Unconfirmed Translation Moving down the document from the current segment, go to the next segment which has not been confirmed. The keyboard shortcut for this option is F5.

SDLX> Go To Previous Unconfirmed Translation Moving up the document from the current segment, go to the next segment which has not been confirmed. The keyboard shortcut for this option is Ctrl+F5.

SDLX> Open/Get Next Unconfirmed Opens the next unconfirmed segment, searches for potential matches in the translation memory and transfers the translation, if any, to your document. Use this button to start translation mode for SDLX ITD files. The keyboard shortcut for this option is Ctrl+F5.

SDLX> Set/Close Next Unconfirmed Open/Get Closes the currently open translation unit, saves it in the translation memory, opens the next segment and transfers the translation, if any, to your document. Use this button to confirm a translation and move on to the next segment when translating SDLX ITD files. The keyboard shortcut for this option is Alt+Ctrl+Enter.

Cleaning up SDLX Files Any batch processing including analysis and clean up of SDLX ITD files must be carried out in SDLX 2005 SP1 or higher.

13-6

FILE FORMATS REFERENCE GUIDE

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.

D

NOTE In order to use the SDL Generic Delimited Filter Settings you must have SDLX 2005 SP1 (Lite version or better) installed. SDLX 2007 is always installed alongside SDL Trados 2007.

Chapter

14

14

Generic Delimited Text Files

GENERIC DELIMITED TEXT FILES You can localize ASCII text files which are delimited using a specified delimiter such as semi-colon or tab. You can use the SDL Trados Filter Settings application to determine how your generic delimited text files should be processed.

Using the Filter Settings Application for the SDL Generic Delimited Filter You can use the SDL Generic Delimited files filter Settings to determine which file types can be processed using this filter.

D

NOTE In order to use the SDL Generic Delimited files filter settings you must have SDLX 2005 SP1 (Lite version or better) installed.

To run the Filter Settings application: 1

14-2

Select Start > Programs > SDL International > SDL Trados 2007 > Trados > Filters > Filter Settings. Alternatively, click the link in the Start view in SDL Trados Synergy. The Filter Settings application opens.

FILE FORMATS REFERENCE GUIDE

Generic Delimited Text Files

2

Click SDL Generic Delimited files and click the Filter options button to open the Generic Delimited Filter Options dialog box.

3

Select any settings you want to define for your filter and click OK.

4

Click Save to save your changes.

5

Click Exit to close the application.

E

TIP

14

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

Modifying the 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:\Documents and Settings\All Users\Application Data\SDL International\Filters. Note that the Application Data folder may be hidden and you will have to set it to be visible if you want to see this folder and any subfolders. Also, if you want to make any changes to files in this folder, you must have read/write access to this folder. Consult your IT department for more information. The settings in the filter settings file determine which elements of the text file will be treated during translation. By default, you modify settings in the SDL Trados Filter Settings application, as outlined above. You may also wish to change settings manually by opening the XML file directly in an appropriate editor.

FILE FORMATS REFERENCE GUIDE

14-3

14

Generic Delimited Text Files

D

NOTE C We recommend that only advanced XML users modify the SDL Generic Delimited filter settings 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, contact SDL Consultancy.

Translation Workflow Translation of your delimited file involves the following steps:

14-4

1

Create a folder structure for your translation project. An orderly folder structure helps you to 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

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

4

Translate your text files in TagEditor.

5

Save the target files in TradosTag (TTX) bilingual format, using the Save Bilingual 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.

6

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

D

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

FILE FORMATS REFERENCE GUIDE

TRANSLATING OPENOFFICE AND STAROFFICE FILES

SDL Trados 2007 supports the translation of OpenOffice and StarOffice files. Open Office and StarOffice files are similar to each other and are handled in the same way by SDL Trados 2007.

D

NOTE If you are working with SDL Trados Synergy, this chapter is not relevant to you, as you can add OpenOffice files directly to Synergy projects.

Chapter

15

15

Overview

OVERVIEW Supported Versions SDL Trados 2007 supports files from OpenOffice 1.1.5, OpenOffice 2 and StarOffice 8. OpenOffice or StarOffice do not need to be installed in order to translate files but in order to see what your files look like once they have been translated you must have the OpenOffice or StarOffice application.

Supported File Types The following StarOffice and Open Office file types are supported by SDL Trados.

OpenOffice C

ODT for word processing

C

ODS for spreadsheets

C

ODP for presentations

StarOffice C

SXW for word processing

C

SXC for spreadsheets

C

SXI for presentations

The SDL OpenOffice Filter Settings File During conversion to and from TradosTag, SDL Trados processes content according to instructions that are outlined in the SDL OpenOffice filter settings file. The name of this file is OpenOfficeFilter_1_0_0_0.xml and it is installed by default to C:\Documents and Settings\All Users\Application Data\SDL International\Filters. Note that the Application Data folder may be hidden and you will have to set it to be visible if you want to see this folder and any subfolders. Also, if you want to make any changes to files in this folder, you must have read/write access to this folder. Consult your IT department for more information.

15-2

FILE FORMATS REFERENCE GUIDE

Overview

15

The settings in the filter settings file determine which elements of the text file will be treated during translation. By default, you modify settings in the SDL Trados Filter Settings application, as outlined above. You may also wish to change settings manually by opening the XML file directly in an appropriate editor.

D

NOTE C We recommend that only advanced XML users modify the SDL OpenOffice filter settings file. Before making any changes, create a backup of the original file. C For more information about modifying the SDL OpenOffice filter settings file, contact SDL Consultancy.

Translation Workflow Translation of your OpenOffice file involves the following steps: 1

Create a folder structure for your translation project. An orderly folder structure helps you to 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

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

4

Translate your text files in TagEditor.

5

Save the target files in TradosTag (TTX) bilingual format, using the Save Bilingual 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.

6

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

D

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

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.

FILE FORMATS REFERENCE GUIDE

15-3

15

Overview

Defining Java Virtual Machine Size filter settings When you are working with OpenOffice files, you may receive a java.lang.OutofMemory error when you attempt use the Save Target As command in TagEditor. This error occurs when the Heap Size of the Java virtual machine is set too low. If you increase the minimum/maximum amount of available Java memory, this error will not occur. You can increase the minimum/maximum amount of available Java memory using the Java Virtual Machine Size filter settings, which you define in the Filter Settings application: 1

Select Start > Programs > SDL International > SDL Trados 2007 > Trados > Filters > Filter Settings. Alternatively, click the link in the Start view in SDL Trados Synergy. The Filter Settings application opens.

2

Click Java Virtual Machine Size to display the Java Virtual Machine Size Filter Settings page.

The filter automatically checks for the total amount of available RAM and adjusts the figures in the Minimum Java Memory and Minimum Java Memory drop-down lists accordingly. 3

To change the minimum and maximum amount of Java memory, select the Change Java virtual machine size checkbox and adjust the values in the Minimum Java Memory and Minimum Java Memory drop-down lists.

Click Save to save your changes and click Exit to close the application.

15-4

FILE FORMATS REFERENCE GUIDE

TRANSLATING TEXT-BASED FILES

This chapter discusses how to prepare text files for translation using the Regular Expression text file filter. Sections include: C

Overview

C

Using the Filter Settings Application for the Regular Expressions Filter

C

Modifying the Regular Expression Settings File

Chapter

16

16

Overview

OVERVIEW The Regular Expression text files filter allows you to add text files directly to SDL Trados Synergy or to open and translate text files directly in TagEditor. Using the filter, you can directly process text files across all SDL Trados applications, such as Synergy, TagEditor, Translator’s Workbench and WinAlign. Text files often contain text for translation or localization in a pre-defined structure. Using the Regular Expression text files filter allows this structure to be retained during the translation process.

Using the Filter Settings Application for the Regular Expressions Filter You can use the Regular Expressions text files filter settings to to define external patterns describing the structure of your text files or to define internal patterns specifing the text blocks that should be converted to internal tags during translation. You can also specify the source and target encoding for your files or use the built-in default codepage detection feature. You can also reset the filter settings back to the default values.

D

16-2

NOTE The regular expressions in this filter follow the implementation in the Microsoft .NET Framework version 2.0.

FILE FORMATS REFERENCE GUIDE

Overview

16

To run the Filter Settings application: 1

Select Start > Programs > SDL International > SDL Trados 2007 > Trados > Filters > Filter Settings. Alternatively, click the link in the Start view in SDL Trados Synergy. The Filter Settings application opens.

2

Click Regular Expressions text files.

3

If you want to specify the source encoding for your files, select an option from the Source encoding drop-down list.

D

NOTE

4

If you want to specify the target encoding for your files, select an option from the Target encoding drop-down list.

5

If you want to use external patterns to define the structure of your text files, click External patterns under Regular Expression text files in the left-hand pane.

If you want to use the built-in default codepage detection feature, leave the default selection, _Default (code-paged detection)_, selected here.

C In the Opening pattern and Closing pattern text boxes, enter opening and closing patterns to define the start and end point of external tags. Any text in external tags should be skipped and not exposed for translation. Click Add to add the external tag setting to the list. C To delete an external tag setting, select it in the list and click Del.

FILE FORMATS REFERENCE GUIDE

16-3

16

Overview

6

If you want to use internal patterns to define which text should be converted to internal tags, click Internal patterns under Regular Expression text files in the left-hand pane.

C In the Internal tag pattern text box, enter the interal pattern you want to use to convert something into an internal tag. Click Add to add the internal tag setting to the list. C To delete an internal tag setting, select it in the list and click Delete.

16-4

7

Click Save to save your changes.

8

Click Exit to close the application.

E

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

FILE FORMATS REFERENCE GUIDE

Overview

16

Modifying the Regular Expression Settings File During conversion to and from TradosTag, the Regular Expression filter processes content according to instructions that are outlined in the Refular Expression Filter Settings file. The name of this file is RegExFileFilter_1_0_0_0.xml and it is installed by default to C:\Documents and Settings\All Users\Application Data\SDL International\Filters. Note that the Application Data folder may be hidden and you will have to set it to be visible if you want to see this folder and any subfolders. Also, if you want to make any changes to files in this folder, you must have read/write access to this folder. Consult your IT department for more information. The settings in the filter settings file determine which elements of the text file will be treated during translation. By default, you modify settings in the SDL Trados Filter Settings application, as outlined above. You may also wish to change settings manually by opening the XML file directly in an appropriate editor.

FILE FORMATS REFERENCE GUIDE

16-5

16

16-6

Overview

FILE FORMATS REFERENCE GUIDE

SUPPORTED LANGUAGES

This appendix covers supported languages and locales for SDL Trados Synergy .

Appendix

A

A

Supported Languages and Locales

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 SDL Trados Synergy and 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

Default

1069

Default

1026

Armenian Basque Bengali Bulgarian A-2

FILE FORMATS REFERENCE GUIDE

Supported Languages and Locales

Language

SubLanguage

ID

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

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

A

Divehi (Maldives)

FILE FORMATS REFERENCE GUIDE

A-3

A

Supported Languages and Locales

Language

SubLanguage

ID

French

Belgium

2060

French

Canada

3084

French

France

1036

French

Luxembourg

5132

French

Switzerland

4108

Gaelic

Ireland

1084

Gaelic

Scotland

3132

German

Austria

3079

German

Germany

1031

German

Liechtenstein

5127

German

Luxembourg

4103

German

Switzerland

2055

Greek

Greece

1032

Israel

1037

Hungarian

Hungary

1038

Icelandic

Iceland

1039

Indonesian

Indonesia

1057

Italian

Italy

1040

Italian

Switzerland

2064

Japanese

Japan

1041

Korea

1042

Georgian (Georgia)

Gujarati (India) Hebrew Hindi (India)

Kannada (India) Kazakh Konkani (India) Korean A-4

FILE FORMATS REFERENCE GUIDE

Supported Languages and Locales

Language

SubLanguage

ID

Latvian-Lettish

Latvia

1062

Lithuanian

Lithuania

1063

Macedonian

Macedonia

1071

Malay

Malaysia

1086

Norwegian

Bokmal

1044

Norwegian

Nynorsk

2086

Polish

Poland

1045

Portuguese

Brazil

1046

Portuguese

Portugal

2070

Romanian

Romania

1048

Russian

Russia

1049

Serbian-Cyrillic

Yugoslavia

3098

Serbian

Yugoslavia

2074

Slovak

Slovakia

1051

Slovenian

Slovenia

1060

Spanish

Argentina

11274

Spanish

Bolivia

16394

Spanish

Chile

13322

Spanish

Colombia

9226

Spanish

Costa Rica

5130

A

Malayalam Marathi (India) Mongolian Northern Sotho

Punjabi (Gurmukhi - India) Quechua (all variants)

Sanskrit (India)

FILE FORMATS REFERENCE GUIDE

A-5

A

Supported Languages and Locales

Language

SubLanguage

ID

Spanish

Dominican Republic

7178

Spanish

Ecuador

12298

Spanish

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

Philippines

1124

Thailand

1054

Turkish

Turkey

1055

Ukrainian

Ukraine

1058

Urdu

Pakistan

1056

Syriac (Syria) Tagalog Tamil (India) Tatar Telugu (India) Thai Tswana

A-6

FILE FORMATS REFERENCE GUIDE

Supported Languages and Locales

Language

SubLanguage

ID

Vietnamese

Vietnam

1066

Welsh

Wales

2108

A

Uzbek (Cyrillic), Uzbek (Latin)

Two-letter Language Codes from ISO 639

Afrikaans

AF

Albanian

SQ

Arabic

AR

Armenian

HY

Azeri (Cyrillic)

AZ-LT

Azeri (Latin)

AZ-CY

Basque

EU

Bengali

BN

Bulgarian

BG

Byelorussian

BE

Catalan

CA

Chinese

ZH

Croatian

SH-HR

Czech

CS

Danish

DA

Dutch

NL

English

EN

Estonian

ET

Faeroese

FO

FILE FORMATS REFERENCE GUIDE

A-7

A

A-8

Supported Languages and Locales

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

FILE FORMATS REFERENCE GUIDE

Supported Languages and Locales

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

FILE FORMATS REFERENCE GUIDE

A

A-9

A

Supported Languages and Locales

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

Two-letter Country Codes From ISO 3166

A-10

Algeria

DZ

Argentina

AR

Australia

AU

Austria

AT

Azerbaijan

AZ

Bahrain

BH

Belgium

BE

Bolivia

BO

Brazil

BR

Canada

CA

Caribbean

CB

FILE FORMATS REFERENCE GUIDE

Supported Languages and Locales

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

FILE FORMATS REFERENCE GUIDE

A

A-11

A

A-12

Supported Languages and Locales

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

FILE FORMATS REFERENCE GUIDE

Supported Languages and Locales

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

FILE FORMATS REFERENCE GUIDE

A

A-13

A

A-14

Supported Languages and Locales

FILE FORMATS REFERENCE GUIDE

GLOSSARY ANSI

A

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

Access rights The 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 are defined in Server Manager.

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

Alignment Process of building a translation memory from previously translated material. WinAlign is the alignment tool.

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

Attribute An unordered set of key-value bindings for an element in an SGML, HTML, or XML document tree.

Ancillary file TradosTag, 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.

B Batch processing The practice of processing multiple files at one time. The Analyse, Translate and Clean Up utilities in Translator’s Workbench can be used to process files individually or in batches. For this reason, they are known as batch tools.

FILE FORMATS REFERENCE GUIDE

Glossary-1

G Bi-directional Refers to those languages that have a rightto-left reading order, visual appearance and alignment. Arabic and Hebrew are bidirectional languages.

Book file Used 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, and assigning page numbering.

C

Character style Font 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 up Feature 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 computer Callout Caption that appears beside a graphic, explaining items in the graphic.

Catalog file Interleaf 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 file File created by S-Tagger for Interleaf from catalog files.

Character set A 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.

Glossary-2

FILE FORMATS REFERENCE GUIDE

Computer in a network that hosts a frontend 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/server Computer 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 file File generated by the S-Tagger verification feature. It details all errors, alerts and warnings about tag changes in the target file. Also known as the verifier report.

G Concordance

DTD

Feature in Translator’s Workbench that allows you to search the translation memory for text fragments during interactive translation. The Concordance tab in the Translation Memory Options dialog box in Translator’s Workbench defines the parameters for concordance searching.

Document 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 the HTML 4.0 DTD; all HTML 4.0 documents are based on this DTD.

Customize verification Settings that allow you to suppress certain alerts and warnings during the verification process. These settings are available in the S-Taggers and in the S-Tag Verifier plug-in in TagEditor. When you select to 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 server The back end in a client/server installation of the SDL Trados translation solution. This is where all server-based translation memories are stored.

DBCS Double-byte Character Set. DBCS languages such as Japanese, Korean and Chinese require special DBCS fonts.

Demo mode Certain SDL Trados applications can be used in demonstration mode when the necessary license information is not available. When an application is running in demo mode, file size limitations and feature restrictions may apply.

DTP Desktop Publishing.

E Element A type of node in an SGML, HTML, or XML document tree. An SGML element is typically represented by a start tag ("") and an end tag (""). The start tag can contain attributes. Both the start tag and end tag for an element typically contain the "tag name" for that element. In XML, an element is always represented either by an explicit start tag and end tag, or by an empty element tag.

Excel filter SDL Trados filter component that converts Excel documents (XLS, XLT) to and from TradosTag (TTX). The Workbench batch tools and the TagEditor editing environment provide direct support for Excel documents by automatically converting them to TradosTag.

Extended characters Accented letters and symbols which do not appear in the standard ASCII character set, for example, ‘à’ or ‘é’.

FILE FORMATS REFERENCE GUIDE

Glossary-3

G External tag Tag 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.

H Hard return Manual 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.

F

Hard returns are also known as forced returns in FrameMaker.

Font Mapper for FrameMaker Font 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.

HTML Hypertext Markup Language. HTML is the authoring language used to create documents on the World Wide Web. HTML is similar to SGML, although it is not a strict subset. HTML defines the structure and layout of a Web document by using a variety of tags and attributes.

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.

FrameMaker FrameMaker is a powerful desktop publishing and book-building package from Adobe. It runs on several platforms; UNIX, Macintosh and Windows. See also S-Tagger for FrameMaker.

Fuzzy match One of five match types identified 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.

Glossary-4

FILE FORMATS REFERENCE GUIDE

I IASCII Interleaf ASCII. IASCII is a text file format which allows you to exchange information between Interleaf and other applications. All formatting, file and page layout is retained in the IASCII file.

InDesign Desktop publishing package from Adobe. SDL Trados supports tagged text files from InDesign 2.0 or later. See also Story Collectors.

G Index marker

License file

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

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

Interleaf A desktop publishing package from BroadVision, which has some similar features to FrameMaker. The STF produced from Interleaf files is similar to the STF produced from FrameMaker files. Interleaf runs on several platforms; UNIX, DOS and Windows. See also S-Tagger for Interleaf.

Internal tag Tag 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 nonbreaking spaces are represented as internal tags. During the translation process, internal tags are treated differently to external tags.

L LAN Local area network. A computer network that spans a relatively small area. LAN computers are usually linked to each other via Ethernet connections. The SDL Trados translation solution can be deployed as a client/server system on a LAN.

See also Demo mode.

M Middleware In a client/server architecture, the middleware sits between the client components and the back-end database server. The main purpose of the middleware is to facilitate successful communication between the database server and its clients. TM Server acts as the middleware in a client/server implementation of the SDL Trados translation solution. See also TM Server.

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.

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

See also WAN.

FILE FORMATS REFERENCE GUIDE

Glossary-5

G MultiTerm SDL terminology management system. MultiTerm exists as a client/server system (MultiTerm 2007) and as a desktop application (MultiTerm Workstation). The main user interface for both versions of the system is called MultiTerm. Both versions of the MultiTerm system are integrated with Translator’s Workbench to provide term recognition during translation. See also Term recognition.

MultiTerm Extract SDL terminology application for extracting terms from documents. MultiTerm Extract extracts terms and presents them in an easyto-use interface for validation and export. Terminology data can be exported directly from MultiTerm Extract to local and remote MultiTerm termbases.

MultiTerm 2007 Client/server version of the SDL terminology management system. In MultiTerm 2007, termbase data can be stored locally or, in a multi-user setup, on a network database server. The main client interface for MultiTerm 2007 is called MultiTerm.

O ORG file File containing structural information for the conversion of STF files to original format using the S-Taggers. The S-Taggers produce an ORG file for each MIF/IASCII file that is converted to STF. The ORG file is used to convert the translated STF file back to its original MIF/IASCII format.

Glossary-6

FILE FORMATS REFERENCE GUIDE

P Page break In Interleaf and FrameMaker, you can set up a component/paragraph style so that it always starts at the top of a page or always stays with the following paragraph. Most documents will contain some components/paragraph styles whose pagination attributes are overridden, for example, when a forced page break has to be inserted.

PageMaker Desktop publishing package from Adobe. SDL Trados supports tagged text files from PageMaker version 6.5 or later. See also Story Collectors.

Paragraph Style Used with FrameMaker, paragraph style properties, such as indents, line spacing, tab stops, font attributes (typeface, size or color), pagination, hyphenation and word spacing, are all assigned within the Paragraph Designer. In Interleaf, paragraph styles are known as components and the style properties are assigned within the component’s master property sheet.

Placeable Part of a segment that has been identified as a non-text item in Translator’s Workbench, for example a number or a hyperlink. Placeables do not require translation but must be placed in the correct location in the target segment.

G PowerPoint filter

Read-only

SDL Trados filter component that converts PowerPoint documents (PPT, PPS, POT) to and from TradosTag (TTX). The Workbench batch tools and the TagEditor editing environment provide direct support for PowerPoint documents by automatically converting them to TradosTag.

Interleaf allows you to apply a read-only property to any component or subcomponent. Components with read-only properties assigned to them cannot be edited in 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.

Pre-translation Process of pre-translating multiple files using the Translate command in Translator’s Workbench to extract data from a particular translation memory. Translator’s Workbench automatically inserts matches from the translation memory into the document for translation.

Repetition match One 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. The first 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.

Public entity set A 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 accented characters, as used in Western European alphabets.

RTF Rich Text Format. This is an interchange file format invented by Microsoft. See also Workbench RTF.

S

Q

Server computer QuarkXPress Desktop publishing package from Quark. SDL Trados supports tagged text files from QuarkXPress version 4.1 or later. See also Story Collectors.

R

A computer on which server software is installed.

SGML Standard Generalized Markup Language, a language used for designing tagged text formats.

Shift-JIS

RC filter A filter used to convert resource files into the TTX format.

A standard for Japanese character encoding, used mainly under Windows and Macintosh.

FILE FORMATS REFERENCE GUIDE

Glossary-7

G Smart quotes Curly 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 characters Symbols 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 FrameMaker SDL 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-Tags Brief coded statements in STF files that represent formatting in FrameMaker and Interleaf documents. S-Tags are divided into external tags and internal tags.

Glossary-8

FILE FORMATS REFERENCE GUIDE

STF file File produced when you convert MIF/IASCII files to STF using the S-Taggers. Formatting from the FrameMaker/Interleaf documents is represented by brief coded statements (S-Tags). STF files are translated using Translator’s Workbench in the TagEditor or Microsoft Word editing environments.

STF file format When 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 Collectors SDL 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 after translation.

Stopword List A 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 Term recognition

T TagEditor SDL Trados translation editor for tagged text formats 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 File Document 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 Manager The Tag Settings Manager is used to manage the tag settings files that are available on your file system. The Tag Settings Manager provides access to the Tag Settings Wizard where you can create and edit tag settings files. You can access both the manager and the wizard from TagEditor, WinAlign, Translator’s Workbench and LM Studio.

TeamWorks Manager TeamWorks Manager is an 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.

Feature in Translator’s Workbench that makes use of the interface between Translator’s Workbench and MultiTerm. When you activate term recognition, terms stored in the selected MultiTerm termbase are automatically suggested to you during translation.

Termbase Database used to store terminology and related information.

TM Anywhere In a client/server implementation of the SDL Trados translation solution, TM Anywhere is a web server application that enables TM Server to communicate with Translator’s Workbench using an Internet connection.

TM Server Middleware 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 GXT Globalization management system for enterprise translations integrating best practice workflow with the proven ability of the SDL Trados desktop translation solution.

FILE FORMATS REFERENCE GUIDE

Glossary-9

G Server Manager Server Manager is the administration client for a client/server implementation of the SDL Trados translation solution. It comprises two separate modules: TM Manager and User Manager. TM Manager is used to configure TM Server and related components, to create serverbased 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.

TradosTag An XML-based file format for representing tagged text and bilingual data. TradosTag (TTX) provides a standard method for processing XML, HTML, SGML, PPT, XLS and 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 memory Database of segment or sentence pairs. Each source language segment is paired with its corresponding target language segment.

See also TM Server.

SDL TeamWorks SDL 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 the TeamWorks system is called TeamWorks.

TM Server TM 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 stored in a group of files on your system.

Glossary-10

FILE FORMATS REFERENCE GUIDE

Translator’s Workbench Translation 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.

TTX See also TradosTag.

T-Windows for Clipboard Editor for translating Clipboard files.

G

W

V Validation In TagEditor, validation refers to the process of validating an XML document after translation using the XML Validator plug-in.

Ventura Desktop publishing package from Corel. SDL Trados supports tagged text files from Ventura version 5 or later.

WAN Wide area network. A computer network that 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.

Warning Verification Refers 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-in SDL 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.

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

WinAlign SDL 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 RTF Workbench RTF documents (also referred to as tagged RTF documents) are files that comply with the Translator’s Workbench standard 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.

FILE FORMATS REFERENCE GUIDE

Glossary-11

G

X XML Extensible Markup Language. XML is a simple, very flexible text format subset of SGML. See also SGML.

XML Validator SDL Trados plug-in that allows you to validate XML documents that have been translated in TagEditor.

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

Glossary-12

FILE FORMATS REFERENCE GUIDE

INDEX A ■

C ■

Adobe FrameMaker see FrameMaker

character entities converting 2-16

Adobe InDesign see InDesign

Clean Up command Translator’s Workbench 2-34

Adobe PageMaker see PageMaker

comparing the TTX workflow to the RTF workflow 9-2

Application Programming Interface (API) QuarkXPress 5-2

conditional ML 2-23

conditional markup language tags 2-23 conditional ML tags 2-23 Context TM 3-5

B ■ Batch functions InDesign exporting stories 6-20 importing stories 6-22 setting the story order 6-18 QuarkXPress exporting stories 5-15 importing stories 5-17 setting the story order 5-14 bilingual target files cleaning up IASCII files 3-7 InDesign files 6-16 MIF files 3-7 ML files 2-33 PageMaker files 4-10 PowerPoint files 10-15 QuarkXPress files 5-12 RoboHelp files 8-25 RTF files 9-24 Ventura files 7-5 Word files 8-4, 9-3 Bookmark Handler macros 8-6 adding template 8-6 running 8-7 browsers 2-17, 2-18

Cross-reference, PageMaker 4-12

D ■ Directory structure InDesign 6-11 PageMaker 4-6 QuarkXPress 5-7 DLG files 12-9 DLL files 12-2 Document layers PageMaker 4-13 Document type definition (DTD) 2-5 DTD tutorial on Tag Settings Wizard 2-8–2-18

E ■ Excel filter 11-2 handling macros 11-5 preparing files 11-5 EXE files 12-2 executable files EXE,DLL, OCX, and LNG files 12-2 Exporting stories from InDesign 6-15 from PageMaker 4-9 FILE FORMATS REFERENCE GUIDE

I-1

I from QuarkXPress 5-11 from Ventura 7-4

F ■ File organization InDesign 6-11 PageMaker 4-6 QuarkXPress 5-7 filter Excel 11-2 Folder structure InDesign 6-11 PageMaker 4-6 QuarkXPress 5-7 Font Mappers FrameMaker 3-3 Interleaf 3-3 FONT tags 2-15 footnotes in RTF Help files 8-17–8-19 translating in Word 8-10 FrameMaker preparing MIF files for conversion 3-5 translating 3-6 using Font Mappers 3-3

■I IASCII files 3-3 cleaning up bilingual target files 3-7 Importing stories InDesign 6-17 PageMaker 4-11 QuarkXPress 5-13 InDesign cleaning up bilingual target files 6-16 directory structure 6-11 story order 6-12 Index entry, PageMaker 4-12 Inline graphics InDesign 6-7 PageMaker 4-13 QuarkXPress 5-7 Installation Story Collector for InDesign 6-8 Story Collector for PageMaker 4-4 Story Collector for QuarkXPress 5-5 Interleaf preparing IASCII files for conversion 3-5 translating 3-6 using Font Mappers 3-3 Internet browsers 2-17, 2-18 Internet Explorer 2-17, 2-18

G ■ Generic Delimited Text files 14-2 Generic Tag Verifier 2-33 Graphics replacing references with placeables 8-20–8-21

J ■ Japanese PageMaker version 6.5 and 7 character support 4-14 Java properties files 12-18 jumps 8-24

H ■ HTML previewing within TagEditor 2-17, 2-18 HTML files translating 2-31

L ■ LNG files 12-2 Local overrides in Word 8-5 localizing 12-18 localizing resource files using SDL Trados 12-9, 16-2

I-2

FILE FORMATS REFERENCE GUIDE

I

M ■

O ■

Macros handling macros in Excel files 11-5

OCX files 12-2

macros Bookmark Handler 8-6 Bookmark Handler template 8-6 PrepareBookmarks 8-6 RestoreBookmarks 8-6 Master page, PageMaker exporting 4-13 META tags 2-15 Microsoft Excel see Excel Microsoft PowerPoint see PowerPoint Microsoft Word see Word MIF files 3-3 cleaning up bilingual target files 3-7 ML files 2-5 ASCX 2-2 ASP, 2-2 ASP.NET 2-2 ASPX 2-2 cleaning up bilingual target files 2-33 DTD 2-3 format 2-2 HTML 2-2, 2-3 INC 2-2 JSP 2-2 PHP 2-2 preparation 2-5 Save Target As 2-33 SGML 2-2, 2-3 tag settings 2-3, 2-5 translating 2-4, 2-31 XML 2-2, 2-3 MultiDoc Pro from Citec 2-17 Multiple files InDesign 6-18 QuarkXPress 5-14

N ■

Opening Story Collector for InDesign 6-12 Story Collector for PageMaker 4-7 Story Collector for QuarkXPress 5-8 opening QuarkXpress files using SDLXtract. 5-4

P ■ PageMaker cleaning up bilingual target files 4-10 creating a folder structure 4-6 cross-references 4-12 directory structure 4-6 exporting master pages 4-13 exporting stories 4-9 index entry 4-12 installing Story Collector 4-4 Japanese version 6.5 and 7 character support 4-14 exporting and importing 4-14 preparing files 4-5 preparing PageMaker 7 files 4-5 tag error 4-13 translation process 4-10 troubleshooting 4-12 Paragraph style, Word local overrides 8-5 Placeables graphics references as 8-20–8-21 internal character styles for Help files 8-20 Plug-in Story Collector for InDesign 6-6 Story Collector for PageMaker 4-4 Story Collector for QuarkXPress 5-2 popups 8-24 PowerPoint cleaning up bilingual target files 10-15 filter 10-5 translating files 10-11–10-14 understanding the conversion process 10-5 PrepareBookmarks macro 8-6 previewing ML files in an external viewer 2-17

Netscape Navigator/Communicator 2-17, 2-18

FILE FORMATS REFERENCE GUIDE

I-3

I

Q ■

S ■

QuarkXPress batch export 5-15, 6-20 batch functions 5-14 cleaning up bilingual target files 5-12 directory structure 5-7 inline graphics 5-7 multiple page spreads 5-10, 6-15 preparing files 5-7 Story Collector 5-2 story order 5-9 story order for multiple files 5-14

Save Bilingual As command Translator’s Workbench 2-34

R ■ RC files 12-9 RC Filter 12-9, 12-18 Replace command Translator’s Workbench 2-34 Resource files 12-9, 16-2 resource files RC andDLG files 12-9, 12-18 RestoreBookmarks macro 8-6 RoboHelp files cleaning up bilingual target files 8-25 translating 8-25 RTF Files Windows help files 8-15 RTF Help files character styles for non-translatable text 8-20 cleaning up bilingual target files 9-24 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

Save Target As ML files 2-33 SDL Generic Delimited Filter 14-2, 15-2 SDL Trados RC File Verifier 12-16 SDL Trados Win32Binary Verifier 12-7 SDLX files 13-1 Segmentation 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-17 Tag Settings Wizard in TagEditor 2-8–2-18 SGML files translating 2-31 Source directory INDD 6-20 ISC 6-20 P65/PMD 4-9 QSC 5-11 QXD 5-11 TXT 4-9 spell-checking and proofreading 8-25 S-Taggers defining 3-3 for FrameMaker 3-2 for Interleaf 3-2 installing 3-2 preparing FrameMaker files for conversion 3-5 preparing Interleaf files for conversion 3-5 using 3-3 STF files 3-3 Stories exporting from InDesign 6-15 multiple files 6-20 exporting from PageMaker 4-9 exporting from QuarkXPress 5-11 multiple files 5-15 importing from InDesign 6-17 multiple files 6-22 importing into PageMaker 4-11 importing into QuarkXPress 5-13 multiple files 5-17 Story Collector for InDesign accessing help 6-9

I-4

FILE FORMATS REFERENCE GUIDE

I batch functions 6-18 creating a folder structure 6-11 describing 6-6 exporting stories 6-15 exporting stories from multiple files 6-20 importing multiple files 6-22 importing stories 6-17 installing 6-8 opening 6-12 preparing files 6-10 sample files 6-9 setting story order 6-12 story order for multiple files 6-18 tag reference 6-24–6-50 translating 6-16 Story Collector for PageMaker describing 4-2 exporting 4-9 importing translated text 4-11 installing 4-4 opening 4-7 preparing files 4-5 preparing PageMaker 7 files 4-5 setting the story order 4-8 tag reference 4-14–4-21 troubleshooting 4-12 verifying the tagged text output 4-9 Story Collector for QuarkXPress 5-2 installing 5-5 Japanese version 4.1 5-6 opening 5-8 setting up a folder structure 5-7 tag reference 5-19–5-26 Story order 5-9, 6-13 Custom 5-9, 6-13 Left-right 5-9, 6-13 PageMaker 4-2 setting for multiple files in InDesign 6-18 setting for multiple files in QuarkXPress 5-14 setting in InDesign 6-12 setting in QuarkXPress 5-9 Top-down 5-9, 6-13 supported browsers 2-17, 2-18 Supported Languages and Locales A-2 Unicode-only A-7

T ■ Tag Settings tutorial on Tag Settings Wizard 2-8–2-18 Tag settings file .NET RESX files 2-6 default DITA settings 2-6 default HTML settings 2-6 default SVG settings 2-6 default XLIFF settings 2-6 default XSL settings 2-6 tag settings file creating 2-8 editing 2-19 managing 2-7 overview 2-5 Tag Settings Manager opening 2-7 Tag Settings Properties 2-19 Tag Settings Wizard tutorial 2-8–2-18 TagEditor Internet browsers 2-17, 2-18 previewing files in an external application 2-17 Tag Settings Wizard 2-8–2-18 translation guidelines 2-31 Tagged text files verifying 2-33 Text importing into Ventura 7-6 TRADOStag description 1-5 file components 1-7 PowerPoint converting from 10-5 translating 13-1 FrameMaker files 3-6 HTML files 2-31 Interleaf files 3-6 Microsoft Word files 8-9, 9-16 ML files 2-31 PowerPoint files 10-11–10-14 RTF Help files 8-23 SGML files 2-31 Story Collector for InDesign 6-16 Ventura files 7-5 XML files 2-31 translating Word files in TagEditor 9-1 translation memory segmentation rules 8-18 setting options for help files 8-18

FILE FORMATS REFERENCE GUIDE

I-5

I Translator’s Workbench Clean Up command Update TM 2-34 Replace command 2-34 Save Bilingual As command 2-34 segmentation rules adding new 8-18 changing, for keyword translation 8-18 using the Clean Up command 2-34

W ■

Troubleshooting, PageMaker 4-12

Word Bookmark Handler macros 8-6 Bookmark Handler template 8-6 cleaning up bilingual target files 8-4, 9-3 footnotes in Help RTF files 8-17–8-19 local overrides 8-5 paragraph styles 8-5 running Bookmark Handler macros 8-7 translating 8-9, 9-16 colored text 8-14 fields 8-13 footnote pane 8-13 footnotes 8-10 after translation 8-12 tips for working with 8-13 hyperlinks 8-13 non-translatable text 8-14 spell-checking and proofreading 8-14 understanding the conversion process 9-4

TTX see TRADOStag TTX workflow 9-2, 9-3 tw4winInternal style 8-20, 8-22 tw4winJump and tw4winPopup styles 8-17

U ■ Unicode-Only Languages, Supported A-7 Update TM Clean Up command in Translator’s Workbench 2-34 using the filter 14-2, 15-2 using the TTX workflow 9-2

V ■ Ventura cleaning up bilingual target files 7-5 exporting text 7-4 importing translated text 7-6 preparing files 7-3 tag reference 7-6–7-10 translating 7-5

web browsers 2-17, 2-18 Win32 binary files 12-2 Windows32 binary files 12-2 Windows32 Binary Filter 12-2

Word files in TagEditor translating 9-1 Workflow translating PageMaker files 4-10

X ■ XML conditional 2-23

verification plug-ins SDL Trados RC File Verifier 12-16

XML files translating 2-31

verificationplug-ins SDL Trados Win32Binary Verifier 12-7

XML Validator 2-33

viewing ML files using an external application 2-17

XPath 2-24

XML Validator Filter 2-33 XPath expressions 2-24 XPath standard. 2-24 XTG files 5-4

I-6

FILE FORMATS REFERENCE GUIDE