Microsoft Helium 6.1.

2 Release Notes
Microsoft Helium Build 6.1.2 October 10th 2007

Note: If your PC is running Windows XP and MSXML 6.0 is not installed, when Helium 6.1 is run
it will display an error message indicating that MSXML 6.0 should be installed from the
following location:

http://msdn.microsoft.com/XML/XMLDownloads/default.aspx

Select the link 'Microsoft Core XML Services (MSXML) 6.0', download the file msxml6.msi and
select 'Run' to install on your computer.

Next download any security updates to MSXML 6.0 from Windows Update at the following url:

http://update.microsoft.com

If your PC is running Windows Vista then there is no need to install MSXML 6.0.

Fixes since Helium 6.0.14

#1661 Validation Error issued on duplicated HTML <title> tags, should be a warning instead.
#1685 Windows Vista: Message box with error is displayed when Helium starts.
#1670 AutoTrx issue: text within locked tags is repeated after the tag.
#1704 Translation report does not include updated files when project contains subfolders
#1708 Helium reports fatal LOOM error when editing terms in the project with reverse locking
enabled.

New Features in Helium 6.1

#1668 XML LOOM Configuration Support
Helium now supports XML based LOOM configurations by default. This allows for more
straightforward management of LOOM configuration files, e.g. an XML configuration file can
easily be copied form one machine to another - there is no need to register it. It also allows for
easier comparison of changes between configurations, i.e. any standard file differencing utility
can be used. XML LOOM configuration files will also be used by the POMHTML parser and
HEAT subparser in LocStudio 6.0.
If a project has been created by a previous version of Helium, its LOOM configuration is stored
in the system registry. When the project is opened in Helium 6.1, the configuration settings are
automatically exported from the registry to the file 'ConfgName.config.xml' where ConfigName is
replaced with the name of the configuration, e.g. MergedReg.config.xml. This file is stored in the
same folder as where the Helium project file (.he) is located. This export from the registry is
performed once only, after the export the configuration information will be loaded directly from
XML file and the registry is no longer used.
Within Helium, there are only minor differences to its operation. The 'Project Settings' and 'New
Project' dialogs list the names of all LOOM xml configuration files which are located in the
Helium project folder. If you want additional configuration files available on these dialogs you
should copy any existing files with the '.config.xml' extension to the Helium project folder or
export the configurations directly from LOOMConfig.
The LOOMConfig tool has also been upgraded to support loading from LOOM XML
configuration files instead of from the registry. It does however allow the user to export any
registry based configurations to LOOM XML configuration (.config.xml) files. Other than the
changes required to load and save XML configuration files, the content within each of the tabs in
LOOMConfig is identical to the previous version. The online help has been updated to describe
the XML LOOM configuration support changes in LOOMConfig.

#1689 Highlight matched strings in Terminology Changes Report

Strings which are matched in the Terminology Changes Report are now highlighted, this is
especially useful where regular expression matching is employed.

#1691 Output of error messages using command line interface

A new command line switch has been added to the Helium command line interface which allows
all output which would have previously appeared in a MessageBox to be redirected to a text
output file. This allows clients which automate Helium via the command line interface to continue
operation with a log of the output saved to the file instead of waiting for the user to click 'OK' to
close the MessageBox. Where a MessageBox has more than one response which requires the
user to respond to a question, the MessageBox will still appear as it is not possible to predict
what default action will be appropriate in all circumstances. However, the message box prompt
and the user response will be saved to the output file. This option is invoked by adding the
switch '/ERR {filename}' to the command line.

