SDL MultiTerm 2009 SP1 Release Notes

Important: SDL MultiTerm 2009 cannot run with SDL MultiTerm 2007 (version 7.x) or TRADOS MultiTerm iX (version 6.x).

SDL MultiTerm Extract including SDL PhraseFinder and MultiTerm Server including MultiTerm 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 Team and MultiTerm Server do not allow users to access any remote termbases.

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

SDL MultiTerm 2009 SP1 comes with the following localized components.

Component	German	French	Spanish	Japanese	Chinese Simplified
MultiTerm Desktop	•	•	•	•	•
MultiTerm Convert	•	•	•	•	•
MultiTerm Extract	•	•		•
SDL PhraseFinder
MultiTerm Online	•	•	•	•	•
MultiTerm Desktop Help
SDL PhraseFinder Online Help
MultiTerm Online Online Help
MultiTerm Extract User Guide	Please consult kb article #2812 for most recent changes

• The minimum requirement for termbase search and look-up in MultiTerm and the MultiTerm Online client browsers is Microsoft Internet Explorer 7 or Mozilla Firefox 3.
• SDL MultiTerm Desktop (Client)
  • The minimum specification to run any of the MultiTerm components is a PC with a 500 Mhz Pentium or higher compatible processor. 1GB RAM is required in addition to the RAM required by the operating system.
  • For optimum performance of the client components, SDL recommends a recent Pentium using Core Duo technology and 2 GB RAM.
  • A mouse or similar pointing device is required.
  • 300 MB of disk space is required for the software and additional space is required for storing termbase data.
  • MultiTerm Convert requires Microsoft Excel 2003 for direct conversion of XLS files to MultiTerm XML.
  • MultiTerm supports direct integration with Microsoft Word through the multiterm8.dot and the multiterm8.dotm files. This feature requires Microsoft Word 2003, or 2007 to be installed on the computer.
  • SDL MultiTerm 2009 requires Microsoft .NET Framework version 3.5 SP1. If Microsoft .NET Framework 3.5 SP1 is not installed on your machine, it is automatically deployed by all setup programs. This might take a while to download and complete. In some cases, a reboot might be required before .NET Framework installation is complete.
  • 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.
• SDL MultiTerm Team
  • SDL MultiTerm Team server components require the Microsoft SQL Server Express database engine, which is included in the Team installers for your convenience.
  • SDL MultiTerm Team supports Windows 2003 Server, Windows 2008 Server, Windows XP, Windows Vista and Windows 7. Both 32-bit and 64-bit operating systems can be used.
  • From a hardware perspective, SDL recommends running SDL MultiTerm Team either on a mid-range server or mid-range desktop computer. Mid-range servers are recommended for optimum performance. A mid-range server typically has an Intel Xeon CPU, 4 GB of RAM and at least 100 GB of free hard disk space; a mid-range desktop computer has a recent Intel or AMD CPU, 3-4 GB of RAM and the same amount of free hard disk space.
  • SDL MultiTerm Team does not support Internet connectivity (SDL MultiTerm Anywhere); it can only be used inside a Local Area Network (LAN). Both domain and workgroup-based LANs are supported. If Internet connecitivity is required, consider upgrading to SDL MultiTerm Server.
  • Server-based, central termbases in a SDL MultiTerm Team installation are managed via the SDL MultiTerm Administrator client application and accessed through the SDL MultiTerm or SDL Trados Studio clients that run on Windows XP SP2 or later, Windows Vista (32 and 64 bit) as well as Windows 7 (32 and 64 bit).
• SDL MultiTerm Server
  • At the database server level, SDL MultiTerm Server supports Microsoft SQL Server 2005 and 2008 (including Microsoft SQL Server Express) on Windows Server platforms.
  • At the middleware level, SDL MultiTerm Server works as an application based using SDL CEAF authentication technologies. It supports Windows 2003 Server and Windows 2008 Server. Both 32-bit and 64-bit operating systems can be used.
  • From a server hardware perspective, SDL recommends a recent mid-range server with an Intel Xeon CPU and 4 GB of RAM. Multi CPU machines are supported. In larger installations, SDL recommends scaling out SDL MultiTerm Server onto dedicated servers, one for SDL MultiTerm Server, one for the Microsoft SQL Server database back-end. In such multi-server installations, as a general recommendation, the database server should have more powerful hardware than the middleware server, so the middleware server can have a slower CPU and 2 GB of RAM while the database server should have a faster CPU and more RAM as specified above. For hard disks, we recommend SCSI hard disks with 100 GB or more storage space within a RAID architecture. Other architectures (such as Serial ATA) are also supported. For more information on finding the right server hardware, contact SDL Professional Services.
  • MultiTerm Anywhere: In terms of Internet connectivity, the proxy can be hosted inside Microsoft Internet Information Server (supporting both HTTP and HTTPS protocols) or as a Windows service.
  • MultiTerm Online: The web application runs on Apache Tomcat 5.5 or higher. It supports Microsoft Internet Explorer 7 or 8 or Mozilla Firefox 3.x.
  • At the client level, SDL MultiTerm Server can be accessed through the SDL MultiTerm or SDL Trados Studio clients that run on Windows XP SP2 or later, Windows Vista (32 and 64 bit) as well as Windows 7 (32 and 64 bit).

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

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.

If you are upgrading from MultiTerm 5.x or MultiTerm '95 Plus, see the SDL MultiTerm Convert / Converting Data from MultiTerm 5 Format topic in the MultiTerm Online help. You can run MultiTerm 5.x and MultiTerm 2009 on the same computer.

1. Run the SP1 installer. It will detect the previous MultiTerm 2009 Desktop version, automatically remove and install the service pack.

1. Uninstall the previous MultiTerm version.
   The uninstall procedure creates a backup of your termbases.
