[ Back | Home ]
IBM TranslationManager
Translator's Reference
Part 4.
Technical information
Version 2.5 - 32bit
26 Feb 1998
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.
The following table shows which tasks can be selected for which menu items.
Note that for every list window you can open a list-specific
menu where you can select the same items as from the
TranslationManager menu bar.
You open this menu by pressing the right mouse button.
The menu shows only the selection of tasks that can be started
from the list window for which you opened the menu.
| Documents | Folders | Translation Memory databases | Dictionaries | Markup tables |
|---|---|---|---|---|
| Open | Open | Open | Open | - |
| - | New... | New... | New... | - |
| Properties... | Properties... | - | Properties... | - |
| Delete | Delete | Delete | Delete | Delete |
| - | - | Merge... | - | - |
| - | - | Organize | Organize | - |
| Analyze... | Analyze... | - | - | - |
| - | - | - | Print... | - |
| Export... | Export... | Export... | Export... | Export... |
| Import... | Import... | Import... | Import... | Import... |
| Global find and change... | Global find and change... | - | - | - |
| Select all | - | - | - | - |
| Deselect all | - | - | - | - |
| New terms lists | Found terms lists | Exclusion lists | Language list | |
|---|---|---|---|---|
| Open | Open | Open | Open | |
| - | - | New... | - | |
| Delete | Delete | Delete | Delete | |
| Print... | Print... | Print... | - | |
| Export... | Export... | Export... | - | |
| Import... | Import... | Import... | - | |
Using the TranslationManager windows is only one way of performing translation tasks with this product. An alternative way is to type instructions directly in the system's command area.
To start a task from the command area:
Note that lowercase letters in a parameter name are optional and need not be typed. A mixture between uppercase and lowercase letters is allowed. However, a muddled letter sequence like in OVerWRiTe must not be used. The parameters can be entered in any order whatever.
To process several commands in sequence, type the individual commands into a batch file (*.BAT or *.CMD) using any text editor. You can execute these commands by starting the batch file.
To avoid retyping of long text strings in commands, you can also type a command and its parameters in a text editor, which is capable of the Copy to clipboard function. You can then paste the text string from the clipboard directly into your system's command area and start the task.
In this chapter diagrams are used to illustrate the programming syntax. To use a diagram, follow a path from left to right, top to bottom, adding elements as you go. In these diagrams, all spaces and other characters are significant.
Each diagram begins with a double right arrowhead and ends with a right and left arrowhead pair. Lines beginning with single right arrowheads are continuation lines. keyword = variable_value
Keywords are all in lowercase, but can be entered in uppercase or in lowercase. Variable values that you provide are shown in italics and are usually in lowercase. Where values are shown in uppercase, they should be entered as they appear.
In a choice of items, the default item is always shown above the main line: keyword= default_value other_value other_value
Optional syntax elements are shown below the main line: keyword = value
A repeat arrow shown above an item or a stack of items indicates that you can specify the item multiple times or specify more than one of the items. A character (such as a comma) on the repeat arrow line indicates that the items must be separated by that character. A repeatable operand is shown like this: keyword = ( , variable_value )
Syntax diagrams can be broken into fragments. A fragment is indicated by vertical bars with the name of the fragment between the bars. The fragment is shown following the main diagram, like so: / KEYWORD = ITEM1 ITEM1 variable1 variable2 variable3
To analyze a document or a set of documents it might be more convenient to use a command instead of TranslationManager windows. It it particularly useful if you have many large documents or folders that you want to analyze overnight.
The following syntax diagram describes how you analyze documents from the Windows or OS/2 command line. Note that lowercase letters in a parameter name are optional and need not be typed.
Command syntax EQFCMD / TAsk = ANALYSIS / FLD = folder / FIles = document_name ( , document_name ) @ list_file_name / OPtions = option ( , option ) / MEm = memdb mandatory only when OPtions=ADDTOMEM ( , memdb ) / OVerwrite = NO YES / QUIET option ADDTOMEM AUTO AUTOLAST AUTOJOIN UNTRANSLATED
where:
ADDTOMEM
TranslationManager can search existing Translation Memory databases
for segments that match segments in the document being analyzed.
Segments that match exactly or almost exactly are copied into the
Translation Memory associated to the document or folder being analyzed.
In that way, you can start to fill a document-specific Translation Memory even before its translation has begun.
AUTO
You can choose to have Translation Manager automatically replace
sentences with matches that already exist in the Translation Memory.
This substitution is done only for exact matches.
The document is then already partially translated when you start
working with it, enabling you to focus on the translation of
new segments.
AUTOLAST
See the explanation for AUTO. However,
if more than one exact match has been found, the most recent translation
of the segment is to be taken.
AUTOJOIN
Joins neighboring segments.
This can be useful if you want to analyze a
document that you have
worked with before and where you joined neighbouring text segments
before you translated them.
During a new analysis run these segments are treated as
separate units again. However,
in the associated Translation Memory there is a match (translation)
for the joined segments only.
To find this match more easily during
automatic substitution, this option joins neighbouring segments
in the document to be analyzed.
Note that neighbouring segments are only joined if for
the first segment a fuzzy match has been found.
UNTRANSLATED
All untranslated segments are to be stored in a separate file.
Note: You can type the commands in uppercase, lowercase, or in mixed case letters. You may not use any wildcard characters, such as an asterisk (*).
The following example shows how to analyze a
document using the EQFCMD command.
| Example |
|---|
eqfcmd /task=analysis /fld=myfol /files=16.scr /options=(addtomem,auto,untranslated) /mem=oldmem |
If you need to create Initial Translation Memory (ITM) databases frequently, you might find it more convenient to use a command instead of the procedure described in "Creating an Initial Translation Memory".
The correctness of the aligned segment pairs in an internal ITM can be checked with a text editor as described in "The Initial Translation Memory editor"or "Revising an Initial Translation Memory from the command area".
When you consider the Initial Translation Memory to be correct, you can begin using it for your translations.
The EQFITM command has additional options compared to the window version:
The EQFITM command has the following format. Command syntax EQFITM / MEm = memdb mandatory, but not filled if /TYPE=NOTM / FIles = file_pairs @ list_file_name - mandatory except for /TYPE=NOANA / MArkup = markup / SGmlmem = mem_file / SRclng = source_language / TGtlng = target_language / TYpe = type ( , type ) file_pairs ( , file_name_original , file_name_translation ) type NOANA NOTM NOCONF PREPARE VISUAL
where:
The following examples show how to use the EQFITM command.
| Example: |
|---|
eqfitm /mem=wpitm /files=(d:\eng\text.doc,d:\ger\text.doc) /markup=eqfwp
/srclng=English(U.S.) /tgtlng=German(national)
|
Note: For better readability, the command is shown on two lines here. However, it must be typed in one line.
In this example, the original WordPerfect document text.doc is located in the directory d:\eng\. The German translation is located in the directory d:\ger\. eqfwp is the name of the TranslationManager markup table used for this document. All matching sentence pairs are put into Translation Memory wpitm. No external Translation Memory (SGML format) is created.
| Example: |
|---|
eqfitm /mem=myitm /files=@itm.lst /markup=eqfami /sgmlmem=xx.out /type=notm
/srclng=English(U.S.) /tgtlng=German(national)
|
Note: For better readability, the command is shown on two lines here. However, it must be typed in one line.
In this example, a Translation Memory myitm is used to find out the source language. The files to be analyzed are contained in itm.lst. itm.lst looks as follows:
| itm.lst |
|---|
|
(
|
The ITM created is placed into an SGML Translation Memory named xx.out, not into myitm (because type notm is specified). The markup table to be used is eqfami because the documents were originally created with Ami Pro.
You must type the command in one line. You can type it in uppercase letters, lowercase letters, or mixed case. You cannot use any wildcard characters, such as asterisks (*).
Note: It is recommended to proofread the external ITM before using it in TranslationManager . Because it has not been created during translation, but consists of machine-generated matches, the alignment of original and translated segments might not be completely correct. This could be the case where two original segments have been combined into one translated segment.
If you have many large documents that you want to export, using the command area of your operating system instead of TranslationManager windows might be more convenient.
Before exporting, ensure that:
The properties of the folder or of the documents give information on the used markup table and other document-related information that is necessary when exporting the respective documents.
To work from the command area, use the EQFCMD command. Its syntax is described in the following chapter.
The following syntax diagrams describe how you export a document from the Windows or OS/2 command area. Note that lowercase letters in a parameter name are optional and need not be typed.
Command syntax EQFCMD / TAsk = DOCEXP / FLD = folder / FIles = file_name ( , file_name ) @ list_file_name / OPtions = TARGET SOURCE / OVerwrite = NO YES / QUIET
where:
Note: You can type the commands in uppercase, lowercase, or in mixed case letters. You may not use any wildcard characters, such as an asterisk (*).
The following example shows how to export a
document using the EQFCMD command with the TASK option.
| Example |
|---|
eqfcmd /task=docexp /fld=pharma /files=c:\med.txt /options=target /overwrite=yes |
If you have many large documents that you want to import, using the command area of your operating system instead of TranslationManager windows might be more convenient.
Before importing, ensure that:
The properties of the folder give information on the used markup language and other document-related information that is necessary when importing the respective documents.
To work from the command area, use the EQFCMD command Its syntax is described in the following chapter.
The following syntax diagram describes how to import from the command area of your operating system. Note that lowercase letters in a parameter name are optional and need not be typed. Command syntax EQFCMD / TAsk = DOCIMP / FLD = folder / FIles = file_name ( , file_name ) @ list_file_name / OVerwrite = NO YES / QUIET
where:
Note: You can type the commands in uppercase, lowercase, or in mixed case letters. You may not use any wildcard characters, such as an asterisk (*).
The following example shows how to import several documents using the EQFCMD command.
| Example |
|---|
eqfcmd /task=docimp /fld=pharma /files=@medlist.lst /overwrite=no |
In this example, the documents to be imported are listed in
file medlist.lst.
medlist.lst looks as follows:
| medlist.lst |
|---|
(d:\medset.doc, d:\medfrm.doc, d:\medb01.doc, d:\medb02.doc) |
The file medlist.lst must be located either on the current directory, or (if it is not in the current directory) you must specify the complete path where it is located. For example, @d:\test\medlist.lst.
Note: There is a @ sign before the drive letter.
All files contained in medlist.lst are to be imported into folder pharma and are located in the root directory of drive D. If one of the files already exists in the specified folder, it is not overwritten and you get a message.
If you need to set up new folders frequently, using the command area of your operating system instead of TranslationManager windows might be more convenient.
To work from the command area, use the EQFCMD command. Its syntax is described in the following chapter.
The following syntax diagram describes how you create a folder from the Windows or OS/2 command area. Note that lowercase letters in a parameter name are optional and need not be typed.
Command syntax EQFCMD / TAsk = FLDCRT / NAme = folder / DEsc = desc / TOdrive = drive / MEm = memdb / MArkup = markuptable / EDit = editor / DIct = dict ( , dict ) / SRclng = source / TGtlng = target / QUIET
where:
Note: You can type the commands in uppercase, lowercase, or in mixed case letters. You may not use any wildcard characters, such as an asterisk (*).
The following example shows how to create a
folder using the EQFCMD command.
| Example |
|---|
eqfcmd /task=fldcrt /name=proj1 /desc="new folder" /todrive=e /mem=ibmmem /markup=eqfbook /edit=standard /dict=(ibmterm,ibm2) /srclng=German(national) /tgtlng=English(U.S.) |
If you need to set up new folders frequently, using the command area of your operating system instead of TranslationManager windows might be more convenient.
To work from the command area, use the EQFCMD command. Its syntax is described in the following chapter.
The following syntax diagram describes how you export a folder from the Windows or OS/2 command area. Note that lowercase letters in a parameter name are optional and need not be typed.
Command syntax EQFCMD / TAsk = FLDEXP / FLD = folder / FIles = document_name ( , document_name ) @ list_file_name / TOdrive = drive / OPtions = option ( , option ) / OVerwrite = YES NO / DEsc = desc @ desc_file_name / QUIET option DICT MEM DELETE
where:
Note: You can type the commands in uppercase, lowercase, or in mixed case letters. You may not use any wildcard characters, such as an asterisk (*).
The following example shows how to export a
folder using the EQFCMD command.
| Example |
|---|
eqfcmd /task=fldexp /fld=pharma /files=(161.scr,1500.scr) /todrive=e /options=(dict,mem) /desc="This is information on the folder" |
It might be more convenient to use a command instead of TranslationManager windows to import a folder. This is especially useful if you have many folders that you want to import.
The following syntax diagram describes how you import a folder from the Windows or OS/2 command line. Note that lowercase letters in a parameter name are optional and need not be typed.
Command syntax EQFCMD / TAsk = FLDIMP / FLD = folder / FRomdrive = drive / OPtions = option ( , option ) / TOdrive = drive / QUIET option DICT MEM
where:
Note: You can type the commands in uppercase, lowercase, or in mixed case letters. You may not use any wildcard characters, such as an asterisk (*).
The following example shows how to import a
folder using the EQFCMD command.
| Example |
|---|
eqfcmd /task=fldimp /fld=pharma /fromdrive=a /todrive=e /options=(dict,mem) |
To set up a new Translation Memory, it might be more convenient to use a command instead of using TranslationManager windows.
The following syntax diagram describes how you create a Translation Memory from the Windows or OS/2 command line. Note that lowercase letters in a parameter name are optional and need not be typed.
Command syntax EQFCMD / TAsk = MEMCRT / NAme = memdb / DEsc = desc / TYpe = SHARED LOCAL / TOdrive = drive / SRclng = source / QUIET
where:
Note: You can type the commands in uppercase, lowercase, or in mixed case letters. You may not use any wildcard characters, such as an asterisk (*).
The following example shows how to create a
Translation Memory using the EQFCMD command.
| Example |
|---|
eqfcmd /task=memcrt /name=medmem /desc="new memory" /type=local /todrive=e /srclng=English(U.S.) |
If you want to delete a Translation Memory, using a command typed in your system's command area instead of TranslationManager windows might be quicker and more convenient.
The following syntax diagram describes how you delete a Translation Memory with the EQFCMD command. Note that lowercase letters in a parameter name are optional and need not be typed.
Command syntax EQFCMD / TAsk = MEMDEL / MEm = memdb / QUIET
where:
Note: You can type the commands in uppercase, lowercase, or in mixed case letters. You may not use any wildcard characters, such as an asterisk (*).
The following example shows how to delete a
Translation Memory using the EQFCMD command.
| Example |
|---|
eqfcmd /task=memdel /mem=medmem |
If you want to export a Translation Memory, using a command typed in your system's command area instead of TranslationManager windows might be more convenient.
The following syntax diagram describes how you export a Translation Memory from the Windows or OS/2 command line. Note that lowercase letters in a parameter name are optional and need not be typed.
Command syntax EQFCMD / TAsk = MEMEXP / OUT = mem_file / TYpe = EXTERNAL / MEm = memdb / OVerwrite = NO YES / QUIET
where:
Note: You can type the commands in uppercase, lowercase, or in mixed case letters. You may not use any wildcard characters, such as an asterisk (*).
The following example shows how to export a
Translation Memory using the EQFCMD command.
| Example |
|---|
eqfcmd /task=memexp /out=d:\mymemo.exp /type=external /mem=oldmemo |
To import a Translation Memory, you might find it more convenient to use a command instead of TranslationManager windows. You might want to do this if you have many Translation Memory databases that you want to import.
The following syntax diagram describes how you import a Translation Memory from the command area. Note that lowercase letters in a parameter name are optional and need not be typed.
Command syntax EQFCMD / TAsk = MEMIMP / FIles = mem_file / TYpe = EXTERNAL / MEm = memdb / QUIET
where:
Note: You can type the commands in uppercase, lowercase, or in mixed case letters. You may not use any wildcard characters, such as an asterisk (*).
The following example shows how to import a
Translation Memory using the EQFCMD command.
| Example |
|---|
eqfcmd /task=memimp /files=d:\mymemo.mem /type=external /mem=oldmemo |
If you want to import a dictionary, using a command typed in your system's command area instead of TranslationManager windows might be more convenient.
The following syntax diagram describes how you import a dictionary from the Windows or OS/2 command area. Note that lowercase letters in a parameter name are optional and need not be typed.
Command syntax EQFCMD / TAsk = DICIMP / FIles = dict_file / DIct = dict_name / OPtions = COMBINE REPLACE IGNORE / PAssword = password / QUIET
where:
Note: You can type the commands in uppercase, lowercase, or in mixed case letters. You may not use any wildcard characters, such as an asterisk (*).
The following example shows how to import a
dictionary using the EQFCMD command.
| Example |
|---|
eqfcmd /task=dicimp /files=d:\mymemo.sgm /options=replace /dict=newmemo |
TranslationManager provides a command to reverse a Translation Memory. The reversed Translation Memory is saved in a new Translation Memory file. This means that the source language of the Translation Memory you want to reverse is turned into the target language. The target language of the reversed Translation Memory is now becoming the source language. This can be useful when you are working in a company which does translations from any to any languages. Or, when a document was initially written in English, translated into German, revised in German for a second release, and now must be translated back into English.
The following syntax diagram describes how you reverse a Translation Memory from your system's command area. Note that lowercase letters in a parameter name are optional and need not be typed.
Command syntax EQFREVM / MEm = memdb / REv = revdb / TYPE = NOCONF
where:
Note: You can type the commands in uppercase, lowercase, or in mixed case letters. You may not use any wildcard characters, such as an asterisk (*).
The following example shows how to reverse a
Translation Memory using the EQFREVM command.
| Example |
|---|
eqfrevm /mem=archive /rev=std1 |
Segments that have been translated by machine are prefixed with an [m]. TranslationManager provides a command to have these m-prefixes removed from machine-translated segments in a Translation Memory. Alternatively, this command lets you add m-flags to segments that did not have such a flag before.
The following syntax diagram describes how you change the m-flags in a Translation Memory with the EQFCMM command. Note that lowercase letters in a parameter name are optional and need not be typed.
Command syntax EQFCMM / MEm = memdb / SEt = NO YES / CLear = NO YES / TYpe = NOCONF
where:
Note: You can type the commands in uppercase, lowercase, or in mixed case letters. You may not use any wildcard characters, such as an asterisk (*).
The following example shows how to change an m-flag in a
Translation Memory using the EQFCMM command.
| Example |
|---|
eqfcmm /mem=biotext /clear=yes /type=noconf |
Instead of using TranslationManager windows to open a document, you might find it more convenient to use a command.
The following syntax diagram describes how you open a document from the Windows or OS/2 command line. Note that lowercase letters in a parameter name are optional and need not be typed.
Command syntax EQFCMD / TAsk = DOCOPEN / FLD = folder / NAme = document_name / QUIET
where:
Note: You can type the commands in uppercase, lowercase, or in mixed case letters. You may not use any wildcard characters, such as an asterisk (*).
The following example shows how to open
a document using the EQFCMD command.
| Example |
|---|
eqfcmd /task=docopen /fld=sample1 /name=device.scr |
This command opens the document DEVICE.SCR which is stored in folder SAMPLE1.
Translators are usually paid for translated words or lines. To prepare the payment it is necessary to count the words that have been translated for a specific project. Also, to plan for a translation project it is necessary to know how many words will have to be translated.
Instead of using TranslationManager windows to count words in a document, using a command might be more convenient.
The following syntax diagram describes how you start to count words from the Windows or OS/2 command area. Note that lowercase letters in a parameter name are optional and need not be typed.
Command syntax EQFCMD / TAsk = WORDCNT / FLD = folder / FIles = document_name ( , document_name ) @ list_file_name / OUT = cnt_name / OVerwrite = NO YES / OPtions = SOURCE TARGET / QUIET
where:
Note: You can type the commands in uppercase, lowercase, or in mixed case letters. You may not use any wildcard characters, such as an asterisk (*).
The following example shows how to count
words using the EQFCMD command.
| Example |
|---|
eqfcmd /task=wordcnt /fld=newfld /files=161.scr /options=target /out=e:\161.cnt |
All words in the translated document 161.scr, which is contained in folder newfld, are counted and the result is stored in the file 161.cnt on drive E.
Command syntax with /TASKLIST option EQFCMD / TASKLIST = list_of_tasks / QUIET
where:
Note: You can type the commands in uppercase, lowercase, or in mixed case letters. You may not use any wildcard characters, such as an asterisk (*).
The following example shows how to specify the export parameters
in a separate file (taskexp.fil)
to export several documents
(med1.txt and med2.txt)
and then call the EQFCMD command with a reference to this file.
| taskexp.fil |
|---|
:\med1.txt /options=target /overwrite=yes /task=docexp /fld=pharma /files=c:\med2.txt /options=target /overwrite=yes |
Enter the EQFCMD command as follows:
| Example |
|---|
eqfcmd /tasklist=taskexp.fil |
This lets you export more than one document with one command. All EQFCMD tasks can be combined.
The next example shows how to specify the import parameters
in a separate file (taskimp.fil)
to import several documents listed in two files
(@meddoca.lst and @meddocb.lst)
and then call the EQFCMD command with a reference to this file.
| taskimp.fil |
|---|
lst /overwrite=no /task=docimp /fld=pharma /files=@meddocb.lst /overwrite=no |
Enter the EQFCMD command as follows:
| Example |
|---|
eqfcmd /tasklist=taskimp.fil |
This lets you import more than one document with one command. All EQFCMD tasks can be combined.
To assign a function to a key or a key combination click on Keys... in the Options menu, select the function and assign it to a key.
To call an editor function
that is assigned to a key combination,
click on Commands...
in the Options menu,
select the command to be executed,
and click on Run.
On the following pages, you find the complete list of the functions available in the Translation Environment. They are grouped as follows:
| Function | Menu | Default key |
|---|---|---|
| Bottom | Cursor | Ctrl+End |
| Top | Cursor | Ctrl+Home |
| Cursor down |
| Down |
| Cursor up |
| Up |
| Cursor left |
| Left |
| Cursor right |
| Right |
| Start of line | Cursor | Home |
| End of line | Cursor | End |
| Start of segment | Cursor | Alt+Home |
| End of segment | Cursor | Alt+End |
| Query (active) line | Cursor |
|
| Go to line dialog | Cursor |
|
| Next line |
| Enter |
| Next word |
| Ctrl+Right |
| Previous word |
| Ctrl+Left |
| Tab backward |
| Backtab |
| Tab forward |
| Tab |
| Go to active segment | Translate |
|
| Go to changed segment |
|
|
| Go to newly translated segment |
|
|
| Go to unchanged segment |
|
|
| Go to bookmark | Translate |
|
| Function | Menu | Default key |
|---|---|---|
| Scroll down |
| Shift+F4 |
| Scroll up |
| Shift+F3 |
| Scroll page down |
| PageDown |
| Scroll page up |
| PageUp |
| Scroll left |
| Shift+F5 |
| Scroll right |
| Shift+F2 |
| Function | Menu | Default key |
|---|---|---|
| Delete character or marked block |
| Delete |
| Delete character and move cursor left |
| Backspace |
| Delete until tag |
|
|
| Delete line |
|
|
| Insert line |
|
|
| Join line(s) | Edit |
|
| Split line | Edit |
|
| Truncate line |
| Ctrl+Delete |
| Delete word |
|
|
| Mark word |
|
|
| Compress current segment |
|
|
| Expand current segment |
|
|
| Truncate segment |
| Alt+Delete |
| Delete segment |
|
|
| Join segments | Translate |
|
| Split joined segments | Translate |
|
| Mark segment |
|
|
| Next untranslated segment | Translate |
|
| Reflow segment | Edit |
|
| Spellcheck segment | Spellcheck |
|
| Translate segment | Translate | Ctrl+Enter |
| Untranslate segment | Translate |
|
| Copy block |
|
|
| Delete block (Clear) | Edit |
|
| Find block | Cursor |
|
| Mark block |
|
|
| Move block |
|
|
| Unmark block | Edit |
|
| Find (and change... ) | Edit |
|
| Undo | Edit | Alt+Backspace |
| Set bookmark | Translate |
|
| Clear bookmark | Translate |
|
| Function | Menu | Default key |
|---|---|---|
| Line wrap (toggle) | Edit |
|
| Insert toggle |
| Insert |
| Add an abbreviation | Translate |
|
| Edit abbreviations | Translate |
|
| Postediting | Translate |
|
| Automatic substitution | Translate |
|
| Spellcheck file | Spellcheck |
|
| Spellcheck segment | Spellcheck |
|
| Edit addendum terms | Spellcheck |
|
| Function | Menu | Default key |
|---|---|---|
| Compact (document) | Style |
|
| Hide tags | Style |
|
| Protect tags | Style |
|
| Shrink tags (in segment) | Style |
|
| Unprotect tags | Style |
|
| Function | Menu | Default key |
|---|---|---|
| File (End_Save) | File | F4 |
| Open | File |
|
| Quit | File | F3 |
| Print (document) | File |
|
| Save | File | F2 |
| Next (document in the ring) | File |
|
| Previous document |
|
|
| Function | Menu | Default key |
|---|---|---|
| Set Colors window | Options |
|
| Set Fonts window | Options |
|
| Run Command window | Options |
|
| Assign Keys window | Options |
|
| Set Margin window | Options |
|
| Set Initial Values window | Options |
|
| Customize Translation Functions window | Options |
|
| Sentence Lookup window | Options |
|
| Function | Menu | Default key |
|---|---|---|
| Copy (to clipboard) | Edit | Ctrl+Insert |
| Cut (to clipboard) | Edit | Shift+Delete |
| Paste (from clipboard) | Edit | Shift+Insert |
| Function | Menu | Default key |
|---|---|---|
| Dictionary window | File |
|
| Original window | File |
|
| Source of proposal window | File |
|
| Translation Memory window | File | F8 |
| Translation window | File |
|
| Look up a term | Translate |
|
| Edit a term | Translate |
|
| Function | Menu | Default key |
|---|---|---|
| Scroll proposal down |
| Ctrl+Down |
| Scroll proposal up |
| Ctrl+Up |
| Display (also) fuzzy matches |
|
|
| Function | Menu | Default key |
|---|---|---|
| Scroll dictionary down |
| Alt+Down |
| Scroll dictionary up |
| Alt+Up |
To print dictionary data, you must first define the layout of your print output in format files that you edit with a text editor. In the format print file you define the entry fields to be printed and how to arrange them in the printout. For general information on printing, see "Printing a dictionary".
TranslationManager provides several sample format files. The following contains an introduction to format file statements.
The print program assumes a page size with a default of 72 lines per page. To modify this layout you can insert printer-specific characters in the format files according to the syntax provided.
This format file prints each headword and its translation. It uses the following format statements to achieve this:
| Part of FORMAT1.FRM |
|---|
<entryprt> ======================= <var name=Headword> <var name=Translation> </entryprt> |
Between <entryprt> and </entryprt> you specify which entry fields you want to be printed for each entry. The names following var name= must be the same names that are defined as entry field names in the dictionary you want to print. To see which entry field names are in a dictionary, select Properties... from the File menu when the Dictionary List window is active and the respective dictionary selected.
<var name=Translation> means that the translation for the headword is printed. If there is more than one translation, only the first translation is printed.
Nontagged information that you type between the <entryprt> and </entryprt> tags is printed for each iteration. In the example above, the ========== is used as a separator line between the entries on your printout.
The following is an example of what your dictionary printout
would look like.
Assume that the dictionary is English-German
and the sample format FORMAT1.FRM has been used for formatting.
Two entries (rule and run) are extracted.
| Sample printout |
|---|
======================= rule regieren ======================= run laufen |
FORMAT2.FRM looks as follows:
| Part of FORMAT2.FRM |
|---|
<entryprt> ======================= <var name =Headword> <repeat name=Headword> <var name='Part of Speech'> <var name=Translation> <var name=Abbrev./Fullform> </repeat> </entryprt> |
<var name=Headword> means that the headword is printed. <repeat...> means that the Part of Speech, the Translation, and the Abbrev./Fullform entry fields are printed until a different headword is found. If the fields for Part of Speech, Translation, or Abbrev./Fullform in the dictionary are not filled, an empty line is printed.
The following sample shows how your dictionary printout
would look.
Assume that the dictionary is English-German
and the sample format FORMAT2.FRM has been used for formatting.
Two entries (rule and run) are extracted.
| Sample printout |
|---|
|
======================= rule verb regieren rule noun Regel ======================= run verb laufen run noun Lauf |
This format file prints all templates for each entry.
It is designed to be formatted with BookMaster outside TranslationManager before you print it. If you print the file without BookMaster, you see a mixture of dictionary entry data and BookMaster tags. Formatting with BookMaster produces a printout resembling entries in printed dictionaries.
The tags used in this format file are described in "Tags for defining the format of a dictionary printout". You must use them in the same sequence as listed there.
This format file prints a dictionary extract with the following structure:
FORMAT4.FRM contains comments on most of the tags used. It is recommended that you read these comments to understand the results the tags produced on the printout.
If you want to see the results of such a printout, print dictionary DICTPRT, which is contained in sample folder SAMPLPRT.
Note: You must first import SAMPLPRT into TranslationManager .
To print a dictionary or an extract from it, you can use one of the format files provided by TranslationManager . You find them on the drive where you installed TranslationManager in the subdirectory \EQF\PRTFORM.
These format files provide a predefined layout for printing dictionary information. They serve as sample files. You must replace all the generic information they contain with your personal data, such as your address, and your name. It is useful to select a format file that contains entry fields that match those of the dictionary you want to print.
To get an idea of how the printout will turn out when using one of these format files, read the explanation that is given after the <comment> tag in each file. However, if you want to print a dictionary with a layout other than those provided, you can define your own format file. You do this as follows:
The selected dictionary is printed at the printer that is defined as LPT1 in your operating system (default setting).
The following is an example of an individual format file and how it looks on the printout.
<comment>
This is my private format file.
It prints entries from dictionary MYDICT in the following way.
The front page gives administrative information about the
printout, such as title, date, and my name.
Then two entries of MYDICT follow.
These entries contain the fields I specified:
Part of Speech, Translation, Synonym, and Context.
Each page has the dictionary name MYDICT in its header section.
The page number is printed at the bottom of each page.
</comment>
<set sysname=$page_length value='61'>
<set sysname=$page_eject value=' '>
<dictfront>
Title: Dictionary <var sysname=$Dictname>
Date: <var sysname=$Date format=dd.mm.yyyy>
Author: Betty Miller
</dictfront>
<pagehead>
<var sysname=$Dictname $Min=45 $Right>
<var name=headword $first_on_page>
=================================================================
</pagehead>
<entryprt>
The term "<var name=Headword>" has the following meaning:
<repeat name=Headword>
Part of Speech: <var name='Part of Speech'>
<repeat name='Part of Speech'>
Translation: <var name=Translation>
Synonym: <var name=Synonym>
Context: <var name=Context>
</repeat>
</repeat>
</entryprt>
<pagefoot>
=================================================================
- <var sysname=$Page_No> -
</pagefoot>
If you used this format file when printing dictionary MYDICT, you would get a printout with the following information on its title page:
Title: Dictionary MYDICT Date: 04/01/94 Author: Betty Miller
After the title page, the entries found are printed in the following way:
MYDICT
assist
=================================================================
The term "assist" has the following meaning:
Part of Speech: verb
Translation: helfen
Synonym:
Context:
Translation: assistieren
Synonym:
Context: to assist sb
The term "access" has the following meaning/s:
Part of Speech: noun
Translation: Zugriff
Synonym:
Context:
Translation: Zutritt
Synonym:
Context:
Part of Speech: verb
Translation: zugreifen
Synonym:
Context:
=================================================================
- 1 -
Each data element to be printed is defined between a start and an end tag (except for <set> and <var>). The end tag always starts with "</". If you use any multiterm words as entry-field names, for example, Part of Speech, you must enclose them in single quotes (for example: <var name='Part of Speech'>). You may type these tags in either uppercase or in lowercase letters. Some of the tags have attributes (<set...>, <repeat...>, <var...>).
You can control the layout of your printout by placing the variables at the appropriate position. The printing of a text or a data element starts where the opening pointed bracket (<) has been placed.
| Start tag, end tag | Meaning |
|---|---|
<description>, </description> | Here you can describe what your printout contains. These tags are optional and have no effect on the layout of your printout. This description is shown in the Print Dictionary window. |
<dictfront>, </dictfront> | Contains administrative information related to the printed dictionary, such as the name of the dictionary and the date of printing. This information is printed once at the beginning of your printout before any entries are printed. These tags are optional. |
<pagehead>, </pagehead> | Here you can specify the information that you want to be printed on the top of each printed page. These tags are optional. |
<entryprt>, </entryprt> | Here specify the structure and contents of the entries you want to be printed. These tags are mandatory. |
<pagefoot>, </pagefoot> | Here you can specify the information that you want to be printed at the bottom of each printed page. These tags are optional. |
<dictback>, </dictback> | Contains information related to the printed dictionary. This information is printed at the end of your printout after all entries have been printed. These tags are optional. |
Within the format files the tags must follow the same sequence as specified here. To modify the layout of your printout, you can use the following additional tags:
| Start tag, end tag | Meaning |
|---|---|
<comment>, </comment> | Here you can specify information that you do not want to appear on your printout. These tags are optional. They can occur anywhere within a format file, but not between another start and end tag. |
<set...> | This tag lets you specify the length of a line and the length of a page of your printout. It can occur anywhere within a format file, but not between another start and end tag. For more information, see "The <set...> attributes". |
<repeat...>, </repeat> | The information specified here is repeated until all information belonging to the specified entry field is printed. These tags are optional and can only occur between <entryprt> and </entryprt>. For more information, see "The <repeat...> attributes". |
<var...> | This tag can have the attribute "name=".
It can occur only between the <pagehead>,
<pagefoot>, and <entryprt> tags and their end-tags.
If it has the attribute "sysname=$..." it can occur only between the <dictfront>, <pagehead>, <entryprt>, <pagefoot>, and <dictback> tags and their corresponding end tags. For more information, see "The <var...> attributes". |
If both $max and $min are specified, the value for $min must be lower or equal to the value of $max.
You can create your own markup table by exporting an existing markup table in external SGML format, modifying it with any text editor, and importing it back into TranslationManager under a different name.
Notice that an exported markup table contains only the nondefault entries.
If you want to create a completely new markup table, you must follow the SGML syntax. For a complete description of SGML refer to ISO 8879, Information Processing - Text and Office Systems - Standard Generalized Markup Language (SGML).
A markup table must begin with <TAGTABLE> and end with </TAGTABLE>.
When you have exported one of the provided markup tables of TranslationManager you may see as second tag in the second line <SEGMENTEXIT>text</SEGMENTEXIT>. This tag calls a TranslationManager function to give the analysis and export functions more information on the supported word-processing system. If you want to modify this markup table to create a new one for your special word processing system you must delete this entry.
The description of a markup tag always starts with the start tag <TAG> and ends with the corresponding end tag </TAG>. To specify additional characteristics of a markup element you can use attributes. For example, a markup tag for lists can have additional information on the type of this list, like numbered or compact.
This additional information can be stored as an attribute. In a markup table the description of an attribute starts with the start tag <ATTRIBUTE> and ends with the corresponding end tag </ATTRIBUTE>.
Markup tables must have the following layout:
<TAGTABLE> <TAG> insert your tag definition here, depending on the following markup table SGML tags, you may insert up to 1000 entries </TAG> <ATTRIBUTE> attributes are optional </ATTRIBUTE> </TAGTABLE>All SGML tags must be enclosed in "<" and ">". There is always a start tag and an end tag.
If a markup tag contains variable parts, you can substitute them by a question mark ("?") for single substitution or by a percentage sign ("%") for multiple substitution.
The following table contains the definition of the SGML tags that you can use to create or change a markup table.
| SGML tag | Definition |
|---|---|
| STRING | Specifies the name of the markup tag or of an attribute.
The specification of STRING is required for an entry in the markup table. |
| ENDDELIM | Specifies one character as end delimiter of the markup tag, if it
has any.
You can enter more than one end delimiter.
TranslationManager checks for all possible string combinations
to determine the end of the tag.
A string as end delimiter is not possible.
When a markup tag has an end delimiter, the specification of its length is omitted or can be set to 0. If a markup tag has no end delimiter , its length must be specified. The specification of ENDDELIM is required for an entry in the markup table, if LENGTH is not defined. |
| TYPE | Defines the type of the markup tag.
If TYPE is not specified, STDEL is taken
as the default.
The following types are possible:
|
| SEGINFO | Determines whether the text following the markup tag is to be segmented.
If SEGINFO is not specified, SEGNEUTRAL is taken as the default.
|
| ASSTEXT | Defines types of text following the markup tag.
If ASSTEXT is not specified, NOEXPL is taken as the default.
|
| ATTRINFO | Specifies if a markup tag has attached attributes (YES/NO). NO is the default. If YES is specified, the ATTRIBUTE SGML tag must be used to specify the attributes. |
| LENGTH | Defines the length of a markup tag. It must be specified only if the length of the tag cannot be determined by a delimiter specified by ENDDELIM. |
| COLPOSITION | Specifies the column position where the markup tag starts. If a markup tag has no special start position and can occur anywhere in a line, COLPOSITION is omitted or can be set to 0. The default is 0. |
| TRANSLATEINFO | Specifies whether the segment associated with the markup tag must be translated or not (YES/NO). If TRANSLATEINFO is not specified, NO is taken as the default. |
The minimum requirements for the specification of an SGML markup tag or attribute are STRING and ENDDELIM, or STRING and LENGTH.
After editing the SGML file, you can import it into TranslationManager . If you import it into an existing markup table, this table is overwritten.
The markup data [soft line feed] is in most cases defined as a so-called inline tag. This means it is contained in the segment:
<TAG> <STRING>[soft line feed]</STRING> <LENGTH>16</LENGTH> <TYPE>STNEUTRAL</TYPE> <SEGINFO>SEGNEUTRAL</SEGINFO> </TAG>The markup table tag ENDDELIM is omitted because the length is defined. All other markup table SGML tags will be set to the default and therefore need not be specified. To indicate this with this markup tag a new segment starts you change the TYPE:
<TAG> <STRING>[soft line feed]</STRING> <LENGTH>16</LENGTH> <TYPE>STDEL</TYPE> <SEGINFO>SEGNEUTRAL</SEGINFO> </TAG>
The following table lists some imaginary markup data with
a description.
| Markup data | Definition | ||
|---|---|---|---|
| [bold]text[/bold] | The text following this tag (until the end tag) is printed bold; this tag is part of the segment and has no influence on segmenting. | ||
| [Heading x]text | This tag describes a heading; the heading text must follow on the same line; x is the level of heading and goes from 1 to 9; this tag ends the previous segment and starts a new segment. | ||
| [page: even] | A page break; the following text starts on an even page; this tag always starts on the first column and has no text following in the same line; a blank must separate the attribute even from the tag. | [page: odd] | A page break; the following text starts on an odd page; this tag always starts on the first column and has no text following in the same line; a blank must separate the attribute odd from the tag. |
| [paragraph] | A paragraph; this tag ends the previous segment and starts a new segment; the tag occurs at the end of the previous paragraph. |
This markup data would lead to the following markup table definitions.
The defaults will not be shown.
| Markup definition | Explanation |
|---|---|
<TAG> <STRING>[bold]</STRING> <LENGTH>6</LENGTH> <TYPE>STNEUTRAL</TYPE> </TAG>or <TAG> <STRING>[bold</STRING> <ENDDELIM>]</ENDDELIM> <TYPE>STNEUTRAL</TYPE> </TAG> | The markup tag should be part of the segment, therefore STNEUTRAL is used; both examples have the same result, you can specify this markup tag by its length or end delimiter. |
<TAG> <STRING>[Heading ?</STRING> <ENDDELIM>]</ENDDELIM> <SEGINFO>SEGRESET</SEGINFO> <ASSTEXT>TSL</ASSTEXT> <TRANSLATEINFO>YES</TRANSLATEINFO> </TAG> | Single substitution is used for the heading level; the end of the tag is ]; the heading requires the reset of segmenting with SEGRESET; the text associated with the tag occurs on the same line; the text associated with the tag is translatable. |
<TAG> <STRING>[page:</STRING> <ENDDELIM> </ENDDELIM> <ATTRINFO>YES</ATTRINFO> <COLPOSITION>1</COLPOSITION> </TAG> | The markup tag ends with a blank; attributes may follow; the tag always starts at the first column in a line. |
<TAG> <STRING>[paragraph</STRING> <ENDDELIM>]</ENDDELIM> <TYPE>ENDDEL</TYPE> </TAG>or <TAG> <STRING>[paragraph]</STRING> <LENGTH>11</LENGTH> <TYPE>ENDDEL</TYPE> </TAG> | The tag ends with ] or is defined by its length; the tag should end the previous segment, therefore ENDDEL is used. |
<ATTRIBUTE> <STRING>even</STRING> <ENDDELIM>]</ENDDELIM> </ATTRIBUTE> | This is an attribute; it ends with ]. |
<ATTRIBUTE> <STRING>odd</STRING> <ENDDELIM>]</ENDDELIM> </ATTRIBUTE> | This is an attribute; it ends with ]. |
The following table contains all markup tags that are used for Microsoft Word for Windows. The first column gives the tag name, the second column indicates whether the tag has an end tag or not, and the third column gives a brief description of the tag.
It may be necessary to insert highlighting tags like bold, italic, or underline if the sentence changes its structure in the target language. If you insert a highlighting tag, the corresponding end tag must be inserted, too. The first table lists the tags that reflect such highlighting that may be changed.
Most of the used markup tags for Microsoft Word for Windows have a start tag and an end tag. The end tag has the same name as the start tag, with a slash in front of the tag name. When the end tag is different from the start tag it is given in addition to the start tag.
The following table lists markup data that may be deleted, inserted, or moved depending on the structure in the target language. These tags are parts of a segment that is to be translated.
| Tag name | End tag | Description |
|---|---|---|
| [-] | no | Required hyphen. |
| [blank] | no | Required blank. |
| [bold] | yes | The text is printed in bold. |
| [caps] | yes | The text is printed as capital letters. |
| [color: code](2)
[/color] | yes | The text is printed colored; the code is the color used. |
| [condensed: space](2)
[/condensed] | yes | The text is printed in condensed form, the respective space between the characters is coded with space. |
| [extended: space](2)
[expanded: space](3) [/extended] [/expanded](3) | yes | The text is printed in expanded form, the respective space between the characters is coded with space. |
| [font: name](2)
[/font] | yes | The text is printed in a special font; the font name is given with name. |
| [fontsize: size](2)
[/fontsize] | yes | The text is printed in a special size; the fontsize is coded with size. |
| [italic] | yes | The text is printed in italic. |
| [lid: lid code](2)
[/lid] | yes | The text has a specific language reference; refer to your Microsoft Word for Windows documentation for the meaning. |
| [line break] | no | Soft line feed. |
| [page] | no | Start of a new page. |
| [rev mark] | yes | The text is revised. |
| [rev strike] | yes | The text is revised by strikethrough. |
| [small caps] | yes | The text is printed as small capital letters. |
| [strike] | yes | The text is printed strikethrough. |
| [subscript: size](2)
[lowered: size](3) [/subscript] [/lowered](3) | yes | The text is printed in subscript; the amount of space the text is lowered is given in size. |
| [superscript: size](2)
[raised: size](3) [/superscript] [/raised](3) | yes | The text is printed in superscript; the amount of space the text is raised is given in size. |
| [subscript](3) | yes | The text is printed in subscript. |
| [superscript](3) | yes | The text is printed in superscript. |
| [underline: code](2)
[/underline] | yes | The text is printed underlined; the type of underline is given with code. |
| [vanish]
[hidden](3) | yes | The text is not printed because it is hidden; the text is not to be translated. |
The following markup has been added to support MS Word 6.0:
| [shadow] | yes | The text is printed shadowed. |
| [bkf: attribute](2) | no | A bookmark starts at this position in text; where attribute is an index to the bookmark end entry. |
| [bkl: attribute](2) | no | A bookmark ends at this position in text; where attribute is the value to which the bookmark start points to. |
| [rev auth: attribute](2)
[/rev auth] | yes | Used when revision marking was set to on in Word; is indicator for the author who did the revision. |
| [DTTM: attribute](2)
[/DTTM] | yes | Used when revision marking was set to on in Word; is indicator for date and time when revision took place. |
| [symb font: name char](2) | no | Indicates that the character given with char is to be printed in the font given with name. |
| [csty: name](2)
[/csty] | yes | For the run of text enclosed in start and ending tag the style given with name is used. |
| [kerning: value](2)
[/kerning] | yes | For the run of text enclosed in start and ending tag automatic kerning was used; where value is the kerning distance. |
The following table lists markup data that must not be changed. It is essential that the markup data remains in its original form. Only the position within the segment may change.
When you copy a Translation Memory proposal that contains one of these tags and there the source segment does not contain such a tag, you must delete this tag after you have copied the Translation Memory proposal.
If your source segment contains such a tag, keep this tag, no matter which type of tags are contained within your Translation Memory proposal.
The variables var1 and var2 are relevant only for TranslationManager .
| Tag name | End tag | Description |
|---|---|---|
| [auto footnote:ref var1,var2] | no | An autonumbered footnote is inserted; ref is the reference number of the footnote. |
| [auto endnote:ref var1,var2](3) | no | An autonumbered endnote is inserted; ref is the reference number of the endnote. |
| [efield] | no | The end of a field, even after all nested fields. |
| [field end: code] | no | The end of the previously inserted field; fields may be nested, the code indicates the type of end field. |
| [field sep] | no | Field separator. |
| [field sep: var1,var2] | no | Field separator of embedded objects. |
| [field: code] | no | Anything that can be inserted with Insert Field or Insert Symbol in Microsoft Word for Windows; code indicates the type of field. |
| [fld](3) | yes | A field entry follows. |
| [footnote:ref var1,var2] | no | A custom footnote is inserted; ref is the reference mark of the footnote. |
| [endnote:ref var1,var2](3) | no | A custom referenced endnote is inserted; ref is the reference mark of the endnote. |
| [comment ref: var1,var2](3) | no | An annotation is inserted. |
| [index entry] | yes | An index entry follows. |
| [index field]
[ix fld](3) | no | An index entry follows. |
| [picture: offset] | no | A graphic or picture is inserted in the document; where offset is used by TranslationManager internally. |
| [object: offset] | no | An object link is inserted in the document; where offset is used by TranslationManager internally. |
| [toc entry] | yes | A table of contents entry follows. |
| [toc field]
[toc fld](3) | no | A table of contents entry follows. |
| [toa entry] | yes | A table of authority entry follows. |
| [toa fld] | no | A table of authority entry follows. |
The following table lists markup data that is outside of translatable segments. They must not be changed.
The variables var1 and var2 are relevant only for TranslationManager .
| Tag name | End tag | Description |
|---|---|---|
| [Annotation Subdoc] | no | The annotation texts follow. |
| [column] | no | The start of a new column if the text is written in columns (as in a newspaper). |
| [comment](3) | no | An annotation text follows. |
| [comment text: var1,var2](3) | no | An annotation text follows. |
| [drawn obj: attributes](3) | no | A drawing object is inserted. |
| [endnote text:ref var1,var2](3) | no | The endnote text for the endnote reference with ref follows. |
| [Endnote Subdoc] | no | The endnote texts follow. |
| [footnote text:ref var1,var2] | no | The footnote text for the footnote referenced with ref follows. |
| [Footnote Subdoc] | no | The footnote texts follow. |
| [hdr textbox](3) | no | A header textbox entry. |
| [header/footer] | no | One header/footer. |
| [Header/Footer Subdoc] | no | Header/footer texts follow. |
| [Header Textbox Subdoc] | no | The header textbox texts follow. |
| [index] | yes | The index follows, it is not translatable. For more information on rebuilding the index, see "Microsoft Word for Windows documents". |
| [lf](3) | no | Hard line feed. |
| [next cell: var1,var2] | no | The next cell in a table starts. |
| [paragraph: var1,var2] | no | Start of a new paragraph. |
| [row] | no | A new row starts in a table. |
| [section: var1,var2] | no | A new section starts. |
| [style: name] | no | Occurs after the paragraph tag and gives the style name for the next paragraph with name. |
| [subdoc](3) | no | The current document is a master document and has as subdocument inserted at this text position. |
| [textbox](3) | no | A textbox entry. |
| [Textbox Subdoc] | no | The textbox texts follow. |
| [toa] | yes | The table of authorities follows, it is not translatable. For more information on rebuilding the table of authorities, see "Microsoft Word for Windows documents". |
| [toc] | yes | The table of contents follows, it is not translatable. For more information on rebuilding the table of contents, see "Microsoft Word for Windows documents". |
In general, all types of translation material can be exchanged with other TranslationManager products. For example, it is possible to exchange folders between a TranslationManager Version 2.0 user who runs the product under OS/2 and a user who has TranslationManager Version 2.0 installed under Windows.
This table shows which data types
you can export to and import from TranslationManager Version 1.0.
| Data type | Export to | Import from |
|---|---|---|
| Folder
(including documents, dictionaries, Translation Memory databases) *) | yes | yes |
| Document | yes | yes |
| External Translation Memory *) | no | yes |
| External dictionary | yes | yes |
| External markup table | yes | yes |
| External terminology list | yes | yes |
*) Use the Export in TranslationManager/2 Version 1.0 format option in the Export Folder window.
This table shows which data types
you can export to and import from Personal TranslationManager.
| Data type | Export to | Import from |
|---|---|---|
| Folder
(including documents, dictionaries, Translation Memory databases) | yes | yes |
| Document | yes | yes |
| External Translation Memory | yes | yes |
| External dictionary | yes | yes |
During export, you can generate a file with the untranslated segments of a document. This file can be processed by other systems, such as a machine translation system. This file format is similar to an external Translation Memory. The following sample contains three segments:
<NTMMemoryDb> <Segment>0000000002 <Control> 00001100000000000000000English(U.S.)German(national)EQFWORDDEVICE.DOC </Control> <Source>Selecting Your Rack-Mounted Devices </Source> <Target></Target> </Segment> <Segment>0000000009 <Control> 00001100000000000000000English(U.S.)German(national)EQFWORDDEVICE.DOC </Control> <Source>Some items to consider are: </Source> <Target></Target> </Segment> <Segment>0000000074 <Control> 00001100000000000000000English(U.S.)German(national)EQFWORDDEVICE.DOC </Control> <Source>This publication assists you in selecting a hardware configuration. </Source> <Target></Target> </Segment> </NTMMemoryDb>
(1) 1 MB equals 1 048 576 bytes.
(2) Do not change the variables, because they are calculated automatically by Microsoft Word for Windows.
(3) Changed or added markup data when dealing with documents originated in Microsoft Word 6.0.