Important Notes
•NTFS file system is mandatory for Helium projects with large number of files.
•Helium 6.x uses a different format for Project Files from Helium 5.x and below.
Once the files are converted to this format, you will no longer be able to open
these projects in older versions of Helium.
•For LocVer validation the Microsoft .Net Framework redistributable package version
2.0 needs to be installed. This should be installed before installing Helium.
•Please read the "Multiple Users" topic in the Helium Help if you intend to have
multiple users working on a project at the same time.
•Helium relies on the Office Unicode Speller API. Some spellers installed with Office
2000 or Office XP do not support this Unicode API. However, all languages in
Office 2003 do support it, so we recommend that you upgrade to Office
2003.
•If you are working on Indic or Middle East languages, please ensure that these
languages are fully enabled on your computer. To do this open the Control
Panel, choose Regional and Language Options, select the Languages tab and
check the Install files for complex script and right-to-left languages option.
•If you have a Script Debugger on your computer, and you attempt to preview files
that have scripting problems, you will be thrown into the debugger
immediately. This is because Helium has disabled the browser dialog asking
if you want to debug. The workaround is to launch Internet Explorer, choose
Tools, Internet Options, Advanced, scroll down to the Browsing section and
check the Disable script debugging option.
•LOOMConfig (Tools, Edit Configurations) needs MSXML 3.0 (or higher) in order to
read DTD or Schema settings. You also need MXSML 3.0 (or higher) if you
want to use the extended MSXML validation in Helium. MSXML is installed
with IE 6.0 or it can be installed from: http://msdn.microsoft.com/xml.
•MidEast Users: When switching the input keyboard layout to RTL (using Ctrl+Shift)
you need to ensure that protected text is not selected within the term (e.g.,
Tags). Also note that the layout is only switched up to the end of the term or
the next newline character.
Trados User Notes
•For Unicode only languages first make sure that your version of Trados Workbemch supports
your language.
•An updated version of TradosGP.dll is required for Unicode only languages like Hindi if you are
using LocStudio 4.8 or earlier. Please contact helisupp@microsoft.com to obtain a copy
of this file.
•For Kazakh language, updated versions of TradosGP.dll and LocCultures.xml are required.
Please contact helisupp@microsoft.com to obtain a copy of these files.
•Trados TM Server users need LocStudio 4.71 (or later).
•When Helium launches TRADOS Workbench, you should not close the TM opened by Helium
(or attempt to open another one). Always use the Helium Options dialog to change TM's.
•If you do not have TRADOS MultiTerm installed, make sure you disable Term Recognition (on
the TRADOS Workbench Options menu). Note: This option is turned off automatically by
Helium setup.
•Remember to reorganize you TRADOS TM's regularly. This is especially important after
importing large amounts of Translation Units (using the Workbench Import command or
by Exporting from Helium). Most TRADOS Workbench errors can be cured by
reorganizing. If this does not work then try to rebuild the TM (export to TMX file and then
import this into a new TM).

Fixes since Helium 6.0.8

#1412 (AWS Intl Support) Update Glossary names should not be lowercased.
#1657 Text from Definitions, Keywords and MT extra fields must be marked up for Trados
glossaries.
#1650 Export and Lookup of Unicode only languages (e.g. Hindi) don't work with Trados
Workbench 7.x.
See Trados User Notes.
#1642 Helium does not create the Translation Report with the Filename includes a full stop
character.
#1658 Files marked as RAW in LOOM configuration, show up in the file pane when new project
is created.
#2576 (LocStudio) Use LocCultures.xml to define language settings in Helium.

Fixes since Helium 6.0 SR1

#1621 META tag inserted does not conform to XHTML 1.0
#1632 Goto What not restored on a new session for some term states
#1633 For CS language targets, should add DIR=RTL tag with quotes
#1638 Issue with Helium Wordcounts and the TopX process
#927 Allow CSS2-like underscores in identifiers (LocStudio)

Note: Helium now requires Microsoft .Net Framework redistributable package version
2.0. Helium Setup detects if Microsoft .Net Framework 2.0 is not present and provides
a link to the installation point.

Fixes since Helium 6.0

#1534 ''' comment type extraction is not supported in C# and VB
#1604 Links are not working in Validation, Terminology Changes and Terminology
Consistency reports
#1608 LocVer Rules: Error status not being saved after user moves away from a translation
#1609 Configuration data & time field to be added to wordcount report
#1610 Helium: Error 1062 (non-loc terms differ) issued incorrectly
#1612 Comments are not parsed after "\" in VB and C# source files
#1614 Reading order in Term Preview incorrect for BiDi languages after first term displayed.
#1615 Issue with TradosGP.dll version 4.70.920 - won't export terms with regular expression
characters.
#1618 Need to check if files are aligned before update
#1619 Helium: Unable to handle white spaces in XML tags
#1620 Helium: Error caused by white spaces between non-localisable tags
#1624 Helium: Should have a suggested name for Zip file that is based on the project name
#1626 Terminology Consistency report: multiple error message boxes when no lookup
glossaries are specified
#1627 Update dialog: empty name for the backup file should not be allowed
#1628 Some Asian translations are garbled when exported from Helium to Trados TM