First Edition, May 1996
This edition applies to IBM TranslationManager Version 2.0 (5622-999) and to all subsequent releases and modifications until otherwise indicated in new editions or technical newsletters.
Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address below.
IBM welcomes your comments. A form for readers' comments may be provided at the back of this publication, or you may send your comments to the following address:
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
© Copyright International Business Machines Corporation 1994, 1996. All rights reserved.
Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule contract with IBM Corp.
In this part, you find descriptions of what you can do with all kinds of translation material in TranslationManager . Each type of data, such as documents, dictionaries, and folders, is considered as an object on which you can perform an action, such as copying, changing, and deleting.
For each TranslationManager object, you find a chapter containing:
Each task is described according to the following structure:
To import an object, for example a folder, is a prerequisite for working with it in TranslationManager . You export an object to work with it outside TranslationManager . Exported objects can be in TranslationManager format or in external format.
Objects in TranslationManager format are files in a compressed format and can be imported only by other TranslationManager users. For files in this format, you only have to specify the drive where to export to, or where to import from. These files are stored in the \EQF\EXPORT directory of the selected drive.
Objects in external format are ASCII encoded files that can be edited with a text editor. They can be imported by other TranslationManager users and processed by other systems. For files in external format you must specify the fully qualified DOS file name where to export to, or where to import from.
Files in external format contain SGML tags that describe the structure of the files and the data it contains. For a complete description of SGML, refer to ISO 8879, Information Processing - Text and Office Systems - Standard Generalized Markup Language (SGML).
In several windows you can request to print information.
You can print:
If you work under OS/2, the printout is sent to the printer that is assigned to your workstation as default printer when no other printer has been specified by you. If you work under Windows, you are prompted with the Print Setup window where you can specify the destination of your printout.
To perform an action on an object in TranslationManager , you can specify the options and parameters in a window specific for this action. At the bottom of the window, you find pushbuttons, where you can:
To perform an action on a list window such as the Translation Memory Listwindow in TranslationManager , you can do either of the following:
When you work with TranslationManager , the system prompts you with message windows if necessary. There are several types of messages:
All messages have a unique number and start with EQF to identify them as TranslationManager messages.
With all message windows where you are asked to confirm actions on an object, you can select a Yes to All button on the first message window that pops up after an action has been requested. When you pressed this button TranslationManager assumes the answer Yes on all subsequent message windows that ask for a confirmation. For example, while analyzing documents of a folder a message asks if you want to overwrite the target document because translation for a document has already started. If you answer Yes to All, all the following messages are then suppressed.
Some actions may require some time to complete, for example:
The progress of such an action is indicated by a so-called progress window (see Figure 2).
Figure 2. Organizing Dictionary sample window
 |
This type of window can be minimized to let you do other work in TranslationManager . When the action is completed, a message with the result of the action is displayed.
If you want to interrupt the action, double-click on the system icon of the progress window. In the following message window, you can confirm the cancelation request.
You may need to define a file when working with one of the following windows:
When you select the output option File and click on Select..., the Select File window is displayed (see Figure 3).
 |
You can complete this entry field with one of the following:
When you have selected the file name, click on Set to return to the previous window.
Results
The drive, directory, and file name you select are used by the respective function.
In the list windows, TranslationManager can show you more information in addition to the names of the list items. You can ask the system to display these view details selectively and in a sequence defined by you.
The details contain properties and statistical information of the list items, such as the:
Details can be displayed for:
To view the details, you can switch between two display modes:
In the Change View Details window, you can change the details arrangement for a specific list window (see "Changing the details setting").
Prerequisites
The respective list window is already selected.
Calling sequence
Select Names from the Utilities menu.
Results
The list window contains only the names of the list items. This may be useful when you need a narrow window on the screen.
Prerequisites
The respective list window is already selected.
Calling sequence
Select Details from the Utilities menu.
Results
The list window contains for each list item the detail information as previously defined. As an example, the Document List window is shown in Figure 4.
Figure 4. Document List window sample with selected details
 |
As a default setting, only the names are displayed. You can change the details to be displayed (see "Changing the details setting"). Once you have defined your setting of the details, they are displayed as selected.
TranslationManager lets you to customize the view details in the respective list window.
If not all details of a list item, for example a folder, fit on one line in the list window, you should set priorities.
As an example, this window is explained for the details of documents in the Document List window.
Prerequisites
The respective list window is already selected, for example a Document List window.
Calling sequence
Select Change details... from the Utilities menu.
The Change View Details window is displayed (see Figure 5).
Figure 5. Change View Details sample window for documents
 |
Options and parameters
Double-click on those view details you want to be displayed in the Document List window.
To deselect an item, double-click on the entry in the Selected box.
Click on Clear to remove all items from the Selected box. You can then begin to define a new sequence of details.
When you have selected the desired details, click on Change to activate the new setting.
Click on Cancel at any time to leave the Change View Details window. No changes are made.
Results
The list window contains the selected details in the newly-defined sequence. This setting remains active throughout the current session until you change it again.
To save the setting for the next time you start TranslationManager , respond with Yes to the prompt Do you want to save the current workbench? when you leave TranslationManager . The current settings will then be used the next time you start TranslationManager .
You can translate many types of document with TranslationManager , such as letters, brochures, booklets and manuals.
You can translate documents that were originally created with a variety of text editors, word processors, and publishing systems. The types of file you can use with TranslationManager include:
A translation project can consist of one file or a set of files. In TranslationManager , each file is treated as a document.
In their original formats, documents consist of text and layout information, called markup. Markup defines things such as the positioning of page breaks and paragraphs endings, highlighting, and font sizes.
When translating a document, TranslationManager must be able to distinguish between this markup and the text that is to be translated. By ignoring the markup information during translation, TranslationManager preserves the original format of the document-- although minor changes in the translated document can be necessary, such as adding space to a table that is full or a translated term that does not fit within a column. TranslationManager uses a different markup table for each document format type.
Each document has a number of properties, such as the source and target languages, the markup table to use with the document, and the name of the Translation Memory to use for translations.
You must specify the properties of a document when you import it into TranslationManager .
By default, all documents in a folder have the same properties, although you can change them for individual documents.
For further information on how to deal with document formats, see "Dealing with specific document formats".
You must first import documents you want to translate into TranslationManager (see "Importing a document").
This can be done by importing documents into an existing folder. At this point, TranslationManager asks you to specify the properties of the document. You can either let the system assign the default properties of the folder to which the document belongs, or you can assign different properties to the document.
Another method for importing documents is to import a complete folder that contains at least one document (see "Importing a folder").
When you go to the Translation Environment to begin translating a new document, TranslationManager analyzes the document to distinguish between the text that requires translation and markup data. It then splits up the document into translatable segments--which usually correspond to individual sentences--and markup data that is not to be translated.
TranslationManager can distinguish between abbreviations ended by a period and the end of a sentence. It uses an abbreviation list to correctly identify sentence boundaries. See "Maintaining abbreviation lists" to learn how to maintain an abbreviation list.
The TranslationManager editor displays the segments to be translated and the markup in different colors so that you can easily distinguish between the two. As you move from segment to segment, the markup data is skipped.
With the TranslationManager editor, you can check the spelling in the translated document and see suggestions for correct spellings.
TranslationManager also includes a word count function, which shows you the number of words and markup tags in the original and translated documents.
Prior to translating a document, you can check a document against the dictionaries that are installed with TranslationManager to compile a list of terms in the document that are not currently in the dictionaries. You can choose to add terms from this new terms list to a dictionary.
When translating a new version of an existing document that has already been translated, you should check whether a Translation Memory for the document already exists, or whether one can be generated.
To continue translating a document that has been partly translated by somebody else, you should first acquire all related translation material. In particular, ask for the Translation Memory and all the dictionaries that were used. These can be passed to you in the form of an exported folder.
You can then display details of the document in the Document List window, such as the properties and processing status of a document, the date of import, date of analysis, and what percentage of the document has already been translated.
After completing a translation, you can choose to export a document back into its original format to load it into the original word processing system for a final layout review.
TranslationManager offers several processing functions for documents, which you start by selecting:
Prerequisites
A folder containing at least one document (except if you import a document).
Calling sequence
Select:
Alternatively, select the Folder List window and double-click on the folder name in the list.
The Document List window for this folder is displayed.
Results
The selected folder is "opened". To perform a task on a document, select at least one document and an action from one of the toolbar menus.
Analyzing a document means splitting it up into translatable pieces called segments. Segments are in most cases equivalent to sentences. This segmentation is performed with the help of markup tables that contain specific information for the type of markup used in the document. You choose the markup table to use as one of the properties of the document.
After the analysis of a document, TranslationManager produces a copy of the original document to be used for the translation, this means, the original version of the document is kept unchanged by TranslationManager .
The system allows you to analyze documents with different results:
To analyze all documents in a folder, see "Analyzing all the documents in a folder".
Segmentation is the basic part of the analysis. You activate it implicitly when you select Open for a document that has not yet been analyzed.
Prerequisites
The folder containing the document must be opened.
Calling sequence
Select:
This takes you to the Translation Environment where the analyzed document is displayed in the Translation window.
Results
The document is segmented. You can start to translate it (see "Translating a document").
If you have Translation Memory databases available from previous translations, you have several options:
Prerequisites
Calling sequence
Select:
The Analyze Documents window (see Figure 6) is displayed.
Figure 6. Analyze Documents window
 |
Options and parameters
From the Available box select with a double-click those Translation Memory databases from where the segments are to be copied. The selected Translation Memory databases are displayed in the Selected box. You must select at least one Translation Memory, you can select a maximum of 10 Translation Memory databases.
To separate previously translated segments and new segments, you can use the following options:
This option is particularly useful in conjunction with the Add segments option. Many Translation Memory databases can be searched in one run for matching segments that are copied into the document-specific Translation Memory, and are substituted in the translation document.
A file with a format similar to an external Translation Memory is created (see "Untranslated segments file") containing empty target segments. This file can be exported for use by other systems such as a machine translation system. If an external system is able to add valid translations for these untranslated segments, the updated file can be imported into TranslationManager as a Translation Memory for translation use.
Click on Analyze to begin with the analysis of the document. As it can take some time to analyze the document, a window is displayed showing the progress of the operation.
Results
The document is segmented.
Depending on the options you selected, the document may already be partially translated, the Translation Memory updated, or a file created containing untranslated segments.
You can begin translating the document.
If you have dictionaries available containing vocabulary associated with the document, you can ask TranslationManager to generate two types of terminology list:
The generated terminology lists may contain terms that are unsuitable as terminology for your translation. In this case, you can create the lists again using exclusion lists or exclusion dictionaries to get fewer terms in the lists.
If you are only interested in terms that occur more than once in a document, you can specify a minimum number of occurrences greater than 1.
To perform the creation of terminology lists, you specify your options and parameters in two subsequent windows.
Prerequisites
Calling sequence
Select:
The List Settings window (see Figure 7) is displayed.
Figure 7. List Settings window
 |
Options and parameters
To create a new terms list, select:
To create the list of all terms of a document that are also in selected dictionaries, select:
For both new terms and found terms lists, you must specify:
If needed, you can limit the generation of terminology lists by the following options:
Click on Set to return to the Analyze Documents window.
To begin analysis, click on Analyze.
Results
The document is segmented.
Depending on the options you selected, new terms lists and found terms lists are created, and can be modified and used for dictionary updates. For information on how to process new terms lists and found terms lists, see Chapter 11. "Working with terminology lists".
You can begin translating the document.
TranslationManager uses language-specific abbreviation lists to identify correct endings of a sentence. This prevents that the period after an abbreviation is interpreted as the end of a sentence during analysis, for example in a sentence like For details see books, films, magazines, etc. and keep the subject in mind.. The period after etc. is not considered to be the end of the sentence.
TranslationManager provides default abbreviation lists for each source language supported. You can add new abbreviations, or delete or modify existing ones.
Prerequisites
Calling sequence
Select:
The list of abbreviations for the selected language is displayed. For example, Edit Abbreviations for: German(national) if you selected this language. You can now make your changes.
Options and parameters
Results
The language-specific list of abbreviations is updated and will be used for subsequent analysis runs. Depending on the language you selected, abbreviations have been changed, added, or removed from the abbreviation list for this language.
To translate a document, you must open it so that the Translation Environment for this document is displayed.
Closing a document means to stop translating a document and to leave the Translation Environment.
Calling sequence
Select Close from the Translation Environment system menu.
This takes you back to the TranslationManager main window.
Results
The translation document, the Translation Memory, and the dictionaries used are saved in their current status. You can start any other TranslationManager task. The translation of this document can be continued at any time.
TranslationManager provides a facility for counting the number of words and markup tags in a document at any time. The result is shown in a window and can be saved in a file.
To count the number of words in all the documents of a folder, see "Counting the words in all documents of a folder".
Prerequisites
At least one document must exist in the selected folder.
Calling sequence
Select:
The Count Words window (see Figure 8) is displayed.
 |
Options and parameters
Click on Count to begin counting words.
Results
The results of the word count are shown, for example, in the Word Count Results - Translation window (see Figure 9).
Figure 9. Word Count Results - Translation window
 |
