You can translate many document types with OpenTM2, 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. documentformats you can use with OpenTM2 The file types you can use with OpenTM2 include:

• ASCII text files
• Documents from word processors and publishing systems:
  • Ami Pro
  • BookMaster ^(R)
  • and IPF
  • HTML
  • Microsoft ^(R)
  • Word for
  • Windows ^(R)
  • RTF
  • WordPerfect
  • SGML
  • FrameMaker
  • Interleaf
  • Lotus ^(R)
  • Notes ^(TM)
  • Ventura
  • PageMaker
  • QuarkXpress
  • Machine-readable information (MRI)
  • Microsoft ^(R)
  • PowerPoint ^(R)
• Machine-readable information that is contained within:
  • Assembler source code
  • Help files of Windows ^® programs
  • Help and message files of OS/2 ^(R) programs
  • Windows ^(R) resource files
  • OS/2 ^(R) resource files
• Unicode documents

A translation project can consist of one file or a set of files. In OpenTM2, 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 paragraph endings, highlighting, and font sizes.

When translating a document, OpenTM2 must be able to distinguish between this markup and the text that is to be translated. By ignoring the markup information during translation, OpenTM2preserves 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. OpenTM2 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 OpenTM2.

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.

Contents [hide] 1 Overview and terminology 2 What you can do with documents 2.1 Prerequisites 2.2 Calling sequence 2.3 Results 3 Analyzing a document 3.1 Analyzing documents using defaults 3.1.1 Prerequisites 3.1.2 Calling sequence 3.1.3 Results 3.2 Analyzing documents using Translation Memory databases 3.2.1 Prerequisites 3.2.2 Calling sequence 3.2.3 Options and parameters 3.2.4 Results 3.3 Editing analysis Profiles 3.3.1 Calling sequence 3.3.2 Results 3.3.3 Options and parameters 3.3.4 Results 3.4 Analyzing documents using dictionaries 3.4.1 Prerequisites 3.4.2 Calling sequence 3.4.3 Options and parameters 3.4.4 Results 3.5 Maintaining abbreviation lists 3.5.1 Prerequisites 3.5.2 Calling sequence 3.5.3 Options and parameters 3.5.4 Results 4 Closing a document 4.1 Calling sequence 4.2 Results 5 Counting the number of words in a document 5.1 Prerequisites 5.2 Calling sequence 5.3 Options and parameters 5.4 Results 6 Counting duplicate words in a document 6.1 Prerequisites 6.2 Calling sequence 6.3 Options and parameters 6.4 Output to 6.5 Results 6.6 Results 7 Counting the number and type of matches in a document 7.1 Prerequisites 7.2 Calling sequence 7.3 Options and parameters 7.4 Results 8 Counting words in segments with fuzzy matches 8.1 Prerequisites 8.2 Calling sequence 8.3 Options and parameters 8.4 Results 9 Dealing with specific document formats 9.1 Ami Pro documents 9.2 ANSI documents 9.3 ASCII documents 9.4 Assembler documents 9.5 BookMaster (R) and Information Presentation Facility documents 9.6 FrameBuilder files 9.7 HTML documents 9.8 Interleaf files 9.9 Lotus (R) Notes (TM) documents 9.10 Microsoft (R) PowerPoint (R) documents 9.11 Microsoft (R) Word for Windows (R) documents 9.12 RTF documents 9.13 SGML documents 9.14 Unicode documents 9.15 Windows (R) help files 9.16 WordPerfect documents 10 Deleting a document 10.1 Prerequisites 10.2 Calling sequence 10.3 Results 11 Exporting a document 11.1 Prerequisites 11.2 Calling sequence 11.3 Exporting a document in OpenTM2 format 11.3.1 Calling sequence 11.3.2 Options and parameters 11.3.3 Results 11.4 Exporting a document in external format 11.4.1 Calling sequence 11.4.2 Options and parameters 11.4.3 Results 11.5 Exporting a document in external format with a path 11.5.1 Calling sequence 11.5.2 Options and parameters 11.5.3 Results 11.6 Exporting a document in validation format 11.6.1 Calling sequence 11.6.2 Options and parameters 11.6.3 Results 11.7 Exporting a document in plain XML format 11.7.1 Calling sequence 11.7.2 Options and parameters 11.7.3 Results 11.8 Exporting translated glossary terms to a Lotus (R) Notes (TM) database 11.8.1 Calling sequence 11.8.2 Options and parameters 11.8.3 Results 11.9 Editing document revision marks for export 11.9.1 Prerequisites 11.9.2 Calling sequence 11.9.3 Options and parameters 11.9.4 Results 12 Importing a document 12.1 Prerequisites 12.2 Calling sequence 12.3 Importing a document in OpenTM2 format 12.3.1 Calling sequence 12.3.2 Options and parameters 12.3.3 Results 12.4 Importing a document in external format 12.4.1 Calling sequence 12.4.2 Options and parameters 12.4.3 Options and parameters 12.4.4 Results 12.5 Importing a document in external format with a path 12.5.1 Calling sequence 12.5.2 Options and parameters 12.5.3 Results 12.6 Importing glossary terms from a Lotus (R) Notes (TM) database 12.6.1 Calling sequence 12.6.2 Options and parameters 12.6.3 Results 13 Copying and moving documents between folders 13.1 Prerequisites 13.2 Calling sequence 13.3 Results 14 Opening a document 14.1 Prerequisites 14.2 Calling sequence 14.3 Results 15 Searching and replacing text in documents 15.1 Prerequisites 15.2 Calling sequence 15.3 Options and parameters 15.4 Results 15.5 Examples 16 Search segments with fuzzy matches 16.1 Prerequisites 16.2 Calling sequence 16.3 Options and parameters 16.4 Results 17 Spellchecking a document 17.1 Prerequisites 17.2 Calling sequence 17.3 Options and parameters 17.4 Results 18 Editing the spellcheck addendum 18.1 Prerequisites 18.2 Calling sequence 18.3 Options and parameters 18.4 Results 19 Translating a document 19.1 Prerequisites 19.2 Calling sequence 19.3 Options and parameters 19.4 Results 20 Opening and translating several documents 20.1 Prerequisites 20.2 Calling sequence 20.3 Results 21 Viewing the properties of a document 21.1 Prerequisites 21.2 Calling sequence 21.3 Results 22 Changing the properties of a document 22.1 Prerequisites 22.2 Calling sequence 22.3 Options and parameters 22.4 Results 23 Viewing the details of a document 24 Including notes for the translator 24.1 Translator’s notes in a source document 24.2 Translator’s notes in the Translation Environment 25 Preview XML documents 25.1 Step by step description to preview a XML document

Overview and terminology

You must first import documents you want to translate into OpenTM2 (see Importing a document).

This can be done by importing documents into an existing folder. At this point, OpenTM2 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, OpenTM2 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.

OpenTM2 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 OpenTM2 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 OpenTM2 editor, you can check the spelling in the translated document and see suggestions for correct spellings.

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

What you can do with documents

OpenTM2 offers several processing functions for documents, which you start by selecting:

1. At least one document from the “Document List” window
2. An action from the associated associated File,View , orUtilities menu

Prerequisites

A folder containing at least one document (except if you import a document).

Calling sequence

Select:

1. The folder with your documents from the “Folder List” window
2. Open from the File menu

Alternatively, select the “Folder List” window and double-click 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

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

The system allows you to analyze documents with different results:

• The documents are segmented (default).
• The documents are segmented, segments can be substituted with segment translations, or a Translation Memory can be filled with these translations.
• The documents are segmented, and terminology lists are created.

To analyze all documents in a folder, see Analyzing all the documents in a folder.

Analyzing documents using defaults

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:

1. The document to analyze from the “Document List” window of the folder
2. Open from the File menu

Alternatively, double-click the document in the “Document List” window.

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

Analyzing documents using Translation Memory databases

If you have Translation Memory databases available from previous translations, you have several options:

• OpenTM2 can search existing Translation Memory databases for segments that match segments in the document to be analyzed. Segments that match exactly or almost exactly can be copied into a new document- or project-specific Translation Memory.

• The system can perform automatic substitutions, that is, it copies the translations of segments that were previously made for an identical source segment (exact match ) into the translation version of the document. Matches are considered to be exact even if the tagging of the segment to be replaced differs from that of the translation proposal.

• The remaining untranslated segments can optionally be send to the machine translation server (only if the target language is supported by the machine translation server).

Prerequisites

• The Translation Memory databases to be searched must exist.
• The folder containing the document must be opened.

Calling sequence

Select:

1. One or more documents from the “Document List” window
2. Analyze from the File menu

The “Analyze Documents” window is displayed.

Figure 44. Analyze Documents window

Options and parameters

On the “General” page:

• Documents to be analyzed

This box contains the documents you selected previously.

• Substitute exact matches in the documents automatically

Select this option to automatically replace original segments with the translations found in the Translation Memory associated with the document. The document is then already partially translated when you start working with it, enabling you to concentrate on the translation of new segments.

This option is particularly useful in conjunction with the Add segments to Translation Memory of folder/document option on the “Miscellaneous” tabbed page. 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.

When you select this option, the Aut. Substitution tab is created, which is described in the following.

• Create lists

When you select this option, the List Settings tab is created, which is described in Analyzing documents using dictionaries.

• Create file containing untranslated segments

Select this option if you want OpenTM2 to create a separate file containing all untranslated segments. If you also selected Substitute exact matches in the documents automatically, this file contains only the remaining untranslated segments.

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 . If an external system is able to add valid translations for these untranslated segments, the updated file can be imported into OpenTM2 as a Translation Memory for translation use.

• Count Translation Memory match information

Select this option to enable OpenTM2 to count the number and type of matches that are found in the Translation Memory for the document. The document is then segmented and the matches are counted but no segments are replaced with matches that are found in the Translation Memory.

If you also select the Substitute exact matches in the documents automatically option, OpenTM2 automatically replaces segments with matches found in the Translation Memory and counts the number and type of matches replaced.

For information on how to view the counting result, refer to Counting the number and type of matches in a document.

• Prepare Redundancy Report

Select this option if you later want to create a Redundancy Report to calculate the costs for a translation project. For more information on Redundancy Reports, refer to Creating a Redundancy Report.

• Send untranslated segments to MT server

Select this option if you want send untranslated segments to the MT (Machine Translation) server. This option is inactive in the current version of OpenTM2.

• Create segment list for Translation Memory Optimizer

Select this option if you want to create a segment list for the Translation Memory Optimizer too

• Protect text in XMP and SCREEN sections

