SDL MultiTerm 2007 Release Notes

These release notes contain late-breaking information regarding this release of the MultiTerm system, and SDL strongly recommends that you read them in their entirety before starting to use the MultiTerm system and any of its related applications.

Copyright (c) 2005-2007 SDL International
Copyright (c) 1990-2005 TRADOS Incorporated.

Table of Contents

General Information

Copy Protection (FLEXlm)

Supported Platforms and Requirements

Software

Localization

How to Contact Us

Information for Upgrade Users

Upgrading from MultiTerm 95 Plus, MultiTerm 5, 5.5

Upgrading from MultiTerm iX (6.x)

Upgrading from MultiTerm 7/7.1

Applying MultiTerm 2007 SP1

Application Specific Information

Installation

MultiTerm

MultiTerm Convert

MS Office/SDL Trados 2007 Integration

MultiTerm Extract

MultiTerm Administrator

MultiTerm Server Console

MultiTerm Server

MultiTerm Anywhere

MultiTerm Online

General Information

Important: SDL MultiTerm 2007 cannot run with MultiTerm iX (version 6.x).

MultiTerm documentation

Updates and localized versions of the MultiTerm documentation will be posted on the SDL download center, for instance at www.translationzone.com/download.

Copy Protection (FLEXlm)

SDL MultiTerm Extract (including SDL PhraseFinder) and SDL MultiTerm Server (including SDL MultiTerm 2007 Team) are copy protected. They use a softkey mechanism for copy protection. The license information is stored in a license file that is used to monitor use of the application and impose any necessary license restrictions. If the license cannot be found, MultiTerm Extract runs in demo mode (see MultiTerm Extract) and MultiTerm Server does not allow users to access any remote termbases.

When you purchase MultiTerm 2007 Extract, MultiTerm 2007 Team, or MultiTerm 2007 Server you receive an email containing the login ID, password, and address (URL) for the SDL Customer Center web site. To obtain a license file, browse to the URL you received in the email, enter your login ID and password, and follow the directions to download your license file. See the SDL Customer Center Help for more information.

During installation of SDL MultiTerm, you need to specify the location of the downloaded license file or a license server. If you do not specify the license details during installation, you can use the MultiTerm Server Console or SDL License Console to add the information to MultiTerm or add the information when starting MultiTerm Extract. For more detailed information about how to apply the license file and connect to the SDL FLEXlm Licence Server, see the MultiTerm Administrator Guide or the MultiTerm Extract Tools Guide.

Note: The license file is hardware specific and the license only works for the dedicated computer. See the SDL Customer Center Help for more information about license files.

Supported Platforms and Requirements

• Hardware
  • The minimum specification to run any of the MultiTerm components is a PC with a 166 MHz Pentium or higher compatible processor. 64 MB RAM is required in addition to the RAM required by the operating system.
  • For optimum performance of the client components, SDL recommends using a Pentium II processor with 450 MHz or higher and at least 256 MB RAM.
  • More detailed information about recommended hardware system requirements for the server components is available in the MultiTerm Administrator Guide.
  • A mouse or similar pointing device is required and a DVD-ROM drive is required to install the MultiTerm client and server components from the product DVD.
  • 150 MB of disk space is required for the software and additional space is required for storing termbase data.
• Companion Software
  • The minimum requirement for termbase search and look-up in MultiTerm and the MultiTerm Online client browsers is Microsoft Internet Explorer 5.0. The minimum requirement for editing procedures is Microsoft Internet Explorer 6.0 or Mozilla Firefox 2.0.
  • MultiTerm requires the Microsoft .Net Framework version 2.0.50727. This is included in the installation file for your convenience.
  • MultiTerm requires the Java runtime engine (JRE) version 1.5.0.10. This is included in the installation file for your convenience.
  • MultiTerm Convert requires Microsoft Excel 2002 (XP) or 2003 for direct conversion of XLS files to MultiTerm XML.
  • MultiTerm supports direct integration with Microsoft Word through the multiterm7.dot and the multiterm7.dotm files. This feature requires Microsoft Word 2000, 2002 (XP), 2003 (SP2) or 2007 to be installed on the computer.
  • MultiTerm Extract uses the term recognition feature in Translator's Workbench to look up term candidates. If you install MultiTerm Extract on a computer that already has an instance of SDL Trados 2006 (7.x), 2007 (8.x), then remove SDL Trados at a later stage, MultiTerm Extract will not be able to look up terms anymore. You must run a repair installation of MultiTerm Extract to make this functionality available again.
  • MultiTerm Extract requires Microsoft PowerPoint 2000 or higher, Microsoft Excel 2002 or higher and TRADOS 6.5 or higher for the direct extraction of terms from PowerPoint and Excel files.
  • MultiTerm Extract requires Microsoft Word 2000 or higher for optimal processing of Word or RTF-based files.
  • MultiTerm Server components support the following database software: Microsoft JET Engine 4, Microsoft SQL Server 2000, Microsoft SQL Server 2000 Desktop Engine (MSDE), Microsoft SQL Server 2005, Microsoft SQL Server 2005 Express as well as Oracle 9i or later.
  • The optional server component MultiTerm Anywhere runs as an MS Windows Service or under Microsoft Internet Information Services (IIS) 5.0 or higher.
  • The optional server component MultiTerm Online runs as a JSP/Java servlet engine application within Apache Tomcat 5.0.x. SDL recommends using Apache Tomcat 5.5.