If you selected Original and output to Screen, the result is displayed in the Word Count Results - Original window with the following columns for each original document:
If you selected Translation and output to Screen, the result is displayed in the Word Count Results - Translation window with the following columns for each translated document:
If you selected the File output option, the results are stored in the same format in the specified file.
To return to the previous window, close the respective Word Count Result window.
Most word processors include facilities for converting document files from one document format to another. If the file format of your word processor is not explicitly supported by TranslationManager , you may be able to use these conversion facilities to convert your file to a format that is supported directly by TranslationManager .
Sometimes, it can be helpful to have a printed version of the original document available to get a better picture of the whole document.
It is recommended that you check your document after translation for any changes concerning the layout. You can edit and print it with the word processor that was used for creating the original document. Minor format corrections might be necessary because translated text has not always the same length as the corresponding original text.
TranslationManager directly supports the document format of Ami Pro. Import these documents using the EQFAMI markup table.
Do not change, delete, or insert markup data outside translatable segments. Inline tags should be handled carefully.
The start of highlighting like bold, italics, underline, or similar is indicated with <+, any character and >. The end of this markup data is indicated with <-, the same character as at the start of this markup tag and >.
Tables, headers, and footers appear at the beginning of the document for translation.
ASCII documents are text files without any formatting tags. In most word-processors, you generate this type of document when you save a document as DOS text file. Import these documents using the EQFASCII markup table.
TranslationManager allows you to translate text contained in Assembler files, that is, information that is enclosed by single quotes. For example:
*2.......10....16......................................................72.......
DC C'THIS IS A ONE LINE TEXT'
DC C'This is a two line text string that will be presented x
under TranslationManager on one line'
Import these documents into a TranslationManager folder, using the EQFASM markup table.
Text spread over more than one line is shown on one line in the Translation window. Translated text that does not fit into one source record is spread into several lines. A continuation character is placed in column 72 and the continuation begins in column 16.
Import these documents using the EQFBOOK markup table.
Import these documents using the EQFHTML2 markup table (for HTML level 2.0 and level 3.0 documents).
TranslationManager directly supports the document format of Microsoft Word for Windows Version 2.0 and Version 6.0. If your documents were created using a different version of Microsoft Word, you need to save the document in one of the versions supported by TranslationManager.
You can import these documents into a folder using the EQFWORD (for Word Version 2.0 documents) or the EQFWORD6 (for Word Version 6.0 documents) markup table.
If the document was saved as a Rich Text Format (RTF) document, you must specify EQFRTF as markup table.
Ensure that you have sufficient disk space available when using one of the EQFWORD markup tables. TranslationManager requires some temporary space (about triple the size of the source document).
If you are working with TranslationManager under OS/2 and you use EQFWORD6 as markup table, you must have Win-OS2 installed. The markup table requires a Windows program during the analysis and export functions which cannot be started unless Win-OS2 is installed.
Files that are saved by the automatic save option of Microsoft Word for Windows cannot be processed by TranslationManager . You must save your document with the Save command from the File menu and then close the file.
Do not use the Allow Fast Save option in the Save category that you can select in the Options window of the Tools menu.
It is recommended to save your file with the option Field Codes set to off.
Under Word for Windows 2.0 you can do this from the View menu. When working with Word for Windows 6.0 you can even switch it off in the View menu which you can access by selecting Options... from the Tools menu.
Otherwise some characters are represented in replace form and this can be confusing during translation.
After you have translated the document, load it into Microsoft Word for Windows for postprocessing it.
You must rebuild the index and the table of contents after you have loaded the translated document in Microsoft Word for Windows.
For documents originating from Word 6.0 you must also rebuild the table of authorities.
To use language-related functions on the translated document in Microsoft Word for Windows, change the language identification by selecting Language from the Format or Tools (when using Word 6.0) menu.
The page numbering in headers or footers can change after translation because the document is now longer or shorter than the source. TranslationManager cannot repaginate Microsoft Word for Windows documents.
For documents originating from Word for Windows 2.0:
To get the correct
page numbers in headers or footers,
select Field Codes from
the View menu to see where codes like
NUMPAGES are inserted.
Delete and reinsert these codes where necessary.
For documents originating from Word for Windows 6.0:
To get the correct
page numbers in fields,
select Select All from
the Edit menu, locate the mouse pointer on one of the fields,
press the right mouse button, and select Update Field.
During translation the layout of the document is determined by markup tags.
Some of the inline markup tags can be changed during translation. This means you can insert or delete tags like [bold], [italics], and [underline]. Make sure you also insert the corresponding ending tag.
In Appendix F. "Displaying markup information for Word documents", you find a list of all markup tags used for Microsoft Word for Windows documents.
Footnote references are represented with a markup tag. The corresponding text to the footnote is appended to the document after the main text.
Do not change, delete, or insert tags outside translatable segments.
The format for index entry tags in Word 2.0 documents is:
[index field][index entry]
"text"[/index entry]
The format for index entry tags in Word 6.0 documents is:
[ix fld][index entry]
"text"[/index entry]
The index string must be enclosed by double quotes.
The format for entries in the table of contents in Word 2.0 documents
is:
[toc field][toc entry]
"text"[/toc entry]
The format for entries in the table of contents in Word 6.0 documents
is:
[toc fld][toc entry]
"text"[/toc entry]
The string for the table of contents must be enclosed by double quotes.
When working with Word 2.0 documents, bookmarks are lost after translation. Annotations are kept in the document but are not translatable.
When working with Word 6.0 documents, bookmarks are kept in the document. Annotations are translatable.
To avoid complications when loading the translated document back in Microsoft Word for Windows, treat the following tags very carefully during translation:
This means when you copy a segment from the Translation Memory with these tags in it, delete these markup tags when they cause a fuzzy match.
If the current source segment contains one of these markup tags ensure that they remain unchanged.
If possible, do not insert one the following tags:
Import OS/2 resource files using the EQFMRI markup table.
Rich Text Format (RTF) is a document format supported by many word processors. Import these documents using the EQFRTF markup table.
Select Check for changes of in-line tags during translation to ensure that braces ({, }) are not misplaced or deleted unintentionally. Otherwise the translated document may no longer be accepted by the original word processor.
These files are used to define help texts for programs running under Windows. They can be saved as RTF documents.
Import these documents using the EQFRTF markup table.
Windows resource files (complying with ANSI) can be imported using the EQFAMRI markup table.
TranslationManager supports WordPerfect document formats that were created with WordPerfect Version 5.x, Version 6.0, and Version 6.1. You can import these documents into TranslationManager using the EQFWP (for WordPerfect Version 5.x documents) or EQFWP6 (for WordPerfect Version 6.0 and 6.1 documents) markup table.
When you have translated the document, you can export it in external format and load it back into WordPerfect to generate a new index and new table of contents, for example, to print and review the translation.
Note: During translation, segments spanning more than two lines in the Translation window are joined including a blank space. As an exception to this rule, a blank is not inserted if an inline tag (such as [bold] or [italic]) is found at the end of a line. However, if you need a blank between the tag and the first word of the following line, it is recommended to join the lines such that no line ends with a tag or to start the following line with a blank before the first word.
When you delete a document, you also delete the translated version of the document. However, segments you have translated are preserved in the Translation Memory.
Prerequisites
The folder containing the document must be open.
Calling sequence
Select:
You must confirm that you want to delete each selected document.
Results
The documents are deleted.
Exporting documents allows you to share documents with other users. Documents can be exported at any time: before, during, and after translation. Partially translated documents can then be translated further by the recipient.
To transfer a document to another TranslationManager user, it is recommended that you export it in TranslationManager format, so that the recipient receives the document in its original format.
If the recipient needs to have the document in a specific word-processor format, export it in external format.
You can start the export procedure from within TranslationManager , or you can export documents in external format by entering the EQFCMD command and its parameters in the command area of your operating system. You may want to do this, for example, if you have many large documents to export. This command and its parameters are explained in "Exporting documents".
Prerequisites
The Document List window of the respective folder is active.
Calling sequence
Select:
The Export Documents window (see Figure 10) is displayed.
Figure 10. Export Documents window for external format
 |
Options and parameters
Depending on the format you selected, this window offers a different number of options and parameters:
To export the document in TranslationManager format, select:
To export the selected document in external format, specify the following options:
To change an existing set of revision marks or to define new revision marks, click on Edit.... This takes you to the Edit Revision Marks window where you define your revision marks (see "Editing document revision marks for export").
This exported file is in the format of an external Translation Memory with empty target segments. You can transfer this file to a machine translation system to translate these segments automatically.
Note: The machine translation system must first be programmed to recognize the source and target language segments in the external format of the Translation Memory.
After the empty target segments have been completed by the machine translation system, you can import the file into TranslationManager as a Translation Memory and use it to translate the rest of the document. The proposals offered in the Translation Memory window are then preceded by an [m] (generated by machine).
Click on Export to start document export.
Results
The document is exported. An exported document in external format is stored as a DOS file in the directory under the file name you specified. The document can then be further processed with the corresponding word-processing system.
An exported document in TranslationManager format is stored in TranslationManager on the selected drive on your workstation in a separate subdirectory of the \EQF\EXPORT\ path under the file name you specified. For example, if the document DEVICE.SCR is exported from the folder SAMPLWP, it is stored as \EQF\EXPORT\SAMPLWP.F00\DEVICE.SCR. The document can be passed to other TranslationManager users for further processing.
During export, TranslationManager can insert revision marks in translated documents.
Revision marks can help reviewing a translated document. When translating an updated version of a previously translated document, many segments will remain unchanged. In most cases you can simply copy the Translation Memory proposals for these segments into the new document. These segments usually need no further checking because they originate from a previous translation.
The only segments that need to be reviewed are those that are translated from scratch, and those that are based on a proposal copied from the Translation Memory window and subsequently changed.
You can choose which segment categories you want to mark.
Prerequisites
Calling sequence
Click on Edit... in the Export Documents window
The Edit Revision Marks window is displayed (see Figure 11).
Figure 11. Edit Revision Marks window
 |
You can mark the following types of segments with revision marks:
TranslationManager lets you choose different symbols for marking the beginning and the end of each type of segment in the Begin text and End text fields.
You can type, for example:
Click on Save to return to the Export Documents window.
Results
The set of revision marks is saved under the name you specified in the Name field. Documents exported in external format are marked accordingly. To see the results of the revision marks, browse the exported document file with a text editor or, if applicable, print the document.
Note: When you have marked the translations with the revision mark, you are recommended not to import these documents in TranslationManager again, because the revision marks might be misinterpreted.
It is recommended to export the revised and finalized translation again without revision marks.
You must import a document into TranslationManager before you can work with it.
A TranslationManager document can be in one of two formats:
This format can be received from another TranslationManager user who previously exported the document in TranslationManager format. When you import a document into TranslationManager you receive the current status of both the original and translated version of the documents.
This format is produced by word-processing systems, such as WordPerfect or Microsoft Word for Windows.
Prerequisites
The active window is the Document List window of the folder into which the document is to be imported.
Calling sequence
Select Import... from the File menu
The Import Documents window is displayed (see Figure 12).
Figure 12. Import Documents window for external format
 |
Options and parameters
Depending on the format selected, this window offers a different number of options and parameters:
To import all documents listed in the Documents list box, click on Select all.
To start a new selection of documents, click on Deselect all.
All selected files are listed in Files. Select the documents you want to import, then click on Import to start the import procedure.
To import documents in external format, select:
Type only the common part of the file name in the Name field to display a subset of the available files in the Files list. Then add an asterisk (*) to represent the part of the file names that is different. For example, to import the files PART01.DOC, PART02.DOC, PART03.DOC, and PART04.DOC, type PART*.DOC in the Name field and press Enter.
If all your document files are located in the same directory, for example, in \PROJECT on the currently selected drive, you can type both the path and file name in the Name field, for example, \PROJECT\PART*.DOC, then press the Enter key.
To display the documents in one of the directories listed in the Directories list, double-click on a directory.
One or more documents from the list to import all documents listed in the Files window.
All selected files are listed in the Files list box. Select the documents you want to import, then click on Import to start the import procedure.
The Document Properties window is displayed for the first document (see Figure 13).
Figure 13. Document Properties window
 |
Options and parameters
If you import documents with the same properties as the folder, you do not specify anything in this window. Click on Change to import the document.
If several documents are selected for importing, you must specify the properties for each document to be imported.
To save the specified properties, click on Change.
Results
The selected document is imported and you can start analyzing and translating.
If the selected document has not been analyzed, TranslationManager automatically analyzes the document based on the properties of the document and the folder. For more information on the analysis, see "Analyzing a document".
Prerequisites
The Document List window of the respective folder is active.
Calling sequence
Select:
You are taken to the Translation Environment, where the selected document is contained in the Translation window.
Results
The document is segmented and you can start translating it.
To leave the Translation Environment, you must close the document.
TranslationManager provides a Global Find and Change function, which works across all or some documents of a folder.
This function might be helpful if you are looking for a particular piece of text whose source document you are not sure of. Also, you may need to change a particular wording but do not want to type the new text manually at each occurrence. TranslationManager can search through a series of documents to locate the required text and change it automatically. Any change is automatically reflected in the associated Translation Memory to be available for future translations.
Note that TranslationManager searches and changes only pieces of text that can be translated. Markup tags cannot be changed.
Prerequisites
Calling sequence
You can start this function from a Folder List window or from a Document List window. Here the start from the Document List window is described.
Select:
The Global Find and Change window is displayed.
Figure 14. Global Find and Change window
 |
Options and parameters
Note that only changes in translated documents are reflected in the Translation Memory.
Results
The specified piece of text is located at every occurrence within a document and changed where necessary. The associated Translation Memory is updated if requested.
A translated document can contain typing errors or misspelled words. TranslationManager offers a spellchecking function you can use at any time during translation.
Spellchecking is supported for all languages for which language support is installed. For each misspelled word, TranslationManager shows a correction proposal, which you can accept, overwrite, or skip.
Note that only the spelling of translated segments is checked.
Prerequisites
The language support file for the target language of the document must be installed.
Calling sequence
If you are not already in the Translation Environment, start it by selecting:
The Spellcheck function starts immediately at the beginning of the translated document, and the Spellcheck window (see Figure 15) is displayed.
 |
Options and parameters
You can accept a spelling in several ways. Select:
When all misspelled words have been either changed or skipped, a message appears telling you that spellchecking is complete.
Results
The corrections you accepted are substituted for the misspelled words in both the document and the Translation Memory.
You can add terms which have been indicated as misspelled by the spellcheck facility (although spelled correctly) to an addendum for the language-support file of the current target language. During the next spellcheck terms of this addendum are considered to be correct. You can modify this addendum at any time, for example, to remove terms that have been added by mistake.
Prerequisites
The document must be translated and you must be in the Translation Environment.
Calling sequence
The Edit Addendum Terms window is displayed.
Options and parameters
The terms in the addendum can be modified as follows:
Clipboard operations (cut, copy, paste) are supported.
To save your changes, select Save.
To leave the window without saving your changes, select Cancel.
Results
The corrections you made are saved and taken into account during subsequent spellchecks.
To prepare the translation of documents you can generate terminology lists, for example, to add new terms to a dictionary or generate a Translation Memory from previous translations.
To translate the documents, the Translation Environment offers common editor functions and specific functions for translation, such as dictionary lookup and copying translation proposals. Using these functions helps you translate documents more efficiently.
When you translate several documents on the same subject, the Translation Memory used will grow and the number of translation proposals will increase.
Prerequisites
Calling sequence
Select:
The Translation Environment is displayed. It consists of a number of windows. The selected document is shown in the Translation window. If the document you selected has already been partially translated, the cursor is positioned on the first untranslated segment and you can continue there.
Options and parameters
For information on how to use the editor functions, see Chapter 4. "Working with the TranslationManager editor".
Results
You can choose the sequence in which you translate documents. You can also translate parts of a document at a time and continue later until the documents are completely translated. If needed, you can export partially translated documents and give them to other TranslationManager users who can continue the translation.
When you have completed the translation of the segments of a document, TranslationManager automatically switches to the post-editing mode where you can review the translation and check the spelling. The Translation Memory you used contains all segments and their translations and can be used for documents containing similar texts. You can postedit it whenever a translation needs to be modified.
The properties of a document are:
The properties must be defined individually for each document when you import documents in external format. They can be changed later.
Prerequisites
The document must be in a folder.
Calling sequence
Select:
The Document Properties window (see Figure 16) is displayed.
Figure 16. Document Properties window
 |
Options and parameters
If the document has the same properties as the folder,
you do not have to enter anything, and
the document "inherits" the folder properties.
Document properties that are different from the folder properties
can be selected from the respective list boxes.
In the Translation Memory field, you can
type the name of a new Translation Memory.
To save the specified properties for this document, click on Change.
Results
The properties are saved for this document.
You can display parts of the properties and the current processing status of a document in the Document List window. This includes such details as the date of import, date of analysis, the percentage of the document that has been translated. Using this data you can easily show the progress of translation work. You can display these details in the Document List window.
The details of a document are:
If nothing is specified for any of the last four items, TranslationManager assumes these properties to be the same as for the folder.
For an imported folder, the details in the Document List window are defined by the sender. You can change them if you like. You can toggle between two display modes:
You can change the arrangement of the document details in the Change Details window described in "Viewing and changing the details of a list item".
Similar to office folders that contain paper files, a TranslationManager folder contains a number of related documents or document files, respectively. A folder, for example, might contain all documents of a specific translation project, or any other collection of documents that belong together.
Each folder has a number of properties, such as the source and target language, or references to the dictionaries and Translation Memory databases to be used for analysis and translation of the documents in the folder. By default, all documents in a folder have the same properties, but you can specify individual properties for each document.
You can send all the documents in a folder to another TranslationManager user.
Folders that are sent or exported contain a number of documents, associated dictionaries and Translation Memory databases, and optionally an accompanying note to the recipient.
To begin working with a folder that has been exported by another user, you must first import it into TranslationManager .
Exporting folders is also useful to make backup copies of your translation material.
TranslationManager includes a number of processing functions for folders, which you can access by selecting a folder from the Folder List window and then selecting a choice from the File, View, or Utilities menu.
Prerequisites
At least one folder must exist, except if you import a folder.
Calling sequence
Select the Folder List window from the main window. The Folder List window is displayed.
Results
This window displays a list of the available folders. When you select a command from one of the menus, you are taken to another window where you can specify processing options.
Documents that are to be translated must first be segmented. Segmentation is done during analysis of a document. You can analyze all the documents in a folder at once.
Prerequisites
Calling sequence
Select:
The Analyze Documents window is displayed (see Figure 6).
Options and parameters
Selecting the following options applies to all documents in the folder:
For a detailed description of these options, see "Analyzing documents using Translation Memory databases", and "Analyzing documents using dictionaries".
When you have selected the desired options, click on Analyze to begin analysis of the documents.
Results
All documents in the folder are segmented. Depending on the options you selected:
To start working with a document, you must first open the folder containing the document. Then the Document List window is displayed.
Closing a folder means to close the Document List window, which takes you back to the Folder List window.
Prerequisites
The Document List window of the folder must be active.
Calling sequence
Select:
This takes you back to the Folder List window.
Results
You can begin working on documents in other folders or any other tasks in TranslationManager .
TranslationManager provides a facility for counting the number of words and markup tags in all documents in a folder before and after translation. You can also perform this task for selected documents in a folder (see "Counting the number of words in a document").
Prerequisites
The folder must contain at least one document.
Calling sequence
Select:
Count Words window (see Figure 8) is displayed.
Options and parameters The options and parameters are the same as described in "Counting the number of words in a document".
Click on Count to begin counting words.
Results The results are displayed in the Word Count Results - Original window or in the Word Count Results - Translation window which are explained in "Counting the number of words in a document".
When you close this window, you are returned to the Folder List window.
If you selected the output option File, the results are also saved in a file with the name you choose.
Grouping documents in a folder is recommended whenever:
A folder also makes it easier to export or import a group of documents.
Prerequisites
Calling sequence
Select:
The New Folder window (see Figure 17) is displayed.
 |