2. Install SDL MultiTerm 2009 Desktop SP1
   The installation procedure detects your existing termbases, renames the mxw_ files according to their friendly name. You will find them in the following location by default:
   C:\Documents and Settings\<YourUserName>\My Documents\SDL MultiTerm\Termbases
3. If you are running SDL MultiTerm Extract you require a new license file. Please contact SDL to receive a new license file.

You must upgrade all MultiTerm client installations when you upgrade your MultiTerm Team installation and vice versa. SDL strongly recommends that you avoid mixed setups of previous and current versions of MultiTerm.

The underlying database format has changed. It is required to manually upgrade your data. Follow the steps below

1. Export all your termbases in MultiTerm XML format (select Termbase > Export). Use the built-in suggested export definition for termbase backups.
2. For each termbase, save each accompanying termbase definition as an XDT file (select Termbase > Save Termbase Definition As).
3. Uninstall SDL MultiTerm 2007 Team server components
4. Install SDL FLEXlm License Server
5. Install SDL MultiTerm 2009 Team server components
6. Configure SDL MultiTerm 2009 Team server components by using the SDL MultiTerm Server Console.
7. Recreate your termbases and re-import your data files.

You must upgrade all MultiTerm client installations when you upgrade your MultiTerm Server installation and vice versa. SDL strongly recommends that you avoid mixed setups of previous and current versions of MultiTerm.

1. Uninstall all server components (MultiTerm Online, MultiTerm Anywhere, MultiTerm Server)
2. Install SDL MultiTerm 2009 Server components (MultiTerm Server, MultiTerm Anywhere, MultiTerm Online)
   Important: In the installer, de-activate the option to recreate the mtmaster database. SDL MultiTerm 2009 will re-use the existing database.
3. Add the new license file to your SDL FLEXlm Server installation.
4. Configure SDL MultiTerm 2009 Server components by using the SDL MultiTerm Server Console.
5. Run the Upgrade Wizard in the SDL MultiTerm Server Console. This will upgrade your databases. It will also move the existing MultiTerm users into SDL Common User Management.

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

• [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 downloaded and installed. After installation of Microsoft .NET, the MultiTerm installation should continue. If it does not, then restart the MultiTerm installer to continue by double-clicking Setup.exe.
• [INFO] The SDL MultiTerm 2009 Desktop installer allows you to select amongst several software components ("features"). Some of them are not selected by default (for instance, the MultiTerm Administrator application). If you want to install them later, please de-install the existing features and re-run the installer, selecting all the features you want. This is due to a limitation in the installer module that cannot yet handle a Modify process.

• [INFO] If you want to edit termbase entries, you must have Internet Explorer 7.0 or later installed on your computer. MultiTerm does not provide support for the task of editing on computers that use earlier versions of Internet Explorer. However, you can use Internet Explorer 6.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.
• [WARNING] If your entry structure allows fields embedded within fields, then the built-in layout definitions cannot yet display the values of the deeper embedded fields. Please adapt the layouts accordingly. For instance, duplicate a built-in layout and modify it to display the embedded field.
• [DEFECT] Displaying multimedia files fails on machines where Microsoft Internet Explorer 7 is installed. Using Internet Explorer 8 resolves this problem.

• [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 Online help.
• [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 2009 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.
• [DEFECT] Installer: De-installing SDL Trados 2007 (if available) after having installed SDL MultiTerm 2009 unregisters the required TControlsLib.dll file. MultiTerm Convert then no longer runs. Workaround:
  1. In Start / Run type cmd.
  2. In the command shell type exactly the following
     regsvr32 C:\Program Files\SDL\SDL MultiTerm\MultiTerm8\Convert\Plugins\TControlsLib.dll
     Hit [Enter]. The file is registered again.
  3. Close the command shell. MultiTerm Convert is functional.

• [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:
  • 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] The Active Term Recognition of TRADOS 6.5 (Translator's Workbench 6.5.5) is not supported to run with MultiTerm 2009; this is due to the more powerful term recognition features introduced since MultiTerm 7. We recommend to upgrade to SDL Trados 2009 when using SDL MultiTerm 2009.
• [WARNING] SDL Trados 2007 (Translator's Workbench, build 8.3.0.863) can connect to SDL MultiTerm 2009 termbases. If this is failing, please re-register your SDL Trados 2007 installation, by using the provided registration shortcut (usually under Start / Programs / SDL International / SDL Trados 2007 / SDL Trados / Register SDL Trados 2007).
• [WARNING] The MS Word integration may loose its functionality if you de-install SDL Trados Studio.
  Workaround: De-install and re-install the SDL MultiTerm Core component (from Add/Remove Programs)

• [INFO] A valid license for SDL MultiTerm Extract 2009 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.6 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 2009 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. Several applications, including SDL PhraseFinder, require however ANSI format. In such a situation, 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 a latest version of SDL Trados installed to always profit from the most recent changes and the latest additions to it.
• [WARNING] SDL MultiTerm Extract uses the SDL Trados 2007 Suite API to access tmw files. Please install SDL Trados 2007 Suite for projects where you directly access tmw files.

• [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.

• [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.
• [INFO] It is recommended to avoid deploying MultiTerm Server onto a machine that acts as a domain controller.

• [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.
• [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 how to configure an application to be run in its own application pool.
• [WARNING] Running MultiTerm Anywhere within Microsoft Internet Information Server on 64 Bit Windows fails. Please set the website to run as 32 Bit. This workaround is described on Chris Crowe's blog.

• [INFO] Editing of entries from within MultiTerm Online is supported from within Microsoft Internet Explorer 7.0 or higher and Mozilla Firefox 3.0 or higher. Other browsers may be also supported but this has not been tested by SDL.
• [INFO] Tomcat is not supporting 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.