• Platforms
  • MultiTerm Desktop components run under Windows 2000 SP4, Windows XP and Windows Vista.
  • MultiTerm Server runs on Windows 2000 Server and Windows 2003 Server. MultiTerm Server also runs on Windows XP operating systems.

Software

SDL MultiTerm 2007 is provided as is. You use SDL MultiTerm at your own risk. SDL cannot take any responsibility for any kind of damage that occurs as a result of using MultiTerm.

Localization

SDL MultiTerm 2007 SP1 comes with the following localized components.

How to Contact Us

If you experience any problems, or have bugs or suggested improvements to report, contact SDL. Contact information for your local SDL office is available on www.sdl.com. and www.translationzone.com. For up-to-date support information, visit support.sdl.com.

Information for Upgrade Users

Information for users who are upgrading from MultiTerm 5.x or MultiTerm '95 Plus

Information for users upgrading from MultiTerm iX (versions 6.x)

Information for users upgrading from MultiTerm 7 (version 7.1)

Information for users applying MultiTerm 2007 SP1 on top of MultiTerm 2007

Application Specific Information

This section contains information about the different components that are part of MultiTerm.

Installation

• [INFO] If you are upgrading from the MultiTerm iX version of MultiTerm Server, you require a new permanent license key from your local SDL office. See above under Copy Protection (FLEXlm).
• [INFO] Make sure all user connections to MultiTerm Server and MultiTerm Anywhere are closed before uninstalling MultiTerm Server, otherwise certain files may not be properly removed. If you have MultiTerm Anywhere or MultiTerm Online installed with your MultiTerm Server, stop both the World Wide Web Publishing and the IIS Admin services before uninstalling MultiTerm Server in order to make sure that all files in use are no longer locked.
• [INFO] Installing MultiTerm Anywhere on a machine where MultiTerm Server is also installed and already running, will require a restart at the end. This is caused by DLLs that are already installed and in use by MultiTerm Server. After reboot the installer re-starts automatically and displays the message "MultiTerm is already installed on this machine." This message has no further meaning in this context. MultiTerm Anywhere is now properly installed.
• [INFO] See support.sdl.com for the latest information on installation issues.
• [INFO] The MultiTerm installers detect whether the required Microsoft .Net version is available on the target computer. If the correct version of Microsoft .Net is not present, it will automatically be installed. After Microsoft .Net has been installed, the MultiTerm installation should continue. If it does not, then restart the MultiTerm installer to continue by double-clicking Setup.exe.
• [WARNING] The original MultiTerm 2007 Anywhere installer contained a problem when installing within Microsoft Internet Information Server ("Fatal error during un-install"). This has been fixed in the SP1 installers. However, since the problem is in the original installers, you still need to follow the workaround as described in knowledge base article #1688.

MultiTerm

• [INFO] If you want to edit termbase entries, you must have Internet Explorer 6.0 or later installed on your computer. MultiTerm does not provide support for editing on computers that use earlier versions of Internet Explorer. However, you can use Internet Explorer 5.0 or Mozilla Firefox to view termbase entries.
• [INFO] The following multimedia formats are supported in this release: BMP, JPG, GIF, ICO, PNG, WMF, AVI. Other formats may be supported but have not yet been tested by SDL.
• [INFO] If you create a new local termbase and directly afterwards use the Modify Termbase Definition command on the Termbase menu to add new index fields to the termbase definition, you must restart MultiTerm before adding new entries to the termbase. If you do not restart, MultiTerm returns an Invalid Pointer error message when you try to save a new entry.
• [INFO] If you change the termbase definition, the Search for Incomplete Entries command does not find incomplete entries according to the modified termbase definition.
• [INFO] If you enter custom text in the General Options page of the Export Wizard and click Back before you click Next, you lose the text that you entered.

MultiTerm Convert