Options and parameters
The options you specify are used for all documents imported into this folder. If individual documents need other properties, you can specify these when importing the documents.
Click on Create to create the new folder.
Click on Cancel to leave this window
without creating a new folder.
Results
If you clicked on Create, the folder is created, an empty Document List window is displayed, and the folder can be filled with documents.
If you entered a new Translation Memory name as a folder property, you are prompted with the New Translation Memory window, to specify some more parameters.
When you delete a folder, it is no longer listed in the Folder List window, and all documents in the original and the translated version are also deleted. You might want to delete a folder when you completed working on the documents in the folder, exported it, and no longer require it. Also, if you have backed up the contents of the folder, you can delete the folder to free disk space on your workstation for other purposes.
You can also delete a folder during or after export. For more information, see "Exporting a folder", and "Deleting an exported folder".
Prerequisites
The folder to be deleted must not be open (that is, the Document List window for the folder must not be displayed).
Calling sequence
Select:
Options and parameters
None.
Before deleting the selected folder, TranslationManager prompts you to confirm that you want to delete the folder and its contents:
Results
If you select Yes, the folder and the documents in it are deleted. The disk space it occupied is freed.
Dictionaries, markup tables, and the Translation Memory databases associated with the folder or its documents are not deleted.
When you export a folder, TranslationManager writes the data to a file in the EQF\EXPORT\ subdirectory on the selected drive. If you no longer need this exported folder file, you can delete it.
Prerequisites
Calling sequence
Select:
The Delete Exported Folder window (see Figure 18) is displayed.
Figure 18. Delete Exported Folder window
 |
Options and parameters
Click on OK to return to the previous window.
To leave the exported folder unchanged, click on Cancel.
To delete the exported folder, click on Delete. For each selected exported folder, a message window prompts you to confirm that you want to delete the exported folder:
If there are no more exported folders selected to delete, click on Cancel to return to the Folder List window.
Results
If you confirmed to delete the exported folder in the \EQF\EXPORT\ subdirectory, it is deleted and cannot be re-imported.
The main purpose of exporting a folder is to make documents available to other users or on other systems. Other translation material, such as dictionaries and Translation Memory databases, can also be exported, either as part of a folder or separately.
Exporting a folder is the easiest way of distributing translated material from one TranslationManager user to another, and it is the recommended way.
You can also include a note for the recipient. This note could, for example, include instructions about which document to translate first or when the translation is due. The recipient can display this note when importing the folder.
When you export a folder to a diskette drive and the folder data volume exceeds the capacity of one diskette, the system writes the data to as many diskettes as necessary.
Prerequisites
The folder to be exported must exist.
Calling sequence
Select:
Figure 19. Export Folder window
 |
Options and parameters
Select from the following options:
Your note is saved and included in the exported folder.
If you selected the required options, select Export to start the export procedure.
If you selected the Add note option, you are prompted with the Add Note to Folder window to type your note for the recipient. To save the note in the exported folder, click on Add to start the export of the folder.
If you selected a diskette drive and the folder data volume exceeds the capacity of a diskette, you are prompted to insert as many diskettes as necessary.
Results
The folder is exported, including all material you selected. If you exported the folder together with documents, any markup tables used by documents are also exported.
TranslationManager stores the exported folder in one file in the subdirectory \EQF\EXPORT of the selected drive. From this subdirectory it can be reimported. The file has the folder name and the extension FXP.
If you selected the Delete folder after export option, the folder is deleted, including all documents in it. However, the referenced markup tables, dictionaries, and Translation Memory databases are not deleted.
When translations are prepared centrally before being distributed to individual translators, you are strongly recommended to use folders as the means of distributing this material, because all related translation material (documents, dictionaries, and Translation Memory databases) can be included in one folder.
Before you can start working with material that has been exported, you must import it in TranslationManager .
A folder exported to a diskette drive can span more than one diskette. The system prompts you to insert the diskettes into the diskette drive in the same sequence they were used during export.
Prerequisites
Calling sequence
Select:
Figure 20. Import Folder window
 |
Options and parameters
You can import a folder from any drive that is defined to your installation.
To begin importing the folder, click on Import.
If you import the folder from a diskette drive and the exported folder was written to more than one diskette, you are prompted to insert the diskettes in the sequence in which they were inserted during export.
Results
The folder is imported. It is added in the Folder List window and you can start using its contents, or the imported dictionaries for document analysis.
If the imported folder contains a dictionary with the same name as an existing one, the Merge Dictionaries window is displayed and you must decide whether to merge the dictionaries and how to merge them (see "Merging dictionaries").
If the folder contains a Translation Memory with the same name as an existing one, the Translation Memory in the folder to be imported is automatically merged into the existing one.
An imported folder also contains the markup tables of the folder and document properties. During import, markup tables in your system are overwritten if they have the same name and the markup table in the folder is a more recent one.
When you open the imported folder, the Document List window displays the details arrangement defined by the sender.
If you select a folder in the Import Folder window or in the Delete Exported Folder window, and you click on Details..., the Folder Details window (see Figure 21) is displayed.
Figure 21. Folder Details window
 |
Options and parameters
The following information of the selected folder is displayed; it cannot be changed in this window.
To print a copy of the details, click on Print.
To return to the previous window (Import Folder or Delete Exported Folder), click on OK.
Results
If you clicked on Print, the folder details are printed. The folder contents remain unchanged.
If you clicked on OK, you can continue specifying options in the previous window.
You open a folder to see which documents it contains. You can then select a document to work with from the Document List window.
Prerequisites
The folder must exist.
Calling sequence
Select:
Alternatively, double-click on the folder to open it.
The Document List window is displayed.
Results
A list of documents in the selected folder is displayed. From this list, you can start document-related functions by selecting one or more documents and an action from one of the menus.
For further information see "What you can do with documents".
TranslationManager provides a Global Find and Change function, which works across all or some documents of a folder.
This function might be helpful if you are looking for a particular piece of text whose source document you are not sure of. Also, you may need to change a particular wording but do not want to type the new text manually at each occurrence. TranslationManager can search through a series of documents to locate the required text and change it as specified. Any change is automatically reflected in the associated Translation Memory to be available for future translations.
Note that TranslationManager searches and changes only pieces of text that can be translated. Markup tags cannot be changed.
Prerequisites
Calling sequence
You can start this function from a Folder List window or from a Document List window. Here the start from the Folder List window is described.
Select:
The Global Find and Change window is displayed.
Figure 22. Global Find and Change window
|
Options and parameters
Note that only changes in translated documents are reflected in the Translation Memory.
Results
The specified piece of text is located at every occurrence within a selection of documents and changed where necessary. The associated Translation Memory is updated if requested.
The properties of a folder are:
When you create a folder, you must define its properties before you can work with the folder. Some of them can be changed later.
The properties defined for each folder apply to all documents in the folder unless individual document properties have been set. It is sometimes not advisable to change the properties of a folder. In particular, you should not change the Translation Memory associated with the folder when you have started translating a document. You can change the associated dictionaries, if necessary.
Prerequisites
Calling sequence
Select:
The Folder Properties window (see Figure 23) is displayed.
Figure 23. Folder Properties window
 |
Options and parameters
The selected properties are shown in the respective fields. The Name field and the Disk drive cannot be changed for an existing folder.
The following fields contain the currently assigned names. They can be changed by selecting another name from the respective list box.
For the Translation Memory to be used, you can also type a new name in the respective field.
The dictionaries to be used in the folder are selected as follows:
To save the changes of the properties, click on Change.
To leave the Folder Properties window without changing the properties, for example, if you only wanted to look at the folder properties, click on Cancel.
Results
If you select Change, the folder properties are changed according to your specifications. Otherwise, they remain unchanged. You are returned to the previous window.
If you entered the name of new Translation Memory, the New Translation Memory is displayed to specify the characteristics of this Translation Memory.
If you changed a markup table name, it is strongly recommended that you analyze the documents in the folder again.
In the Folder List window, you can display additional information about a folder. You can define which details you want to be displayed and in which order.
The displayable folder details are as follows:
You can toggle between two display modes:
You can change the arrangement of the folder details in the Change Details window described in "Viewing and changing the details of a list item".
A Translation Memory is a database that contains existing translations. You use a Translation Memory to find and reuse these translations.
During analysis TranslationManager splits a document into translatable segments, which usually correspond to sentences.
A Translation Memory contains pairs of such segments consisting of an original (source) segment and a translated (target) segment that together make up a Translation Memory segment. Each Translation Memory can contain source sentences in one source language, but translated sentences in several target languages.
The type of match is always evaluated by comparing a sentence in the source document with source sentences in the Translation Memory.
TranslationManager proposes both exact matches and fuzzy matches. Exact matches are found if two source segments are completely identical. Fuzzy matches are found if two source segments are almost identical.
All types of fuzzy matches are indicated by a character enclosed in brackets in front of the proposal. For example, [f] indicates a fuzzy match.
If two source sentences differ from each other by only a digit or a number, TranslationManager proposes this as a fuzzy match, with the number already replaced with the new value. Such a fuzzy replacement match is indicated by [r]. The various types of matches are described in detail in "Translation Memory matches".
Whenever you translate a segment, TranslationManager automatically adds your translation to the Translation Memory associated with the current document. The Translation Memory is therefore being continuously updated--the translation of one sentence may even be offered as a translation proposal for the next matching segment.
When the same original sentence appears in several places in a document, TranslationManager also allows you to store several different translations of the sentence. In this way, you can translate a segment in different ways according to the context.
Translation Memory databases provide an efficient method of translating whenever you deal with similar or repetitive texts (for example revised editions of manuals).
During translation, you can select automatic substitution. This option automatically copies existing translated segments into the translation document for as long as it finds exact matches for the current source segments. Automatic copying stops when no exact match, or more than one exact match, has been found for a source segment. Now you must continue translating the segment manually. Afterwards automatic copying can be restarted.
Translation Memory databases can be even combined with one another. Use the merge option to merge the contents of one Translation Memory with another.
Translation Memory databases can have two formats:
If you have translated documents that were translated outside TranslationManager , you can generate an Initial Translation Memory (ITM), this means you can fill a Translation Memory with existing translation segments. When you start the translation of a document that is similar to an existing one, you can benefit from your previous translations that are now available in the Initial Translation Memory.
An exported Translation Memory in SGML format is also helpful for reusing existing translations. If you have previously saved files or databases in another format, you can access them with TranslationManager by using a program to convert them to the format of an external Translation Memory.
During translation in the Translation Environment, TranslationManager searches for matching segments, this means it checks whether the Translation Memory contains a previous translation of the current segment.
The system differentiates mainly between an exact match, which is completely identical, and a fuzzy match, which is an almost identical match where the fuzziness can have various degrees.
When TranslationManager displays a matching segment in the Translation window of the Translation Environment, the type of fuzzy match is indicated by a preceding flag in brackets, for example [f]. Exact matches do not have such a flag.
An exact match is found when the Translation Memory contains a segment identical to the current segment in the document to be translated (this means when the segments are identical with respect to text, tagging, and punctuation) and when the segment translation was accepted by a human translator during translation.
If an identical source segment is placed in the Translation Memory by the EQFITM command or was imported as machine-generated translation, it is not regarded as an exact match. It is flagged by a preceding [m].
A fuzzy match is recognized, if the two segments overlap more than 40 %.
TranslationManager can also show combinations of these types of matches.
The following table shows
the categories of matches and the flagging
displayed in the
Translation Memory window.
| Type of match | Flag |
|---|---|
| Exact | (not flagged) |
| Matches with minor deviations: |
|
| - Machine | [m] |
| - Replacement | [r] |
| - Machine and replacement | [mr] |
| Fuzzy matches: |
|
| - Fuzzy | [f] |
| - Fuzzy and replacement | [rf] |
| - Fuzzy and machine | [mf] |
| - Fuzzy, machine, and replacement | [mrf] |
Most of the tasks concerning Translation Memory databases
begin from the
Translation Memory List window.
Calling sequence
Select:
This usually takes you to another window, where you can specify the necessary options and parameters and where you can start the requested procedure.
Before you can use a Translation Memory, it must be initialized. To initialize a Translation Memory, you need to specify values for a number of parameters.
The procedure described here creates an empty Translation Memory. This can subsequently be filled by translating in the Translation Environment, by copying segments from other Translation Memory databases during analysis, or by importing external Translation Memory databases.
For a description of the other methods of creating and filling a Translation Memory, see:
Prerequisites
At least one language-support file must be installed.
Calling sequence
Select:
The New Translation Memory window (see Figure 24) is displayed.
Figure 24. New Translation Memory window
 |
Options and parameters
Click on Create to create the new Translation Memory.
Results
The Translation Memory is created, but is still empty. You can now begin to fill it by translating text or by actions such as import, merge, or analysis.
SGML format is used as the TranslationManager data exchange format for Translation Memory databases.
If you have already a translation database in a format of your own and want to use the information in it with TranslationManager , you must first convert it into a file in SGML format, for example, by a conversion program that understands your database format and the SGML format. This file can then be imported into TranslationManager .
Besides generating an Initial Translation Memory (ITM), this is another method of filling a Translation Memory before beginning a translation.
When you export a Translation Memory, TranslationManager creates a file in SGML format.
During import, you can also merge an external Translation Memory with an internal Translation Memory.
A Translation Memory in SGML-based format includes, in addition to the original and translation segments, SGML tags that describe the data structure of each segment.
You can also use this format to create an external Translation Memory containing your own translation database data.
An external Translation Memory is an ASCII coded file. It starts with <NTMemoryDb> and ends with </NTMemoryDb>.
The starting tag is followed by a description of the Translation Memory, enclosed between <Description> and </Description> tags.
The description is followed by the segment pairs.
The number of segment pairs is not limited.
The individual segment pairs are tagged in the
following format:
| Example |
|---|
.. <-* </Control> <-* <Source>...</Source> <-* <Target>...</Target> <-* </Segment> <-* |
The symbol <-* stands for the combination of the Carriage return and the line feed characters. This character combination is usually generated when you press the Enter key on the keyboard to return you to the beginning of the next line.
The following describes the SGML structure sequentially.
"The Translation Memory format" shows a small part of an external Translation Memory.
The following shows part of of a SGML-based Translation Memory containing two segments. The separator in the segment control information is indicated by the symbol §. The combination of the Carriage return and the Line Feed characters ( <-*) is not shown in this example.
<NTMemoryDb> <Description> This is a Translation Memory sample </Description> · <Segment>0000000001 <Control> 000015§0§0000000668798940§English(U.S.)§German(national)§§EQFBOOK§DEMO.SCR </Control> <Source>The amount of data that you wish to process </Source> <Target>Die Datenmenge, die verarbeitet werden soll </Target> </Segment> · <Segment>0000000043 <Control> 000003§0§0000000668798783§English(U.S.)§German(national)§EVS§EQFBOOK§DEMO.SCR </Control> <Source>The IBM 9370 system includes a processor, I/O devices and the appropriate software to fulfill your data processing requirements. </Source> <Target>Das System IBM 9370 umfaßt den Prozessor, E/A Geräte sowie die entsprechende Software, um den Ansprüchen bei der Informationsverarbeitung gerecht zu werden. </Target> </Segment> · </NTMemoryDb>
| Start tag, end tag | Description |
|---|---|
| <NTMemoryDb>, </NTMemoryDb> | Start and end of a Translation Memory |
| <Segment>, </Segment> | Start and end of a Translation Memory segment |
| <Description>, </Description> | Start and end of a Translation Memory description |
| <Control>, </Control> | Start and end of the segment control information |
| <Source>, </Source> | Start and end of a source sentence |
| <Target>, </Target> | Start and end of a target sentence |
The control information for each segment consists of several pieces of information, each of a specific length. The maximum length of each data element is contained in square brackets. The data elements must be separated by a character with the ASCII code 21 (X'15'), represented by the symbol §.
The control information has the following layout:
If you no longer need a Translation Memory, for example, if you have specified incorrect parameters or it has been filled with the wrong data, you can delete it.
For learning how to delete a shared Translation Memory, see .
Prerequisites
The Translation Memory must exist.
Calling sequence
Select:
Before TranslationManager deletes the requested Translation Memory, a message window is displayed asking you to confirm that you want to delete the Translation Memory.
Options and parameters
Results
If you select Yes, the Translation Memory is deleted, and the disk space is freed. Otherwise, the Translation Memory remains unchanged. References to this Translation Memory may still exist in certain folders. Update the folder properties so that the deleted Translation Memory is no longer referenced.
To make a Translation Memory available to another system or user, you can export it to create an external Translation Memory. An external Translation Memory is in an SGML-based data exchange format that you can use to pass your Translation Memory data to users who do not work with TranslationManager .
Prerequisites
The Translation Memory must exist.
Calling sequence
Select:
Figure 25. Export Translation Memory window
 |
