Presupuesto

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.

T r a n s l a t i o n

3

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.

NOTE

D

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:

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

₃

FILE FORMATS REFERENCE GUIDE 3-7

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

D

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

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

translation production. NOTE

D

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.

NOTE

D

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

C o n c l u s i o n

3

CONCLUSION

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

Interleaf/QuickSilver translation process and know where to find detailed information on all tasks involved in this process:

Task Checked?

Understand how S-Taggers works and how to install the S-Taggers ✔ Prepare FrameMaker and Interleaf/QuickSilver files for translation _✔ Verify the tag content of the target files against the tag content of the original source files

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

Chapter

P A G E M A K E R F I L E S

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

O v e r v i e w

4

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.

TIP

E

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

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.