• [INFO] MultiTerm Convert directly supports Microsoft Excel 2002 (XP) and 2003. Users of Excel 97, 2000, or 2007 must save their Excel file as a tab-delimited text file, open the file in a Unicode text editor, save the file again as UTF-8, and then follow the workflow for spreadsheet and database exchange formats. This procedure is explained in detail in the MultiTerm User Guide.
• [INFO] Automatic attribute fields in a MultiTerm 5 (MTW) file are converted to the corresponding history fields in the MultiTerm XML file. However, to assign history fields to descriptive fields in the new MultiTerm 7 termbase, you must explicitly select the Keep history option for each descriptive field in the termbase definition that requires a history. The Keep history option is available in the Termbase Wizard in MultiTerm and MultiTerm Administrator.

MS Office/SDL Trados 2007 Integration

• [WARNING] Office 2003 requires at least Service Pack 2. If Service Pack 2 is not installed, Microsoft Word exits as soon as you try to connect to MultiTerm.
• [WARNING] When adding new entries from within Microsoft Word and choosing to add the segments from your Word document as a context example, the following may occur:
  • Microsoft Word documents translated with Translator's Workbench contain hidden markers that have the style tw4winMark mark assigned to them. In these cases the full source/target segment pair will end up being added as the context sentence, including the Translator's Workbench markers, for example: {0>Source sentence.<}0{>Target segment.<0}. To avoid this, create a copy of the bilingual Word document and run the MtRemoveTw4winStyles macro on it. This macro is included in the MultiTerm - Word interface (MultiTerm7.dot). To do this, press [Alt]+[F8] on your keyboard and browse for the macro called MtRemoveTw4winStyle. Click Run to run the macro and remove all the Translator's Workbench markers.
  • Due to a limitation in Microsoft Word's sentence detector, context sentences are not copied over from the document if there is an image immediately after the segment. In this case you will have to fill in the context sentence either manually in the Submit to termbase dialog box or remove the images from your document.
• [WARNING] On the Microsoft Windows Vista platform, please do not open any of the MultiTerm mdb files (for instance mtmaster.mdb) manually with Microsoft Access. This will break the functionality of MultiTerm within Microsoft Word. The reason for this is that under Vista, Microsoft Access creates compatibility copies of mdb files which break the MultiTerm/Word integration.
• [INFO] Navigating to cross references from within the Entry Display window is not supported. The Entry Display window is accessed when searching for terms in SDL Trados 2007 or when you click Display Entry in the MultiTerm Hit List from Microsoft Word.
• [WARNING] The Active Term Recognition of TRADOS 6.5 (Translator's Workbench 6.5.5) does not run with MultiTerm 2007; this is due to the more powerful term recognition features introduced since MultiTerm 7. We recommend upgrading to SDL Trados 2007 when using SDL MultiTerm 2007.
• [WARNING] If you are installing SDL MultiTerm 2007 Extract after SDL Trados 2006, then the Active Term Recognition from within Translator's Workbench is no longer available. This is related to the term recognition component of MultiTerm Extract. To repair this, re-register the SDL Trados 2006 components:
  1) Start the Windows File Explorer.
  2) Browse to the installation folder of SDL Trados 2006 (by default C:\Program Files\SDL International\T2006\TT\).
  3) Locate the file SelfRegister.bat.
  4) Double-click the file to run the self registration.
  

MultiTerm Extract

• [INFO] A valid license for SDL MultiTerm Extract 2007 also enables SDL PhraseFinder to run.
• [DEMO] SDL PhraseFinder is not featured with a demo mode.
  When MultiTerm Extract is running in demo mode, the following restrictions apply:
  
  

  Monolingual Term Extraction Project	MultiTerm Extract extracts source language terms starting with a, b, c, and d, up to a maximum of 100 terms. If the source language is not Latin alphabet-based, the first 100 terms are extracted. No export functionality is available and projects cannot be saved.
  Bilingual Term Extraction Project	MultiTerm Extract extracts source language terms starting with a, b, c, and d (and associated translation proposals), up to a maximum of 100 terms. If the source language is not Latin alphabet-based, the first 100 terms are extracted. No export functionality is available and projects cannot be saved.
  Translation Project	MultiTerm Extract processes the first 20 terms that are common to both the termbase and the bilingual input files. No export functionality is available and projects cannot be saved.
  QA Project	MultiTerm Extract processes QA projects that contain one file only; the file must be less than 100KB in size. No export functionality is available and projects cannot be saved.
  Dictionary Compilation Project	MultiTerm Extract extracts source language terms starting with a, b, c, and d (and associated translation proposals), up to a maximum of 100 words. If the source language is not Latin alphabet-based, the first 100 words are extracted. No export functionality is available and projects cannot be saved.

  
  