Options and parameters
Click on Export to begin exporting the Translation Memory.
If you selected a diskette drive and the data volume of the Translation Memory exceeds the capacity of the diskette, TranslationManager informs you that it cannot export the Translation Memory in this way. You then must export the Translation Memory in a folder. For more information, see "Exporting a folder".
Results
The Translation Memory is exported as a file that you can pass to other users or systems. The default file extension is EXP. The internal Translation Memory remains unchanged.
You can generate a Translation Memory already before you start translating a document in TranslationManager . In this way, you can immediately benefit from having a filled Translation Memory when you start translating, for example, updated versions of existing documents.
Such a Translation Memory is called an Initial Translation Memory (ITM). TranslationManager lets you create an Initial Translation Memory based on existing translations--both a source file, containing the original document, and a target file, containing the corresponding translated document, must be available.
TranslationManager scans both files to find the corresponding target segment for each original segment, that is, it aligns the segments of the two files. You are recommended to check the combinations of segments afterwards.
When you use an Initial Translation Memory during a translation, the proposals in the Translation Memory window are prefixed with [m] (created by machine). Such machine proposals are treated as fuzzy matches, this means they are not used during automatic substitution.
To generate an Initial Translation Memory, you can choose between two methods. You can start generating an Initial Translation Memory:
The following sections describe how to:
Prerequisites
Calling sequence
The Create Initial Translation Memory window is displayed:
Figure 26. Create Initial Translation Memory window
 |
Options and parameters
A source file is defined by the following parameters:
To change the path information displayed in the Current directory field, select a different directory from the list box.
The target file is defined similar to the source file:
To change the path information displayed in the Current Directory field, select a different directory from the list box.
When the generation of the Initial Translation Memory is completed, a message window appears containing the number of paired segments. If you pressed the Create... button, the contents of the Initial Translation Memory is presented in a window on the screen. How you work with this window is described in "Revising an Initial Translation Memory".
Results
The Initial Translation Memory is filled with matching source and target segments, using the file pairs you selected.
It is recommended that you check the correctness of the matches made by TranslationManager . You can do this before you start translation work with this Translation Memory as described in "Revising an Initial Translation Memory from the command area", or online using the Initial Translation Memory specific editor (see "Revising an Initial Translation Memory"). This editor is invoked by selecting the Create... button in the Create Initial Translation Memory window.
If you start to use the Initial Translation Memory without any further checking, it is recommended to treat the machine-generated matches, (prefixed by [m]) in the same way as fuzzy matches (prefixed by [f]). When you copy these proposals into your translation, check whether they need to be adapted and change them where necessary.
If you choose to use automatic substitution during analysis, machine-generated matches are not used.
If you receive an external Translation Memory, you can import it into TranslationManager .
During import, you can also merge the data from an external Translation Memory into a Translation Memory that already exists in TranslationManager .
Translation Memory databases can be imported only in external format.
Prerequisites
Calling sequence
Select:
Figure 27. Import Translation Memory window
 |
Options and parameters
Other methods are:
If you specify a Translation Memory that does not exist, the New Translation Memory window is displayed for you to create it (see "Creating a Translation Memory").
If you specify an existing Translation Memory that is not empty, the contents of the Translation Memory to be imported are merged into it.
When you have specified your input, click on Import to begin importing.
For information on importing Translation Memory databases from other TranslationManager products, see Appendix G. "Exchanging data with other TranslationManager products".
Results
The Translation Memory data is imported into the selected target Translation Memory and you can begin to work with it. The external Translation Memory remains unchanged.
If several translators are working on a large document, each of them uses and updates a separate Translation Memory.
For the translation of subsequent releases of the document, it is useful to merge these to create a single consolidated Translation Memory.
You can merge Translation Memory databases in two ways:
The merging of two Translation Memory databases is described using two sample names, TMEM01 and TMEM02.
Prerequisites
Calling sequence
Select:
Figure 28. Merge Translation Memory window
 |
Options and parameters
The Into Translation Memory list box displays all available Translation Memory databases. Select the Translation Memory, for example TMEM02, into which to merge the previously selected Translation Memory TMEM01.
When you have selected the target Translation Memory, click on Merge to begin merging the Translation Memory databases.
Results
The contents of TMEM01 is merged into the target Translation Memory TMEM02. The Translation Memory TMEM01 remains unchanged. You can begin to use the extended Translation Memory TMEM02.
Occasionally TranslationManager prompts you to organize a Translation Memory. A Translation Memory must be organized to delete obsolete segments, to repair a defective Translation Memory, or to upgrade a backlevel Translation Memory.
Prerequisites
The Translation Memory to be organized must exist.
Calling sequence
Select:
Organizing begins immediately. As it may take some time to organize a large Translation Memory, a window is displayed showing you the progress.
Options and parameters
None.
Results
The Translation Memory is now organized and the new number of segments in the Translation Memory is displayed. You can continue to use it.
To increase the reliability of the automatically generated Initial Translation Memory, it is necessary to check the correctness of the relation between source and target segments.
With the Initial Translation Memory editor you can see the contents of the Initial Translation Memory at a glance to verify the correspondence between source and target segments. When a target segment does not correspond to a source segment, you can perform the necessary changes.
The original segments are displayed in the Source window, the corresponding translations in the Target window. The segment pairs are synchronized with each other. That means that a target segment is displayed at the same level on the screen as the source segment and with the same background color.
The following describes how to work with the Initial Translation Memory editor.
Prerequisites The Create Initial Translation Memory window must be invoked and filled in.
Calling sequence Select:
The Edit Initial Translation Memory window is displayed. It consists of two windows. One window shows source segments, the other window shows the corresponding target segments.
Figure 29. Edit Initial Translation Memory window
 |
Options and parameters For information on how to work with the Initial Translation Memory editor see "The Initial Translation Memory editor".
Results
You are now ready to verify the correctness of the automatically generated pairs of source segments and their translated equivalents. When you leave the editor the segment pairs are stored in the Translation Memory.
| Menu or key | Function |
|---|---|
| Save (F2) | Saves the current segment connections. If you have selected another pair of files, the segment connections resulting from these files will be displayed next. |
| Quit (F3) | Quits the Edit Initial Translation Memory window without saving changes. |
| End-Save (F4) | Quits the Edit Initial Translation Memory window and saves any changes to the selected Translation Memory. |
| Toggle window (Ctrl+t) | Activates the opposite window (Source or Target). |
| Menu or key | Function |
|---|---|
| Connect segments (Ctrl+c) | Relates a source segment with a target segment. |
| Delete connection (Ctrl+d) | Removes a connection of a source segment with a target segment. |
| Ignore segment (Ctrl+i) | Removes a marked segment which you do not want to be connected with another segment, or that does not have a match in the opposite file. |
| Undo ignore (Ctrl+u) | Makes a previously ignored segment available for connection with a matching segment in the opposite file. Note that the segment must be marked before you use Undo ignore. |
| Join segments (Ctrl+j) | Combines the currently active segment with the following one. |
| Split joined segments (Ctrl+s) | Splits a previously joined segment at the current cursor position. |
| Add an abbreviation (Ctrl+a) | Adds the term where the cursor is positioned to the list of abbreviations associated to the current source language. |
| Menu | Function |
|---|---|
| Colors... | Lets you define the colors for the segments in the Source and Target windows. |
| Fonts... | Lets you set the font and font size for the source and target window in the Set Fonts window. |
| Arrange | Changes the arrangement of the source and target windows. You can arrange them vertically (the target document is positioned next to the source document on the right half of the screen) or horizontally (the target document is positioned below the source document on the lower half of the screen). |
| Parallel | Positions the segments in the source window parallel to their matches in the target window. That means that lines may be inserted in either the source or the target window to achieve that a segment is presented at the same position as its counterpart. |
| Menu | Function |
|---|---|
| Next connection (Shift+Down) | Moves the cursor to the next connected segment pair. |
| Previous connection (Shift+Up) | Moves the cursor to the previous connected segment pair. |
| Next unaligned (Alt+Down) | Moves the cursor to the next segment for which no matching segment has been found. This can be either in the same or in the opposite window. |
| Previous unaligned (Alt+Up) | Moves the cursor to the previous segment for which no matching segment has been found. This can be either in the same or in the opposite window. |
| Synchronize (Ctrl+Enter) | Positions the current segment and its match in the opposite window beside one another at the same level. |
| Mark segment (Ctrl+m) | Marks the segment where the cursor is positioned. A segment must be marked to connect and to remove it. |
| Unmark segment (Ctrl+n) | Removes the marking from a segment. Only one segment in a window can be marked. |
| Menu | Function |
|---|---|
| Protect | Changes the display of markup information. The markup tags are shown but cannot be overwritten (see the example given in Figure 1). |
| Shrink | Changes the display of markup information. All markup tags outside segments are not shown. A replacement character is shown instead (see the example given in Figure 1). |
| Compact | Changes the display of markup information. All information that is not to be translated and all markup tags within a segment are not shown. A replacement character is shown instead (see the example given in Figure 1). |
The status bar at the bottom of the window displays the following information from left to right:
All matches placed in an Initial Translation Memory are indicated by an [m] prefix. It is recommended that you check the correctness of these matches before using them if you have not already done this using the Initial Translation Memory editor.
An alternative method to perform this check is to retranslate the original document now with TranslationManager , and to compare the sentences in the original document with the translation proposals from the Initial Translation Memory. For each sentence, you can either accept or reject the saved translation. If you accept the translation proposal, the [m] flag is removed. Translations you reject, however, retain the [m] flag. Finally, the EQFDMM command deletes all translations that still have the machine translation flag.
To check the correctness of a newly-generated Initial Translation Memory, proceed as follows:
Press Ctrl+Enter to store the translation of the segment now as a human translation that removes the [m] flagging and proceeds to the next segment.
where:
When all machine-generated matches are removed from the Translation Memory, this is indicated by a completion message.
The following example shows how to remove all machine-generated
matches from a Translation Memory called INTERITM:
| Example |
|---|
eqfdmm /mem=interitm |
To improve the quality of your translations, you may wish to check the contents of a Translation Memory from time to time, and modify or remove translations that are stored there. Doing these changes directly in the Translation Memory lets you benefit from polished translations the next time you use this repository.
Therefore, TranslationManager offers a Translation Memory that can be manipulated. You can browse its contents, make changes to existing translations, or delete complete entries from it. You can work on a Translation Memory contents in an editor window as if you were editing normal text. The original segments are displayed in the Original window, the corresponding translations in the Translation window. You make your changes in the Translation window.
Translation Memory files can be huge. To make it easier for you to find a certain translation, you have the choice to narrow down what you are looking for. For example, you can search for a certain translation segment, or for translations made within a certain time frame.
The following describes how to open a Translation Memory in order to work with it.
Note: Use this function with care. A Translation Memory that has grown over a period of time is an essential asset for all your translations. Therefore it is good practice to avoid any uncontrolled changes. There is no Quit or Undo function. All changes become effective immediately.
Prerequisites The Translation Memory you want to work with must exist.
Calling sequence Select:
You are first prompted with the Look up a Translation window to specify what you are looking for in the selected Translation Memory. For more information on how to work with this window see "Searching a translation".
After you specified the search criteria, the Edit Translation Memory window (see Figure 30) is displayed. It consists of two windows. The Original window lets you view the original text, in the Translation window you can make your changes. By pressing Ctrl+Enter you can move from segment to segment.
Figure 30. Edit Translation Memory window
 |
Options and parameters For information on how to use the Translation Memory editor functions, see "The Translation Memory editor".
Results
You open a Translation Memory to work on the translations that are stored in it. In the Edit Translation Memory window you can browse the original texts and revise the corresponding translations. If you need to change or remove translated text, you can do this in the Translation window where you are assisted by an editor. How you use this editor is explained in "The Translation Memory editor".
Translation Memory files can be huge. You can search for a certain translation segment or for specific translations.
In the Look up a Translation window you specify the individual search criteria. The Look up... button starts the search in the Translation Memory and displays the found Translation Memory contents in the Edit Translation Memory window.
The following describes how to specify the search criteria.
Prerequisites The Translation Memory you want to work with must exist.
Calling sequence Select:
The Look up a Translation window (see Figure 31) is displayed.
Figure 31. Look up a Translation window
 |