Select this option to protect text inside of and <screen> sections in IDDOC or DITA documents. Without this option the text will be translatable.</dd> </dl> <ul> <li><strong>Use analysis profile</strong></li> </ul> <dl> <dd>Select this option to use an analysis profile for the analysis of documents. An analysis profile contains markup table specific analysis settings which will override the analysis settings specified in the analysis window. Select an analysis profile from the analysis profile list or enter the name of a new analysis profile. Press the <strong>Edit</strong> button to specify or modify the analysis settings in the profile. Press the <strong>Delete</strong> button to delete the currently selected analysis profile.</dd> </dl> <p>On the “Miscellaneous” page:</p> <ul> <li><strong>Add segments to Translation Memory of folder/document</strong></li> </ul> <dl> <dd>Select this option if you want the Translation Memory databases that you can select from the <strong>Available</strong> list to be searched for matches. All exact matches or fuzzy matches found in the selected Translation Memory databases are then added to the Translation Memory databases associated with the folder or documents that are being analyzed.</dd> </dl> <dl> <dd>From the <strong>Available</strong> list, select with a double-click those <strong>Translation Memory databases</strong> from where the segments are to be copied. The selected <strong>Translation Memory databases</strong> are displayed in the <strong>Selected</strong> box. You must select at least one <strong>Translation Memory</strong>, and you can select a maximum of 10 <strong>Translation Memory databases</strong>.</dd> </dl> <ul> <li><strong>Stop search at first memory with exact match</strong></li> </ul> <dl> <dd>Select this option if the search for memory segments should stop at the first memory containing an exact match. This avoids duplicate exact matches from subsequent Translation Memory databases in the list. Without this option OpenTM2 will extract matches from all selected Translation Memory databases.</dd> </dl> <p>On the “Aut. Substitution” page, which is only shown when the <strong>Substitute exact matches in the documents automatically</strong> option is selected:</p> <ul> <li><strong>Use exact context match when more than one found</strong></li> </ul> <dl> <dd>Select this option if you expect segments with more than one exact match in the associated <strong>Translation Memory</strong> and you want the system to choose the one from the same document. In this case, the document must contain only one exact match. If this option is not selected, OpenTM2 skips the automatic substitution for a segment when more than one exact translation is found for a source segment.</dd> </dl> <ul> <li><strong>Use latest exact match when more than one is found</strong></li> </ul> <dl> <dd>Select this option if you expect segments with more than one exact match in the associated <strong>Translation Memory</strong> and you want the system to choose the most recent translation of the segment. If this option is not selected, OpenTM2 skips the automatic substitution for a segment when more than one exact translation is found for a source segment.</dd> </dl> <ul> <li><strong>Adjust leading white space to white space in source segment</strong></li> </ul> <dl> <dd>Select this option if the text is to have the same leading white space (blank, tab stop, and line feed) before and after the automatic substitution.</dd> </dl> <ul> <li><strong>Adjust trailing white space to white space in source segment</strong></li> </ul> <dl> <dd>Select this option if the text is to have the same trailing white space (blank, tab stop, and line feed) before and after the automatic substitution.</dd> </dl> <ul> <li><strong>Respect CRLF in segment</strong></li> </ul> <dl> <dd>The Translation Memory may contain two matching target segments for a source segment, one with carriage return line feed (CRLF), and one without. If you select this option, the target segment containing CRLF is taken during automatic substitution.</dd> </dl> <ul> <li><strong>No blank at segment end even if source segment has one</strong></li> </ul> <dl> <dd>A source segment may differ from its matching target segment in that the source segment contains one or more blanks at its end. If you select this option, such segments are considered an exact match during automatic substitution and the additional blanks at the end of the source segment are removed.</dd> </dl> <ul> <li><strong>Use joined segments when found</strong></li> </ul> <dl> <dd>Select this option to join segments. This can be useful if you want to analyze a document that you have worked with before and where you joined neighboring 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 neighboring segments in the document to be analyzed. Note that two neighboring segments are only joined if for the first segment in the sequence a fuzzy match has been found.</dd> </dl> <ul> <li><strong>Ignore path in document names</strong></li> </ul> <dl> <dd>Select this option if any path information in the document name is to be ignored when a document is checked for exact-exact matches.</dd> </dl> <ul> <li><strong>No substitution if source and target segment is identical</strong></li> </ul> <dl> <dd>Select this option to suppress the automatic substitution of segments when the source segment is identical with the target segment found in the <strong>Translation Memory</strong>.</dd> </dl> <ul> <li><strong>Ignore memory proposals with comments</strong></li> </ul> <dl> <dd>Select this option to suppress the automatic substitution of segments when the memory proposal has a comment.</dd> </dl> <ul> <li><strong>Use TMO replacement list for IDDOC to DITA converted projects</strong></li> </ul> <dl> <dd>Select this option to specify a TMO replacement list to be applied on IDDOC proposals for DITA documents. Once this option is selected, the name of the replacement list can be typed in the list name field or be selected using the <strong>Select….</strong> button</dd> </dl> <ul> <li><strong>List</strong></li> </ul> <dl> <dd>The fully qualified file name of a TMO replacement list.</dd> </dl> <p>When you select both <strong>Use exact context match…</strong> and <strong>Use latest exact match…</strong>, the system combines both requirements and chooses the latest of the exact context matches. You then get fewer automatic substitutions than with <strong>Use latest exact match…</strong> but more than with <strong>Use exact context match…</strong>.</p> <p>Click <strong>Analyze</strong> 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.</p> <h5><span id="Results-3">Results</span></h5> <p>The document is segmented.</p> <p>Depending on the options you selected, the document may already be partially translated, the <strong>Translation Memory</strong> updated, or a file created containing untranslated segments.</p> <p>You can begin translating the document.</p> <h4><span id="Editing_analysis_Profiles">Editing analysis Profiles</span></h4> <p>An analysis profile allows the specification of analysis settings for a specific group of markup tables. When an analysis profile is specified in the analysis window the settings from the profile overide the settings specified in the analysis window. When the markup table of the analyzed document does not match the markup tables defined in the profile the analysis profile settings are ignored and the settings from the analysis window are used instead.</p> <h5><span id="Calling_sequence-4">Calling sequence</span></h5> <p>Select:</p> <ol> <li>Activate the analysis window</li> <li>Select the option</li> <li>Select an analysis profile from the analysis profile list or enter the name of a new analysis profile</li> <li>press the button</li> </ol> <h5><span id="Results-4">Results</span></h5> <p>The analysis profile window is displayed The “Analyze profile” window is displayed.</p> <p><a href="http://www.beo-doc.de/opentm2wiki/index.php/File:AnalysisprofilewindowArtwork.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/8/8e/AnalysisprofilewindowArtwork.gif" alt="AnalysisprofilewindowArtwork.gif" width="481" height="499"></a></p> <p><em><strong>Figure 45. Analysis Profile window</strong></em></p> <h5><span id="Options_and_parameters-2">Options and parameters</span></h5> <ul> <li><strong>Markup table group</strong></li> </ul> <dl> <dd>Select one of the markup table groups. The markup tables and the analysis settings for the selected group are displayed.</dd> </dl> <ul> <li><strong>Available</strong></li> </ul> <dl> <dd>This list shows the available markup tables. Markup tables already selected (in the same or another markup table group) are not listed here. To move a markup table to the selected list either double-click the markup table name or select the markup table name and press the “>” button.</dd> </dl> <ul> <li><strong>Substitute exact matches in the documents automatically</strong></li> </ul> <dl> <dd>Select this option to automatically replace original segments with the translations found in the Translation Memory associated with the document.</dd> </dl> <ul> <li><strong>Create file containing untranslated segments</strong></li> </ul> <dl> <dd>Select this option if you want OpenTM2 to create a separate file containing all untranslated segments. If you also selected <strong>Substitute exact matches in the documents automatically</strong>, this file contains only the remaining untranslated segments.</dd> </dl> <ul> <li><strong>Count Translation Memory match information</strong></li> </ul> <dl> <dd>Select this option to enable OpenTM2 to count the number and type of matches that are found in the Translation Memory for the document. The document is then segmented and the matches are counted but no segments are replaced with matches that are found in the Translation Memory.</dd> </dl> <ul> <li><strong>Adjust leading white space to white space in source segment</strong></li> </ul> <dl> <dd>Select this option if the text is to have the same leading white space (blank, tab stop, and line feed) before and after the automatic substitution.</dd> </dl> <ul> <li><strong>Adjust trailing white space to white space in source segment</strong></li> </ul> <dl> <dd>Select this option if the text is to have the same trailing white space (blank, tab stop, and line feed) before and after the automatic substitution.</dd> </dl> <ul> <li><strong>Respect CRLF in segment</strong></li> </ul> <dl> <dd>The Translation Memory may contain two matching target segments for a source segment, one with carriage return line feed (CRLF), and one without. If you select this option, the target segment containing CRLF is taken during automatic substitution.</dd> </dl> <ul> <li><strong>Use joined segments when found</strong></li> </ul> <dl> <dd>Select this option to join segments. This can be useful if you want to analyze a document that you have worked with before and where you joined neighboring 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 neighboring segments in the document to be analyzed. Note that two neighboring segments are only joined if for the first segment in the sequence a fuzzy match has been found.</dd> </dl> <ul> <li>Click <strong>Save </strong>to save the analysis profile.</li> <li>Click <strong>Cancel </strong>to leave this window without saving the analysis profile.</li> </ul> <h5><span id="Results-5">Results</span></h5> <p>If you clicked on <strong>Save</strong>, the analysis profile is saved or created (if it is a new one) and can be used for the analysis process.</p> <ul> <li><strong>Usage of analysis profile</strong></li> </ul> <dl> <dd>An analysis profile can be used when the analysis settings for documents must be different depending on the markup table of the document.</dd> </dl> <dl> <dd>Normally you would select all documents of one markup table and perform the analysis for these documents and when select the documents which require different analysis settings and repeat the analysis for these documents.</dd> </dl> <dl> <dd>With the help of an analysis profile this can be simplified. Just select one of the markup tables in markup table group 1 and select the settings required for this markup table, go to markup table group 2, select the second markup table and select the settings required for this markup table and save the profile. Select the profile in the analysis window and run the analysis process. For all documents with the markup table selected in the first markup table group the settings from the first markup table group are used and for all documents with a the markup table selected in the second group the settings from the second markup table group are used. For all other documents the settings from the analysis window are used.</dd> </dl> <h4><span id="Analyzing_documents_using_dictionaries">Analyzing documents using dictionaries</span></h4> <p>If you have <em>dictionaries</em> available containing vocabulary associated with the document, you can ask <strong>OpenTM2</strong> to generate two types of <em>terminology list</em>:</p> <ul> <li> <em>New terms</em> list. This list contains all terms in your document that are not defined in the referenced dictionaries. You can use this list of terms to add entries to these dictionaries.</li> </ul> <ul> <li> <em>Found terms</em> list. This list contains all terms in your document that are already defined in the referenced dictionaries. You can use this list of terms to fill a separate dictionary related to the document.</li> </ul> <p>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 <em>exclusion lists</em> or <em>exclusion dictionaries</em> to get fewer terms in the lists.</p> <p>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.</p> <p>To perform the creation of terminology lists, you specify your options and parameters in two subsequent windows.</p> <h5><span id="Prerequisites-4">Prerequisites</span></h5> <ul> <li>Dictionaries and, optionally, exclusion lists must be available</li> <li>The folder containing the document must be opened</li> </ul> <h5><span id="Calling_sequence-5">Calling sequence</span></h5> <p>Select:</p> <ol> <li>One or more documents from the “Document List” window.</li> <li> <strong>Analyze…</strong> from the <strong>File</strong> menu. The “Analyze Documents” window is displayed.</li> <li> <strong>Create Lists’<em> The </em></strong><em>List Settings</em> tab is created.</li> <li> <strong>List Settings</strong> tab</li> </ol> <p>The “List Settings” page is displayed.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7b.GIF"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/5/51/Eqfb7s7b.GIF" alt="Eqfb7s7b.GIF" width="446" height="480"></a></p> <p><em><strong>Figure 46. Analyze Documents window — List Settings page</strong></em></p> <p> </p> <h5><span id="Options_and_parameters-3">Options and parameters</span></h5> <p>To create a new terms list, select:</p> <ul> <li><strong>Create list of new terms</strong></li> </ul> <dl> <dd>Select this option to create a list of new terms. The system provides the folder name as the default name for the list to be generated. You can specify any other name. For this type of list, you can also select:</dd> </dl> <ul> <li><strong>Include new multiword terms</strong></li> </ul> <dl> <dd>Select this option to include multiword terms that are not hyphenated, such as data management, in the list of new terms. Choose whether the first word of these terms can be a noun, an adjective, or either of them.</dd> </dl> <ul> <li><strong>Include context information</strong></li> </ul> <dl> <dd>If a new term is found, the system can save the original segment (containing the term) as <em>context</em> information. This option is useful if you intend to copy the new terms to a dictionary that can contain context information.</dd> </dl> <ul> <li><strong>Minimum number of occurrences</strong></li> </ul> <dl> <dd>Specify how often a term must occur in the document so that it is included in the new terms list.</dd> </dl> <p>To create the list of all terms of a document that are also in selected dictionaries, select:</p> <ul> <li><strong>Create list of found terms</strong></li> </ul> <dl> <dd>Select this option to create a list of found terms. The system provides the folder name as the default name for the list to be generated. You can specify any other name. For this type of list, you can also select:</dd> </dl> <ul> <li><strong>Include context information</strong></li> </ul> <dl> <dd>If a term is found in one of the selected dictionaries, the system can save the original segment (containing the term) as <em>context</em> information. This option is useful if you intend to copy the found terms to a dictionary that can contain context information.</dd> </dl> <ul> <li><strong>Minimum number of occurrences</strong></li> </ul> <dl> <dd>Specify how often a term must occur in the document so that it is included in the found terms list.</dd> </dl> <ul> <li><strong>Add found terms to dictionary</strong></li> </ul> <dl> <dd>To copy the found terms to a dictionary, select a dictionary from this list box.</dd> </dl> <p>For both new terms and found terms lists, you must specify:</p> <ul> <li><strong>Dictionaries to be used for analysis</strong></li> </ul> <dl> <dd>Select the dictionaries to be used for generating terminology lists from the <strong>Available</strong> list box. The dictionaries are listed in the <strong>Selected</strong> list box in the order in which you select them, and the dictionaries are searched in this order. You must select at least one dictionary, and you can select up to 10.</dd> </dl> <p>If needed, you can limit the generation of terminology lists by the following options:</p> <ul> <li><strong>Use exclusion lists</strong></li> </ul> <dl> <dd>If you have terms you want to exclude from the lists to be generated, use an exclusion list. For each language for which you installed the language support, <strong>OpenTM2</strong> already provides an exclusion list. It contains so-called noise terms. Select the exclusion lists to be used from the list box.</dd> </dl> <ul> <li><strong>Use exclusion dictionaries</strong></li> </ul> <dl> <dd>If you have a dictionary that contains well-defined terms that you want to exclude from the terminology lists to be generated, select it from the list box.</dd> </dl> <p>Click <strong>Set</strong> to return to the “Analyze Documents” window.</p> <p>To begin analysis, click <strong>Analyze</strong>.</p> <h5><span id="Results-6">Results</span></h5> <p>The document is segmented.</p> <p>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 <a title="Working with terminology lists" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_terminology_lists">Working with terminology lists</a>.</p> <p>Analyzing documents using machine translation (MT)</p> <p>You can begin translating the document.</p> <h4><span id="Maintaining_abbreviation_lists">Maintaining abbreviation lists</span></h4> <p>OpenTM2 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. OpenTM2 provides default abbreviation lists for each source language supported. You can add new abbreviations, or delete or modify existing ones.</p> <h5><span id="Prerequisites-5">Prerequisites</span></h5> <p>The “Language List” window must be active (<strong>Display Language List </strong>from the Utilities menu).</p> <ul> <li>The language you want to work with must be in active state.</li> </ul> <h5><span id="Calling_sequence-6">Calling sequence</span></h5> <p>Select:</p> <ol> <li>An active language</li> <li> <strong>Open </strong>from the <strong>File </strong>menu or double-click the name of the language</li> </ol> <p>The list of abbreviations for the selected language is displayed. For example, <strong>Edit Abbreviations for: German(national)</strong> if you selected this language. You can now make your changes.</p> <h5><span id="Options_and_parameters-4">Options and parameters</span></h5> <ul> <li><strong>Abbreviations list</strong></li> </ul> <dl> <dd>To update an abbreviation, overtype it. To add a new one, switch to Insert mode and press Enter at the line before which you want to insert it. To delete an abbreviation, use the Backspace key. Note that you end the abbreviation with a full stop.</dd> </dl> <ul> <li><strong>Save</strong></li> </ul> <dl> <dd>To save any changes and close this window.</dd> </dl> <ul> <li><strong>Cancel</strong></li> </ul> <dl> <dd>To close this window without saving any changes.</dd> </dl> <ul> <li><strong>Help</strong></li> </ul> <dl> <dd>To get information on how to interact with this window.</dd> </dl> <h5><span id="Results-7">Results</span></h5> <p>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.</p> <h3><span id="Closing_a_document">Closing a document</span></h3> <p>To translate a document, you must open it so that the <strong>Translation Environment</strong> for this document is displayed.</p> <p>Closing a document means to stop translating a document and to leave the <strong>Translation Environment</strong>.</p> <h5><span id="Calling_sequence-7">Calling sequence</span></h5> <p>Select <strong>Close</strong> from the <strong>Translation Environment</strong> system menu.</p> <p>This takes you back to the <strong>OpenTM2</strong> main window.</p> <h5><span id="Results-8">Results</span></h5> <p>The translation document, the <strong>Translation Memory</strong>, and the dictionaries used are saved in their current status. You can start any other <strong>OpenTM2</strong> task. The translation of this document can be continued at any time.</p> <h3><span id="Counting_the_number_of_words_in_a_document">Counting the number of words in a document</span></h3> <p><strong>OpenTM2</strong> 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.</p> <p>To count the number of words in all the documents of a folder, see <a title="Working with folders" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_folders#Counting_the_words_in_all_documents_of_a_folder">Counting the words in all documents of a folder</a>.</p> <h5><span id="Prerequisites-6">Prerequisites</span></h5> <p>At least one document must exist in the selected folder.</p> <h5><span id="Calling_sequence-8">Calling sequence</span></h5> <p>Select:</p> <ol> <li>At least one document from the “Document List” window</li> <li> <strong>Count Words… </strong>from the <strong>Utilities </strong>menu</li> </ol> <p>The “Count Words” window is displayed.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7c.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/b/ba/Eqfb7s7c.gif" alt="Eqfb7s7c.gif" width="608" height="488"></a></p> <p><em><strong>Figure 47. Count Words window</strong></em></p> <h5><span id="Options_and_parameters-5">Options and parameters</span></h5> <ul> <li><strong>Documents</strong></li> </ul> <dl> <dd>This box contains the list of the documents you selected in the “Document List” window.</dd> </dl> <ul> <li><strong>Options</strong></li> </ul> <dl> <dd>One of the following options can be selected at a time. Select:</dd> </dl> <ul> <li><strong>Original</strong></li> </ul> <dl> <dd>To count the number of words in the document before translation.</dd> </dl> <ul> <li><strong>Translation</strong></li> </ul> <dl> <dd>To count the number of words in the translated document.</dd> </dl> <ul> <li><strong>Translation memory match information</strong></li> </ul> <dl> <dd> See <a title="Working with documents" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_documents#Counting_the_number_and_type_of_matches_in_a_document">Counting the number and type of matches in a document</a> for an explanation. </dd> </dl> <ul> <li><strong>Duplicate words</strong></li> </ul> <dl> <dd> See <a title="Working with documents" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_documents#Counting_duplicate_words_in_a_document">Counting duplicate words in a document</a> for an explanation. </dd> </dl> <ul> <li><strong>Fuzzy matches by class</strong></li> </ul> <dl> <dd> See <a title="Working with documents" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_documents#Counting_the_number_and_type_of_matches_in_a_document">Counting the number and type of matches in a document</a> for an explanation. </dd> </dl> <ul> <li><strong>Output to</strong></li> </ul> <dl> <dd>In this block you define where you want the system to save the results:</dd> </dl> <ul> <li><strong>Screen</strong></li> </ul> <dl> <dd>The result of the word count is displayed on your screen. This option is selected automatically.</dd> </dl> <ul> <li><strong>File</strong></li> </ul> <dl> <dd>Select this option to also store the count results in a file. You can:</dd> </dl> <dl> <dd> <ul> <li>Accept the proposed file name.</li> <li>Type a file name of your choice.</li> <li>Click <strong>Select… </strong>to display the “Select File” window from where you can choose the file name without having to type it (for a detailed description, see <a title="General concepts" href="http://www.beo-doc.de/opentm2wiki/index.php/General_concepts#Specifying_an_output_file">Specifying an output file</a>). </li> <li>Select the format of the count result file. The supported formats are <ul> <li>ASCII (plain text)</li> <li>HTML</li> <li>XML</li> </ul> </li> </ul> </dd> </dl> <p>Click <strong>Count</strong> to begin counting words.</p> <h5><span id="Results-9">Results</span></h5> <p>If you selected <strong>Original</strong> and output to <strong>Screen</strong>, the result is displayed in the “Word Count Results – Original” window (see Figure 48) with the following columns for each original document:</p> <ul> <li><strong>Documents</strong></li> </ul> <dl> <dd>The name of the document</dd> </dl> <ul> <li><strong>Untranslated</strong></li> </ul> <dl> <dd>The number of words</dd> </dl> <ul> <li><strong>Markup</strong></li> </ul> <dl> <dd>The number of markup tags</dd> </dl> <ul> <li><strong>Total</strong></li> </ul> <dl> <dd>The number of words and markup tags</dd> </dl> <p>If you selected <strong>Translation</strong> and output to <strong>Screen</strong>, the result is displayed in the “Word Count Results – Translation” window (see Figure 48) with the following columns for each translated document:</p> <ul> <li><strong>Documents</strong></li> </ul> <dl> <dd>The name of the document.</dd> </dl> <ul> <li><strong>Translated</strong></li> </ul> <dl> <dd> The number of original words already translated. Note that copying a marked part of a <strong>Translation Memory</strong> proposal (see <a title="Working with the OpenTM2 Editor" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_the_OpenTM2_Editor#Moving_around_marked_text">Moving around marked text</a>) is counted as one character. </dd> </dl> <ul> <li><strong>Untranslated</strong></li> </ul> <dl> <dd>The number of original words not yet translated.</dd> </dl> <ul> <li><strong>Target words</strong></li> </ul> <dl> <dd>The number of translated words in the translated document.</dd> </dl> <ul> <li><strong>Markup</strong></li> </ul> <dl> <dd>The number of markup tags.</dd> </dl> <ul> <li><strong>Total</strong></li> </ul> <dl> <dd>The number of translated words and markup tags.</dd> </dl> <p><a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7d.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/d/d2/Eqfb7s7d.gif" alt="Eqfb7s7d.gif" width="727" height="201"></a></p> <p><em><strong>Figure 48. Word Count Results – Translation window</strong></em><br> If you selected the <strong>File</strong> output option, the results are stored in the same format in the specified file.</p> <p>To return to the previous window, close the respective “Word Count Result” window.</p> <h3><span id="Counting_duplicate_words_in_a_document">Counting duplicate words in a document</span></h3> <p><strong>OpenTM2</strong> provides a facility for counting duplicate words for one or more documents. The result is shown in a window and can be saved in a file. Duplicate words are words in segments which are contained more than once in the documents and will become exact matches once the first occurence of such a segment has been translated.</p> <p>To count the number of words in all the documents of a folder, see <a title="Working with folders" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_folders#Counting_the_words_in_all_documents_of_a_folder">Counting the words in all documents of a folder</a>.</p> <p>Using the <strong>“Include memory match information”</strong> option, information on memory matches can be included in the created reslts.</p> <h5><span id="Prerequisites-7">Prerequisites</span></h5> <p>At least one document must exist in the selected folder.</p> <h5><span id="Calling_sequence-9">Calling sequence</span></h5> <p>Select:</p> <ol> <li>At least one document from the “Document List” window</li> <li> <strong>Count Words… </strong>from the <strong>Utilities </strong>menu</li> </ol> <p>The “Count Words” window (see Figure 47) is displayed.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7c3.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/3/34/Eqfb7s7c3.gif" alt="Eqfb7s7c3.gif" width="608" height="488"></a></p> <p><em><strong>Figure 49. Count Words window</strong></em></p> <h5><span id="Options_and_parameters-6">Options and parameters</span></h5> <ul> <li><strong>Documents</strong></li> </ul> <dl> <dd>This box contains the list of the documents you selected in the “Document List” window.</dd> </dl> <ul> <li><strong>Options</strong></li> </ul> <p>Select:</p> <dl> <dd> <ul> <li>Duplicate words</li> </ul> <dl> <dd>To count the number of duplicate words in the selected documents.</dd> </dl> </dd> </dl> <dl> <dd> <ul> <li>Include memory match information</li> </ul> <dl> <dd>To show information on memory matches in the results.</dd> </dl> </dd> </dl> <h5><span id="Output_to">Output to</span></h5> <p>In this block you define where you want the system to save the results:</p> <ul> <li><strong>Screen</strong></li> </ul> <dl> <dd>The result of the word count is displayed on your screen. This option is selected automatically.</dd> </dl> <ul> <li><strong>File</strong></li> </ul> <dl> <dd>Select this option to also store the count results in a file. You can:</dd> </dl> <dl> <dd> <ul> <li>Accept the proposed file name.</li> <li>Type a file name of your choice.</li> <li>Click <strong>Select… </strong>to display the “Select File” window from where you can choose the file name without having to type it (for a detailed description, see …).</li> <li>Select the format of the count result file. The supported formats are <ul> <li>ASCII (plain text)</li> <li>HTML</li> <li>XML</li> </ul> </li> </ul> </dd> </dl> <p>Click <strong>Count</strong> to begin counting words.</p> <h5><span id="Results-10">Results</span></h5> <p>Result without “Include memory match information” option selected. The results of the word count are shown, for example, in the “Word Count Results – Duplicate Words” window.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:DuplicateCounts.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/e/e4/DuplicateCounts.gif" alt="DuplicateCounts.gif" width="1065" height="201"></a></p> <p><em><strong>Figure 50. Word Count Results – Duplications Words window</strong></em></p> <p>The window contains the following columns:</p> <ul> <li><strong>Documents</strong></li> </ul> <dl> <dd>The name of the document.</dd> </dl> <ul> <li><strong>Translated</strong></li> </ul> <dl> <dd>The number of translated words in the documents.</dd> </dl> <ul> <li><strong>Untranslated</strong></li> </ul> <dl> <dd>The number of untranslated words in the documents.</dd> </dl> <ul> <li><strong>Duplicate words</strong></li> </ul> <dl> <dd>The number of words in duplicate segments. The first occurence of these segments is counted in the “To be translated” column.</dd> </dl> <ul> <li><strong>To be translated</strong></li> </ul> <dl> <dd>The number of words which have to be translated manually.</dd> </dl> <ul> <li><strong>Markup</strong></li> </ul> <dl> <dd>The number of tags in the documents.</dd> </dl> <p>If you selected the <strong>File</strong> output option, the results are stored in the same format in the specified file.</p> <p>To return to the previous window, close the respective “Word Count Result — Duplicate Words” window.</p> <h5><span id="Results-11">Results</span></h5> <p>Result with “Include memory match information” option selected. The results of the word count are shown, for example, in the “Word Count Results – Duplicate Words” window.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:DuplicateCounts2.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/e/ef/DuplicateCounts2.gif" alt="DuplicateCounts2.gif" width="1065" height="217"></a></p> <p><em><strong>Figure 51. Word Count Results with memory match information- Duplications Words window</strong></em></p> <p>The window contains the following columns:</p> <ul> <li><strong>Documents</strong></li> </ul> <dl> <dd>The name of the document.</dd> </dl> <ul> <li><strong>Duplicate words (Repetitions)</strong></li> </ul> <dl> <dd>All words in segments, which had already one occurrence in one of the document(s). The first occurrence of the segment is listed in one of the fuzzy columns and any additional occurrence of the segment is listed in the duplicate words column.</dd> </dl> <ul> <li><strong>95-99% Fuzzy</strong></li> </ul> <dl> <dd>The number of words in segments for which there is a fuzzy match in the memory with a fuzziness of 95% up to 99% or segments for which another segment would become a 95-99% fuzzy match proposal during the translation of the document(s).</dd> </dl> <ul> <li><strong>75-94% Fuzzy</strong></li> </ul> <dl> <dd>The number of words in segments for which there is a fuzzy match in the memory with a fuzziness of 75% up to 94% or segments for which another segment would become a 75-94% fuzzy match proposal during the translation of the document(s).</dd> </dl> <ul> <li><strong>0-74% Fuzzy</strong></li> </ul> <dl> <dd>The number of words in segments for which there is a fuzzy match in the memory with a fuzziness of 0% up to 74% or segments for which another segment would become a 0-74% fuzzy match proposal during the translation of the document(s).</dd> </dl> <ul> <li><strong>Total untranslated</strong></li> </ul> <dl> <dd>The total number of words in segments which have no exact match in the Translation Memory. This column contains the total of the duplictae words column and th efuzzy columns.</dd> </dl> <ul> <li><strong>Exact matches (100% Matches)</strong></li> </ul> <dl> <dd>The number of words in segments for which there is one or more exact match in the Translation Memory.</dd> </dl> <p>If you selected the <strong>File</strong> 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 — Duplicate Words” window.</p> <h3><span id="Counting_the_number_and_type_of_matches_in_a_document">Counting the number and type of matches in a document</span></h3> <p><strong>OpenTM2</strong> provides a facility for counting the number and type of <strong>Translation Memory</strong> matches for one or more documents. The result is shown in a window and can be saved in a file.</p> <h5><span id="Prerequisites-8">Prerequisites</span></h5> <p>At least one document must exist in the selected folder.</p> <h5><span id="Calling_sequence-10">Calling sequence</span></h5> <p>Select:</p> <ol> <li>At least one document from the “Document List” window</li> <li> <strong>Count words… </strong>from the <strong>Utilities</strong> menu</li> </ol> <p>The “Count Words” window is displayed<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7c2.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/d/d0/Eqfb7s7c2.gif" alt="Eqfb7s7c2.gif" width="608" height="488"></a></p> <p><em><strong>Figure 52. Count Words window</strong></em></p> <h5><span id="Options_and_parameters-7">Options and parameters</span></h5> <ul> <li><strong>Documents</strong></li> </ul> <p>This box contains the list of the documents you selected in the “Document List” window.</p> <ul> <li><strong>Options</strong></li> </ul> <dl> <dd>Select:</dd> </dl> <dl> <dd> <ul> <li>Translation Memory match information</li> </ul> <dl> <dd>To count the number and type of matches found in the <strong>Translation Memory</strong> for the selected documents.</dd> </dl> </dd> </dl> <dl> <dd> <ul> <li>Count replace matches separately</li> </ul> <dl> <dd>To show the matches replaced automatically, in separate columns.</dd> </dl> </dd> </dl> <ul> <li><strong>Output to</strong></li> </ul> <dl> <dd>In this block you define where you want the system to save the results:</dd> </dl> <dl> <dd> <ul> <li>Screen</li> </ul> <dl> <dd>The result of the word count is displayed on your screen. This option is selected automatically.</dd> </dl> </dd> </dl> <ul> <li><strong>File</strong></li> </ul> <dl> <dd>Select this option to also store the count results in a file. You can:</dd> </dl> <dl> <dd> <ul> <li>Accept the proposed file name.</li> <li>Type a file name of your choice.</li> <li>Click … to display the “Select File” window from where you can choose the file name without having to type it (for a detailed description, see … ).</li> <li>Select the format of the count result file. The supported formats are</li> </ul> <dl> <dd> <ul> <li>ASCII (plain text)</li> <li>HTML</li> <li>XML</li> </ul> </dd> </dl> </dd> </dl> <p>Click <strong>Count</strong> to begin counting the matches.</p> <h5><span id="Results-12">Results</span></h5> <p>The results of the word count are shown, for example, in the “Word Count Results - <strong>Translation Memory</strong> Matches” window.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7i.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/6/61/Eqfb7s7i.gif" alt="Eqfb7s7i.gif" width="1255" height="201"></a></p> <p><em><strong>Figure 53. Word Count Results – Translation Memory window</strong></em></p> <p>The window contains the following columns:</p> <ul> <li><strong>Documents</strong></li> </ul> <dl> <dd>The name of the documents.</dd> </dl> <ul> <li><strong>Total</strong></li> </ul> <dl> <dd>The number of words in the documents.</dd> </dl> <ul> <li><strong>Exact-Exact</strong></li> </ul> <dl> <dd>The number of words in segments with identical matches.</dd> </dl> <ul> <li><strong>Exact (1)</strong></li> </ul> <dl> <dd>The number of words in segments having exactly one proposal.</dd> </dl> <ul> <li><strong>Exact (2+)</strong></li> </ul> <dl> <dd>The number of words in segments having more than one exact proposal.</dd> </dl> <ul> <li><strong>Fuzzy</strong></li> </ul> <dl> <dd>The number of words in segments with fuzzy proposals. If you did not select <strong>Count replace matches separately</strong>, the number displayed also includes the number of words in segments automatically replaced and automatically replaced in a fuzzy match.</dd> </dl> <ul> <li><strong>MachMatch</strong></li> </ul> <dl> <dd>The number of segments translated by machine.</dd> </dl> <ul> <li><strong>No match</strong></li> </ul> <dl> <dd>The number of words in segments with no proposal.</dd> </dl> <p>If you selected <strong>Count replace matches separately</strong>, you get the following fields in addition:</p> <ul> <li><strong>Replace</strong></li> </ul> <dl> <dd>The number of words in segments automatically replaced.</dd> </dl> <ul> <li><strong>FuzzyRepl</strong></li> </ul> <dl> <dd>The number of words in segments automatically replaced in a fuzzy match.</dd> </dl> <p>If you selected the <strong>File</strong> output option, the results are stored in the same format in the specified file.</p> <p>Note that the criteria for fuzzy matches can be customized, as described in <a title="General concepts" href="http://www.beo-doc.de/opentm2wiki/index.php/General_concepts#Viewing_and_changing_the_system_preferences">Viewing and changing the system preferences</a>. This also influences the “No match” counter.</p> <p>If there is no <strong>Translation Memory</strong> match data available for a document, for example because the document has not been analyzed yet or neither the <strong>Substitute exact matches in the documents automatically</strong> options nor the <strong>Count Translation Memory match information</strong> option was selected during analysis, the “Word Count Results - <strong>Translation Memory</strong> Matches” window contains the text No match ….</p> <p>To return to the previous window, close the “Word Count Result — <strong>Translation Memory</strong> Matches” window.</p> <h3><span id="Counting_words_in_segments_with_fuzzy_matches">Counting words in segments with fuzzy matches</span></h3> <p>OpenTM2 provides a facility for counting words in segments with fuzzy matches. The result is shown in a window and can be saved in a file. The words in segments with fuzzy matches are grouped in classes. The column Class-0 lists the number of words in segments with fuzzy matches which are only different in white space or inline tagging. The column Class-1 lists the number of words in segments with one different word , class-2 with two different words and so on. To count the number of words in all the documents of a folder, see <a title="Working with documents" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_documents#Counting_the_number_of_words_in_a_document">Counting the number of words in a document</a>.</p> <h5><span id="Prerequisites-9">Prerequisites</span></h5> <p>At least one document must exist in the selected folder and the document has to be analyzed.</p> <h5><span id="Calling_sequence-11">Calling sequence</span></h5> <p>Select:</p> <ol> <li>At least one document from the “Document List” window</li> <li>from the menu</li> </ol> <p>The “Count Words” window (see Figure 52) is displayed.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Count_Words.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/b/b3/Count_Words.gif" alt="Count Words.gif" width="608" height="490"></a></p> <p><em><strong>Figure 54. Count Words window</strong></em></p> <h5><span id="Options_and_parameters-8">Options and parameters</span></h5> <ul> <li><strong>Documents</strong></li> </ul> <dl> <dd>This box contains the list of the documents you selected in the “Document List” window.</dd> </dl> <ul> <li><strong>Options</strong></li> </ul> <dl> <dd>Select:</dd> </dl> <dl> <dd> <ul> <li>Fuzzy matches by class</li> </ul> <dl> <dd>To count the number of words in segments with fuzzy matches in the selected documents.</dd> </dl> </dd> </dl> <dl> <dd> <ul> <li><strong>Output to</strong></li> </ul> <dl> <dd>In this block you define where you want the system to save the results:</dd> </dl> </dd> </dl> <dl> <dd> <ul> <li><strong>Screen</strong></li> </ul> <dl> <dd>The result of the word count is displayed on your screen. This option is selected automatically.</dd> </dl> </dd> </dl> <dl> <dd> <ul> <li><strong>File</strong></li> </ul> <dl> <dd>Select this option to also store the count results in a file.You can:</dd> </dl> </dd> </dl> <ul> <li><strong>Output to</strong></li> </ul> <dl> <dd>In this block you define where you want the system to save the results:</dd> </dl> <ul> <li><strong>Screen</strong></li> </ul> <dl> <dd>The result of the word count is displayed on your screen. This option is selected automatically.</dd> </dl> <ul> <li><strong>File</strong></li> </ul> <dl> <dd> Select this option to also store the count results in a file. You can: <p></p> <ul> <li>Accept the proposed file name.</li> <li>Type a file name of your choice.</li> <li>Click …to display the “Select File” window from where you can choose the file name without having to type it (for a detailed description, see <a title="General concepts" href="http://www.beo-doc.de/opentm2wiki/index.php/General_concepts#Specifying_an_output_file">Specifying an output file</a>). </li> <li>Select the format of the count result file. The supported formats are</li> </ul> <dl> <dd> <ul> <li>ASCII (plain text)</li> <li>HTML</li> <li>XML</li> </ul> </dd> </dl> </dd> </dl> <p>Click <strong>Count</strong> to begin counting words</p> <h5><span id="Results-13">Results</span></h5> <p>The results of the word count are shown, for example, in the “Word Count Results – Fuzzy Matches per Class” window (see Figure 53).<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:FuzzyCountResult.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/8/87/FuzzyCountResult.gif" alt="FuzzyCountResult.gif" width="1065" height="184"></a></p> <p><em><strong>Figure 55. Word Count Results – Fuzzy Matches per Class window</strong></em></p> <p>The window contains the following columns:</p> <ul> <li><strong>Documents</strong></li> </ul> <dl> <dd>The name of the documents.</dd> </dl> <ul> <li><strong>Total</strong></li> </ul> <dl> <dd>The number of words in the documents.</dd> </dl> <ul> <li><strong>Class-zero</strong></li> </ul> <dl> <dd>The number of words in segments with fuzzy matches where no source words are different.</dd> </dl> <ul> <li><strong>Class-1</strong></li> </ul> <dl> <dd>The number of words in segments with fuzzy matches where one source word is different.</dd> </dl> <ul> <li><strong>Class-2</strong></li> </ul> <dl> <dd>The number of words in segments with fuzzy matches where two source words are different.</dd> </dl> <ul> <li><strong>Class-3</strong></li> </ul> <dl> <dd>The number of words in segments with fuzzy matches where three source words are different.</dd> </dl> <ul> <li><strong>Class-4</strong></li> </ul> <dl> <dd>The number of words in segments with fuzzy matches where four source words are different.</dd> </dl> <ul> <li><strong>Class-5</strong></li> </ul> <dl> <dd>The number of words in segments with fuzzy matches where five source words are different.</dd> </dl> <ul> <li><strong>Class-6up</strong></li> </ul> <dl> <dd>The number of words in segments with fuzzy matches where six or more source words are different.</dd> </dl> <p>If you selected the output option, the results are stored in the same format in the specified file.</p> <p>To return to the previous window, close the respective “Word Count Result – Fuzzy Matches per Class” window.</p> <h3><span id="Dealing_with_specific_document_formats">Dealing with specific document formats</span></h3> <p><strong>OpenTM2</strong> can work with documents that originate from a variety of word processors and formats.</p> <p>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 <strong>OpenTM2</strong>, you may be able to use these conversion facilities to convert your file to a format that is supported directly by <strong>OpenTM2</strong>.</p> <p>Sometimes, it can be helpful to have a printed version of the original document available to get a better picture of the whole document.</p> <p>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.</p> <h4><span id="Ami_Pro_documents">Ami Pro documents</span></h4> <p><strong>OpenTM2</strong> directly supports the document format of Ami Pro Version 2 or 3, which usually has the file extension SAM. Import such documents using the EQFAMI markup table. If they were designed for processing by Lotus ^(R) Notes ^(TM), import them using the LOTUSAMI markup table.</p> <p>Do not change, delete, or insert markup data outside translatable segments. Inline tags should be handled carefully.</p> <p>The start of highlighting like bold, italics, underline, or similar is indicated with <strong><+</strong>, any character, and <strong>></strong>. The end of this markup data is indicated with <strong><-</strong>, the same character as at the start of this markup tag, and <strong>></strong>.</p> <p>Tables, headers, and footers appear at the beginning of the document for translation.</p> <h4><span id="ANSI_documents">ANSI documents</span></h4> <p><strong>OpenTM2</strong> provides the following markup tables to import different ANSI (Windows ISO 8859-x) documents:</p> <ul> <li>EQFALINE for files in which everything is translatable.</li> <li>EQFAQUOT for files in which translatable text is enclosed in single quotes.</li> <li>EQFAMRI for files in which translatable text is enclosed in double quotes.</li> <li>EQFANSI for ANSI documents. This markup table is combined with a user exit.</li> </ul> <p>The EQFALINE markup table is used for ANSI documents that are completely translatable. In such documents, each line is translated separately. This means that text segmentation is based on a line basis. Such documents do not contain comments.</p> <p>The EQFAQUOT markup table is used for files in which translatable text is enclosed in single quotes (‘) and the EQFAMRI markup table for files in which translatable text is enclosed in double quotes (“). Comments, which are not translatable, begin with two backslashes (\\) and end with the end of the current line or begin with \* and end with *\. In the latter case, comments can span several lines. Replacement variables that start with a percent sign (%) and have a well-defined format like %8.8s or %ld, are not translatable.</p> <h4><span id="ASCII_documents">ASCII documents</span></h4> <p><strong>OpenTM2</strong> provides the following markup tables to import different ASCII documents, which are text files without any formatting tags:</p> <ul> <li>EQFLINE for files in which everything is translatable</li> <li>EQFQUOTE for files in which translatable text is enclosed in single quotes</li> <li>EQFMRI for files in which translatable text is enclosed in double quotes</li> <li>EQFASCII for ASCII documents</li> </ul> <p>The EQFLINE markup table is used for ASCII documents that are completely translatable. In such documents, each line is translated separately. This means that text segmentation is based on a line basis. Such documents do not contain comments.</p> <p>The EQFQUOTE markup table is used for files in which translatable text is enclosed in single quotes (‘) and the EQFMRI markup table for files in which translatable text is enclosed in double quotes (“). Comments that are not translatable begin with two backslashes (\\) and end with the end of the current line or begin with \* and end with *\. In the latter case, comments can span several lines. Replacement variables that start with a percent sign (%) and have a well-defined format like %8.8s or %ld, are not translatable.</p> <h4><span id="Assembler_documents">Assembler documents</span></h4> <p><strong>OpenTM2</strong> allows you to translate text contained in Assembler files, that is, information that is enclosed by single quotes. For example:</p> <pre>*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 OpenTM2 on one line'</pre> <p>Import these documents into a <strong>OpenTM2</strong> folder, using the EQFASM markup table.</p> <p>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.</p> <h4><span id="BookMaster_R_and_Information_Presentation_Facility_documents">BookMaster (R) and Information Presentation Facility documents</span></h4> <p>Import these documents using the EQFBOOK markup table.</p> <h4><span id="FrameBuilder_files">FrameBuilder files</span></h4> <p><strong>OpenTM2</strong> supports FrameBuilder Version 5.5 files, which usually have the file extension MIF. Import these files using the EQFFRBLD markup table.</p> <h4><span id="HTML_documents">HTML documents</span></h4> <p>Import HTML level 2.0 and 3.0 documents using the EQFHTML2 markup table and level 4.0 documents using EQFHTML4. The latter markup table is combined with a user exit.</p> <h4><span id="Interleaf_files">Interleaf files</span></h4> <p><strong>OpenTM2</strong> supports Interleaf (ASCII) files, which usually have a file extension of DOC. Import these files using the EQFINT2 markup table.</p> <h4><span id="LotusARANotesATMAdocuments">Lotus ^(R) Notes ^(TM) documents</span></h4> <p>Import Lotus ^(R) Notes ^(TM) documents using the LOTUSNGD markup table.</p> <h4><span id="MicrosoftARAPowerPointARAdocuments">Microsoft ^(R) PowerPoint ^(R) documents</span></h4> <p>Import Microsoft ^(R) PowerPoint ^(R) documents using the EQFPPT markup table.</p> <h4><span id="MicrosoftARAWord_for_WindowsARAdocuments">Microsoft ^(R) Word for Windows ^(R) documents</span></h4> <p><strong>OpenTM2</strong> supports the following document formats of Microsoft ^(R) Word for Windows ^(R):</p> <ul> <li>Word Version 2.0</li> <li>Word Version 6.0</li> <li>Word Version 7.0 (Word 97)</li> <li>Word Version 8.0 (Word 98)</li> <li>Word Version 9.0 (Word 2000)</li> </ul> <p>Import these documents using the EQFMSWRD markup table.</p> <p><strong>Note: </strong>The markup tables EQFWORD and EQFWORD6 are no longer supported. Therefore, analyze existing Word documents again using the new markup table EQFMSWRD.</p> <h4><span id="RTF_documents">RTF documents</span></h4> <p>Rich Text Format (RTF) is a document format supported by many word processors. Import these documents using the EQFRTF markup table.</p> <p>Select <strong>Check for changes of inline tags</strong> 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.</p> <h4><span id="SGML_documents">SGML documents</span></h4> <p>Import SGML documents that were designed for processing by Lotus ^(R) Notes ^(TM) using the EQFSGML markup table.</p> <h4><span id="Unicode_documents">Unicode documents</span></h4> <p>Unicode enables you to display, and work with, documents in <strong>OpenTM2</strong> that have different character sets, such as German and Japanese, or different code pages.</p> <p>OpenTM2 provides the following markup tables to import Unicode documents:</p> <ul> <li>EQFUTF8 for files which are encoded in UTF-8 format</li> <li>UNICODE for files which are encoded in UTF-16 format</li> </ul> <dl> <dd>To use Unicode you must import the documents using the UNICODE or the EQFUTF8 markup table.</dd> </dl> <h4><span id="WindowsARAhelp_files">Windows ^(R) help files</span></h4> <p>These files are used to define help texts for programs running under Windows ^(R). They can be saved as RTF documents.</p> <p>Import these documents using the EQFRTF markup table.</p> <h4><span id="WordPerfect_documents">WordPerfect documents</span></h4> <p><strong>OpenTM2</strong> 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 <strong>OpenTM2</strong> using the EQFWP (for WordPerfect Version 5.x documents) or EQFWP6 (for WordPerfect Version 6.0 and 6.1 documents) markup table.</p> <p>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.</p> <p><strong>Note: </strong>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.</p> <h3><span id="Deleting_a_document">Deleting a document</span></h3> <p>When you delete a document, you also delete the translated version of the document. However, segments you have translated are preserved in the <strong>Translation Memory</strong>.</p> <h5><span id="Prerequisites-10">Prerequisites</span></h5> <p>The folder containing the document must be open.</p> <h5><span id="Calling_sequence-12">Calling sequence</span></h5> <p>Select:</p> <ol> <li>One or more documents from the “Document List” window of the appropriate folder. To delete all documents in a folder, choose <strong>Select all </strong>from the <strong>File</strong> menu.</li> <li> <strong>Delete </strong>from the <strong>File </strong>menu.</li> </ol> <p>You must confirm that you want to delete each selected document.</p> <h5><span id="Results-14">Results</span></h5> <p>The documents are deleted.</p> <h3><span id="Exporting_a_document">Exporting a document</span></h3> <p>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.</p> <p>To transfer a document to another <strong>OpenTM2</strong> user, it is recommended that you export it in OpenTM2 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.</p> <p>For proofreading or validation the translated document can be exported as validation document</p> <p>In addition, you can export translated glossary terms contained in a document to a Lotus ^(R) Notes ^(TM) database.</p> <p>You can start the export procedure from within <strong>OpenTM2</strong>, 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 <a title="Working with documents" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_documents#Exporting_documents">Exporting documents</a>.</p> <h5><span id="Prerequisites-11">Prerequisites</span></h5> <p>The “Document List” window of the respective folder is active.</p> <h5><span id="Calling_sequence-13">Calling sequence</span></h5> <p>Select:</p> <ol> <li>One or more documents from the “Document List” window</li> <li> <strong>Export </strong>from the<strong> File</strong> menu</li> </ol> <p>The “Export Documents” window is displayed.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7m.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/c/cd/Eqfb7s7m.gif" alt="Eqfb7s7m.gif" width="606" height="509"></a></p> <p><em><strong>Figure 56. Export Documents window</strong></em></p> <h4><span id="Exporting_a_document_in_OpenTM2_format">Exporting a document in OpenTM2 format</span></h4> <h5><span id="Calling_sequence-14">Calling sequence</span></h5> <p>To export a document that is in <strong>OpenTM2</strong> format, select <strong>OpenTM2 Format</strong> from <strong>Export as</strong>. The “<strong>OpenTM2</strong> Format” page is displayed.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7l.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/5/5c/Eqfb7s7l.gif" alt="Eqfb7s7l.gif" width="606" height="509"></a></p> <p><em><strong>Figure 57. Export Documents window (OpenTM2 format)</strong></em></p> <h5><span id="Options_and_parameters-9">Options and parameters</span></h5> <ul> <li><strong>Export</strong></li> </ul> <dl> <dd>This box contains a list of the documents you selected in the “Document List” window.</dd> </dl> <ul> <li><strong>To</strong></li> </ul> <p>Specify the drive to which you want to export the documents. You can also click <strong>Browse</strong> to display the “Browse for Folder” window on which you can select the appropriate drive.</p> <p>Click <strong>Export</strong> to start document export.</p> <h5><span id="Results-15">Results</span></h5> <p>The document is exported and stored in <strong>OpenTM2</strong> on the selected drive on your workstation in a separate subdirectory of the <tt>\eqf\export</tt> path under the file name you specified. For example, if the document <tt>device.html</tt> is exported from the folder <tt>samplehtml3</tt>, it is stored as <tt>\eqf\export\samplehtml3.f00\device.html</tt>. The document can be passed to other <strong>OpenTM2</strong> users for further processing.</p> <h4><span id="Exporting_a_document_in_external_format">Exporting a document in external format</span></h4> <p>You use the external format to distribute a translated document for checking, for example.</p> <h5><span id="Calling_sequence-15">Calling sequence</span></h5> <p>To export a document in external format, select <strong>External Format</strong> from <strong>Export as</strong>. The “External Format” page is displayed.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7m.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/c/cd/Eqfb7s7m.gif" alt="Eqfb7s7m.gif" width="606" height="509"></a></p> <p><em><strong>Figure 58. Export Documents window (External format)</strong></em></p> <h5><span id="Options_and_parameters-10">Options and parameters</span></h5> <ul> <li><strong>Export</strong></li> </ul> <dl> <dd>This box contains a list of the documents you selected in the “Document List” window.</dd> </dl> <ul> <li><strong>Translation</strong></li> </ul> <p>Select this option to export the documents in their translated version.</p> <ul> <li><strong>Path</strong></li> </ul> <dl> <dd>Type the path name where you want the translated documents to be stored on the selected drive. Use a trailing backslash (\). You can also click <strong>Browse</strong> to display the “Browse for Folder” window on which you can select the appropriate path.</dd> </dl> <ul> <li><strong>With revision marks</strong></li> </ul> <dl> <dd>Select this option to have the parts of the exported document that have been newly translated marked. Revision marks can be individually defined by you. To specify a set of revision marks to be used, do one of the following:</dd> </dl> <dl> <dd> <ul> <li>Type the name of an existing set of revision marks or a new name.</li> <li>Select an existing name from the list box.</li> </ul> </dd> </dl> <dl> <dd> To change an existing set of revision marks or to define new revision marks, click <strong>Edit…</strong>. This takes you to the “Edit Revision Marks” window where you define your revision marks (see <a title="Working with documents" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_documents#Editing_document_revision_marks_for_export">Editing document revision marks for export</a>). </dd> </dl> <ul> <li><strong>Original</strong></li> </ul> <dl> <dd>Select this option to export the documents in their original version.</dd> </dl> <ul> <li><strong>Path</strong></li> </ul> <dl> <dd>Type the path name on the selected drive where you want the original document to be stored. Use a trailing backslash (\). You can also click <strong>Browse</strong> to display the “Browse for Folder” window on which you can select the appropriate path.</dd> </dl> <ul> <li><strong>Untranslated segments</strong></li> </ul> <dl> <dd>You can select this option only if you selected <strong>Create file containing untranslated segments</strong> during analysis, which generates a file containing untranslated segments. Select this option if you want to export this file.</dd> </dl> <dl> <dd>This exported file is in the format of an external <strong>Translation Memory</strong> with empty target segments. You can transfer this file to a machine translation system to translate these segments automatically.</dd> </dl> <dl> <dd> <strong>Note: </strong>The machine translation system must first be programmed to recognize the source and target language segments in the external format of the <strong>Translation Memory</strong>.</dd> </dl> <dl> <dd>After the empty target segments have been completed by the machine translation system, you can import the file into <strong>OpenTM2</strong> as a <strong>Translation Memory</strong> and use it to translate the rest of the document. The proposals offered in the <strong>Translation Memory</strong> window are then preceded by an <em>[m]</em> (generated by <strong>m</strong>achine).</dd> </dl> <ul> <li><strong>Path</strong></li> </ul> <dl> <dd>You must type the path name on the selected drive where you want the untranslated segments file to be stored. Use a trailing backslash (\). You can also click <strong>Browse</strong> to display the “Browse for Folder” window in which you can select the appropriate path.</dd> </dl> <p>Click <strong>Export</strong> to start document export.</p> <h5><span id="Results-16">Results</span></h5> <p>The document is exported in external format and stored as an HTML file in the directory under the file name you specified. The document can then be further processed with the corresponding word-processing system.</p> <h4><span id="Exporting_a_document_in_external_format_with_a_path">Exporting a document in external format with a path</span></h4> <p>You can export a document in external format with its entire path information. You use this format to distribute a translated document for checking, for example, using the relative path information of the document to build the fully qualified name for the document to be exported.</p> <h5><span id="Calling_sequence-16">Calling sequence</span></h5> <p>To export a document in external format, select <strong>External Format with relative path</strong> from <strong>Export as</strong>. The “External Format with relative path” page is displayed.</p> <p><a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7n.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/e/e7/Eqfb7s7n.gif" alt="Eqfb7s7n.gif" width="606" height="509"></a></p> <p><em><strong>Figure 59. Export Documents window (External format with path information)</strong></em></p> <h5><span id="Options_and_parameters-11">Options and parameters</span></h5> <p>The page displayed differs from the “External” page in only one field, <strong>Start path</strong> instead of <strong>Path</strong>. The following sections describe only this field. For an explanation of all other fields, refer to <a title="Working with documents" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_documents#Exporting_a_document_in_external_format">Exporting a document in external format</a>.</p> <ul> <li><strong>Start path</strong></li> </ul> <dl> <dd>Type the path name on the selected drive where you want the translated or original document to be stored. Use a trailing backslash (\). The path that you specify in this field will also be stored as part of its name. For example, if the document name is vers\docs\device.html and the start path is \target\, the document is exported under \target\vers\docs\device.html.</dd> </dl> <h5><span id="Results-17">Results</span></h5> <p>The document is exported in external format under its name and path information and stored as an HTML file in the directory under the file name you specified. The document can then be further processed with the corresponding word-processing system.</p> <p>If the path that you specified does not exist yet, you are asked whether you want to create the new path. If you are exporting one document, click <strong>Yes</strong>. If you are exporting several documents and the path is to apply to all documents, click <strong>Yes to All</strong>.</p> <h4><span id="Exporting_a_document_in_validation_format">Exporting a document in validation format</span></h4> <p>You can export a document in validation format for proofreading or translation validation.</p> <h5><span id="Calling_sequence-17">Calling sequence</span></h5> <p>To export a document in validation format, select <strong>Validation Format</strong> from <strong>Export as</strong>.</p> <p><a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Export_Documents_Validation_format.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/e/e5/Export_Documents_Validation_format.gif" alt="Export Documents Validation format.gif" width="726" height="561"></a></p> <p><em><strong>Figure 60. Export Documents window (Validation format)</strong></em></p> <h5><span id="Options_and_parameters-12">Options and parameters</span></h5> <ul> <li><strong>Path</strong></li> </ul> <dl> <dd>Type the path name on the selected drive where you want the validation document to be stored. Use a trailing backslash (\). You can also click <strong>Browse</strong> to display the “Browse for Folder” window on which you can select the appropriate path.</dd> </dl> <ul> <li><strong>Name</strong></li> </ul> <dl> <dd>Type the name of the validation document. When no name is specified, the name of the document is used as name for the validation document. In combined mode the name of the folder is used. The name can only be specified when only one document has been selected or when all documents are combined into one validation document. You can also click <strong>Browse</strong> to display the “Select validation document name” window on which you can select the appropriate document name.</dd> </dl> <ul> <li><strong>Format</strong></li> </ul> <dl> <dd> <ul> <li>HTML:</li> </ul> <dl> <dd>Use the HTML file format if you want to <strong>display</strong> the validation or proofreading document in the browser. No further modifications can be applied to this file format.</dd> </dl> <ul> <li>XML:</li> </ul> <dl> <dd>Use the XML file format if you either want to display the validation or proofreading document in the browser by applying a style sheet or if you want to process the XML file using custom tools.</dd> </dl> <ul> <li>DOC:</li> </ul> <dl> <dd>Use the DOC file format if you want to <strong>display and edit</strong> the validation or proofreading document in MS WORD or even in Open Office. Further processing is possible e.g. by using TRACK CHANGES or by using ADD COMMENTS. These functions are dedicated to MS WORD or Open Office.</dd> </dl> <ul> <li>ODT:</li> </ul> <dl> <dd>Use the ODT file format if you want to <strong>display and edit </strong>the validation or proofreading document in Lotus Symphony or in Open Office.</dd> </dl> </dd> </dl> <ul> <li><strong>Combine into one document</strong></li> </ul> <dl> <dd>Select this option to combine all exported documents into one file. The name of the folder is used for the combined document. Note: this option is only active when more than one document is selected for the export.</dd> </dl> <ul> <li><strong>Type of Validation Document</strong></li> </ul> <dl> <dd> <ul> <li>Export for Validation:</li> </ul> <dl> <dd>This format is dedicated for <strong>validation</strong> purposes only. Validators request a dedicated format of the output which supports dedicated tasks and information. Please refer to the header of the generated document which contains detailed information for validators. Compared to the proofreading format users can’t adjust the output by exporting single match types, the output is more static.</dd> </dl> <ul> <li>Export for Proofreading:</li> </ul> <dl> <dd>This format is dedicated for <strong>proofreading</strong> purposes only. Proofreaders request a dedicated format of the output which supports dedicated tasks and information. Compared to the validation format users can adjust the output by exporting single match types.</dd> </dl> </dd> </dl> <ul> <li><strong>Remove inline tagging from text</strong></li> </ul> <dl> <dd>When the “Remove inline tagging from text” option is selected, all inline (neutral) tags contained in the segments are removed from the validation/proofreading document.</dd> </dl> <ul> <li><strong>Preserve links and images</strong></li> </ul> <dl> <dd>When the “Preserve links and images “links in the document are left as active links within the validation document and images are converted to image links. This option works independently from the “”Remove inline tagging from the text “option.</dd> </dl> <ul> <li><strong>Include word count info</strong></li> </ul> <dl> <dd>Check this option to add a column containing the number of source words of this segments to the proofreading document.</dd> </dl> <ul> <li><strong>Include existing match info</strong></li> </ul> <dl> <dd>Check this option to show information on the memory proposals which were available at the time the segment was translated.</dd> </dl> <ul> <li><strong>Show mismatches only</strong></li> </ul> <dl> <dd>Check this option to show only segments where the available memory proposals were not used by the translator; e.g. the segment was translated manually although an exact match existed.</dd> </dl> <ul> <li><strong>Colors used in Validation Documents =====</strong></li> </ul> <dl> <dd> <ul> <li>gray : protected segments</li> <li>green : segments with an extract match</li> <li>yellow : segments with fuzzy matches</li> <li>orange : segments with machine matches or replacement matches</li> <li>red : segments without matches</li> </ul> </dd> </dl> <p><a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Valformat.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/9/91/Valformat.gif" alt="Valformat.gif" width="1236" height="602"></a></p> <p><em><strong>Figure 61. Proofreading example</strong></em></p> <p>Match type options:</p> <ul> <li><strong>Auto Substituted</strong></li> </ul> <dl> <dd>Select this option to include segments which have been substituted automatically into the validation document.</dd> </dl> <ul> <li><strong>Exact</strong></li> </ul> <dl> <dd>Select this option to include segments which have been translated using an exact match into the validation document.</dd> </dl> <ul> <li><strong>Modified Exact</strong></li> </ul> <dl> <dd>Select this option to include segments which have been translated using an exact match which has been modified manually into the validation document.</dd> </dl> <ul> <li><strong>Machine</strong></li> </ul> <dl> <dd>Select this option to include segments which have been translated using a machine translation into the validation document.</dd> </dl> <ul> <li><strong>Replace</strong></li> </ul> <dl> <dd>Select this option to include segments which have been translated using a replace match into the validation document.</dd> </dl> <ul> <li><strong>Fuzzy</strong></li> </ul> <dl> <dd>Select this option to include segments which have been translated using a fuzzy match into in the validation document.</dd> </dl> <ul> <li><strong>New</strong></li> </ul> <dl> <dd>Select this option to include segments which have been translated manually into the validation document.</dd> </dl> <ul> <li><strong>Not Translated</strong></li> </ul> <dl> <dd>Select this option to include segments which have not been translated into the validation document.</dd> </dl> <ul> <li><strong>Protected</strong></li> </ul> <dl> <dd>Select this option to include protected (= not translatable) segments into the validation document.</dd> </dl> <ul> <li><strong>Select All / Deselect All</strong></li> </ul> <dl> <dd>Click <strong>Select All</strong> to select all match types, click <strong>Deselect All</strong> to deselect all match types.</dd> </dl> <h5><span id="Results-18">Results</span></h5> <p>The document is exported as a validation document.</p> <p>If the path that you specified does not exist yet, you are asked whether you want to create the new path. If you are exporting one document, click <strong>Yes</strong>. If you are exporting several documents and the path is to apply to all documents, click <strong>Yes to All</strong>.</p> <h4><span id="Exporting_a_document_in_plain_XML_format">Exporting a document in plain XML format</span></h4> <p>You can export a document in XML format for processing the segments of the document with other tools.</p> <h5><span id="Calling_sequence-18">Calling sequence</span></h5> <p>To export a document in validation format, select <strong>Plain XML Format</strong> from <strong>Export</strong> as.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:XMLDocExport.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/5/59/XMLDocExport.gif" alt="XMLDocExport.gif" width="726" height="561"></a></p> <p><em><strong>Figure 62. Export Documents window (Plain XML format)</strong></em></p> <h5><span id="Options_and_parameters-13">Options and parameters</span></h5> <ul> <li><strong>Path</strong></li> </ul> <dl> <dd>Type the path name on the selected drive where you want the XML document to be stored. Use a trailing backslash (\). You can also click <strong>Browse</strong> to display the “Browse for Folder” window on which you can select the appropriate path.</dd> </dl> <ul> <li><strong>Name</strong></li> </ul> <dl> <dd>Type the name of the XML document. When no name is specified, the name of the document is used as name for the XML document. In combined mode the name of the folder is used. The name can only be specified when only one document has been selected or when all documents are combined into one XML document. You can also click <strong>Browse</strong> to display the “Select XML document name” window on which you can select the appropriate document name.</dd> </dl> <ul> <li><strong>Combine into one document</strong></li> </ul> <dl> <dd>Select this option to combine all exported documents into one file. The name of the folder is used for the combined document. Note: this option is only active when more than one document is selected for the export. Have been substituted automatically into the validation document.</dd> </dl> <h5><span id="Results-19">Results</span></h5> <p>The document is exported as a XML document. If the path that you specified does not exist yet, you are asked whether you want to create the new path. If you are exporting one document, click Yes. If you are exporting several documents and the path is to apply to all documents, click <strong>Yes to All</strong>.</p> <h4><span id="Exporting_translated_glossary_terms_to_a_LotusARANotesATMAdatabase">Exporting translated glossary terms to a Lotus ^(R) Notes ^(TM) database</span></h4> <p>You can export translated glossary terms that are contained in a document to a Lotus ^(R) Notes ^(TM) database.</p> <h5><span id="Calling_sequence-19">Calling sequence</span></h5> <p>To export the terms to Lotus ^(R) Notes ^(TM), select <strong>Lotus </strong>^(R)<strong> DGW</strong> from <strong>Export as</strong>.</p> <p>The “Lotus ^(R) DGW” page is displayed.</p> <p><a href="http://www.beo-doc.de/opentm2wiki/index.php/File:LotusDocExport.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/8/82/LotusDocExport.gif" alt="LotusDocExport.gif" width="718" height="601"></a></p> <p><em><strong>Figure 63. Export Documents window (Lotus Notes)’</strong></em></p> <h5><span id="Options_and_parameters-14">Options and parameters</span></h5> <ul> <li><strong>Mark term as approved</strong></li> </ul> <dl> <dd>Select this option if all the terms to be exported are to be marked as approved.</dd> </dl> <p>Click <strong>Export</strong> to start the export.</p> <h5><span id="Results-20">Results</span></h5> <p>The translated glossary terms are exported and stored in a Lotus ^(R) Notes ^(TM) database.</p> <h4><span id="Editing_document_revision_marks_for_export">Editing document revision marks for export</span></h4> <p>During export, <strong>OpenTM2</strong> can insert revision marks in translated documents.</p> <p>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 <strong>Translation Memory</strong> proposals for these segments into the new document. These segments usually need no further checking because they originate from a previous translation.</p> <p>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 “<strong>Translation Memory</strong>” window and subsequently changed.</p> <p>You can choose which segment categories you want to mark.</p> <h5><span id="Prerequisites-12">Prerequisites</span></h5> <ul> <li>The “Export Documents” window must be active, and you must export the documents in external format.</li> <li>The export options<strong> Translation </strong>and <strong>With revision marks </strong>must have been selected.</li> </ul> <h5><span id="Calling_sequence-20">Calling sequence</span></h5> <p>Click <strong>Edit…</strong> in the “Export Documents” window</p> <p>The “Edit Revision Marks” window is displayed.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7k.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/1/18/Eqfb7s7k.gif" alt="Eqfb7s7k.gif" width="341" height="360"></a></p> <p><em><strong>Figure 64. Edit Revision Marks window</strong></em></p> <h5><span id="Options_and_parameters-15">Options and parameters</span></h5> <ul> <li><strong>Name</strong></li> </ul> <dl> <dd>If this field is still empty, type a name for the revision marks.</dd> </dl> <ul> <li><strong>Description</strong></li> </ul> <dl> <dd>Type a text to describe the set of revision marks; this is optional.</dd> </dl> <p>You can mark the following types of segments with revision marks:</p> <ul> <li>Segments that have been translated from scratch without using a proposal from the Translation Memory (<strong>… translated from scratch</strong>)</li> <li>Segments that have been copied from a Translation Memory proposal and then changed <strong>(… modified proposal</strong>)</li> <li>Segments that have been copied from a Translation Memory proposal but not changed (<strong>… unmodified proposal</strong>)</li> </ul> <p><strong>OpenTM2</strong> lets you choose different symbols for marking the beginning and the end of each type of segment in the <strong>Begin text</strong> and <strong>End text</strong> fields. You can type, for example:</p> <ul> <li>Tags that produce symbols when the exported document is formatted and printed.</li> <li>Control characters that change the font type when the exported document is formatted and printed. Control characters are only recognized by certain word processors or printers.</li> <li>Eye-catching characters, such as a string of asterisks (****** ).</li> </ul> <p>Click <strong>Save</strong> to return to the “Export Documents” window.</p> <h5><span id="Results-21">Results</span></h5> <p>The set of revision marks is saved under the name you specified in the <strong>Name</strong> field. Documents exported in external format are marked accordingly. To see the result of the revision marks, browse the exported document file with a text editor or, if applicable, print the document.</p> <p><strong>Note: </strong>When you have marked the translations with the revision mark, you are recommended not to import these documents in <strong>OpenTM2</strong> again, because the revision marks might be misinterpreted.</p> <p>It is recommended to export the revised and finalized translation again without revision marks.</p> <h3><span id="Importing_a_document">Importing a document</span></h3> <p>You must import a document into <strong>OpenTM2</strong> before you can work with it.</p> <p>A <strong>OpenTM2</strong> document can be in one of the following formats:</p> <ul> <li> <strong>OpenTM2</strong> format</li> </ul> <dl> <dd>This format can be received from another <strong>OpenTM2</strong> user who previously exported the document in <strong>OpenTM2</strong> format. When you import a document into <strong>OpenTM2</strong>, you receive the current status of both the original and translated version of the documents.</dd> </dl> <ul> <li>External format (with and without relative path)</li> </ul> <dl> <dd>This format is produced by word-processing systems, such as WordPerfect or Microsoft ^(R) Word for Windows ^(R).When you import a document in external format you can decide whether you want to import it either under its name only or under its name and path information. Name and path uniquely identify a document in a folder. If you import a document under its name and path, you can have several documents in a folder with the same name, provided that the path differs.</dd> </dl> <p>In addition, you can extract glossary terms from a Lotus ^(R) Notes ^(TM) database and import them as a document into <strong>OpenTM2</strong>.</p> <h5><span id="Prerequisites-13">Prerequisites</span></h5> <p>The active window is the “Document List” window of the folder into which the document is to be imported.</p> <h5><span id="Calling_sequence-21">Calling sequence</span></h5> <p>Select <strong>Import…</strong> from the <strong>File</strong> menu. The “Import Documents” window is displayed.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7t.GIF"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/b/b2/Eqfb7s7t.GIF" alt="Eqfb7s7t.GIF" width="606" height="430"></a></p> <p><em><strong>Figure 65. Import Documents window</strong></em></p> <h4><span id="Importing_a_document_in_OpenTM2_format">Importing a document in OpenTM2 format</span></h4> <h5><span id="Calling_sequence-22">Calling sequence</span></h5> <p>To import a document that is in <strong>OpenTM2</strong> format, select <strong>OpenTM2 Format</strong> from <strong>Import from</strong>.</p> <p>The “<strong>OpenTM2</strong> Format” page is displayed.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7f.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/3/34/Eqfb7s7f.gif" alt="Eqfb7s7f.gif" width="606" height="430"></a></p> <p><em><strong>Figure 66. Import Documents window (OpenTM2 format)</strong></em></p> <h5><span id="Options_and_parameters-16">Options and parameters</span></h5> <ul> <li><strong>From</strong></li> </ul> <dl> <dd>To specify the current location of the documents:</dd> </dl> <dl> <dd> <ul> <li>Specify the drive where the documents to be imported currently reside. You can also click <strong>Browse </strong>to display the “Browse for Folder” window on which you can select the appropriate drive.</li> <li>Double-click the folder containing the documents to be imported, in the <strong>Folders l</strong>ist.</li> <li>Click one or more document names in the <strong>Documents</strong> list.</li> </ul> </dd> </dl> <p>To import all documents listed in the <strong>Documents</strong> list, click <strong>Select all</strong>.</p> <p>To start a new selection of documents, click <strong>Deselect all</strong>.</p> <ul> <li><strong>To folder</strong></li> </ul> <p>Shows the name of the folder to which you want to import the documents.</p> <p>All files contained in the selected folder are listed in <strong>Documents</strong>. Select the documents you want to import, then click <strong>Import</strong> to start the import procedure.</p> <h5><span id="Results-22">Results</span></h5> <p>The selected documents are imported and you can start analyzing and translating.</p> <h4><span id="Importing_a_document_in_external_format">Importing a document in external format</span></h4> <h5><span id="Calling_sequence-23">Calling sequence</span></h5> <p>To import a document produced by word-processing systems, select <strong>External Format</strong> from <strong>Import from</strong>.</p> <p>The “External Format” page is displayed.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7o.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/4/40/Eqfb7s7o.gif" alt="Eqfb7s7o.gif" width="606" height="430"></a></p> <p><em><strong>Figure 67. Import Documents window (External format)</strong></em></p> <h5><span id="Options_and_parameters-17">Options and parameters</span></h5> <ul> <li><strong>From</strong></li> </ul> <p>To specify the current location of the documents:</p> <dl> <dd> <ul> <li>Specify the path in which the documents to be imported currently reside. You can also click <strong>Browse</strong> to display the “Browse for Folder” window on which you can select the appropriate path.</li> <li>Type the <strong>Name</strong> of the document to be imported. You can use global file name characters in this field as follows:Type only the common part of the file name in the <strong>Name</strong> field to display a subset of the available files in the <strong>Files</strong> 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 <strong>Name</strong> field and press Enter.</li> <li>The <strong>Documents</strong> list displays the files that match the specification you have entered in the<strong> Name</strong> field. Select the files you want to import as documents.</li> </ul> </dd> </dl> <p>To import all documents listed in the <strong>Documents</strong> list box, click <strong>Select all</strong>.</p> <p>To start a new selection of documents, click <strong>Deselect all</strong>.</p> <ul> <li><strong>To folder</strong></li> </ul> <dl> <dd>Shows the name of the folder to which you want to import the documents.</dd> </dl> <p>All selected files are listed in <strong>Documents</strong>. Select the documents you want to import, then click <strong>Import</strong> to start the import procedure.</p> <p>The “Document Properties” window is displayed for the first document.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7g.GIF"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/5/56/Eqfb7s7g.GIF" alt="Eqfb7s7g.GIF" width="531" height="444"></a></p> <p><em><strong>Figure 68. Document Properties window</strong></em></p> <h5><span id="Options_and_parameters-18">Options and parameters</span></h5> <p>If you import documents with the same properties as the folder, you do not specify anything in this window. Click <strong>Change</strong> to import the document.</p> <p>If several documents are selected for importing, you must specify the properties for each document to be imported.<br> On the “Settings” page, specify:</p> <ul> <li><strong>Alias</strong></li> </ul> <dl> <dd>An alias name for the document. Such a name is useful if you want to get the same exact matches from the <strong>Translation Memory</strong> as for another document that you already translated. You then assign the name of the other document as alias name for this document. Assume, for example, that document docupdate is an update of docnew and you want to get the same exact matches from the <strong>Translation Memory</strong> that docnew received. In this case, you would assign docnew as the alias name to docupdate.</dd> </dl> <dl> <dd>If an alias name exists, <strong>OpenTM2</strong> uses this name instead of the actual document name to access the correct <strong>Translation Memory</strong>.</dd> </dl> <p>The same alias name can be assigned to several documents. An alias name can have up to 256 characters.</p> <ul> <li><strong>Folder settings</strong></li> </ul> <dl> <dd>In this box, the properties are displayed that are already defined for the folder in general:</dd> </dl> <dl> <dd> <ul> <li>Translation Memory</li> </ul> <dl> <dd>The name of an existing <strong>Translation Memory</strong> </dd> </dl> </dd> </dl> <dl> <dd> <ul> <li>Markup</li> </ul> <dl> <dd>The name of an existing markup table</dd> </dl> </dd> </dl> <dl> <dd> <ul> <li>Source language</li> </ul> <dl> <dd>The name of a supported source language</dd> </dl> </dd> </dl> <dl> <dd> <ul> <li>Target language</li> </ul> <dl> <dd>The name of a supported target language</dd> </dl> </dd> </dl> <dl> <dd> <ul> <li>Editor</li> </ul> <dl> <dd>The editor used for the documents in the folder</dd> </dl> </dd> </dl> <dl> <dd> <ul> <li>Conversion</li> </ul> <dl> <dd>The code page used for the documents in the folder</dd> </dl> </dd> </dl> <ul> <li><strong>Document settings</strong></li> </ul> <dl> <dd>Each document can have its own properties and can be different from those of the folder.If you import a document for the first time, the boxes in this group are empty.</dd> </dl> <p>If you import a document that already exists in the folder, the properties that you specified for the first import and that differ from the folder properties are displayed as default values, which you can change.</p> <p>If the document has the same properties as the folder, you do not have to enter anything, and the document <em>inherits</em> the folder properties. Document properties that are different from the folder properties can be selected from the respective list boxes:</p> <dl> <dd> <ul> <li>Translation Memory</li> </ul> <dl> <dd>The name of an existing <strong>Translation Memory</strong> </dd> </dl> </dd> </dl> <dl> <dd> <ul> <li>Markup</li> </ul> <dl> <dd>The name of an existing markup table</dd> </dl> </dd> </dl> <dl> <dd> <ul> <li>Source language</li> </ul> <dl> <dd>The name of a supported source language</dd> </dl> </dd> </dl> <dl> <dd> <ul> <li>Target language</li> </ul> <dl> <dd>The name of a supported target language</dd> </dl> </dd> </dl> <dl> <dd> <ul> <li>Editor</li> </ul> <dl> <dd>The editor to be used for the imported document</dd> </dl> </dd> </dl> <dl> <dd> <ul> <li>Conversion</li> </ul> </dd> <dd>The code page to be used for the imported document</dd> </dl> <ul> <li><strong>Use settings for remaining documents</strong></li> </ul> <dl> <dd>This option is only displayed if you want to import more than one document. If you want to assign the same properties to all documents, select this option.</dd> </dl> <p>For information on the “Admin” page, refer to <strong>Admin page</strong> described in <a title="Working with documents" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_documents#Changing_the_properties_of_a_document">Changing the properties of a document</a>.</p> <p>To save the specified properties, click <strong>Change</strong>.</p> <h5><span id="Results-23">Results</span></h5> <p>The selected documents are imported and you can start analyzing and translating.</p> <h4><span id="Importing_a_document_in_external_format_with_a_path">Importing a document in external format with a path</span></h4> <p>You can import a document in external format with its entire path information. You can then have several documents in a folder that have the same name provided that the path differs.</p> <h5><span id="Calling_sequence-24">Calling sequence</span></h5> <p>To import a document produced by word-processing systems, select <strong>External Format with relative path</strong> from <strong>Import from</strong>.</p> <p>The “External Format with relative path” page is displayed.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7p.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/c/c8/Eqfb7s7p.gif" alt="Eqfb7s7p.gif" width="606" height="430"></a></p> <p><em><strong>Figure 69. Import Documents window (External format with path information)</strong></em></p> <h5><span id="Options_and_parameters-19">Options and parameters</span></h5> <ul> <li><strong>Start path</strong></li> </ul> <dl> <dd>Specify the drive on which the documents to be imported reside or specify the entire path in which they are stored. What you specify depends on which path information you want to become part of the documents’ name. If you do not want the full path information become part of the documents’ name, type the directory to be omitted in this field. For example, if you do not want directory tm to be part of the documents’ name, type TM in the <strong>Start path</strong> field. Document part01.doc is then imported under the name project\part01.doc.</dd> </dl> <p>You can also select the path from the “Browse for Folder” window after clicking <strong>Browse</strong>.</p> <ul> <li><strong>Name</strong></li> </ul> <dl> <dd>Type the name of the document to be imported. You can use global file name characters in this field as follows:</dd> </dl> <dl> <dd>Type only the common part of the file name 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 <strong>Name</strong> field and then press Enter. The files list then lists all documents whose name matches your specifications. The name of the documents listed also contains the path information that you did not specify in the <strong>Start path</strong> field and therefore becomes part of the documents’ name.</dd> </dl> <ul> <li><strong>Files</strong></li> </ul> <dl> <dd>Displays the files that match the specifications you entered in the <strong>Start path</strong> and <strong>Name</strong> fields.</dd> </dl> <ul> <li><strong>To folder</strong></li> </ul> <dl> <dd>Shows the name of the folder to which you want to import the documents.</dd> </dl> <p>Select the documents you want to import from the files list. To import all documents listed in the files list, click <strong>Select all</strong>. To start a new selection of documents, click <strong>Deselect all</strong>. Click <strong>Import</strong> to start the import procedure.</p> <p>The “Document Properties” window is displayed for the first document (see <a title="Working with documents" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_documents#Importing_a_document_in_external_format">Figure 68</a>). For more information about the contents of this window, refer to <a title="Working with documents" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_documents#Importing_a_document_in_external_format">Importing a document in external format</a>.</p> <h5><span id="Results-24">Results</span></h5> <p>The selected documents are imported. If you left the <strong>Start path</strong> field empty, the documents are imported under their name and full path information. If you specified a path in the <strong>Start path</strong> field, the path information of the imported documents excludes the specified path.</p> <p>You can now start analyzing and translating the imported documents.</p> <h4><span id="Importing_glossary_terms_from_a_LotusARANotesATMAdatabase">Importing glossary terms from a Lotus ^(R) Notes ^(TM) database</span></h4> <p>You can import the glossary terms of a Lotus ^(R) Notes ^(TM) database into <strong>OpenTM2</strong>. The name of the document’s markup table is always LOTUSNGD.</p> <h5><span id="Calling_sequence-25">Calling sequence</span></h5> <p>To import the glossary terms from Lotus ^(R) Notes ^(TM), select <strong>Lotus </strong>^(R)<strong> DGW</strong> from <strong>Import from</strong>.</p> <p>The “Lotus ^(R) DGW” page is displayed.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7u.GIF"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/5/50/Eqfb7s7u.GIF" alt="Eqfb7s7u.GIF" width="606" height="430"></a></p> <p><em><strong>Figure 70. Import Documents window (Lotus Notes)</strong></em></p> <h5><span id="Options_and_parameters-20">Options and parameters</span></h5> <ul> <li><strong>Server</strong></li> </ul> <dl> <dd>Select or specify the server on which the database containing the glossary terms is located.</dd> </dl> <ul> <li><strong>Databases</strong></li> </ul> <dl> <dd>Displays all databases available on the selected server. Click a database to select it.</dd> </dl> <ul> <li><strong>File name</strong></li> </ul> <dl> <dd>Displays the database that you selected in <strong>Databases</strong>.</dd> </dl> <ul> <li><strong>Source language</strong></li> </ul> <dl> <dd>Select the source language of the glossary terms.</dd> </dl> <ul> <li><strong>Target language</strong></li> </ul> <dl> <dd>Select the target language of the glossary terms.</dd> </dl> <ul> <li><strong>Extract untranslated terms only</strong></li> </ul> <dl> <dd>Select this option if you want to import only the terms that have not been translated yet.</dd> </dl> <p>Click <strong>Import</strong> to start the import.</p> <h5><span id="Results-25">Results</span></h5> <p>The glossary terms are extracted from the specified Lotus ^(R) Notes ^(TM) database and are stored in a document in the SOURCE directory of the target folder. The name of the document is equal to that of the Lotus ^(R) Notes ^(TM) database.</p> <h3><span id="Copying_and_moving_documents_between_folders">Copying and moving documents between folders</span></h3> <p>You can copy or move one or more documents in a folder to another folder. This is an alternative to exporting and then importing documents, and it is recommended if you deal with a large number of documents. The advantage of this method is that you use the Windows-like multiple-select and drag-and-drop techniques to copy or move documents. Nevertheless, internally OpenTM2 exports the selected documents to a temporary directory and imports them into the target folder. OpenTM2 maintains the history log files of the source and target folders, as described in <strong>Results</strong>.</p> <h5><span id="Prerequisites-14">Prerequisites</span></h5> <p>The source folder containing at least one document must be open, and the corresponding “Document List” window must be shown. The “Document List” window with the target folder must be open. You can also have your folder list displayed in the Explorer-like tree view. Make sure that the target folder is visible.</p> <h5><span id="Calling_sequence-26">Calling sequence</span></h5> <ol> <li>Select one or more documents in the “Document List”window that you want to copy or move. Do this by holding down the Ctrl key and clicking the documents. To select a series of documents, use the Alt key respectively.</li> <li>If you want to drag and drop the selected documents to the target folder: <ol> <li>To move the documents, drag them to the target folder. Note the small drag icon.</li> <li>To copy the documents, press SHIFT and drag them to the target folder. Note the small plus symbol beside the drag icon, indicating a copy operation.</li> </ol> </li> <li>If you want to use the move/copy menu: <ol> <li>With the documents still selected, click right on the document.</li> <li>Open the target folder</li> <li>Click <strong>PASTE</strong> </li> <li><strong>Select document list window</strong></li> <li>Right mouse click on document list window</li> <li>Click <strong>Copy</strong> respectively <strong>Move</strong> (The button corresponds to your previous selection.)</li> </ol> </li> </ol> <h5><span id="Results-26">Results</span></h5> <p>The selected documents are copied or moved to the selected target folder.</p> <p>The history log files of the source and target folder are updated as follows:</p> <ul> <li>The history log entries of the selected documents from the source folder are merged into the target folder’s history log. They are not deleted from the source folder’s history log.</li> <li>The target folder’s history log gets an entry that indicates that the documents were copied, respectively moved, with the “copy/move”function.</li> <li>The source folder’s history log only gets an entry when documents were moved, indicating this fact.</li> </ul> <h3><span id="Opening_a_document">Opening a document</span></h3> <p>You must open a document before you can start translating.</p> <p>If the selected document has not been analyzed, <strong>OpenTM2</strong> automatically analyzes the document based on the properties of the document and the folder. For more information on the analysis, see<a title="Working with documents" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_documents#Analyzing_a_document">Analyzing a document</a>.</p> <h5><span id="Prerequisites-15">Prerequisites</span></h5> <p>The “Document List” window of the respective folder is active.</p> <h5><span id="Calling_sequence-27">Calling sequence</span></h5> <p>Select:</p> <ol> <li>The document from the “Document List” window</li> <li> <strong>Open</strong> from the <strong>File </strong>menu</li> </ol> <p>Alternatively, double-click the document in the “Document List” window.</p> <p>You are taken to the <strong>Translation Environment</strong>, where the selected document is contained in the “Translation” window.</p> <h5><span id="Results-27">Results</span></h5> <p>The document is segmented and you can start translating it.</p> <p>To leave the <strong>Translation Environment</strong>, you must close the document.</p> <h3><span id="Searching_and_replacing_text_in_documents">Searching and replacing text in documents</span></h3> <p>OpenTM2 provides a Global Find and Replace function, which works across all or some documents of a folder.</p> <p>This function might be helpful if you are looking for a particular piece of text of which source document you are not sure . Also, you may need to change a particular wording, but do not want to type the new text manually at each occurrence. OpenTM2 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.</p> <p>Note that OpenTM2 searches and replaces only pieces of text that can be translated. Markup tags cannot be changed. You can control whether OpenTM2 searches in protected text areas, like inline tags, for translatable text. This is helpful if you want to include markup tag attribute values in the search process.</p> <h5><span id="Prerequisites-16">Prerequisites</span></h5> <p>The folder must exist, and its documents must have been analyzed.</p> <h5><span id="Calling_sequence-28">Calling sequence</span></h5> <p>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.</p> <p>Select:</p> <ol> <li>One or more documents you want to have searched through from the “Document List” window</li> <li> <strong>Global Find and Replace… </strong>from <strong>the File menu</strong> </li> </ol> <p>The “Global Find and Replace” window is displayed.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:GlobalFind.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/e/e7/GlobalFind.gif" alt="GlobalFind.gif" width="806" height="508"></a></p> <p><em><strong>Figure 71. Global Find and Replace window</strong></em></p> <h5><span id="Options_and_parameters-21">Options and parameters</span></h5> <ul> <li><strong>Find</strong></li> </ul> <dl> <dd>the text for which you are looking. You can also select one of the last five terms that you searched for.</dd> </dl> <dl> <dd>If you are searching for 2 or more terms combined with AND, all terms must be contained in the same segment to form a match.</dd> </dl> <dl> <dd>If you are searching for several terms combined with OR, either one of the terms must be contained in the same segment to form a match.</dd> </dl> <dl> <dd>If a search term is negated with the NOT operator, a segment will only match if the negated term is not contained in the segment.</dd> </dl> <dl> <dd> <strong>Note: </strong>You can use wildcards. * is the placeholder for multiple characters, ? is the placeholder for a single character.</dd> </dl> <dl> <dd> <strong>Note: </strong>If a search string contains AND / OR / NOT enclose the search string between double quotes. If you want to search terms containing double quotes the search term has to be enclosed in double quotes and the double quote being searched has to be duplicated. e.g. if you want to search for the term <em>Null”</em> (“Null” followed by a double quote) the term has to be entered as <em>“Null”””</em> in the find field.</dd> </dl> <ul> <li><strong>Replace with</strong></li> </ul> <dl> <dd>To change the term you are searching for to another term, type the term with which you want to replace the term that you specified in the <strong>Find</strong> box. You can also select one of your last five replacements.</dd> </dl> <dl> <dd> <strong>Note: </strong>You can only replace terms in translated segments.</dd> </dl> <ul> <li><strong>Case</strong></li> </ul> <dl> <dd>Specify whether the search should <strong>respect</strong> or <strong>ignore</strong> case sensitivity.</dd> </dl> <ul> <li><strong>Documents</strong></li> </ul> <dl> <dd>Displays the list of documents that are to be searched.</dd> </dl> <ul> <li><strong>Update Translation Memory</strong></li> </ul> <dl> <dd>Select this box if you want your changes to be reflected in the Translation Memory. Any changed text segment is then updated in the Translation Memory associated to the folder.</dd> </dl> <ul> <li><strong>Confirm on replace</strong></li> </ul> <dl> <dd>Select this check box if you want OpenTM2 to stop before a text is changed. You are then prompted to confirm the change.</dd> </dl> <ul> <li><strong>Find in translatable text only</strong></li> </ul> <dl> <dd>Select this check box if you want OpenTM2 to search the text you are looking for in translatable text only.</dd> </dl> <dl> <dd>If this check box is not selected, OpenTM2 searches also in protected text areas, like inline tags, for translatable text. This process might locate markup tag attribute values.</dd> </dl> <ul> <li><strong>Whole words only</strong></li> </ul> <dl> <dd>Select this check box if you want to find whole words only, not occurrencies where the Find string is part of a word.</dd> </dl> <dl> <dd>If this check box is not selected, the Find term is also found if it is part of a word</dd> </dl> <ul> <li><strong>Wildcard for single characters</strong></li> </ul> <dl> <dd>Select here the character to be used as wildcard for single characters or de-activate the single character wildcard by selecting “None”. When used in the search string the wildcard character matches any character of the document.</dd> </dl> <dl> <dd>Example: assuming that “?” has been selected as wildcard for single characters, the search string “f?r” will match the following words: “fur”, “for” but not the words “father”, “feather”, “fr”</dd> </dl> <ul> <li><strong>Wildcard for multiple characters</strong></li> </ul> <dl> <dd>Select here the character to be used as wildcard for multiple characters or de-activate the multiple character wildcard by selecting “None”. When used in the search string the wildcard character matches none, one or more characters in the document.</dd> </dl> <dl> <dd>Example: assuming that “*” has been selected as wildcard for multiple characters, the search string “f*r” will match the following words: “four”, “father”, “feather”, “fr”, “for”</dd> </dl> <ul> <li><strong>Display box</strong></li> </ul> <dl> <dd>This area shows a part of the document containing the found piece of text. The found part is highlighted. You are also informed about the name of the document and the number of the segment containing the piece of text.</dd> </dl> <dl> <dd>For easier perception of found text the lines are wrapped if they exceed the available width. You can enlarge the text area by enlarging the “Global Find and Replace” window. This retains the dialog control elements, but dynamically resizes the available window space for the text area.</dd> </dl> <ul> <li><strong>Find</strong></li> </ul> <dl> <dd>Starts the search for the term that you specified in the <strong>Find</strong> box in the first document listed and displays a small portion of the document in which the first occurrence of the term is found, in the text area. The term found is highlighted. You can then select either of the following:</dd> </dl> <dl> <dd> <ul> <li> <strong>Open document </strong>to view the entire document in which the term was found.</li> <li> <strong>Find </strong>to move to the next occurrence of the term, which can be in the same or in another document to be searched. Select this button until you have reached the end of the last document to be searched or you want to stop searching.</li> </ul> </dd> </dl> <ul> <li><strong>Replace</strong></li> </ul> <dl> <dd>If you selected the <strong>Confirm on change</strong> check box, a small portion of the document in which the first occurrence of the term is found is displayed in the display box and the found term is highlighted. You can then select one of the following:</dd> </dl> <dl> <dd> <ul> <li> <strong>Open document </strong>to view the entire document in which the term was found.</li> <li> <strong>Find </strong>to move to the next occurrence of the term without changing the term. The next occurrence can be in the same or in another document to be searched.</li> </ul> </dd> </dl> <dl> <dd>If you did not select the <strong>Confirm on change</strong> check box, all occurrences of the term are replaced without you being asked to confirm the changes.</dd> </dl> <dl> <dd>If you selected the <strong>Update Translation Memory</strong> check box, changes to translated segments are reflected in the Translation Memory associated with the folder.</dd> </dl> <ul> <li><strong>Cancel</strong></li> </ul> <dl> <dd>Stops the search and the interaction with this window and returns you to the starting point. Any changes you have made are not saved.</dd> </dl> <ul> <li><strong>Help</strong></li> </ul> <dl> <dd>Gives information to help you interact with this window.</dd> </dl> <h5><span id="Results-28">Results</span></h5> <p>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.</p> <h5><span id="Examples">Examples</span></h5> <ul> <li><strong>“and”</strong></li> </ul> <dl> <dd>Finds all occurrences of the string and. The double quotes around the term are required as and is a logical operator</dd> </dl> <ul> <li><strong>IBM and not SAP</strong></li> </ul> <dl> <dd>Finds all occurrences of the string <strong>IBM</strong> in segments which do not contain the term <strong>SAP</strong> </dd> </dl> <ul> <li><strong>f*r</strong></li> </ul> <dl> <dd>Finds all occurrences of strings starting with <strong>f</strong> and ending with <strong>r</strong>, e.g. for, fur, futur, fair, far</dd> </dl> <ul> <li><strong>f?r</strong></li> </ul> <dl> <dd>Finds all occurrences of strings starting with <strong>f</strong> followed by one other character followed and ending with <strong>r</strong>, e.g. for, far, fur</dd> </dl> <ul> <li><strong>“one”””</strong></li> </ul> <dl> <dd>Finds all occurrences of the term <strong>one</strong> followed by a double quote</dd> </dl> <ul> <li><strong>“”””</strong></li> </ul> <dl> <dd>Finds all occurrences of a single double quote</dd> </dl> <h3><span id="Search_segments_with_fuzzy_matches">Search segments with fuzzy matches</span></h3> <p>OpenTM2 provides a Search Segments with Fuzzy Matches function, which works across all or some documents of a folder or across a group of folders.</p> <p>This function might be helpful in the pre-translation process to identify segments which can be easily translated by using a fuzzy memory proposal and change some tagging or a few words.</p> <p>Note that OpenTM2 searches and replaces only pieces of text that can be translated. Markup tags cannot be changed. You can control whether OpenTM2 searches in protected text areas, like inline tags, for translatable text. This is helpful if you want to include markup tag attribute values in the search process.</p> <h5><span id="Prerequisites-17">Prerequisites</span></h5> <p>The folder must exist, and its documents must have been analyzed.</p> <h5><span id="Calling_sequence-29">Calling sequence</span></h5> <p>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.</p> <p>Select:</p> <ol> <li>One or more documents you want to have searched through from the “Document List” window</li> <li>from the menu</li> </ol> <p>The “Search Segments With Fuzzy matches” window is displayed.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:FuzzySearch.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/1/10/FuzzySearch.gif" alt="FuzzySearch.gif" width="1065" height="580"></a></p> <p><em><strong>Figure 72. Search Segments With Fuzzy matches window</strong></em></p> <h5><span id="Options_and_parameters-22">Options and parameters</span></h5> <ul> <li><strong>Search fuzzy matches up to</strong></li> </ul> <dl> <dd>Select here the class of the segments with fuzzy matches being searched.</dd> </dl> <dl> <dd>The class is the number of different words between the segment and the memory proposal.</dd> </dl> <dl> <dd>Differences in white spaces and inline tagging are ignored.</dd> </dl> <ul> <li><strong>Search results</strong></li> </ul> <dl> <dd>In this area the results of the search are displayed.</dd> </dl> <dl> <dd>For each entry the folder name, the document name, the segment number, the segment data and the source of the memory proposal is shown.</dd> </dl> <dl> <dd>The differences between the segment text and the memory proposal are highlighted.</dd> </dl> <ul> <li><strong>Start search</strong></li> </ul> <dl> <dd>Starts the search for segments with fuzzy matches.The segments which match the selected class are displayed in the result area.</dd> </dl> <ul> <li><strong>Stop search</strong></li> </ul> <dl> <dd>Stops the current search.</dd> </dl> <ul> <li><strong>Open document</strong></li> </ul> <dl> <dd>Opens the document which contains the selected segment and makes the segment the active one. Opens the document which contains the selected segment and makes the segment the active one.You can also open the document and position to the segment by double-clicking the entry in the result list.</dd> </dl> <ul> <li><strong>Cancel</strong></li> </ul> <dl> <dd>Stops the search and the interaction with this window and returns you to the starting point.Help Gives information to help you interact with this window.</dd> </dl> <h5><span id="Results-29">Results</span></h5> <p>The segments matching the selected class are displayed in the result area. Results displayed in the Search Segments With Fuzzy matches window (see <a title="Working with documents" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_documents#Search_segments_with_fuzzy_matches">Search segments with fuzzy matches</a>).<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:FuzzySearchResult.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/c/cb/FuzzySearchResult.gif" alt="FuzzySearchResult.gif" width="806" height="535"></a></p> <p><em><strong>Figure 73. Search Segments With Fuzzy matches window</strong></em></p> <h3><span id="Spellchecking_a_document">Spellchecking a document</span></h3> <p>A translated document can contain typing errors or misspelled words. <strong>OpenTM2</strong> offers a spellchecking function you can use at any time during translation.</p> <p>Spellchecking is supported for all languages for which language support is installed. For each misspelled word, <strong>OpenTM2</strong> shows a correction proposal, which you can accept, overwrite, or skip.</p> <p>Note that only the spelling of translated segments is checked.</p> <h5><span id="Prerequisites-18">Prerequisites</span></h5> <p>The language support file for the target language of the document must be installed. No spellchecking is supported for the following languages: Romanian, Slovene, Croation, Slovakian, Lithuania, Latvia, Estonia.</p> <h5><span id="Calling_sequence-30">Calling sequence</span></h5> <p>If you are not already in the <strong>Translation Environment</strong>, start it by selecting:</p> <ol> <li>A document from the “Document List” window</li> <li> <strong>Open </strong>from the <strong>File </strong>menu</li> <li>The “Translation” window</li> <li> <strong>File… </strong>from <strong>the Spellcheck menu</strong> </li> </ol> <p>The Spellcheck function starts immediately at the beginning of the translated document, and the “Spellcheck” window is displayed.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7h.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/0/0b/Eqfb7s7h.gif" alt="Eqfb7s7h.gif" width="506" height="202"></a></p> <p><em><strong>Figure 74. Spellcheck window</strong></em></p> <h5><span id="Options_and_parameters-23">Options and parameters</span></h5> <ul> <li><strong>Misspelled word</strong></li> </ul> <dl> <dd>The first word in the document that is misspelled or not in the language support file.</dd> </dl> <ul> <li><strong>Similar Words</strong></li> </ul> <dl> <dd>A list of correctly spelled alternatives for the misspelled word. Double-click the correctly spelled word to select it. Or, click <strong>Skip</strong> to continue with the next misspelled word without selecting any of the alternatives. For some words, this list may be empty.</dd> </dl> <ul> <li><strong>Change to</strong></li> </ul> <dl> <dd>The word selected as the correctly spelled one. You can overtype it if you need a new spelling.</dd> </dl> <p>You can accept a spelling in several ways. Select:</p> <ul> <li><strong>Change</strong></li> </ul> <dl> <dd>To accept the spelling in the <strong>Change to</strong> field.</dd> </dl> <ul> <li><strong>Addendum</strong></li> </ul> <dl> <dd>To add a new spelling to the target language support file. Then this spelling will not be shown as misspelled anymore.</dd> </dl> <ul> <li><strong>Temp Add</strong></li> </ul> <dl> <dd>To add the new spelling temporarily to the target language support file. When you leave <strong>OpenTM2</strong>, this new spelling is not saved.</dd> </dl> <p>When all misspelled words have been either changed or skipped, a message appears telling you that spellchecking is complete.</p> <h5><span id="Results-30">Results</span></h5> <p>The corrections you accepted are substituted for the misspelled words in both the document and the <strong>Translation Memory</strong>.</p> <h3><span id="Editing_the_spellcheck_addendum">Editing the spellcheck addendum</span></h3> <p>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.</p> <h5><span id="Prerequisites-19">Prerequisites</span></h5> <p>The document must be translated, and you must be in the Translation Environment.</p> <h5><span id="Calling_sequence-31">Calling sequence</span></h5> <p>Select <strong>Edit addendum terms…</strong> from the <strong>Spellcheck</strong> menu.</p> <p>The “Edit Addendum Terms” window is displayed.</p> <h5><span id="Options_and_parameters-24">Options and parameters</span></h5> <p>The terms in the addendum can be modified as follows:</p> <ul> <li>To change a term, overtype it.</li> <li>To add a term, press Enter, and type the new term.</li> <li>To remove a term, mark it and press Enter.</li> </ul> <p>Clipboard operations (cut, copy, paste) are supported. To save your changes, select <strong>Save</strong>. To leave the window without saving your changes, select <strong>Cancel</strong>.</p> <h5><span id="Results-31">Results</span></h5> <p>The corrections you made are saved and taken into account during subsequent spellchecks.</p> <h3><span id="Translating_a_document">Translating a document</span></h3> <p>To prepare the translation of documents you can generate terminology lists, for example, to add new terms to a dictionary or generate a <strong>Translation Memory</strong> from previous translations.</p> <p>To translate the documents, the <strong>Translation Environment</strong> 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.</p> <p>When you translate several documents on the same subject, the <strong>Translation Memory</strong> used will grow, and the number of translation proposals will increase.</p> <h5><span id="Prerequisites-20">Prerequisites</span></h5> <ul> <li>The document must have been imported.</li> <li>To begin translating a document, it must be opened.</li> </ul> <h5><span id="Calling_sequence-32">Calling sequence</span></h5> <p>Select:</p> <ul> <li>The document to be translated from the “Document List” window</li> <li> <strong>Open </strong>from the <strong>File </strong>menu</li> </ul> <p>The <strong>Translation Environment</strong> 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.</p> <h5><span id="Options_and_parameters-25">Options and parameters</span></h5> <p>For information on how to use the editor functions, see <a title="Working with the OpenTM2 Editor" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_the_OpenTM2_Editor">Working with the OpenTM2 Editor</a>.</p> <h5><span id="Results-32">Results</span></h5> <p>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 <strong>OpenTM2</strong> users who can continue the translation.</p> <p>When you have completed the translation of the segments of a document, <strong>OpenTM2</strong> automatically switches to the postediting mode where you can review the translation and check the spelling. The<strong>Translation Memory</strong> 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.</p> <h3><span id="Opening_and_translating_several_documents">Opening and translating several documents</span></h3> <p>You can open several documents and translate them in parallel in the Translation Environment.</p> <p>If the selected documents have not been analyzed, <strong>OpenTM2</strong> automatically analyzes them based on the properties of the documents and the folder. For more information on the analysis, see <a title="Working with documents" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_documents#Analyzing_a_document">Analyzing a document</a>.</p> <h5><span id="Prerequisites-21">Prerequisites</span></h5> <p>The “Document List” window of the respective folder is active.</p> <h5><span id="Calling_sequence-33">Calling sequence</span></h5> <p>You have two choices:</p> <ul> <li>You select several documents from the “Document List” window and then <strong>Open </strong>from the <strong>File</strong> menu.</li> <li>You open one or more documents while translating using <strong>Open… </strong>from the <strong>File </strong>menu (see <a title="Working with the OpenTM2 Editor" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_the_OpenTM2_Editor#Viewing_other_documents_while_translating">Viewing other documents while translating</a>. </li> </ul> <h5><span id="Results-33">Results</span></h5> <p>In either case, the opened documents are displayed in the “Translation” window together with the respective dictionary and <strong>Translation Memory</strong>. If you used the first choice, the document selected first is the active one. If you used the second choice, the document opened last is the active one.</p> <p>You can switch to another opened document by either clicking it or by selecting it from the <strong>Translation Environment</strong> option from the <strong>File</strong> menu.</p> <p>You can close the opened documents one by one.</p> <h3><span id="Viewing_the_properties_of_a_document">Viewing the properties of a document</span></h3> <p>The main properties of a document are:</p> <ul> <li> <strong>Translation Memory</strong>The <strong>Translation Memory</strong> to be used for the translation of the document.</li> <li> <strong>Source language</strong> The language of the original document.</li> <li> <strong>Target language</strong> The language of the translated document.</li> <li> <strong>Editor</strong> The editor associated with the document.</li> <li> <strong>Markup table</strong> The markup table associated to the document. The markup table is used during analysis and translation of the document.</li> </ul> <h5><span id="Prerequisites-22">Prerequisites</span></h5> <p>The document must be in a folder.</p> <h5><span id="Calling_sequence-34">Calling sequence</span></h5> <p>Select:</p> <ol> <li>A document from the “Document List”window</li> <li> <strong>Properties Summary… </strong>from the <strong>File </strong>menu</li> </ol> <h5><span id="Results-34">Results</span></h5> <p>A document in HTML format is displayed containing a summary of the document properties.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Docpropertywindow.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/d/d3/Docpropertywindow.gif" alt="Docpropertywindow.gif" width="504" height="520"></a></p> <p><em><strong>Figure 75. Document Properties document</strong></em></p> <p>If you want to view more properties or change the properties of a document, refer to <a title="Working with documents" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_documents#Changing_the_properties_of_a_document">Changing the properties of a document</a>.</p> <h3><span id="Changing_the_properties_of_a_document">Changing the properties of a document</span></h3> <p>The properties must be defined individually for each document when you import documents in external format. They can be changed later.</p> <h5><span id="Prerequisites-23">Prerequisites</span></h5> <p>The document must be in a folder.</p> <h5><span id="Calling_sequence-35">Calling sequence</span></h5> <p>Select:</p> <ol> <li>A document from the “Document List” window</li> <li> <strong>Properties… </strong>from <strong>the File menu</strong> </li> </ol> <p>The “Document Properties” window is displayed.<br> <a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Eqfb7s7j.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/4/4a/Eqfb7s7j.gif" alt="Eqfb7s7j.gif" width="531" height="419"></a></p> <p><em><strong>Figure 76. Document Properties window</strong></em></p> <h5><span id="Options_and_parameters-26">Options and parameters</span></h5> <p>On the “Settings” page:</p> <ul> <li><strong>Short name</strong></li> </ul> <dl> <dd>This field shows the document short name. This name is the internally used file name of the document.</dd> </dl> <ul> <li><strong>Alias</strong></li> </ul> <dl> <dd>Either this field contains the alias name that you specified during the import of the document or you can specify an alias name here.</dd> </dl> <dl> <dd>An alias name is useful if you want to get the same exact matches from the <strong>Translation Memory</strong> as for another document that you already translated. You then assign the name of the other document as alias name for this document. Assume, for example, that document docupdate is an update of docnew and you want to get the same exact matches from the <strong>Translation Memory</strong>that docnew received. In this case, you would assign docnew as the alias name to docupdate.</dd> </dl> <dl> <dd>If an alias name exists, <strong>OpenTM2</strong> uses this name instead of the actual document name to access the correct <strong>Translation Memory</strong>.</dd> </dl> <dl> <dd>The same alias name can be assigned to several documents. An alias name can have up to 256 characters.</dd> </dl> <ul> <li><strong>Folder settings</strong></li> </ul> <dl> <dd>This box contains the properties that are specified for the folder in general. They cannot be changed in this window.</dd> </dl> <ul> <li><strong>Document settings</strong></li> </ul> <dl> <dd>This box contains the individual settings per document. Initially these boxes are empty.</dd> </dl> <dl> <dd>If the document has the same properties as the folder, you do not have to enter anything, and the document “inheritsâ€&#157; the folder properties. Document properties that are different from the folder properties can be selected from the respective list boxes. In the <strong>Translation Memory </strong>field, you can type the name of a new <strong>Translation Memory</strong>.</dd> </dl> <p>On the “Admin” page:</p> <ul> <li><strong>Folder administration</strong></li> </ul> <dl> <dd>Contains part of the information specified on the “Admin” page of the “Folder Properties” window. You cannot change any of the fields.</dd> </dl> <ul> <li><strong>Document administration</strong></li> </ul> <dl> <dd>Contains administration information about the document:</dd> </dl> <dl> <dd> <ul> <li>Translator’s name</li> </ul> <dl> <dd>If the document is still to be translated, specify or select the name of the person to receive this document next. This can be the actual translator or the vendor, for example. If the document is already translated and on its way back to the project coordinator, leave this field blank.</dd> </dl> </dd> </dl> <dl> <dd> <ul> <li>Translator’s e-mail</li> </ul> <dl> <dd>If the document is still to be translated, specify or select the e-mail address of the person to receive this document next. This can be the actual translator or the vendor, for example. If the document is already translated and on its way back to the project coordinator, leave this field blank.</dd> </dl> </dd> </dl> <dl> <dd> <ul> <li>Shipment number</li> </ul> <dl> <dd>Contains the shipment number assigned to the folder containing this document. You cannot change this field.</dd> </dl> </dd> </dl> <p>The “Statistics” page contains information about the translation status of the document. The data cannot be changed in this window.</p> <ul> <li><strong>Date of source file</strong></li> </ul> <dl> <dd>The date and time at which the source file was last modified outside OpenTM2.</dd> </dl> <ul> <li><strong>Size</strong></li> </ul> <dl> <dd>The number of bytes the document occupies on your disk.</dd> </dl> <ul> <li><strong>Translated</strong></li> </ul> <dl> <dd>The date and time at which translation was completed.</dd> </dl> <ul> <li><strong>Analyzed</strong></li> </ul> <dl> <dd>The date and time at which the document was analyzed.</dd> </dl> <ul> <li><strong>Date of export</strong></li> </ul> <dl> <dd>The date and time at which the document was last exported.</dd> </dl> <ul> <li><strong>Date of import</strong></li> </ul> <dl> <dd>The date and time at which the document was last imported.</dd> </dl> <ul> <li><strong>Last update</strong></li> </ul> <dl> <dd>The date and time at which the document was last updated in the <strong>Translation Environment</strong>.</dd> </dl> <ul> <li><strong>Completion rate</strong></li> </ul> <dl> <dd>The percentage to which the document is already translated.</dd> </dl> <ul> <li><strong>Changed segments</strong></li> </ul> <dl> <dd>The number of segments that were copied during the translation from the <strong>Translation Memory</strong> and then changed.</dd> </dl> <ul> <li><strong>New segments</strong></li> </ul> <dl> <dd>The number of segments that were entered entirely new without copying a match from the <strong>Translation Memory</strong>.</dd> </dl> <ul> <li><strong>Copied segments</strong></li> </ul> <dl> <dd>The number of segments that were copied from the <strong>Translation Memory</strong> and saved unchanged.</dd> </dl> <p>To save the specified properties for this document, click <strong>Change</strong>.</p> <h5><span id="Results-35">Results</span></h5> <p>The properties are saved for this document.</p> <h3><span id="Viewing_the_details_of_a_document">Viewing the details of a document</span></h3> <p>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.</p> <p>The details of a document are:</p> <ul> <li><strong>Name</strong></li> </ul> <dl> <dd>The name of the document</dd> </dl> <ul> <li><strong>Date of source file</strong></li> </ul> <dl> <dd>The date and time at which the source file was last modified outside OpenTM2.</dd> </dl> <ul> <li><strong>Translated</strong></li> </ul> <dl> <dd>The date when translation of the document was completed</dd> </dl> <ul> <li><strong>Analyzed</strong></li> </ul> <dl> <dd>The date when the document was analyzed</dd> </dl> <ul> <li><strong>Exported</strong></li> </ul> <dl> <dd>The date when the document was last exported</dd> </dl> <ul> <li><strong>Imported</strong></li> </ul> <dl> <dd>The date when the document was last imported</dd> </dl> <ul> <li><strong>Updated</strong></li> </ul> <dl> <dd>The date (and optionally the time) that the document was last updated</dd> </dl> <ul> <li><strong>Size</strong></li> </ul> <dl> <dd>The number of bytes of the original document</dd> </dl> <ul> <li><strong>Complete %</strong></li> </ul> <dl> <dd>The percentage of the document that has already been translated</dd> </dl> <ul> <li><strong>Changed</strong></li> </ul> <dl> <dd>The number of segments that were copied from the <strong>Translation Memory</strong> window during translation and subsequently changed</dd> </dl> <ul> <li><strong>Shipment</strong></li> </ul> <dl> <dd>The shipment number of the document</dd> </dl> <ul> <li><strong>Markup</strong></li> </ul> <dl> <dd>The markup table used for this document</dd> </dl> <ul> <li><strong>Translation Memory</strong></li> </ul> <dl> <dd>The <strong>Translation Memory</strong> used for this document</dd> </dl> <ul> <li><strong>Source language</strong></li> </ul> <dl> <dd>The language of the original document</dd> </dl> <ul> <li><strong>Target language</strong></li> </ul> <dl> <dd>The language into which the document is translated</dd> </dl> <ul> <li><strong>Editor</strong></li> </ul> <dl> <dd>The editor used for this document</dd> </dl> <ul> <li><strong>Alias</strong></li> </ul> <dl> <dd>The alias name for the document</dd> </dl> <ul> <li><strong>Source</strong></li> </ul> <dl> <dd>The last update date and time of the source document</dd> </dl> <ul> <li><strong>Name without path</strong></li> </ul> <dl> <dd>The document name without any path information</dd> </dl> <ul> <li><strong>Extension</strong></li> </ul> <dl> <dd>The file extension of the document</dd> </dl> <p>If nothing is specified for any of the last four items, <strong>OpenTM2</strong> assumes these properties to be the same as for the folder.</p> <p>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:</p> <ul> <li>Displaying the names only</li> <li>Displaying selected details</li> </ul> <p>You can change the arrangement of the document details in the “Change Details” window described in <a title="Working with OpenTM2 components and functions" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_OpenTM2_components_and_functions#Viewing_and_changing_the_details_of_a_list_item">Viewing and changing the details of a list item</a>.</p> <h3><span id="Including_notes_for_the_translator">Including notes for the translator</span></h3> <p><strong>OpenTM2</strong> enables you to include notes in the source document to be translated. Thus, you can give the translator hints, tips, or instructions. The author of the document might want to inform the translator about the specific meaning of an expression. Or the project coordinator might want to give the translator the correct translation for a word.</p> <p>Translator’s notes can be inserted at any place in a document. You can specify two levels of notes to emphasize different importance, which is then displayed with different colors, fonts, and indentation in the Translation Environment.</p> <h4><span id="Translator8217s_notes_in_a_source_document">Translator’s notes in a source document</span></h4> <p>OpenTM2 supports translator’s notes for document types that allow for annotations or hidden text that do not appear in a printed document. For example, SGML documents, BookMaster ^(R) documents, and word processors like Microsoft ^(R) Word for Windows ^(R) Version 6, and WordPerfect, allow for annotations.</p> <p>OpenTM2 uses this capability to nest translator’s notes inside annotations.</p> <p>The following example shows the source of a BookMaster ^(R) document any how the author has added an annotation and several translator’s notes. Note that :annot. and :eannot. are BookMaster ^(R)markup tags, which enclose an ordinary annotation. trnote1: and trnote2: are OpenTM2 extensions that start a level 1 and level 2 translator’s note. The latter need to be nested inside BookMaster ^(R)annotations.</p> <pre>...text... :annot. This is an ordinary BookMaster annotation from the author, not a translator's note. OpenTM2 ignores it. :eannot. ...text... :annot.trnote1: Important: Always translate "Insert" with "Einfuegen" in order to be consistent throughout the documentation and the menu items. :eannot. ...text... :annot.trnote2: If time: check for proper translation of "Manual change". :eannot.</pre> <p>If you just want to add translator’s notes, you can specify them by adding trnote1: or trnote2: markups inside annotation markups of a document. Both markups are identical for all supported document types. Upper case notation is supported.</p> <p>If you work with markup tables in more detail, note that the trnote1: and trnote2: markups are defined in the markup tables that support an annotation or hiding method.</p> <h4><span id="Translator8217s_notes_in_the_Translation_Environment">Translator’s notes in the Translation Environment</span></h4> <p>A note in a document is referred to by <strong><TRNOTE></strong> in the Translation Environment. You can view all translator’s notes contained in the currently displayed document in one of the following ways:</p> <ul> <li>Double-click <strong><TRNOTE></strong> </li> <li>Select <strong>Commands </strong>from the <strong>Options </strong>menu, select the <strong>TRNote window</strong> entry, and then press <strong>Run.</strong> </li> <li>Use the keys that you assigned to this command using the <strong>Keys </strong>dialog.</li> <li>Select the <strong>Translatior’s note</strong> entry from the <strong>File</strong> menu.</li> </ul> <p>You then get the “Translator’s Note” window containing all notes available in your current document. When you double-click a note in this window, the input focus is set on the segment next to the note.</p> <p><strong><TRNOTE></strong> is treated like any markup tag in <strong>OpenTM2</strong>:</p> <ul> <li>You can hide it or display it in shrink mode.</li> <li>You can change its name in the field on the “Display” page of the “Customize Translation Functions” window (see <a title="Working with the OpenTM2 Editor" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_the_OpenTM2_Editor#Setting_up_the_profile">Setting up the profile</a>). This changes the term in the Translation Environment, but has no effect on how translator’s notes are marked up in a source document. </li> <li>You can change its foreground and background colors. The defaults are black and cyan, respectively. You might want to change them if you work with documents that contain many translator’s notes, or notes that are difficult to perceive in context (see <a title="Working with the OpenTM2 Editor" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_the_OpenTM2_Editor#Customizing_colors_and_fonts">Customizing colors and fonts</a>). </li> <li>You can change its font, style, and size (if you work with the RTFEdit editor) to differentiate it from surrounding text (see <a title="Working with the OpenTM2 Editor" href="http://www.beo-doc.de/opentm2wiki/index.php/Working_with_the_OpenTM2_Editor#Customizing_colors_and_fonts">Customizing colors and fonts</a>). </li> </ul> <h3><span id="Preview_XML_documents">Preview XML documents</span></h3> <p>The markup table IBMXML is enabled to perform a XML-document preview. In order to preview the XML document, the steps described below should be followed. XML documents require a style sheet (*.XSL) document in order to be properly displayed. Import the XSL document into the folder and analyze it in order to be used by the preview function or select the XSL document from the hard disk drive.</p> <h4><span id="Step_by_step_description_to_preview_a_XML_document">Step by step description to preview a XML document</span></h4> <ol> <li>Import and analyze the XML document.</li> <li>Open the XML document in the translation editor.</li> <li>Either click on <strong>“Translateâ€&#157;- “Show Translationâ€&#157; </strong>or click on the preview-icon in the icon list.</li> <li>Window <em>Select XSL document from TM Folder</em> opens.</li> </ol> <p><a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Xslselection_neu.GIF"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/e/ed/Xslselection_neu.GIF" alt="Xslselection neu.GIF" width="631" height="380"></a></p> <p><em><strong>Figure 77. Select XSL document from TM Folder window</strong></em></p> <p> </p> <ol> <li>If the XSL document is part of the folder: <ol> <li>From select the XSL document which is required to preview the XML document.</li> <li>Optionally select a directory where additional files are stored on. This can be graphics, include files etc. Click on button <strong>“Browse…â€&#157; </strong>and select the appropriate directory in order to fill in the path-information to entry field <strong>“Misc. Filesâ€&#157; </strong>or manually type the path to the additional files.</li> <li>Click on <strong>“OKâ€&#157;</strong> and the preview window opens.</li> </ol> </li> <li>If the XSL document is not part of the folder: <ol> <li>Optionally select a directory where additional files are stored on. This can be graphics, include files etc. Click on button <strong>“Browse…â€&#157; </strong>and select the appropriate directory in order to fill in the path-information to entry field <strong>“Misc. Filesâ€&#157; </strong>or manually type the path to the additional files.</li> <li>Click on button <strong>“Select Non-TM XSLâ€&#157; </strong>in order to select the appropriate XSL-document from the hard disk drive. The preview starts automatically.</li> </ol> </li> </ol> <p><a href="http://www.beo-doc.de/opentm2wiki/index.php/File:Xslpreview.gif"><img loading="lazy" src="http://www.beo-doc.de/opentm2wiki/images/d/d8/Xslpreview.gif" alt="Xslpreview.gif" width="658" height="430"></a></p> <p><em><strong>Figure 78. Translation Preview window</strong></em></p> </div> </article> </div> </div> </div> </div> <footer id="colophon" class="site-footer" role="contentinfo"> <div class="menu-prin-footer-container"> <ul id="menu-prin-footer" class="menu"> <li id="menu-item-991" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-has-children menu-item-991"> <a href="/project/">Project</a> <ul class="sub-menu"> <li id="menu-item-992" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-has-children menu-item-992"> <a href="/project/about/">About</a> <ul class="sub-menu"> <li id="menu-item-1506" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-1506"> <a href="/enterprise/">Enterprise</a> </li> <li id="menu-item-1507" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-1507"> <a href="/language-service-provider/">Language Service Provider</a> </li> <li id="menu-item-1505" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-1505"> <a href="/translators/">Translators</a> </li> </ul> </li> <li id="menu-item-999" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-999"> <a href="/project/team/">The Team</a> </li> </ul> </li> <li id="menu-item-1000" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-1000"> <a href="/download/">Download</a> </li> <li id="menu-item-1004" class="menu-item menu-item-type-post_type menu-item-object-page current-page-ancestor menu-item-1004"> <a href="/documentation/">Documentation</a> </li> <li id="menu-item-1016" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-1016"> <a href="/support/">Support</a> </li> <li id="menu-item-1479" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-1479"> <a href="/issue-tracker/">Issue Tracker</a> </li> <li id="menu-item-1021" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-1021"> <a href="/contribute/">Contribute</a> </li> <li id="menu-item-1024" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-1024"> <a href="/contact-team/">Contact</a> </li> </ul> </div> </footer> </div> <script type="text/javascript" id="toc-front-js-extra"> /* <![CDATA[ */ var tocplus = {"visibility_show":"show","visibility_hide":"hide","width":"Auto"}; /* ]]> */ </script> <script type="text/javascript" src="/wp-content/plugins/table-of-contents-plus/front.min.js" id="toc-front-js"></script> <script type="text/javascript" src="/wp-content/themes/open2/js/small-menu.js" id="small-menu-js"></script> <script type="text/javascript" src="/wp-content/themes/open2/js/FlexSlider/jquery.flexslider-min.js" id="flex-script-js"></script> <script type="text/javascript" src="/wp-includes/js/wp-embed.min.js" id="wp-embed-js"></script> </body> </html>