• [INFO] The installation program that installs the Sun Java Runtime Environment 1.5.0.10 by default activates the Java runtime environment in Internet Explorer. If this represents a security problem for you, you can deactivate it again after installation. Do this in the Advanced tab of the Internet Options dialog box in Internet Explorer.
• [INFO] SDL MultiTerm 2007 allows you to export terminology lists in a flat text format. This format is compatible to feed the Microsoft Word custom.dic file - user-enhanced spell checker content - or SDL PhraseFinder blocked list. Note that MultiTerm always exports in Unicode format. However, several applications, including SDL PhraseFinder, require ANSI format. For these applications, open the export .txt file in a Unicode editor (for instance notepad.exe) and save it in ANSI format.
• [WARNING] SDL MultiTerm Extract uses the common SDL Trados File Filter Framework. While SDL MultiTerm Extract ships its own filter framework, it is recommended to always have the latest version of SDL Trados installed to profit from the most recent changes and the latest additions to it.

MultiTerm Administrator

• [INFO] If you enter custom text in the General Options page of the Export Wizard and click Back before you click Next, you lose the text that you entered.

MultiTerm Server Console

• [INFO] Make sure that the information you enter in the DCOM and Services tabs is correct. If the information is incorrect, the MultiTerm Server services are unable to run and you are unable to log in to MultiTerm Server.

MultiTerm Server

• [INFO] MultiTerm Server depends on the system locale to render the names of termbases and termbase objects correctly in the MultiTerm client interfaces. If you have several different locales on a single network, SDL recommends using English names for these items. English names use the ASCII character set and thus ensure compatibility across different language installations.
• [WARNING] In Oracle based environments, please make sure that character sets are correctly specified:
  The NLS_CHARACTERSET must be set to UTF-8, the NLS_NCHAR_CHARACTERSET must be set to UTF-16. When rolling out MultiTerm Server on Oracle, we recommend contacting your local SDL Office to assist you with preparing Oracle database systems.
• [WARNING] In Oracle version 10.2 based environments, please make sure that you are running at least patch 3, i.e. 10.2.0.3. It should suffice to install this Oracle client patch on the machine where MultiTerm Server is running. However, it is recommended to install this patch both on the Oracle client (MultiTerm Server) as well as on the Oracle server machine. In the latter case, it is required to also update the database (via Oracle Database Upgrade Assistant).
• [INFO] It is recommended that you avoid deploying MultiTerm Server onto a machine that acts as a domain controller.

MultiTerm Anywhere

• [INFO] A very technical error message may pop up when a user tries to use a MultiTerm Anywhere connection to access an installation of MultiTerm Server that is either unavailable or non-existant: Loading of the WSDL file failed. This message means that the SOAP interface to connect to MultiTerm Server is not available.
• [INFO] Using MultiTerm Anywhere in conjunction with Oracle 9i version 9.2.0.3 you get the error message Provider not found when trying to connect to the MultiTerm Server using the SOAP protocol. Granting read, write and execute rights on the Oracle home directory to the Windows account that runs the ASP.net for the MultiTerm Anywhere Windows Service or Microsoft IIS fixes this problem.
• [WARNING] Running MultiTerm Anywhere within Microsoft Internet Information Server 6 under Windows 2003 may cause an error when leaving the system idle for several hours.
  You can resolve this by running MultiTerm Anywhere within its own application pool. Please consult the IIS documentation on how to configure an application to be run in its own application pool.

MultiTerm Online

• [INFO] Editing entries from within MultiTerm Online is supported from within Microsoft Internet Explorer 6.0 or higher and Mozilla Firefox 1.0 or higher. Other Mozilla/Gecko versions may also be supported but this has not been tested by SDL.
• [INFO] The following multimedia formats are supported in this release: BMP, JPG, GIF, ICO, PNG, WMF, AVI. More formats may be supported but have not yet been tested by SDL.
• [INFO] Tomcat does not support Unicode-based URIs by default. MultiTerm needs Unicode URI enabled to support linking to multilingual data. Do the following:
  1. Open the Tomcat server.xml configuration file (by default in <Tomcat installation directory>\conf\server.xml)
  2. Find the Connector element and append the following attribute to it: URIEncoding="UTF-8"

     You should then have an element like:
     <Connector port="8080" maxThreads="150"
minSpareThreads="25" maxSpareThreads="75" enableLookups="false"
redirectPort="8443" acceptCount="100" debug="0"
connectionTimeout="20000" disableUploadTimeout="true" URIEncoding="UTF-8"/>

  3. Restart the Tomcat service.