Options and parameters
Results
The Translation Memory is searched according to the search criteria specified in the Look up a Translation window.
The found matches are loaded into the editor and displayed in the Edit Translation Memory window where you can revise them. How you revise Translation Memory entries is described in "The Translation Memory editor".
To revise the entries in a Translation Memory, you are assisted by an editor. The functions of this editor support you when changing the Translation Memory entries.
The editor consists of two windows. The Original window shows original segments, the Translation window shows the corresponding translations. By pressing Ctrl+Enter you can move from segment to segment.
From the menu bar of the Edit Translation Memory window you can select the following items:
| Menu or key | Function |
|---|---|
| Next | Loads another collection of segments into the editor if more segments are found in the Translation Memory than the number set to be loaded in the Look up a Translation window. |
| Previous | Unloads the segments that were loaded from the editor previously. Opposite to Next. |
| Save (F5) | Saves any changes made in the Translation Memory. Returns you to the Look up a Translation window. |
| End-Save (F4) | Saves any changes made in the Translation Memory. Quits the Translation Memory editor and returns you to the TranslationManager main window. |
| Toggle windows (Ctrl+t) | Activates the opposite window (Original or Translation). |
Many of the editor functions are tied to
the Translation window only. If a function on the
Edit menu cannot be performed in the Original
window, the function is disabled whenever the Original
window becomes active.
If a key-stroke editor function does not apply to the active window,
the system beeps.
| Menu or key | Function |
|---|---|
| Find and change... | Locates a term and changes it as specified.
Works in Translation and Original window. Changes in the original text are not allowed. |
| Cut | Copies a marked text section to the system clipboard and
removes text afterwards.
Works in Translation window only. |
| Copy | Copies a marked text section to the system clipboard for later
pasting.
Works in Translation and Original window. Text cannot be pasted into Original window though. |
| Paste | Inserts text from clipboard into active segment at
current cursor position.
Works in Translation window only. |
| Split line (Alt+s) | Splits line at current cursor position.
Works in Translation window only. |
| Join line (Alt+j) | Combines current line with following line.
Works in Translation window only. |
| Undo | Restores the original state as it was before an action was performed.
Works in Translation window only. |
| Unmark block (Alt+m) | Removes marking from a text section.
Works in Translation and Original window. |
| Delete
Current segment removes only the currently active segment
from the Translation Memory.
| All segments removes all segments from the Translation Memory
(those that were loaded in the editor).
Works in Translation and Original window. |
The following key combinations let you manipulate text in both
the Original window and the Translation window.
Note that the two windows are synchronized with each other.
That means, whenever you activate a segment in the Translation
window, it becomes active in the Original window too and vice versa.
The matching segment in the opposite window is presented beside the
active one at the same level.
| Keys | Function |
|---|---|
| Ctrl+Shift+Left | Marks previous word from cursor position to beginning of word. |
| Ctrl+Shift+Right | Marks next word from cursor position to end of word including the blank space. |
| Ctrl+Insert | Copies marked block to system clipboard. |
| Ctrl+Delete | Deletes all characters from current cursor position to end of
line in active segment.
Works in Translation window only. |
| Ctrl+Home | Moves cursor to first segment in window. |
| Ctrl+End | Moves cursor to last segment in window. |
| Ctrl+left | Moves cursor to beginning of previous word. |
| Ctrl+right | Moves cursor to beginning of next word. |
| Ctrl+Enter | Activates next segment or segment where cursor is positioned. |
| Ctrl+t | Toggles between Original and Translation window. |
| Shift+left | Extends text marking by one character to the left. |
| Shift+right | Extends text marking by one character to the right. |
| Shift+Up | Extends text marking to the previous line. |
| Shift+Down | Extends text marking to the next line. |
| Shift+Insert | Inserts text from clipboard at current cursor position in active segment. |
| Alt+Delete | Deletes all characters from current cursor position to
end of active segment.
Works in Translation window only. |
| Alt+j | Joins current line with following line.
Works in Translation window only. |
| Alt+s | Splits line at current cursor position.
Works in Translation window only. |
| Alt+n | Loads next collection of segments. |
| Alt+p | Loads previous collection. |
| Alt+m | Removes marking from a text section. |
| Up | Moves cursor one line up. |
| Down | Moves cursor one line down. |
| Right | Moves cursor one character right. |
| Left | Moves cursor one character left. |
| Home | Moves cursor to beginning of current line. |
| End | Moves cursor to end of current line. |
| Page Up | Moves text one page up. |
| Page Down | Moves text one page down. |
| Delete | If a text section has been marked, the marked text is removed. If no text has been marked, the character where the cursor is positioned is removed. |
| Backspace | Moves cursor back by one character in the active segment and deletes this character. |
| Insert | Switches from insert mode to overtype mode and vice versa. When you insert text in insert mode, the existing text is moved to the right to make room for the new text. If you want to type over the existing text, switch to overtype mode. |
| F3 | Quits the Translation Memory editor and returns you to the workbench. |
| F4 | Saves any changes made in the Translation Memory and returns you to the Look up a Translation window. |
| Enter | Moves to next line. |
| Double-click left mouse button | Marks entire segment beginning from the cursor position. |
| Double-click right mouse button | Removes marking from a segment. |
| Menu | Function |
|---|---|
| Colors... | Lets you change foreground and background colors. Note that if you change colors in the Translation or Original window, it will change colors in the translation editor windows accordingly. See also "Configuring the editor" to learn how to work with the Set Colors window. |
| Fonts... | Lets you change fonts and their sizes. Note that if you change a font or a font size in the Translation or Original window, it will change the font or font size in the translation editor windows accordingly. See also "Configuring the editor" to learn how to work with the Set Fonts window. |
| Arrange | Lets you arrange windows. Horizontal positions the Translation window below the Original window. Vertical positions the Translation window next to the Original window on the right half of the screen. |
| Menu | Function |
|---|---|
| Protect | Markup tags within a translation cannot be overwritten. |
| Unprotect | Markup tags within a currently active translation can be overwritten. |
| Hide | Markup tags within a translation are not shown (they are there, but invisible). |
| Compact | Markup tags within a translation are replaced by a special character indicating the position of the tag. |
An external Translation Memory contains segments in their original sequence. That is, the segments are placed in an external Translation Memory in the sequence in which they occur in the documents.
You can edit the external Translation Memory with an editor of your choice as follows:
In the Translation Memory List window, you can display additional information about a Translation Memory. You can define which details you want to be displayed and in which order.
The Translation Memory details are:
You can toggle between two display modes:
You can change the arrangement of the Translation Memory details in the Change Details window described in "Viewing and changing the details of a list item".
A dictionary is a database that contains terms, their translations, and other related information.
TranslationManager provides a set of bilingual dictionaries with general vocabulary for English, German, French, Spanish, and Italian.
You need dictionaries to look up the translations of individual terms or have these terms displayed automatically in the dictionary window during translation.
A dictionary entry contains all data relating to a term (or headword). The dictionary entry structure describes which data elements can be stored for a term in a dictionary.
TranslationManager provides a general dictionary structure that you can use as a model for building a dictionary serving your own purposes. Headword and Translation are mandatory fields. Certain entry fields, for example Synonym and Related term, are reserved for search criteria available during lookup in a dictionary.
TranslationManager can handle dictionaries with simple and complex structures.
The general dictionary entry structure in TranslationManager is divided into four embedded levels, to contain for example, verb and noun entries, different meanings (senses), and translation variants.
In TranslationManager a dictionary can have two formats:
All dictionary data in other text-processor or database formats needs to be converted into SGML by, for example, a program or database macro.
You can create your own dictionaries from existing terminology imported into TranslationManager , or from scratch while you are translating.
To use commercially available online dictionaries covering special areas, contact any one of the dictionary providers whose addresses are given on request from IBM Germany, Department 5412, FAX +49-(0)7031-16-6858.
For more information on the dictionary structure and on how to construct an SGML-based file, see:
A dictionary entry is divided into the following levels:
The entry level can have any number of homonym levels. For example, there are separate homonym levels for the noun copy and the verb copy.
A homonym level can also have any number of sense levels depending on the individual definition of a headword or contextual information. For example, the noun bank can mean both the river bank or a financial institution.
A sense level can have any number of target levels depending on the individual translation variants. For example, the German word Schnecke has two English translations, snail and slug.
The entry fields and how they are distributed over the four levels is only suggested by TranslationManager . The entry fields Headword and Translation are mandatory. All other predefined fields can be deleted or renamed. You can even omit particular levels. For example, you can omit the homonym and sense level if you want to have only headwords and translations in your dictionary.
You can also add new fields to any of the levels. You can do this when creating a new dictionary in the New dictionary window by selecting Add fields... or by including them in the SGML dictionary file.
For the list of all predefined entry fields and their corresponding SGML tags see "List of dictionary-entry fields and their SGML tags".
To search for one or more dictionary entries, the specified term can be used as one of the following search criteria:
The first four entry fields can only be used as search criteria
when they exist at the entry level shown in the following table.
The entry fields are:
| Entry field | Level |
|---|---|
| Headword | Entry |
| Synonym | Sense |
| Other Related Terms | Sense |
| Abbrev./Fullform | Sense |
In the TranslationManager default entry structure, these fields are defined at these levels.
If you are importing an SGML dictionary file and want to use any of the above search criteria, see "List of dictionary-entry fields and their SGML tags" for the SGML tags required.
Dictionaries are used during analysis and translation:
The properties of a dictionary are its main characteristics such as the source language, the dictionary structure, information on its location and a brief description of its contents. You can specify them in the Dictionary Properties window.
Parts of these properties
can also be displayed as details
(or view details)
in the
Dictionary List window.
TranslationManager offers several lookup functions for terms in dictionaries and their data:
TranslationManager dictionaries can be printed to a printer or to a file. You can select the entry fields to be printed and how to arrange them in the printout. This layout is defined in a print format file. You can also use filters to print selected entries only.
A dictionary can be shared with other users by means of the dictionary export function, or if it has been defined to reside on a shared disk when it was created. If you receive an exported dictionary, you can import it into your system.
During import, you can also merge the contents of one dictionary into another. In addition, you can create dictionaries tailored to suit your own needs. To create a new dictionary, you must determine the dictionary structure, this means which data elements in a dictionary are important to you. You can start using the TranslationManager default structure or using other existing dictionary structures that you can subsequently change.
TranslationManager dictionaries can be protected with a password against unauthorized changes if necessary.
Most of the processing functions TranslationManager offers for dictionaries can be started from the Dictionary List window.
Prerequisites
The dictionary must exist (except if you import a dictionary).
Calling sequence
Select:
The Dictionary List window is displayed.
This window displays a list of the existing dictionaries. When you select a command from one of the menus, you are taken to another window where you can specify processing options.
An SGML-based file contains dictionary data and SGML tags describing the data structure and the relation between the data elements.
SGML-based dictionaries can be created by:
If you have dictionary data in a format other than SGML you must convert it before you can import it.
Importing the ASCII encoded SGML-based file into TranslationManager converts the dictionary into the internal format recognized by TranslationManager .
An SGML-based dictionary is divided into the following:
The dictionary is enclosed by a dictionary start tag <dict> and a dictionary end tag </dict>.
The header section contains general information about the dictionary such as:
The dictionary header is marked with a header start tag <header> and a header end tag </header>.
The only information that you must provide in the header section is the source language of the dictionary. You can specify any of the languages for which you have a language support file installed (if you need to specify another language, see "What you can do for other languages"). TranslationManager needs this information for reducing terms to their stem form when looking them up in the dictionary.
The header section can have the following tags:
| Start tag | End tag | Description | |||
|---|---|---|---|---|---|
| <type> | </type> | Type of dictionary | <source> | </source> | Source language |
| <ltarget> | </ltarget> | Target language | |||
| <createdate> | </createdate> | Date when dictionary was created |
| Example of a header section |
|---|
<header> <type>Bilingual</type> <source>English(U.S.)</source> <ltarget>German(national)</ltarget> <createdate>31/05/94</createdate> </header> |
The maptable section determines how a dictionary entry is structured. It serves as a model for the structure of an entry. The fields you defined in the maptable section are reflected in the dictionary entries.
The maptable contains the total of all allowed fields (up to a maximum of 38) in a dictionary entry. If a dictionary entry contains entry field tags not included in the maptable section, the information between the tags is not imported during dictionary import and only the entry fields listed in the maptable are taken into account. The information between a start tag and its end tag contains the name you want to give the entry field of the dictionary. You find these names displayed when you look up or edit a term in a dictionary.
For example, if you specify <hdterm> Source Term <\hdterm>, the terms you look up in the dictionary are shown under Source Term. If you want to use another name, rename Source Term into any other name you would like to use instead.
The following is an example of a maptable section:
| Example of a maptable section |
|---|
<maptable>
<hdterm>Source term</hdterm>
<hom>
<epos>English category</epos>
<sense>
<edef>Formal English definition</edef>
<target>
<trans>NL term</trans>
</target>
</sense>
</hom>
</maptable>
|
The maptable begins with the start maptable tag <maptable> and ends with the end maptable tag </maptable>. The <hom>, <sense> and <target> start tags with their respective end tags mark the homonym, sense, and target levels.
If you want to use the search criteria described
in "Searching a dictionary entry",
use the following start and end SGML tags:
| Searching for ... | Level | Tags |
|---|---|---|
| Headwords | Entry | <hdterm> and </hdterm> |
| Abbreviations | Sense | <eabbr> and </eabbr> |
| Synonyms | Sense | <esyn> and </esyn> |
| Related terms | Sense | <erel> and </erel> |
If you use the tags listed above, TranslationManager establishes a correct relation between the entry field name and the term you want to look up in the dictionary.
If you want TranslationManager to add date information automatically to your dictionary entries, add the Creation Date and Update fields to the maptable.
You can add any number of individually defined
entry fields to any level.
The entry field names are numbered
and automatically mapped to an entry field name denoted by you
in the maptable.
Entry fields you add to the entry, homonym, or sense level
start with the tag <euser id=xxx>
and end with the tag </euser>,
where xxx is the running number.
Entry fields you add to the target level
start with <tuser id=xxx>
and end with </tuser>.
| Example of date-information fields and user-defined fields |
|---|
<maptable>
<hdterm>...</hdterm>
.
.
<ecrdate>Creation date</ecrdate>
.
.
<hom>
.
.
<sense>
.
.
<euser id=1>Entry code</euser>
<elupdate>Last update</elupdate>
.
.
<target>
<trans>...</trans>
<tcrdate>Translation creation date</tcrdate>
<tlupdate>Translation update</tlupdate>
<tuser id=2>Related definition</tuser>
</target>
</sense>
</hom>
</maptable>
|
The entry section lists the actual entries in the dictionary one after the other. Each entry starts with an <entry> tag and ends with an </entry> tag. Each entry contains the same entry field tags as used in the maptable section. Whereas the maptable contains the general description of the structure of an entry, the entry section contains real data.
The levels below the entry level can be repeated as often as necessary, for example, to contain multiple senses or translations.
For an example of an SGML-based dictionary see "Sample of an SGML-based dictionary".
| Level | Entry field name | Start tag | End tag |
|---|---|---|---|
| Entry | Headword | <hdterm> | </hdterm> |
| Entry | Reliability Code | <erlcode> | </erlcode> |
| Entry | Author | <eauthor> | </eauthor> |
| Entry | Creation Date | <ecrdate> | </ecrdate> |
| Entry | Status Code | <estatcode> | </estatcode> |
| Homonym | Part of Speech | <epos> | </epos> |
| Homonym | Morphology | <emorph> | </emorph> |
| Homonym | Hyphenation | <ehyph> | </ehyph> |
| Sense | Source of Headword | <esrc> | </esrc> |
| Sense | Abbrev./Fullform | <eabbr> | </eabbr> |
| Sense | Author of Update | <eauthupdate> | </eauthupdate> |
| Sense | Last Update | <elupdate> | </elupdate> |
| Sense | Definition | <edef> | </edef> |
| Sense | Source of Definition | <esdef> | </esdef> |
| Sense | Synonym | <esyn> | </esyn> |
| Sense | Other Related Terms | <erel> | </erel> |
| Sense | Context | <econtext> | </econtext> |
| Sense | Source of Context | <escontext> | </escontext> |
| Sense | Comments | <comment> | </comment> |
| Sense | Note on Usage | <eusage> | </eusage> |
| Sense | Idiom | <eidiom> | </eidiom> |
| Target | Language | <tlanguage> | </tlanguage> |
| Target | Translation | <trans> | </trans> |
| Target | Company/Subject Code | <tsubjcode> | </tsubjcode> |
| Target | Source of Translation | <tsrc> | </tsrc> |
| Target | Abbrev./Fullform | <tabbr> | </tabbr> |
| Target | Reliability Code | <trlcode> | </trlcode> |
| Target | Author | <tauthor> | </tauthor> |
| Target | Author of Update | <tauthupdate> | </tauthupdate> |
| Target | Creation Date | <tcrdate> | </tcrdate> |
| Target | Last Update | <tlupdate> | </tlupdate> |
| Target | Status Code | <tstatcode> | </tstatcode> |
| Target | Part of Speech | <tpos> | </tpos> |
| Target | Morphology | <tmorph> | </tmorph> |
| Target | Hyphenation | <thyph> | </thyph> |
| Target | Definition | <tdef> | </tdef> |
| Target | Source of Definition | <tsdef> | </tsdef> |
| Target | Synonym | <tsyn> | </tsyn> |
| Target | Other Related Terms | <trel> | </trel> |
| Target | Context | <tcontext> | </tcontext> |
| Target | Source of Context | <tscontext> | </tscontext> |
| Target | Comments | <tcomment> | </tcomment> |
| Target | Note on Usage | <tusage> | </tusage> |
| Target | Idiom | <tidiom> | </tidiom> |
The following is an example of an SGML-based dictionary containing a header section, a maptable, and two entries. The text to the right of the vertical line is explanatory information or comments to the tags. All explanatory information must be omitted when you actually create an SGML-based dictionary.
<dict> | start of dictionary
<header> | start of header section
<source>English (U.S.)</source> | source language (required)
</header> | end of header section
<maptable> | start of maptable section
<hdterm>Source term</hdterm> |
<eauthor>Created by</eauthor> |
<ecrdate>Term Creation Date</ecrdate> |
<hom> |
<epos>Category</epos> |
<sense> |
<edef>Definition</edef> |
<euser id=210>Private glossary</euser>| user-defined entry field
| added to sense level
<target> |
<tsubjcode>Subject code</tsubjcode> |
<trans>Translation</trans> |
<tuser id=1>Project code</tuser> | user-defined entry field
| added to target level
</target> |
</sense> |
</hom> |
</maptable> | end of maptable section
<entry> | start of first entry
<hdterm>file</hdterm> | headword: file
<eauthor>Fred Miller</eauthor> | author: Fred Miller
<ecrdate>940401</ecrdate> | creation date: 4/01/94
<hom> | start of homonym level
<epos>n</epos> | part of speech: noun
<sense> | start of sense level
<target> | start of target level
<tsubjcode>EDV</tsubjcode> | subject code
<trans>Datei</trans> | translation
</target> | end of target level
</sense> | end of sense level
</hom> | end of homonym level
</entry> | end of first entry
<entry> | start of second entry
<hdterm>abend</hdterm> | headword: abend
<eauthor>Peter G.</eauthor> | author: Peter G.
<ecrdate>940501</ecrdate> | creation date: 5/01/94
<hom> | start of homonym level
<epos>v</epos> | part of speech: verb
<sense> | start of sense level
<target> | start of target level
<tsubjcode>EDV</tsubjcode> | subject code
<trans>abnormal beenden</trans> | translation
<tuser id=4>AS400</tuser> | user-defined entry field
| not in maptable, field
| is ignored when this
| dictionary is imported
</target> | end of target level
</sense> | end of sense level
</hom> | end of homonym level
<hom> | start of homonym level
<epos>n</epos> | part speech: noun
<sense> | start of sense level
<target> | start of target level
<tsubjcode>EDV</tsubjcode> | subject code
<trans>abnormale Beendigung</trans> | translation
</target> | end of target level
</sense> | end of sense level
</hom> | end of homonym level
</entry> | end of second entry
</dict> | end of dictionary
TranslationManager offers you several ways of setting up a new dictionary.
If you create a new dictionary via the New Dictionary window in TranslationManager and you do not use the modelling option, the following entry fields are offered as default fields:
| Entry field | Level |
|---|---|
| Headword *) | Entry |
| Part of Speech | Homonym |
| Abbrev./Fullform *) | Sense |
| Definition | Sense |
| Synonym *) | Sense |
| Other Related Terms *) | Sense |
| Context | Sense |
| Translation | Target |
| Company/Subject Code | Target |
The entry fields marked with *) can be used as predefined search criteria in the Look up a Term window (see "Searching a dictionary entry").
If you are working with a more comprehensive structure and require more entry fields, select -Master- on the Use Existing Dictionary as Model window, which offers an extensive dictionary structure. You can rename or delete any fields from this set of entry fields and you can also add new user-defined fields to it.
TranslationManager adds and updates time stamp information automatically,
provided the following date fields are selected
in the New dictionary window
from the -Master- model dictionary.
| Entry field | Level | Contents |
|---|---|---|
| Creation Date | entry | The date when a headword was added to a dictionary. |
| Last Update | sense | The date when information at the sense level of an entry was added or modified. |
| Creation Date | target | The date when a translation for a headword was added. |
| Last Update | target | The date when a translation entry field was last updated. |
Prerequisites
None.
Calling sequence
Select:
The New Dictionary window is displayed (see Figure 32).
Figure 32. New Dictionary window
 |
Options and parameters
Select the drive on which you want the new dictionary to reside. A dictionary grows with time, so select a drive with enough space.
To avoid unauthorized modification of a dictionary, you can protect it by clicking on Protect... which takes you to the Protect Dictionary window where you can type a password of your own. Click on Protect to return to the New Dictionary window. From now on, the dictionary can only be modified when the correct password is supplied. For more information on how to protect and unprotect dictionaries see "Protecting a dictionary".
Click on Create to create the new dictionary.
Results
The dictionary is created but still empty. When the dictionary has been created, its entry structure is fixed and can no longer be changed. You can now start to fill it by importing an SGML-based file, by entering terms from a new terms list, or by editing dictionary entries.
All dictionaries have a dictionary entry structure. In TranslationManager you can use the given default structure, use an existing dictionary structure with or without changes, or define a new structure based on all the available entry fields.
Prerequisites Decide on which dictionary entry fields your dictionary is to contain.
Calling sequence
Select:
The Use Existing Dictionary as Model window is displayed (see Figure 33).
Figure 33. Use Existing Dictionary as Model window
 |
Options and parameters
The list of existing dictionaries is displayed in the list box. Select a dictionary with the structure you want to use as a model from this list or select -Master-, which contains all the entry fields predefined by TranslationManager .
Click on Select to return to the New Dictionary window where you can view and change the selected entry structure by selecting the Change entry fields option.
Results
You have determined which entry structure to use as a base for the new dictionary.
Select this function to make modifications to a dictionary entry structure. You can delete entry fields, rename entry fields, or add new user-defined entry fields. You can determine the size of the entry field and what entry field data you want to have displayed on which panel of the Lookup Entry window.
Prerequisites
Decide on which dictionary entry fields your dictionary is to contain.
Calling sequence
Select:
The Change Entry Fields window is displayed (see Figure 34).
Figure 34. Change Entry Fields window
 |
Options and parameters
Select Omit if you want
the entry field and its data
not to be displayed on any of the lookup panels.
The entry field is not deleted from the entry structure.
Select Aut. Lookup to display the complete entry field
information in
the window showing the found dictionary proposals during translation.
For each selected entry field you can click on one of the following:
When all of the entry field settings are complete, click on Change. This takes you back to the New Dictionary window.
Results
The entry structure of the selected dictionary is changed according to your specifications, this means the dictionary can have more or fewer entry fields, changed entry field names and sizes, and changed lookup display options.
In TranslationManager , all entry fields are automatically assigned a name. You can change the field name to any other name. The changed names are used in all windows where dictionary entry data is displayed. For example, you may want to change Headword to Term, or Part of speech to Category. You can also change the field names to another language of your preference.
You can change the entry field names of an existing dictionary when you create a new dictionary.
Prerequisites
Decide which dictionary entry field names you want to use in your dictionary.
Calling sequence
When creating a new dictionary, select:
When changing the properties of an existing dictionary, select:
The Change Entry Field Name window is displayed.
Options and parameters
Enter the new field name in the Displayed as field. Click on Change to rename the selected field.
Results
The selected dictionary entry field is renamed.
You are returned to the Change Entry Fields window when you create a new dictionary or to the Dictionary Properties window when you change the properties of an existing dictionary.
The predefined entry fields in TranslationManager dictionaries are only examples of possible fields you can use when you create a new dictionary and determine its structure.
You can add your own user-defined fields to any of the four levels that make up the dictionary structure.
You can only add user-defined fields when you create a new dictionary. When the dictionary already exists, you cannot change its structure.
Prerequisites Decide which dictionary entry fields you want to add to your dictionary structure.
Calling sequence
The Add Entry Field Name window is displayed.
Options and parameters
Type a name for the entry field you want to add in the Displayed as field. Click on Add to add the new field to your structure.
Results
The entry field is added to the dictionary structure at the same level as the entry field you have selected before clicking on Add field.... You are returned to the Change Entry Fields window.
A dictionary filter is a means by which data in a dictionary can be selected so that only entries that meet specified conditions are displayed or printed.
In TranslationManager filters can be used in combination with printing (see "Printing a dictionary") or dictionary lookup (see "Looking up a dictionary entry"). You can use an existing filter, change an existing one, or create a new one.
In TranslationManager a filter condition consists of:
For example, the condition Headword LIKE = 'a*' selects all (and only) the entries beginning with the letter a.
There are two types of operators:
The operators have the following meanings:
Note: All filters depend on the dictionary entry structure. This means that a filter created for a one dictionary possibly refers to entry fields that are not contained in another dictionary. In such cases, it is recommended to create a new filter for each dictionary.
Prerequisites
Either the Look up a Term window or the Print Dictionary window is active.
Calling sequences
The Edit Dictionary Filter window is displayed (see Figure 35).
Figure 35. Edit Dictionary Filter window
 |
Options and parameters
The dictionary-filter parameters are as follows:
You can choose a name from this list box if you want to use an existing filter as a model. Type a new filter name in the Save to box before saving your changes. Otherwise the existing filter is overwritten.
When you double-click on a field name in this list box, the field name is put in the SELECT field.
When you select a field name from the list box (single click) and double-click on an operator, the Set Dictionary Condition window is displayed, where the condition can be set. The resulting condition is displayed in the WHERE field.
You can type the condition directly into the field (leave a blank between field names, operators, and operands) or select an entry field and double-click on an operator. This activates the Set Dictionary Condition window where the condition can be set. The resulting condition is displayed in the WHERE field.
A condition expression requires a field name, an operator, and a value. The Boolean operators AND and OR join expressions, NOT negates an expression. Use parentheses to clarify complex expressions.
You can enter a new name, or select an existing name. If you select an existing filter name, the existing filter is overwritten.
Select Save to create the new or changed filter.
For example, if you want to create a filter that selects only those entries in the dictionary that begin with the letter a, define the filter as follows:
Results
The changed or new filter is saved and can be used for dictionary lookup or printing. You are returned to the previous window.
Deleting a dictionary can be useful, when you have exported it or archived it outside of TranslationManager and no longer need it, and you require free space on your disk.
For deleting a shared dictionary, see "Deleting a shared dictionary".
Prerequisites
Make sure that you have a backup copy of the dictionary before deleting it if it contains data of importance.
Calling sequence
Select:
Options and parameters
A confirmation message appears before the dictionary is deleted.
If you select No, the delete function is canceled.
If you select Yes, the dictionary is deleted.
Results
If you selected Yes, the dictionary is deleted. References to this dictionary may still exist in certain folders. Update the folder properties so that the deleted dictionary is not referenced anymore.
Individual dictionary entries can be changed, for example, a new translation can be added or an existing obsolete translation deleted.
You can edit a dictionary entry at any time before, after, or during translation.
Prerequisites The dictionary must exist.
Calling sequence
There are several ways to get to the Edit Entry in Dictionary window:
In all cases, the Edit Entry in Dictionary window is displayed (see Figure 36).
Figure 36. Edit Entry in Dictionary window
 |
Options and parameters
The entry displayed in the Edit Entry in Dictionary window is split up into templates. A template is the complete dictionary entry information related to one translation. This window shows one template at a time.
If the term does not exist,
only one empty template is displayed.
If, on the other hand, the term exists,
the first template (translation) is displayed.
To delete the entire entry from the dictionary, click on Delete at the bottom of the window.
Click on Save to save your changes to the dictionary displayed in the Save to dictionary list box. In the Translation Environment, you can choose between any of the dictionaries opened for translation (defined as a folder property). Outside the Translation Environment, you can only save the data to the dictionary you explicitly selected.
Results
A new term is added to the dictionary, or an existing term is changed or deleted.
There are two ways to export dictionary data, within a folder in the internal TranslationManager format or as an external dictionary in SGML format.
Export a dictionary if you want to pass the dictionary on to other TranslationManager users or to create a backup copy of a dictionary. Protected dictionaries must be exported in a folder. For more information on folder export, see "Exporting a folder".
Exporting a dictionary into an SGML-based file is required if you want to use the dictionary data in environments other than TranslationManager .
Prerequisites
Sufficient disk space for the exported dictionary is available.
Calling sequence
Select:
The Export dictionary window is displayed (see Figure 37).
Figure 37. Export Dictionary window
 |
Options and parameters
Select the drive to which you want to export the dictionary. Ensure that you have sufficient space on this drive.
Click on Export to begin the dictionary export.
If you specified a new directory name you are prompted to confirm whether you want to create this new directory.
Results
An SGML-based dictionary file is created at the specified location and can be given to other users or programs for further usage.
You can import a dictionary as an external dictionary (SGML-based) or within a folder in the TranslationManager format.
If you want to work with terminology created outside TranslationManager , create an SGML-based file (for more details, see "Creating an SGML-based dictionary") and import this file into TranslationManager . You can either import the file into a new dictionary or merge the data into an existing dictionary.
Dictionaries imported in a folder are in TranslationManager format. If the dictionary does not exist, a new dictionary is created; if it does exist, the folder dictionary is merged into the existing one. For more information on folder import, see "Importing a folder".
When merging two dictionaries, the dictionary structure of the destination dictionary is maintained. Data in entry fields that exist only in the source dictionary and not in the destination dictionary will not be regarded and data may be lost. Entry fields not contained in the external dictionary will be empty in the dictionary after importing.
If you select to import an external dictionary under a new dictionary name, the New Dictionary window is displayed where all the properties are shown as they are coded in the SGML-based file. You can change certain properties if you want to, although this is not always advisable as the changed properties may be different from what is specified in the SGML file.
Prerequisites The SGML-based file for import must have been created according to the description in "Creating an SGML-based dictionary".
Calling sequence
Select:
The Import Dictionary window is displayed (see Figure 38).
Figure 38. Import Dictionary window
 |
Options and parameters
Select the drive where the file is stored.
Click on Import to begin the import function.
If TranslationManager detects an incorrect SGML tag in the SGML-based file, a message is displayed, asking you if you want to skip the entry containing the error or to cancel the import process.
If you selected to import an external dictionary under a new dictionary name, the New Dictionary window is displayed where all the properties are shown as they are coded in the SGML-based file. For more information, see "Creating a new dictionary in TranslationManager".
If you selected to merge the external dictionary into an existing dictionary in TranslationManager , remember that the dictionary structures may differ and that there may be identical terms. In case of conflicts you are prompted to specify additional options for merging dictionaries in the Merge Dictionary Entries window. For more information, see "Merging dictionaries".
Results
The external dictionary data is imported either under a new name or merged with an existing dictionary. You can begin to use it in TranslationManager . The external dictionary is unchanged.
There are several ways to look up dictionary entries in TranslationManager :
Outside the Translation Environment you can look up entries only in one dictionary at a time.
How to search for terms in a dictionary is described in "Searching a dictionary entry". How to edit an existing entry in a dictionary after you have retrieved it, is described in "Editing a dictionary entry".
Prerequisites
Calling sequence
Outside the Translation Environment, follow this procedure to look up a dictionary entry:
During translation in the Translation Environment, there are several ways to look up a dictionary entry:
If the specified term does not exist in the selected dictionary, the Look up a Term window is displayed (see Figure 42) showing existing terms preceding and following the marked term in alphabetical sequence. For more information on searching, see "Searching a dictionary entry".
In all cases, if the specified term exists in the dictionary, the Lookup Entry window is displayed (see Figure 39).
Figure 39. Lookup Entry window
 |
Options and parameters
The large center box contains entries for the found term in the displayed dictionary according to the panel selection.
Click on Print to print the data of the term
on your workstation printer.
Click on Edit... if you want to edit
the entry data of the found term
in the Edit Entry in Dictionary window.
For more information on editing,
see "Editing a dictionary entry".
Click on Copy to copy a marked text to the clipboard.
Click on Cancel to leave the window.
Results
The entries for the selected term are displayed.
The entries are changed,
printed, or copied to the clipboard
depending on the options you selected on this window.
Merging two dictionaries is only supported when you import an external dictionary into an existing one in TranslationManager .
When you do this, remember that the dictionary structure of the destination dictionary has precedence. You are warned if the dictionary structures differ, and TranslationManager allows you create a new dictionary instead, to prevent any loss of data.
If, during dictionary merge,
the same term exists in both dictionaries,
the
Merge Dictionary Entries window is displayed
(see Figure 40).
Figure 40. Merge Dictionary Entries window
 |
Options and parameters
Click on Merge to begin or to continue
the merging.
Click on Cancel to
leave the merging and importing program.
Results The external dictionary data is merged with the existing dictionary according to the specified options. The external dictionary is unchanged.
To look at dictionary data, you must open it. In a dictionary, you can search for specified terms, you can look up the data of an existing term, you can change the entry data of an existing term and you can add entries for new terms.
Opening a dictionary can be done in several ways outside the Translation Environment and during translation in the Translation Environment.
Opening a dictionary is automatically done, when you use one of the following functions:
Organizing makes the dictionary compact and increases performance. Dictionaries to which you frequently make changes should be organized periodically.
If an error occurs during dictionary processing, you are prompted to organize the dictionary because organizing often rectifies the error.
Prerequisites The dictionary must exist.
Calling sequence
Select:
The organize procedure starts immediately.
Options and parameters
None.
Results
The dictionary is organized and you can continue using it.
You can choose to print a complete dictionary or parts of it.
If you only want to print part of a dictionary, for example all entries with a headword starting with the letter a, or only some of the entry fields, or only the headwords and the translations, you can define a filter for the print function.
You must define the layout of your print output in format files that you edit with a text editor. In the print format file you define the entry fields to be printed and how they are arranged in the printout.
You can send your printout to an attached workstation printer or have the printout data sent to a file.
Before printing a dictionary or part of a dictionary, the output file structure must be determined. If you decide not to use one of the format files provided by TranslationManager you must create this file in the subdirectory \EQF\PRTFORM. For more information on how to use the sample format print files, see "Defining the printout format". For a detailed description of the structure and syntax of a print format file see "Defining your own format file".
Prerequisites
Calling sequence
Select:
The Print Dictionary window (see Figure 41) is displayed.
Figure 41. Print Dictionary window
 |
Options and parameters
Click on Edit... to define the new filter or to change an existing one, which takes you to the Edit Dictionary Filter window. For more information on how to define filter conditions, see "Defining a dictionary filter".
Click on Print to start the printing function.
Results
If you selected the Printer option,
the dictionary printout is sent to your attached printer.
If you selected the File option,
the dictionary printout is stored in the specified file.
TranslationManager provides sample print-format files that you can use to print dictionary data or as a basis for defining your own print output format.
To become acquainted with format files, use the FORMAT1.FRM print format file for printing one of the sample dictionaries provided in a sample folder (for example SAMPLE2).
When you change a format file or create one of your own, make sure you follow the required syntax of the format file. All print-format files are located in the subdirectory \EQF\PRTFORM.
The following sample files are provided by TranslationManager :
Experienced users can use the print function also for generating new external dictionaries, which again can be imported and used in TranslationManager . For example, you can:
To avoid uncontrolled modification, you can protect dictionaries, that is, everyone can browse these dictionaries, but only authorized persons responsible for updating dictionaries (for example, a terminologist) can make changes to them. You protect them by assigning a password to them.
You can protect dictionaries on the New Dictionary window when creating a new dictionary or on the Dictionary Properties window when viewing its properties by pressing the Protect... button.
If you are not authorized to edit a protected dictionary but want to make changes to existing entries or add new entries, you can do this by creating a new dictionary using the protected dictionary as a model. For more details see "Creating a new dictionary in TranslationManager". You can then use the new dictionary as an addendum dictionary to the protected one. Redefine any dictionary search sequence so that this addendum dictionary precedes the protected dictionary.
You can send this addendum dictionary to a person who is authorized to edit protected dictionaries and can update these dictionaries on the basis of the modifications and additions made in your addendum dictionary.
When you start creating a new dictionary, the unprotected mode is the default setting. This mode allows you to carry out any modifications to that dictionary.
The following table shows you which tasks
you can perform with unprotected
and protected dictionaries:
| Dictionary task | Unprotected | Protected |
|---|---|---|
| Export to SGML-based dictionary | Yes | No |
| Delete a dictionary | Yes | Yes |
| Export folder with dictionary | Yes | Yes |
| Look up a dictionary entry | Yes | Yes |
| Edit a dictionary entry | Yes | No |
| Organize a dictionary | Yes | Password |
The following table shows the merge options
that are available:
| Dictionary merge from | To unprotected dictionary | To protected dictionary |
|---|---|---|
| SGML-based dictionary | Yes | Password |
| Unprotected folder dictionary | Yes | No |
| Protected folder dictionary | No | No |
Calling sequence
To protect an existing dictionary, select:
To protect a new dictionary, select:
The Protect Dictionary window is displayed. Enter your new password twice and confirm by clicking on Protect.
Results
The dictionary is protected, for example, only those that know the password have read-write access to the dictionary. Those who do not know the password have read-only access.
The protection status of a dictionary can be revoked if the password assigned to the respective dictionary is known.
Calling sequence
Select:
The Query Password for Dictionary window is displayed.
This window is also displayed, when you try to perform an action that makes changes to the dictionary.
In this window you can enter the dictionary password and confirm by pressing the OK button.
Results
The dictionary is unprotected and everyone can change it.
If you want to know whether a certain term is included in a dictionary, you can search for this term in several ways, this means with a:
Searching for a term can be done outside the Translation Environment and during translation in the Translation Environment.
To search for a term, you specify the term and the search parameters in the Look up a Term window.
If more than one term matches with the specified search criteria, you can select the term you are currently interested in to display its data.
If the term is found in the dictionary, you can display and edit the complete entry in subsequent windows (Look up Entry and Edit Entry in Dictionary).
If the specified term is not found in the dictionary, you can add a new entry for this term.
What you can do on the following windows, is described in "Looking up a dictionary entry", and "Editing a dictionary entry".
Prerequisites The dictionary must exist.
Calling sequence
To search for a term outside the Translation Environment, select:
Alternatively, double-click on the dictionary in the Dictionary List window in the main window.
To search for a term in the Translation Environment, select:
The Look up a Term window is displayed (see Figure 42).
Figure 42. Look up a Term window
 |
Options and parameters
Select one of the following search types:
Click on Edit... to define the new filter or to change an existing one, which takes you to the Edit Dictionary Filter window. For more detail on how to define filters, see "Defining a dictionary filter".
Click on Look up... to start the search.
Click on Edit... if you expect that an entry exists for the specified term and you want to edit it.
Results
If you selected the Headword search type and an entry for the specified term is found in the dictionary, the Lookup Entry window is automatically displayed containing the data for this entry. For more information, see "Looking up a dictionary entry".
If you selected the Headword search type and the term is not found in the dictionary and you clicked on Look up..., a message appears asking if you want to add the term to the dictionary. If you add the term, you are automatically taken to the Edit Entry in Dictionary window. For more information, see "Editing a dictionary entry".
If you selected Neighborhood search, and the term is not found in the dictionary, a list of up to 60 terms is displayed in alphabetical order where the specified term would appear in the middle.
If more than one term satisfies the specified search criteria, a list of up to 60 terms is displayed from which you can select a term and use it for a Headword search request.
If the specified term exists in the selected dictionary and you selected Edit..., the Edit Entry in Dictionary windows is displayed For more information, see "Editing a dictionary entry".
Sharing dictionaries with other translators in a LAN system helps you keep your own used disk space small and you can work with a dictionary even if another translator is using it at the same time. You may find this especially convenient when you work with fellow translators on the same project. For example, if you must translate a term that a fellow translator has added to the shared dictionary only recently, you can instantly use your colleague's translation by copying it from the shared dictionary.
If you wish to work with shared dictionaries, you must note the following prerequisites:
To use a dictionary that is shared by many translators you must include it in your list of local dictionaries. To remove it from this list you must disconnect it.
Prerequisites
The shared dictionary must exist.
Calling sequence
Select:
The Connect Shared Dictionaries window is displayed.
Options and parameters
Select Connect to update your list window.
Results
The selected dictionary has been added to your local list window and can now be used like any other dictionary. If you disconnected it, it is no longer shown in the list window.
If you no longer need a dictionary, you can delete it. When you delete a dictionary that is shared by others, the following conditions apply:
Prerequisites
The dictionary must exist.
Calling sequence
Select:
Before TranslationManager deletes the selected file, you are prompted to confirm that you want to delete the file.
Options and parameters
Results
If you are the owner of the deleted dictionary, it is deleted physically, the disk space is freed, and it can no longer be used by any other translator in the network.
If the dictionary was created by someone else and you just shared it, it is removed from the respective list window and you can no longer access it. However, it is still available on the shared disk to be used by other translators.
In the Translation Memory List and Dictionary List window, you can display additional information about a shared Translation Memory or dictionary. The Owner column shows the user ID of the person who created the shared resource.
The properties of a dictionary are its individual characteristics. Some properties, for example the dictionary structure and the size of an entry field, can not be changed when the dictionary has been created. Others, for example which lookup panels are to display which data, can be changed.
Prerequisites The dictionary must exist.
Calling sequence
Select:
This takes you to the Dictionary Properties window (see Figure 43).
Figure 43. Dictionary Properties window
 |
Options and parameters The Dictionary Properties window lists the characteristics of the selected dictionary.
For an existing dictionary, only the following properties can be changed:
Aut. Lookup displays the complete entry field information in the window showing the found dictionary proposals during translation.
To change the name given to an entry field click on Change name.... For example, you can change the name of the Headword entry field to Term. For more information on renaming entry fields see "Renaming a dictionary entry field".
To avoid unauthorized modification of a dictionary, you can protect it by clicking on Protect and typing a password on the Protect Dictionary window. Then the dictionary can only be modified when the correct password is entered. For more detail on how to protect and unprotect dictionaries see "Protecting a dictionary".
Click on Change to change dictionary properties.
Results
The dictionary properties are changed according to your specifications.
In its simplest form, the Dictionary List window lists all of the available dictionaries. However, if you want to see more specific details of each dictionary, you can change your view of the Dictionary List window to have it display individual properties, such as the source language, location, or description of a dictionary.
The details selectable for a dictionary are:
You can toggle between two display modes:
You can change the arrangement of the dictionary details in the Change Details window.
For a general description see "Viewing and changing the details of a list item".
TranslationManager creates terminology lists during document analysis. The lists are compiled by comparing terms in a document with selected dictionaries.
In TranslationManager , you can generate and work with the following types of terminology lists:
A terminology list usually contains terms of only one language. When you copy a term from a terminology list to a dictionary, the source language of the dictionary must be the same.
All types of terminology lists can be exported, this means they are converted to an external format that is SGML based. A file with this format can be used to exchange the data of a list with other users or applications.
External terminology lists can be edited or created by other systems; to use them in TranslationManager , you import them.
A description of the external format is given in "Creating an external terminology list".
You can start most of the functions related to terminology lists from the related list window, as shown in the following example.
Prerequisites
None.
Calling sequence
Select:
One of the list windows is displayed, for example the New Terms Lists window.
The list window contains the list of existing terminology lists, in this example all new terms lists.
Actions on a terminology list can be started by selecting a list name and an action from the File menu.
Depending on the type of terminology list to be created, there are different ways to do this:
You can also create an exclusion list from an existing new terms list or found terms list. This is explained in "Opening and changing a terminology list".
Another general way is to create an external terminology list outside of TranslationManager , which can be imported. This is explained in "Creating an external terminology list".
New terms lists and found terms lists are created during analysis of a document.
Prerequisites
Calling sequence
Select:
Options and parameters
For a detailed description of the options see "Analyzing a document".
Results
The terminology lists are created according to your specifications.
You can create an exclusion list from an existing new terms list or found terms list. This procedure is explained in "Opening and changing a terminology list".
You can also create an exclusion list from the New Exclusion List window or the Edit Exclusion List window.
Prerequisites
The Exclusion Lists window is active.
Calling sequence
Select New... from the File menu
The New Exclusion List window is displayed.
Options and parameters
The upper list box is empty. Here you can define the terms for the new exclusion list:
To save the terms in the new exclusion list, select the Create button.
If you do not want to create the exclusion list anymore, select the Cancel button.
Results
If you selected the Create button, the exclusion list is created with the terms entered and you can use it in the analysis of a document.
If you selected the Cancel button, no new exclusion list is created.
Although TranslationManager offers functions for the creation of terminology lists where you only specify some parameters in a window, you can also create them outside of TranslationManager .
This can be useful when you already have terminology lists available in a format of your own, which you must only convert to the format you can import in TranslationManager .
External new terms lists and external found terms lists must be created in an SGML format to import them.
External exclusion lists are created without SGML tags. If you want to create an exclusion list outside of TranslationManager you can write a list of terms in an editor of your choice, where each line contains one term, and then import it in external format. The list can have any number of terms. For details on importing terminology lists see "Importing a terminology list".
A new terms list requires as first tag in the first line <NTLIST> and as the very last tag in the last line of the list the tag </NTLIST>. The same applies to a found terms list, except that you must use the tags <FTLIST> and </FTLIST>.
The description of an entry always starts with the start tag <TERM> and ends with the corresponding end tag </TERM>.
The term itself is between the start tag <LEMMA> and the end tag </LEMMA>.
To add context information to a term, the context information must have the start tag <CONTEXT>, and the end tag </CONTEXT>. Adding context information is optional; you can include more than one context.
To insert the term address to a terminology list without context information, your entry would look as follows:
<TERM> <LEMMA>address</LEMMA> </TERM>
When you want to insert the term hardware to a terminology list with information about two contexts, your entry would look as follows:
<TERM> <LEMMA>hardware</LEMMA> <CONTEXT>However, before selecting your hardware devices, you should understand your data processing requirements. </CONTEXT> <CONTEXT>This publication assists you in selecting a hardware configuration. </CONTEXT> </TERM>
You can insert as much context information as you want, but each piece of context information needs the start and the end tag.
A new terms list with the entries hardware, software, term, context and with some context information for the first and last entry would have the following layout:
<NTLIST> <TERM> <LEMMA>hardware</LEMMA> <CONTEXT>Your hardware requirements are as follows:</CONTEXT> </TERM> <TERM> <LEMMA>software</LEMMA> </TERM> <TERM> <LEMMA>term</LEMMA> </TERM> <TERM> <LEMMA>context</LEMMA> <CONTEXT>The context information must be stored between a start and end tag.</CONTEXT> </TERM> </NTLIST>
You do not have to sort your entries in alphabetical order. This is done during importing.
How to import the new list is described in "Importing a terminology list".
Prerequisites
The list window that contains the terminology list to be deleted is active.
Calling sequence
Select:
Options and parameters
Before the system deletes the selected list, it asks you to confirm whether you really want it:
Results
If you selected Yes, the list is deleted; otherwise it remains unchanged.
You can export a terminology list to give it to another user, for example, another translator who needs it for the translation of another document. You can choose to export the list in TranslationManager or external format.
In order to exchange the data with other TranslationManager users, select the TranslationManager format. If you want to pass the list to another program you should select external format.
When you export in external format the found terms lists and the new terms lists are exported in SGML format. You can find a description of this format in "Creating an external terminology list".
When you export an exclusion list in external format, it is written as an ASCII coded file.
Prerequisites
The list window that contains the terminology list to be exported is active.
Calling sequence
Select:
For an exclusion list, the Export Exclusion List window is displayed (see Figure 44).
Figure 44. Export Exclusion List window
 |
Options and parameters
Depending on the format selected, this window offers a different number of options and parameters:
For exporting in TranslationManager format, specify the following:
For exporting in external format, specify the following:
To start the exporting function, select Export.
Results
The selected terminology list is now exported in the selected format. The file in the internal format can only be used by TranslationManager users. The file in the external format can be used or changed by other applications. In "Creating an external terminology list" you find a description of how to work with external lists.
If a terminology list has been created by another TranslationManager user, you must import it to make it available in TranslationManager .
Prerequisites
Calling sequence
Select Import... from the File menu
For an exclusion list, the Import Exclusion List window is displayed (see Figure 45).
Figure 45. Import Exclusion List window
 |
Options and parameters
Depending on the format selected, this window offers a different number of options and parameters:
For importing in TranslationManager format, specify the following:
When you have selected a drive the terminology lists are automatically displayed in the list box. Select the list you want to import.
For importing in external format, specify the following:
Select the drive where the external list is stored.
To start the importing function, select the Import button.
Results
The terminology list is stored in TranslationManager and can be used for further processing.
You open a list to work with it, for example, to copy entries from the terminology list to a dictionary or to another list.
Prerequisites
The list window that contains the terminology list to be opened is active.
Calling sequence
Select:
One of the following windows is displayed, depending on the type of list selected:
The Edit Exclusion List window is explained in "Editing an exclusion list".
Figure 46. Work with New Terms List window
 |
Options and parameters
In the list box you see the terms contained in the opened new or found terms list.
You can select and mark one or more terms in order to specify the processing:
To begin the processing of the selected terms,
you click on Process.
If you marked any term to add to a dictionary,
you can specify more options in the
Mark Term for Dictionary window
(see "Editing a dictionary entry").
When the processing is completed,
the list contains the remaining terms for which no
processing was specified.
The marked terms need not be processed immediately. To save the list in its current status of marking, click on Save.
To leave the terms list in its original status, click on Cancel.
Results
If you selected Process, the terminology list is changed depending on your selections. If you made changes to any dictionary or exclusion list, they are active during the next analysis or translation of a document.
If you selected Save, the terminology list is saved including the new processing marks.
If you selected the Cancel button, the terminology list remains unchanged.
You can mark new terms and found terms to add them to a dictionary. You do this by clicking on Mark for dictionary... and Process in one of the following windows:
The Mark Term for Dictionary window is displayed (see Figure 47).
Figure 47. Mark Term for Dictionary window
 |
Options and parameters
To save the processing information for this term, click on Mark.
To skip the current term, select the Skip button.
If several terms are marked for the dictionary, the next term is displayed in the Term field. If all marked terms were displayed, you are returned to the previous window.
Results
The selected term is prepared for addition to a dictionary. When all terms marked for dictionary are processed, you can add more information, depending on the structure of the selected dictionary in the Edit Entry in Dictionary window. You can find more information about editing entries in dictionaries in "Editing a dictionary entry".
When you have opened an exclusion list, the Edit Exclusion List window is displayed.
Options and parameters
The list box contains terms from the selected exclusion list.
Clipboard operations (cut, copy, paste) are supported.
To save the terms in the selected exclusion list, select the Save button.
To leave the exclusion list in its original status, select Cancel.
Results
If you selected Save, the exclusion list is changed depending on your selections. If you made changes to the exclusion list, they are active during the next analysis of a document.
If you selected Cancel, the exclusion list remains unchanged.
To do paperwork on terminology lists, you can print them on the printer attached to your workstation.
Prerequisites
The respective list window that contains the terminology list to be printed is active.
Calling sequence
Select:
The printing function is started immediately. The respective list window remains displayed.
Options and parameters
None.
Results
The selected terminology list is directly routed to your attached printer. The first line of the printout contains the type of terminology list and the list name. Then the contents of the list follow. Each entry is printed in a separate line. If your list contains context information it is also printed.
For all types of terminology lists, the system keeps some view details that can be displayed in the corresponding list window.
These details are:
You can toggle between two display modes:
You can change the arrangement of the details of terminology lists in the Change Details window described in "Viewing and changing the details of a list item".
TranslationManager can handle documents created by the most popular word-processing systems and a wide range of other document types.
Documents usually are a mixture of text and layout information, which describes the formatting of the document. This layout information is called markup data. It defines for example, the start of a new page, the start of a paragraph, or character layout like boldness, italics, or underline.
In most of the word-processing systems that display a text in WYSIWYG mode (What You See Is What You Get), you usually do not see this markup but only its effects. Some systems allow you to display and check the markup data, for example in WordPerfect with the Reveal codes option.
In other systems that generate the formatting printout in a separate step, you usually edit the markups yourself.
The table that stores the description of the markup data is called markup table in TranslationManager . TranslationManager needs this markup table to differentiate between the text to be translated and the markup data.
Markup tables are used
It is important for you to know which markup table is to be used for which type of document. You must tell TranslationManager what kind of markup table should be associated with a folder or a document.
For more information on associating a markup table with a document see either "Viewing and changing the properties of a document", or "Importing a document".
For information on associating a folder with a markup table, see "Creating a folder", or "Viewing and changing the properties of a folder".
The association of a document or folder with a markup table is essential because the different word processors have different layout descriptions. All these layout descriptions are understood by TranslationManager and processed in a general way.
The following table shows
the available markup table names
and the supported document types.
| Markup table | Type of document |
|---|---|
| EQFAMI | AmiPro texts (AmiPro for Windows, Version 2.0) |
| EQFAMRI | Windows resource texts (format complying with ANSI) |
| EQFASCII | ASCII texts |
| EQFASM | Assembler documents |
| EQFBOOK | BookMaster and Information Presentation Facility (IPF) texts |
| EQFHTML2 | HTML texts (level 2.0) |
| EQFMRI | OS/2 resource texts |
| EQFRTF | Rich Text Format (RTF) files coming from Word for Windows, AmiPro, or other word processors |
| EQFWORD | Word for Windows texts (Version 2.0) |
| EQFWORD6 | Word for Windows texts (Version 6.0) |
| EQFWP | WordPerfect texts (Version 5.0) |
| EQFWP6 | WordPerfect texts (Version 6.0 and 6.1) |
TranslationManager allows you to add more formats. For detailed information on creating external markup tables see "Creating a markup table", and Appendix E. "What you can do with external markup tables".
For information on how to use the markup tables and how to prepare the different document types for translation, see "Dealing with specific document formats".
Markup tables can be exchanged with other users or applications. This may be necessary, when you have changed a markup table for your special translation needs and another translator may want to share your changes for similar translation environments.
To give the markup table to someone else you must transfer it out of TranslationManager . This process is called export. The recipient must import the exported markup table into TranslationManager again.
Markup tables can also be exchanged via exported folders. When you export a folder with a document using a specific markup table, this markup table is included in the exported folder and can be loaded implicitly during folder import in the recipient's system.
If you want to change an existing markup table, you have to export it. The exported file can be changed with any text editor. The changed file can be imported into TranslationManager , either under the old name or a new name of your choice.
If you want to create a new markup table you must do this outside the TranslationManager program and use the specific format for markup tables.
Once you have generated the table, you can import it into TranslationManager and start using it for your translations.
Prerequisites
None.
Calling sequence
Select Utilities from the Display markup table list menu
The Markup Table List window is displayed.
The window contains all existing markup tables in your system.
Most of the actions related to markup tables can be started by selecting a list name and an action from the File menu, such as Delete, Export..., or Import....
A markup table can only be changed in external format. If you change a markup table, make sure you are familiar with the SGML format of markup tables.
See Appendix E. "What you can do with external markup tables" for the format of markup tables.
Before you change a markup table provided by TranslationManager , it is recommended to make a backup copy of the original version because the original markup tables cannot be reinstalled.
A markup table can only be created in external format. If you change a markup table, make sure you are familiar with the SGML format for markup tables.
See Appendix E. "What you can do with external markup tables" for the syntax and semantics of markup tables.
You can also base a new markup table on an existing one. To do this, export an existing markup table that already contains a correct SGML syntax, then change the markup data in this file with any text editor. The changed file can be imported into TranslationManager . TranslationManager detects syntactical errors during import.
The external markup table can be imported either under the old name or a new name.
As the original markup tables provided by TranslationManager cannot be reinstalled, it is recommended to make a backup copy before you change them.
If you no longer need a markup table, you can delete it. For markup tables provided by TranslationManager , it is recommended to create a backup copy by exporting the table, because it cannot be reinstalled separately but only by a system reinstallation.
Prerequisites
Calling sequence
Select File from Delete menu
Options and parameters
Before the system deletes the selected markup table, it asks you to confirm whether you really want to delete it.
If you select No, you will leave the delete function.
If you select Yes, the markup table will be deleted.
Results
If you selected Yes, the markup table is deleted. Otherwise it remains unchanged. References to this markup table may still exist in certain folders. Update the folder properties so that the deleted markup table is no longer associated with a folder.
You can export a markup table to give it to other users, for example, other translators who must use the same modified markup table in their translation environment.
Markup tables can only be exported in external format.
Each markup tag described in the markup table is exported together with its nondefault data. You can find a table containing the definition of markup table SGML tags and the data defaults that are used for TranslationManager in Appendix E. "What you can do with external markup tables".
Prerequisites
Calling sequence
Select Export... from the File menu.
The Export Markup Table window is displayed.
Figure 48. Export Markup Table window
 |
Options and parameters
Select the drive to which you want to export the markup table.
To start the exporting function, select the Export button.
Results The selected markup table is exported to the specified file and saved on the selected drive and directory.
If another user has prepared a markup table for your translation environment, you must import it in order to be able to use it in TranslationManager .
Markup tables can only be imported in external format.
Prerequisites
The Markup Table List window must be active.
Calling sequence
Select Import... from the File the menu
The Import Markup Table window is displayed (see Figure 49).
Figure 49. Import Markup Table window
 |
Options and parameters
To start the importing function, select the Import button.
Results
The markup table is now available in TranslationManager , you can start to associate it with documents or folders.
Language-support files are monolingual morphological data files. With TranslationManager they are used to perform:
When an original document contains the English word bought, for example, TranslationManager actually looks up the infinitive form of the verb, buy, in the dictionary. The English (U.S.) language-support file contains the information necessary to associate bought with buy.
When an original document contains the German word Autoradio (car radio), TranslationManager looks up Autoradio. If it does not find this compound, it decomposes it and looks up its parts Auto and Radio.
A paragraph of text is divided into sentences during analysis to allow a sentence-by-sentence translation.
For translations from a given source language, you must install the corresponding language-support file.
For translations into a target language, the installation of the language-support file is optional unless you need to check the spelling of the target file.
The Language List window contains lists of all the language-support files available in TranslationManager and their current installation status.
Prerequisites
None.
Calling sequence
Select Display language list from the Utilities menu
The Language List window is displayed.
Options and parameters
None.
Results
The Language List window shows all available languages and their current status. The State column indicates whether the language-support file for the respective language is installed (indicated by active or inactive).
There are several reasons for a language being shown as inactive:
If you need a language-support file for any of the languages supported by TranslationManager , you can install it on top of your current installation.
If you translate into languages for which language support is not available, such as Hungarian, you cannot check the spelling of the translated documents.
Language-support files can be installed, extended, or deleted. For a list of supported source languages see "What you get from IBM".
You can delete a language-support file when you no longer need it. You may want to do this, for example, if you no longer translate from or into this language.
Prerequisites
None.
Calling sequence
Select:
Options and parameters
Before TranslationManager deletes the selected language-support file, you are asked to confirm your request:
Results
If you select Yes, the language-support file is deleted. Otherwise, it remains unchanged. A reference to this source language may still exist in certain folders, dictionaries, and Translation Memory databases. Update the respective properties so that the deleted language-support file is no longer referred to.
Occasionally, documents contain words with a spelling not recognized by TranslationManager although you consider them spelled correctly.
Such words can be added to an addendum of the respective language support and are then accepted by the spellchecking function. For more information, see "Spellchecking a document".
Select the language-support files for the languages you normally work in during the initial installation of TranslationManager . If you subsequently need to install additional language-support files, refer to "Installing more language-support files" for details of how to do so.
If you need to translate from a language that is not included in the list of currently supported languages, contact your local IBM representative and ask about the availability of new language-support files.
The list of target languages includes all languages for which language-support files exist, and certain other languages that are supported by OS/2 or Windows. If you want to translate into other languages, select Other Languages from the list of languages.
TranslationManager comes with sample translation material that you can use for practising. The samples are contained in folders to help you become familiar with the concepts of file organization and navigation in TranslationManager .
The installation of the sample folders is a selectable component in the installation procedure (Samples). You can use these folders in addition to the folders referred to in A Quick Tour and the Translator's Workbook.
The following table
lists the sample folders you can
select when installing TranslationManager.
| Folder | Format | Original | Translation |
|---|---|---|---|
| SAMPLAMI | Ami Pro | English(U.S.) | Spanish |
| SAMPLPRT | OS/2 resource file | English(U.S.) | German(national) |
| SAMPLRTF | RTF | English(U.S.) | Spanish |
| SAMPLWP | WordPerfect | English(U.S.) | Spanish |
| SAMPLW4W | Word 2.0 | English(U.S.) | German(national) |
| SAMPLE1 | BookMaster | English(U.S.) | German(national) |
| SAMPLE2 | OS/2 program file | English(U.S.) | German(national) |
| SAMPLE3 | BookMaster | English(U.S.) | Italian |
| SAMPLE4 | BookMaster | English(U.S.) | Spanish |
| SAMPLE5 | BookMaster | English(U.S.) | French(national) |
| SAMPLE6 | BookMaster | German(national) | English(U.S.) |
| SAMPLE7 | BookMaster | English(U.S.) | Japanese |
| SAMPLE8 | BookMaster | English(U.S.) | Russian |
| SAMPLE9 | BookMaster | English(U.S.) | Arabic |
| SAMPLE10 | BookMaster | English(U.S.) | Polish |
Each sample folder contains several documents, a dictionary, and a Translation Memory specially prepared for demonstration purposes. The SAMPLE1 folder, for example, contains:
The text of the sample documents is the same for all formats, except:
The document DEVICE.SCR is already analyzed, the document TRANS.DOC is not analyzed.
To install the sample folders, select the Samples option during installation. The installation procedure prepares the folders for subsequent import and use.
TranslationManager performs a morphological stem reduction so that you can look up terms in the original document and check the spelling in translated documents. To use these features with the material in a sample folder, you must first install the appropriate language-support files for the source and target languages. For example, to use folder SAMPLWP you must install the English(U.S.) language-support file because the original sample documents are in English. To check which language-support files have been installed, select Display language list from the Utilities menu of the TranslationManager workbench. State active tells you that a language has been installed.
To have TranslationManager check the spelling of a translated document, you must install the language-support file for the target language. For example, for SAMPLWP the Spanish language-support file must be installed.
To study the material in one of the sample folders, import it first. You can then open a document. The Translation Environment is displayed and you can start to translate the document. From the Dictionary window you can also look up terms in the supplied sample dictionary, and from the Translation Memory window you can copy entire sentences.
During translation, sentences you translate are added to the sample Translation Memory.
To return a sample folder to its initial status, delete the associated dictionary, Translation Memory, and folder. Then import the folder again, as described in "Installing a sample folder". Otherwise, if you only import the folder again, the contents of the initial and updated folders are merged.
To see samples of SGML-based files for data exchange, you can export a sample dictionary or a sample Translation Memory in external format.
The following describes a number of tasks related to working with the sample material. They contain short overviews of how to proceed and references to the detailed task descriptions to be found elsewhere in this book.
If you no longer need any of the sample material, for example, because you are translating other document types or because you are now sufficiently familiar with it, you can delete selected sample folders.
For details of how to delete parts of the samples, see:
To remove the sample folders from your disk entirely, see "Deleting an exported folder".
To import a sample folder and to start a translation exercise is described using the folder SAMPLE1 as an example.
Prerequisites
Calling sequence
Results
The folder SAMPLE1 is imported into TranslationManager . The analyzed document DEVICE.SCR is opened. You can start translating it.
Usually, the sample material is installed during the initial installation of TranslationManager . If you want to install the sample material later, refer to "Reinstalling TranslationManager".
Before documents can be translated, TranslationManager analyzes them to prepare them for translation. The DEVICE.SCR documents have already been analyzed. The TRANS.DOC documents are analyzed automatically when you open them, or you can explicitly select one of the analysis functions.
After importing and opening a document, you are taken to the
Translation Environment, where the following windows are displayed:
The document DEVICE.SCR contains one chapter of a complete book. Other document files of the book have been translated already, that is, a Translation Memory exists for them.
When you translate a sample document, remember that you can stop at any point in the session by:
To copy a proposal from the Translation Memory into the Translation window, press and hold down the Ctrl key and type the number of the required proposal.
To copy a proposal from the Dictionary window into the Translation window, press and hold down the Ctrl key and type the letter of the required proposal.
You can edit the translation document file in either insert or replace mode.
If the suggested translation contains special characters that are not available on your keyboard, ignore them or type other characters instead.