&nbsp;

Enhancements

http://autoupdate.lionbridge.com/ltb/KnownIssues.htm

We are very pleased to announce a new release of Linguistic ToolBox ver. 2.46. In this release, we have rationalized the functionality of the Segment Checker component and we have introduced several new ignorability options in order to enable users to block false positives and to allow more flexibility from the checks that need to be carried out.

With this release, we have also included new and updated support files, don’t forget to check these out! Special attention should be paid to the new and updated Microsoft Style Guide rules for these languages: Spanish, German, Portuguese (Portugal), Russian, Korean, Chinese (Traditional) and Chinese (Simplified).

If you have any technical questions or in case you identify any bugs, please contact us.

New Features

· New Ignore options under Check inconsistency and Check reverse inconsistency.

o Don’t check inconsistencies between locked and other segments: enables users to exclude from the checks those inconsistencies (direct and/or reverse) that are produced by locked segments and other segments. This feature is only appropriate for those teams that cannot modify locked segments due to inconsistencies.

o Don’t check inconsistencies between ignored ‘matches equal or above’ and other segments: enables users to exclude from the checks those inconsistencies (direct and/or reverse) that are produced by ignored ‘matches equal or above’ and other segments. This feature is only appropriate for those teams that cannot modify segments over a certain match percentage due to inconsistencies.

· New Ignore options for the Check if target is empty. These two options allow users to easily block false positives.

o Ignore list: enables users to ignore source segments that don’t have an equivalent target by using a one column list of the segments that need to be ignored (Unicode .txt).This option is very convenient if the segments that need to be ignored don’t follow a certain pattern or for users unfamiliar with the creation of rules for Linguistic ToolBox. Note that each list entry must contain the whole segment that is supposed to be ignored, and that these entries are case-sensitive.

o Ignore rule: enables users to ignore source segments that don’t have an equivalent target by using a rule containing either regular expressions or list entries in a rule format. The rules created for this option, must have content in the Source column and must use the Error mode. This option is very useful to ignore those segments that follow a certain pattern, or where entries need to be case-insensitive

· New Ignore options for the Random Sampling component. New ignore options enable users to be able to exclude specific segments from the sample to be generated.

o Ignore duplicated segments Ignores instances of repeated segments.

o Ignore empty target segments Ignores source segments that don’t have a corresponding target segment

o Ignore alphanumeric only segments Ignores segments that only contain alphanumeric strings (including Roman numbers)

o Ignore numeric only segments Ignores segments that only contain numeric strings

Changes

· The Segment Checker tab has changed as follows with a view to make the UI more logical and intuitive.

· The content has been divided into three different areas of functionality:

o Inconsistency

o Translation

o Segment length

· The below ignore options now only affect the Check inconsistency and Check reverse inconsistency:

o Ignore case and punctuation

o Ignore end punctuation

o Ignore hotkeys

· The below ignore options now only affect the Check if source equals target and Check if target is empty:

o Ignore alphanumeric only segments

o Ignore CaMel words

Enhancements

· The parser has been improved to deal with the following situations:

o Situations where there is more than one tag within a <ph> group.

o Situations where there is more than one tag within an internal tag in .rtf files.

o The pattern <ph><tag>text1</tag><tag2>text2</tag2></ph> is now interpreted as a whole and protected as ^TAG^.

· The behaviour of the Check if Target is empty regular expression has been made more accurate when detecting unsegmented text that contains line breaks in .rtf files.

Defects fixed

· Issues related to incorrect behaviour of the option Ignore case and punctuation in the Segment Checker.

· Issue in the LocStudio Filter Settings window, the filter Modified after was not applied to all files once the user clicked on the Apply Filters to all files button.

· Issue with the parsing of segments containing references to footnotes in bilingual Trados Word files. Previously LTB processed those segments incorrectly and as a consequence bilingual checks could not be performed.

Support Files Updates

Core Configuration

· Updated: The file LTB_Core_Config.zip has been updated with these changes:

· Term and Punctuation:

o Core ALL STANDARD Literals - CaMel-Alphanumerics [UL].rul (new)

o New Core FI STANDARD Number Format [UL] EN-FI.rul (new)

o Core ALL STANDARD Tags Generic.rul (updated)

o Core ZH-TW STANDARD Duplicated Words [UL] ALL-ZHTW.rul (updated)

o New Core DE STANDARD Number Format [UL] EN-DE.rul (updated)

o New Core EN STANDARD Number Format [UL] EN-EN.rul (updated)

o New Core EN STANDARD Number Format 1,000.0 to 1 000,0 [UL].rul (updated)

o New Core EN STANDARD Number Format 1,000.0 to 1,000.0 [UL].rul (updated)

o New Core EN STANDARD Number Format 1,000.0 to 1.000,0 [UL].rul (updated)

o New Core ES STANDARD Number Format [UL] EN-ES.rul (updated)

o New Core FR STANDARD Number Format [UL] EN-FR.rul (updated)

o New Core IT STANDARD Number Format [UL] EN-IT.rul (updated)

o New Core NL STANDARD Number Format [UL] EN-NL.rul (updated)

o New Core PT-BR STANDARD Number Format [UL] EN-PTBR.rul (updated)

o New Core SV STANDARD Number Format [UL] EN-SV.rul (updated)

Term and Punctuation Rules

· New rules (23):

o DE CUSTOM Microsoft Style Guide EN-DE.rul

Microsoft Style Guide Rule for German according to the Style Guide from February 2012.

o JA CUSTOM Microsoft Character Spacing (MS Style Guide ver.7).rul

o JA CUSTOM Microsoft Katakana (MS Style Guide ver.7).rul

o JA CUSTOM Microsoft MacUI (MS Style Guide ver.7).rul

o JA CUSTOM Microsoft Standard Expressions (MS Style Guide ver.7).rul

o JA CUSTOM Microsoft Style Guide ver.7 - WindowsOS.rul

o JA CUSTOM Microsoft Style Guide ver.7.rul

Microsoft Style Guide Rules for Japanese according to the Style Guide ver. 7. Please replace your ver. 6 rules from your configurations with the latest version of the rules.

o KO CUSTOM Microsoft Style Guide EN-KO.rul

Microsoft Style Guide Rule for Korean according to the Style Guide from February 2012.

o PT CUSTOM Microsoft Style Guide EN-PT.rul

Microsoft Style Guide Rules for Portuguese (Portugal) according to the Style Guide from March 2011.

o RU CUSTOM Microsoft Style Guide EN-RU.rul

Microsoft Style Guide Rule for Russian according to the Style Guide from January 2012.

o ZH-CN CUSTOM Microsoft Style Guide (UA) EN-ZHCN.rul

Rule only applicable for UA.

o ZH-CN CUSTOM Microsoft Style Guide (UI) EN-ZHCN.rul

Rule only applicable for UI.

o ZH-CN CUSTOM Microsoft Style Guide EN-ZHCN.rul

Microsoft Style Guide Rules for Chinese (Simplified) according to the Style Guide from February 2012.

o ZH-TW CUSTOM Microsoft Style Guide EN-ZHTW.rul

Microsoft Style Guide Rules for Chinese (Traditional) according to the Style Guide from January 2012.

o New Core FI STANDARD Number Format [UL] EN-FI.rul

New core rule for number checks. Checks that numeric values are present with the correct format (with thousands or decimal separators) in the target segment and that any numeric value present in the target segment is also present in the source. This rule has been updated to carry out more exhaustive checks and to include language specific information to make the rules more accurate and to reduce false positives.

o Core ALL STANDARD Literals - CaMel-Alphanumerics [UL].rul

Checks for correspondence of "CaMel" words and alphanumeric expressions between source and target. Uses external lists Camel_Alphanumeric_Blockers.txt and ordinal_suffixes.txt to block matches in both source and target segments.

o ALL STANDARD Punctuation (Parenthesis, Brackets and Braces).rul

Detects punctuation issues related to orphaned or duplicate parentheses/brackets/braces in the target. Note: This rule is source independent. This rule does not check for orphaned Japanese brackets.

o ALL STANDARD Literals - Acronyms [UL].rul

Checks that acronyms are the same in the source and target. Use acronym_blockers.txt to prevent matches. Note: Only use this rule if you don’t have clear requirements on acronyms, if you do, use a custom terminology rule instead.

o ALL STANDARD Strict Literals - Acronyms [UL].rul

Checks that acronyms are the same in the source and target. Use source_strict_acronym_blockers.txt and target_strict_acronym_blockers.txt to prevent matches. Note: Only use the STRICT if you know exactly which acronyms can be blocked, or for situations where there always needs to be a one to one correspondence.

o DE STANDARD Detect Formal Style EN-DE.rul

Detects instances of usage of formal style in German. This rule is applicable for those cases where the guideline is to use the "personal" you (du) in German rather than the "formal" you (Sie). This rule is source-dependent.

o DE STANDARD Detect Informal Style EN-DE.rul

Detects instances of usage of informal style in German. This rule is applicable for the general cases where the guideline is to use the "formal" you (Sie) in German rather than the "personal" you (du). This rule is source dependent.

o DE STANDARD Strict Detect Formal Style ALL-DE.rul

o DE STANDARD Strict Detect Informal Style ALL-DE.rul

Detects instances of usage of informal style in German. This rule is applicable for the general case where the guideline is to use the "formal" you (Sie) in German rather than the "personal" you (du). This rule is more strict than the DE STANDARD Detect Informal Style version.

· Updated rules (17):

o ES CUSTOM Microsoft Style Guide EN-ES.rul

Microsoft Style Guide Rules for Spanish according to the Style Guide from February 2012.

o DE CUSTOM Microsoft Common Errors EN-DE.rul

Rule updated to remove checks that are now included in the DE CUSTOM Microsoft Style Guide EN-DE.rul.

o New Core FR STANDARD Number Format [UL] EN-FR.rul

o New Core SV STANDARD Number Format [UL] EN-SV.rul

Rules updated to fix a defect and improve rule ID. 5 to allow using the Version Blockers to prevent matches in decimal numbers without an integer, for example: .5.

o New Core EN STANDARD Number Format 1,000.0 to 1 000,0 [UL].rul

Rules updated to fix a defect and to remove Finnish from the Target language.

o New Core EN STANDARD Number Format 1,000.0 to 1,000.0 [UL].rul

o New Core EN STANDARD Number Format 1,000.0 to 1.000,0 [UL].rul

o New Core EN STANDARD Number Format [UL] EN-EN.rul

o New Core DE STANDARD Number Format [UL] EN-DE.rul

o New Core ES STANDARD Number Format [UL] EN-ES.rul

o New Core IT STANDARD Number Format [UL] EN-IT.rul

o New Core NL STANDARD Number Format [UL] EN-NL.rul

o New Core PT-BR STANDARD Number Format [UL] EN-PTBR.rul

o Core ALL STANDARD Tags Generic.rul

Updated to catch up special cases where the tags are different between source and target but were not previously detected because they were internal groups, for example: <tag><ph></ph></tag>.

o Core ZH-TW STANDARD Duplicated Words [UL] ALL-ZHTW.rul

Checks for accidentally duplicated words in Traditional Chinese. Use DupWordsPhrases_Blockers_ZHTW.txt list to define exceptions. (NOTE: Entries in the list file are CASE-SENSITIVE; be sure to enter any common case variants needed.) This rule has been updated to hardcode contextual exceptions.

o ES STANDARD Common Errors ALL-ES.rul

o ES STANDARD False Friends EN-ES.rul

Updated: new entries have been added and obsolete entries have been deleted.

· Deleted rules (3):

o ZH-TW STANDARD Style Check ALL-ZHTW.rul

All the checks contained within the deleted rule are now included in the rule Core ZH-TW STANDARD Spacing ALL-ZHTW.rul.

o DE STANDARD STRICT Formal Style.rul

This rule has now been renamed to DE STANDARD Strict Detect Informal Style ALL-DE.rul for clarity purposes.

o DE STANDARD Formal Style.ru.

This rule has now been renamed to DE STANDARD Detect Informal Style EN-DE.rul for clarity purposes.

Lists

· CheckifSourceEqualsTarget_IgnoreList_EN-FR.txt

This list contains an exhaustive lists of words that are spelled the same in both English and French and can be added under the Segment Checker>Check if source equals target to block those segments that would cause false positives in English-French translations. Find this list at this location: ...\MyLTB\Support\Lists

Dictionaries

· Updated dictionaries (5):

o Assamese.xpl

o Finnish.xpl

o French.xpl

o French (Canada).xpl

o Sinhalese.xpl

· New dictionaries (1):

o Bengali.xpl

Documentation

· Help file has been updated with changes related to this release.

· Information about the functionality and usage of the rules installed with the Term and Punctuation has been updated with changes related to this release, a new field “User Lists” has been added to this table to indicate those .rul files that reference User lists: http://autoupdate.lionbridge.com/ltb/_LTB_Installation_Rules_Description.html

· Previous Release Notes are available at: http://autoupdate.lionbridge.com/ltb/PreviousReleaseNotes.htm

Known Issues

___________________________________________________________________________________________________________________________________________

Lionbridge Linguistic ToolBox ver. 2.45 - Release Notes

February 15th, 2012

Contents

New Features

We are very pleased to announce a new release of Linguistic ToolBox ver. 2.45. In this release, we have introduced several new features that are going to have a big impact on the user experience of our internal LTB users.

· Easier way to create multilingual configuration files

· Easier way to adapt Term and Punctuation rules to specific project requirements by using external user support lists

· Windows 7 users now can drag and drop files in the Input files tab

With this release, we have also included new and updated support files, don’t forget to check these out! Especial attention must be paid to the new checks for number rules and to the character corruption rules for 38 new languages.

If you have any technical questions or in case you identify any bugs, please contact us.

New Features

· New LTB default Installation path. LTB is no longer installed under the Program Files folder, the default installation for LTB going forward is: C:\Users\User_Name\Documents\MyLTB

Note: When installing this new version from the install.exe, previous executable files from the previous location will be automatically removed, however user specific support lists will remain in the previous installation folder, usually at this location: C:\Program Files\Lionbridge\Linguistic Toolbox

· New Method to create Multilingual Configuration files. In this new version of LTB, all LTB internal users can now easily create multilingual configuration files. To do this users just need to select the Source language and in the Target language field, select [ All ]. Then, add all the relevant checks in LTB and save the multilingual configuration file as usual: File>Manage Configurations>Save.

· New functionality to allow advanced users to easily use project specific support lists and to save project specific support files within a configuration file. In the Term and Punctuation component, now there is a new grid available called User lists. This grid now allows users to add user defined external support lists. This new functionality will allow internal users to be able to easily modify some of the Term & Punctuation rules by using external user support lists instead of having to modify certain rules with regular expressions. All the standard installation rules that have referenced external user support lists contain [UL] in the file name, to find out more about how to use the user support lists for each .rul file, please check the details in the rule Description (in the Linguistic Editor, go to Edit and then, select Properties).

Changes

· In the Term and Punctuation tab, the button Refresh lists according to selected languages has now been renamed to Refresh rules according to selected languages

· Now, when activating the Term and Punctuation component, LTB does not load any rules in the grid automatically. This new behaviour speeds up the start up of the Term and Punctuation component. To add the required lists for each language, users can use the Add button to select individual rules or click on Refresh rules according to selected languages to see all rules available for the selected source and target languages.

· New languages added: Luxembourgish, Maori (New Zealand), Quechua (Bolivia), Quechua (Ecuador), Quechua (Peru) and Uyghur (China),

Defects fixed

· Issue preventing drag and drop of files in the Input file tab for Windows 7

· Issue with language-neutral dictionaries not loading automatically from within a configuration file This issue has now been fixed and now configuration files including a language-neutral dictionary (a dictionary with Language:

[ All ]) automatically display these dictionaries in the Spelling tab.

· Issue with QUICK not eliminating substring matches to reduce noise This issue has now been fixed and will reduce substantially the output from the QUICK component. It is very common for SW reference files to contain terms that are substrings of other terms, for example “Print” and “Print All Pages”. For such cases, the QUICK check will ignore the substrings when it matches on the longer string (the “superstring”).

· Issue with parsing double byte characters when processing unformatted segments Previously LTB used to incorrectly remove some double byte characters when processing unformatted segments in a Chinese OS.

· Issue when adding a folder with a period in the name with the Add Folder button

· Issue with LTB not recognizing in the Add Input files tab, HTML files.

Enhancements

Support Files Updates

Core Configuration

· Updated: The file LTB_Core_Config.zip has been updated with these changes:

· Term and Punctuation:

o New Core NL STANDARD Number Format [UL] EN-NL.rul (new)

o New Core PT-BR STANDARD Number Format [UL] EN-PTBR.rul (new)

o New Core SV STANDARD Number Format [UL] EN-SV.rul (new)

o New Core DE STANDARD Number Format [UL] EN-DE.rul (updated)

o New Core ES STANDARD Number Format [UL] EN-ES.rul (updated)

o New Core IT STANDARD Number Format [UL] EN-IT.rul (updated)

o New Core EN STANDARD Number Format [UL] EN-EN.rul (new)

o New Core EN STANDARD Number Format 1,000.0 to 1,000.0 [UL].rul (new)

o New Core EN STANDARD Number Format 1,000.0 to 1 000,0 [UL].rul (updated)

o New Core EN STANDARD Number Format 1,000.0 to 1.000,0 [UL].rul (updated)

o Core EN STANDARD Literals – Numbers.rul (removed from Core, and now renamed EN STANDARD Literals – Numbers.rul)

o Core ALL STANDARD URLs [UL].rul (updated rule)

o Core ALL STANDARD Duplicated Words [UL].rul (updated rule)

o Core ZH-TW STANDARD Spacing ALL-ZHTW (new rule)

o Core ZH-TW STANDARD Duplicated Words [UL] ALL-ZHTW.rul (new rule)

Term and Punctuation Rules

· New rules (83):

o New Core EN STANDARD Number Format [UL] EN-EN.rul

o New Core NL STANDARD Number Format [UL] EN-NL.rul

o New Core PT-BR STANDARD Number Format [UL] EN-PTBR.rul

o New Core SV STANDARD Number Format [UL] EN-SV.rul

o New Core EN STANDARD Number Format 1,000.0 to 1,000.0 [UL].rul (new)

New core rule for number checks. Checks that numeric values are present with the correct format (with thousands or decimal separators) in the target segment and that any numeric value present in the target segment is also present in the source. This rule has been updated to carry out more exhaustive checks but does not include language specific information.

o XX STANDARD Detect Corrupt Chars or Wrong Lang EN-XX.rul (x38 languages)

Detects possible corrupt characters in target (and to a limited extent in source) segments for Afrikaans, Albanian, Amharic, Assamese, Azeri, Bengali, Bosnian (Cyrillic), Bosnian (Latin), Byelorussian, Gaelic (Ireland), Gujarati, Hausa, Igbo, Kannada, Khmer, Kirghiz, Konkani, Macedonian, Malay, Malayalam, Maltese, Maori (New Zealand), Marathi, Nepali, Oriya, Punjabi, Quechua, Sesotho, Sinhalese, Swahili, Tamil, Tatar, Telugu, Tswana, Welsh, Xhosa, Yoruba and Zulu.

o XX STANDARD Monolingual Detect Corrupt Chars or Wrong Lang.rul (x38 languages)

Detects possible corrupt characters in monolingual files for these languages: Afrikaans, Albanian, Amharic, Assamese, Azeri, Bengali, Bosnian (Cyrillic), Bosnian (Latin), Byelorussian, Gaelic (Ireland), Gujarati, Hausa, Igbo, Kannada, Khmer, Kirghiz, Konkani, Macedonian, Malay, Malayalam, Maltese, Maori (New Zealand), Marathi, Nepali, Oriya, Punjabi, Quechua, Sesotho, Sinhalese, Swahili, Tamil, Tatar, Telugu, Tswana, Welsh, Xhosa, Yoruba and Zulu.

o Core ZH-TW STANDARD Spacing ALL-ZHTW.rul

This rules replaces the previous rule: ZH-TW STANDARD Spacing ALL-ZHTW.rul and includes the functionality of the rule Core (Not French) STANDARD Spacing.rul.

o Core ZH-TW STANDARD Duplicated Words [UL] ALL-ZHTW.rul

This rule replaces the previous rule ZH-TW STANDARD Literals - Duplicated Words ALL-ZHTW.rul and includes the functionality of the rule Core ALL STANDARD Duplicated Words [UL].rul

· Updated rules (23):

o New Core EN STANDARD Number Format 1,000.0 to 1 000,0 [UL].rul (updated)

o New Core EN STANDARD Number Format 1,000.0 to 1.000,0 [UL].rul (updated, previously named Core EN STANDARD Number Format 1,000.0 to 1.000,0.rul (updated)

o EN STANDARD Literals – Numbers.rul (updated, previously named Core EN STANDARD Literals – Numbers.rul)

This rule has now been removed from the Core. Checks that any numeric value (sequence of digits) in the source segment is present in the target segment and that any numeric value present in the target segment is also present in the source. NOTE: This rule does not check for the correct thousand or decimal separators.

o New Core DE STANDARD Number Format EN-DE [UL].rul

o New Core ES STANDARD Number Format EN-ES [UL].rul

o New Core FR STANDARD Number Format EN-FR [UL].rul

o New Core IT STANDARD Number Format EN-IT [UL].rul

New changes have been introduced to make this rule even more accurate and to reduce false positives further.

o Core ALL STANDARD URLs [UL].rul

Checks that any URL or e-mail address in the source segment is present in the target segment. Use external User lists to define Exceptions: 1. Use Whole_String_SOURCE_URL_Blockers.txt and Whole_String_TARGET_URL_Blockers.txt to specify precisely full item matched by the LTB rule that should be excluded. 2. Use Partial_String_SOURCE_URL_Blockers.txt and Partial_String_TARGET_URL_Blockers.txt to specify any portion of a URL/address that should be blocked. This blocks ANY partial match so use with CARE! The SOURCE blocker lists only prevent matches in source segments, and the TARGET blocker lists only prevent matches in target segments; the same rule looks in both segments, so you generally will need to put an entry in a blocker list for both segments to prevent false positives.

o Core ALL STANDARD Duplicated Words [UL].rul

Updated to remove further false positives for French. Also Chinese (Traditional) and Chinese (Hong Kong) have been removed from the rule properties. Use the external user support list DupWordsPhrases_Blockers.txt list to define exceptions. (NOTE: Entries in the list file are CASE-SENSITIVE; be sure to enter any common case variants needed.)

o XX STANDARD Detect Corrupt Chars or Wrong Lang EN-XX.rul (x2 languages)

Detects possible corrupt characters in target (and to a limited extent in source) segments for Armenian and Vietnamese.

o XX STANDARD Monolingual Detect Corrupt Chars or Wrong Lang.rul (x2 languages)

Detects possible corrupt characters in monolingual Armenian and Vietnamese.

o ES STANDARD Monolingual Detect Old Spelling.rul

o ES STANDARD Detect Old Spelling ALL-ES.rul

Introduced new check on the usage of the % sign.

o ES STANDARD Common Errors ALL-ES.rul

New checks added.

o FI STANDARD Rude_words_and_vulgarisms ALL-FI.rul

o FI STANDARD Additional_grammar_and_punctuation_check ALL-FI.rul

New checks have been added to these rules.

o ZH-TW STANDARD PoliCheck ALL-ZHTW.rul

o ZH-TW STANDARD Offensive Terms ALL-ZHTW.rul

o ZH-TW STANDARD Punctuation EN-ZHTW.rul

o ZH-TW STANDARD Forbidden CHS Terms All-ZHTW.rul

These rules has been reviewed to reduce the number of false positives.

Dictionaries

· Updated dictionaries (6):

o Albanian.xpl

o English (UK).xpl

o Finnish.xpl

o French (Canada).xpl

o Malay.xpl

o Norwegian (Bokmal).xpl

· New dictionaries (1):

o Luxembourgish.xpl

Documentation

· Help file has been updated with changes related to this release.

· Previous Release Notes are available at: http://autoupdate.lionbridge.com/ltb/PreviousReleaseNotes.htm

Known Issues

There are updates for Known Issues related to this release: http://autoupdate.lionbridge.com/ltb/KnownIssues.htm

___________________________________________________________________________________________________________________________________________

Lionbridge Linguistic ToolBox ver. 2.44 - Release Notes

October 31st, 2011

Contents

Entity Extactor Rules

We are very pleased to announce a new release of Linguistic ToolBox ver. 2.44. In this release, we are tackling one of the options in LTB that usually has produced a large number of false positives: Segment Checker> Check if source equals target. This is a very useful check that detects instances of untranslated segments, but until now, we have not had any method to avoid false positives for this check other than blocking locked segments or matches equal or above to a certain percentage. In this new release we are introducing for the option Check if source equals target, two new Ignore options to allow users to easily block false positives for those segments that need to stay untranslated as per the instructions.

In addition, we have also carried out critical updates to the rules for Punctuation and Spacing, where the number of false positives have now been reduced drastically. We highly recommend our users to update any configuration files that use any of the Punctuation and Spacing rules installed by default with LTB.

If you have any technical questions or in case you identify any bugs, please contact us.

Changes

· New Ignore options for Check if source equals Target. These two options allow users to easily block false positives.

o Ignore list: enables users to ignore segments that must remain unstranslated by using a one column list of the segments that need to be ignored (Unicode .txt).This option is very convenient if the segments that need to be ignored don’t follow a certain pattern or for users unfamiliar with the creation of rules for Linguistic ToolBox. Note that each list entry must contain the whole segment that is supposed to be ignored, and that these entries are case-sensitive.

o Ignore rule: enables users to ignore segments that must remain unstranslated by using a rule containing either regular expressions or list entries in a rule format. The rules created for this option, must have content in the Source column and must use the Error mode. This option is very useful to ignore those segments that follow a certain pattern, or where entries need to be case-insensitive.

· Segment Checker Ignore options: The Segment Checker Ignore options that are common to the main features of this component have been moved under the Ignore Options box. Note that the functionality remains the same, this is only a cosmetic change in the UI.

· New Language added: Spanish (United States). Spanish (United States) has now been added to the list of Source and Target languages.

Defects fixed

· Issue with how LTB used to process new line metacharacters. LTB used to replace soft carriage returns, \n and \r by a space when processing the segments that contained these metacharacters, as a consequence any Term and Punctuation checks related to these metacharacters were not working correctly for certain file types. Now, LTB when processing these segments does not change these instances by a space.

· Issue with LTB not processing the translatable text included within an image tag This issue is now fixed and the translatable text is now processed correctly in image tag, below an example:

· Issue when a rule referenced an empty list. LTB used to produce an unhandled exception when a rule referenced an empty external list, now this has been fixed.

• Issue when a importing rules from the Linguistic Editor template into a .rul file. Previously LTB added in certain occasions additional quotes when importing from the Linguistic Editor template, these additional quotes prevented the rules from finding any matches during execution.

Support Files Updates

Core Configuration

· Updated: The file LTB_Core_Config.zip has been updated with these changes:

· Term and Punctuation:

o Core ALL STANDARD Duplicated Words.rul (updated)

o CORE ALL STANDARD Punctuation.rul (updated)

o Core ALL (Not French) STANDARD Spacing.rul (new rule, previously named: Core ALL (Not French) STANDARD Punctuation space before.rul )

o Core FR STANDARD Spacing ALL-FR.rul (new rule, previously named: Core FR STANDARD Punctuation space before ALL-FR.rul)

o Core FR-CA STANDARD Spacing ALL-FRCA.rul (new rule, previously named: Core FR-CA STANDARD Punctuation space before ALL-FRCA.rul)

o Core FR STANDARD Date Time EN-FR.rul (updated rule)

o New Core DE STANDARD Number Format EN-DE.rul (updated rule)

o New Core ES STANDARD Number Format EN-ES.rul (updated rule)

o New Core IT STANDARD Number Format EN-IT.rul (updated rule)

Term and Punctuation Rules

· New rules (46):

o Core ALL (Not French) STANDARD Spacing.rul (new rule, previously named: Core ALL (Not French) STANDARD Punctuation space before.rul )

This rule contains all spacing checks from the previous version of the rule Core ALL STANDARD Punctuation. This rule now uses formatted segments to avoid false positives related to the processing of certain tags.

o Core FR STANDARD Spacing ALL-FR.rul (new rule, previously named: Core FR STANDARD Punctuation space before ALL-FR.rul)

o Core FR-CA STANDARD Spacing ALL-FRCA.rul (new rule, previously named: Core FR-CA STANDARD Punctuation space before ALL-FRCA.rul)

o ALL STANDARD Strict Spacing.rul

This rule contains all spacing checks from the previous version of the rule ALL STANDARD Strict Punctuation. This rule now uses formatted segments to avoid false positives related to the processing of certain tags.

o FR STANDARD Grammar ALL-FR.rul

Detects common grammatical issues in French.

o FR STANDARD Negative-Affirmative Sentences EN-FR

Detect instances where affirmative sentences may have been translated as negative and vice versa. For example, prevents situations where "yes" may have been translated as "no".

o FR-CA STANDARD False Friends EN-FRCA.rul

Detects instances of common false friends for French (Canada).

o FR-CA STANDARD Equivalent Trade and Registered Marks.rul

Checks that registered marks, trademarks, copyright marks, service marks and sound recording copyright marks found in the source have been rendered in the Target with the equivalent symbol for French (Canada). ONLY USE this rule when the requirement for these marks is to use the French (Canada) equivalent in the Target. DO NOT Use in conjunction with the rule: ALL STANDARD Check Trade and Registered Marks.

o NB STANDARD Common English words left in Target EN-NB.rul

Detects instances of common English words left in the translation. In order to avoid duplicated output, this rule should only be used when in the Spelling component the option Ignore untranslated segments is enabled. This rule is case insensitive

• Microsoft Rules

o XX CUSTOM Microsoft Style Guide - Fictitious Information (e-mails) EN-XX.rul (New rule x 29 languages)

Checks for compliance with the Microsoft Fictitious information guidelines regarding e-mails.

o DA CUSTOM Microsoft Style Guide Punctuation EN-DA.rul

Checks for punctuation errors according to the Microsoft Style Guide for Danish for February 2011.

o FI CUSTOM Microsoft Style Guide Capital letter after colon EN-FI.rul

o FI CUSTOM Microsoft Style Guide Copyright symbols EN-FI.rul

o FI CUSTOM Microsoft Style Guide Noun case suffixes EN-FI

o FI CUSTOM Microsoft Style Guide Punctuation EN-FI.rul

Checks for errors on different topics according to the Microsoft Style Guide for Finnish.

o ZH-HK STANDARD Offensive Terms ALL-ZHHK.rul

Checks for instances of offensive terms in Chinese (Hong Kong SAR) segments.

o ZH-HK STANDARD PoliCheck ALL-ZHHK.rul

Checks for the most common geopolitical errors for Chinese (Hong Kong SAR).

· Updated rules (21):

o Core ALL STANDARD Punctuation.rul

All rules related to spacing have been removed from this rule and moved into the STANDARD Spacing rules. In addition, this rule has been fully reviewed to avoid duplicated output.

o ALL STANDARD Strict Punctuation.rul

All rules related to spacing have been removed from this rule and moved into the STRICT Spacing rules. All duplicated rules in the ALL STANDARD Strict Punctuation rule and the Core ALL STANDARD Punctuation have been removed from this rule. Thus going forward, this rule needs to be ALWAYS USED IN CONJUNCTION with the Core ALL STANDARD Punctuation.

o ES STANDARD Punctuation ALL-ES.rul

This rule has been updated to add a Spanish specific check with regards to the conjunction “, y” that was previously placed in the ALL STANDARD STRICT Punctuation.rul.

o FR STANDARD Punctuation ALL-FR.rul

o Core ALL STANDARD Duplicated Words.rul

In this release we have improved the exceptions for French: “vous vous” and have added an exception for Catalan: “a més a més”. We have added to this rule an external list to define exceptions: DupWordsPhrases_Blockers.txt list (NOTE: Entries in the list file are CASE-SENSITIVE; be sure to enter any common case variants needed and keep a copy of this list with a different name in order for this list not to be overwritten with the LTB autoupdate.)

o New Core DE STANDARD Number Format EN-DE.ru

o New Core ES STANDARD Number Format EN-ES.rul

o New Core IT STANDARD Number Format EN-IT.rul

New changes have been introduced to make this rule even more accurate and to reduce false positives further.

o ALL STANDARD Common English words left in target EN-ALL

Properties updated.

o Core FR STANDARD Date Time EN-FR.rul

This rule has been updated to correct a typo in rule ID. 40

o DA STANDARD Common English words left in Target EN-DA.rul

o IT STANDARD Common Errors ALL-IT.rul

New entries have been added and new exceptions have been defined to make the rule more accurate.

o IT STANDARD False Friends EN-IT.rul

Updated with new entries to avoid false positives related to the words: million and billion.

o IT STANDARD Grammar ALL-IT.rul

Added new common grammar errors (especially to detect concordance typos).

o IT STANDARD Punctuation EN-IT.rul

All checks from this rule already included in the Core ALL Standard Punctuation.rul and in the new Core ALL (Not French) STANDARD Spacing.rul have now been removed to avoid duplication.

o JA STANDARD CommonErrors ALL-JA.rul

o ZH-TW STANDARD Common Typos ALL-ZHTW.rul

o ZH-TW STANDARD PoliCheck ALL-ZHTW.rul

o ZH-TW STANDARD Forbidden CHS Terms All-ZHTW.rul

o ZH-TW STANDARD Offensive Terms ALL-ZHTW.rul

o ZH-TW STANDARD Punctuation EN-ZHTW.rul

These rule has been reviewed to reduce the number of false positives.

Entity Extractor Rules

· New rules (3):

o EN CUSTOM Microsoft Fictitious Company Names and URLs.rul

Detects instances of Microsoft Fictitious Company Names/Product Names or URLs as per the Microsoft Fictitious Company Name list.

o EN CUSTOM Microsoft Fictitious E-mails

Detects instances of e-mail addresses in the source as per the guidelines from: Fictitious Email Addresses.xls (Microsoft Fictitious information regarding e-mails).

o EN CUSTOM Microsoft Fictitious Proper Names.rul

Detects instances of Fictitious people names in Microsoft Content from these two lists:

1. International fictitious Names List

2. Fictitious people names secondary list

Localization teams must only use names from the two lists provided.

Dictionaries

· Updated dictionaries (3):

o Finnish.xpl

o French.xpl

o French (Canada).xpl

Documentation

· Help file has been updated with changes related to this release.

· Information about the functionality and usage of the rules installed with the Term and Punctuation has been updated with changes related to this version: http://autoupdate.lionbridge.com/ltb/_LTB_Installation_Rules_Description.html

___________________________________________________________________________________________________________________________________________

Lionbridge Linguistic ToolBox ver. 2.43 Update 2 - Release Notes

September 5th, 2011

Contents

We are pleased to announce a new release of Linguistic ToolBox ver. 2.43 Update 2. This update includes new fields in LTB Statistics tab for the word count excluding Ignored segments, fixes for important defects and a number of new and updated support files.

If you have any technical questions or in case you identify any bugs, please contact us.

Changes

· New fields in the LTB Statistics tab. The LTB Statistic tab now shows these new fields indicated below. Please note that now you can see the number of segments and word count including and excluding Ignore segments. Ignore segments on this context are those segments that have been ignored by these options: Ignore locked segments or marked as non-translatable and Ignore matches equal or above.

o No. of segments: Including and Excluding Ignored segments.

o No. of source words: Including and Excluding Ignored segments.

o No. of target words: Including and Excluding Ignored segments.

o Ratio False Positives to Source word count: Including and Excluding Ignored segments.

o Ratio False Positives to Total No. Entries: Including and Excluding Ignored segments.

Defects fixed

· Issue when processing Microsoft LocStudio input files with a Date filter applied. LTB produced this error message: "String was not recognized as a valid Date Time."

· Issue with LTB duplicating checks when processing Microsoft LocStudio .Lsproj files. These .Lsproj files only contain references to .lcl files and as a consequence when processing these files through LTB the checks on .lcl files used to be incorrectly duplicated.

· Issue with the Linguistic Editor’s Target Reference Mode and Source Reference Mode not taking into account case-sensitivity with the MCase option.

· Issue with LTB not using the Default report path set in File>Preferences>Output when loading a configuration file.

Support Files Updates

Core Configuration

· Updated: The file LTB_Core_Config.zip has been updated with these changes:

o Term and Punctuation:

o New Core ES STANDARD Number Format EN-ES.rul (new rule)

o New Core IT STANDARD Number Format EN-IT.rul (new rule)

o New Core DE STANDARD Number Format EN-DE.rul (updated rule)

o New Core FR STANDARD Number Format EN-FR.rul (updated rule)

o Core EN STANDARD Number Format 1,000.0 to 1.000,0.rul (updated rule)

Term and Punctuation Rules

· New rules (3):

o New Core ES STANDARD Number Format EN-ES.rul

o New Core IT STANDARD Number Format EN-IT.rul

o DA STANDARD Common English words left in Target EN-DA.rul

· Updated rules (12):

o ALL STANDARD Spacing.rul

Checks for extra or missing spaces in formatted files.

o ALL STANDARD Common English words left in Target EN-ALL.rul

o FR STANDARD Common English words left in target EN-FR.rul

Updated to be case insensitive.

o ES STANDARD Detect Old Spelling ALL-ES.rul (previously named: ES STANDARD Spanish Spelling Reform ALL-ES.rul)

o ES STANDARD Negative-Affirmative Sentences EN-ES.rul

o New Core DE STANDARD Number Format EN-DE.rul

o New Core FR STANDARD Number Format EN-FR.rul

o Core EN STANDARD Number Format 1,000.0 to 1.000,0.rul

Updated to remove all variants of Spanish and Italian from the list of languages for this rule.

· Microsoft Rules

o JA CUSTOM Microsoft MacUI (MS Style Guide ver.6).rul

Detects the Windows UI strings that are different from Mac UI strings according to the Microsoft Style Guide ver. 6.

o JA CUSTOM Microsoft Style Guide ver.6.rul

Checks compliance with the Microsoft Style Guide Requirements (Style Guide 6). Note that most unchanged rules are still based on Style Guide 5.

o JA CUSTOM Microsoft Character Spacing (MS Style Guide ver.6).rul

Updated to remove false positives when LTB detects editorial symbol and delimiter.

o JA CUSTOM Microsoft Katakana (MS Style Guide ver.6).rul

Updated to revise the incorrect description in error log written out.

Dictionaries

· Updated dictionary (1):

o Italian.xpl

Documentation

· Help file has not been updated with changes related to this release.

· Previous Release Notes are available at: http://autoupdate.lionbridge.com/ltb/PreviousReleaseNotes.htm

Known Issues

There are updates for Known Issues related to this release: http://autoupdate.lionbridge.com/ltb/KnownIssues.htm

___________________________________________________________________________________________________________________________________________

Lionbridge Linguistic ToolBox ver. 2.43 - Release Notes

August 3rd, 2011

Contents

New Features

Entity Extractor Rules

Term and Punctuation Rules. 1

We are very pleased to announce a new release of Linguistic ToolBox ver. 2.43. In this version we have added a new Quality Control Component: the LTB Random Sampling. This new component automatically generates a random bilingual sample of a selected number of words to be used for LQI. This version also includes some fixes for important defects and a large number of new and updated support files. Please pay particular attention to the new updated rules for the Microsoft account.

If you have any technical questions or in case you identify any bugs, please contact us.

New Features

· New component: LTB Random Sampling. The LTB Random Sampling component automatically generates a bilingual sample of a selected number of words to be used for LQI or other purposes. This functionality can be used either on its own or combined with pre-defined LTB checks that are executed on the automatically generated sample to provide the reviewer with additional information on potential linguistic issues.

Defects fixed

· Issue with spell-checking on monolingual files. Previously users got this error message when trying to carry out the spell-checking on monolingual files: “Input files, target language [None] is not installed in Microsoft Word.”

· Issue with LTB temporary dictionaries created to save “correct” and “incorrect” words. These dictionaries were case-insensitive instead of case-sensitive.

· Issue with LTB not saving the Filter using previous report report within a configuration file.

· Issue with how support “lists” were converted to regular expressions.

Support Files Updates

Core Configuration

· Updated: The file LTB_Core_Config.zip has been updated with these changes:

o Term and Punctuation:

o New Core DE STANDARD Number Format EN-DE.rul (new rule)

o New Core FR STANDARD Number Format EN-FR.rul (new rule)

o Core EN STANDARD Number Format 1,000.0 to 1.000,0.rul (updated rule)

o Core EN STANDARD Number Format 1,000.0 to 1 000,0.rul (updated rule)

Entity Extractor Rules

· New rules (1):

o ALL STANDARD Segmentation Checker.rul

Checks for the most common type of segmentations issues in files prepared for translation: articles found at the end of the segment, instances of letters in initial uppercase not at the beginning of the sentence and possible sentence fragment (begins with lowercase, ends with period) and highlights situations where potential sub-segmentation may be required.

Term and Punctuation Rules

· New rules (10):

o New Core DE STANDARD Number Format EN-DE.rul

o New Core FR STANDARD Number Format EN-FR.rul

o ALL STANDARD Spacing.rul

Checks for extra or missing spaces in formatted files.

o FR STANDARD Common English words left in target EN-FR.rul

Detects instances of common English words left in the translation. This rule has been modified to eliminate false positives caused by words that are the same in English and French.

o IT STANDARD Grammar ALL-IT.rul

Detects common grammar issues for Italian.

· Microsoft Rules

o ALL CUSTOM Microsoft Style Guide TradeMarked Names.rul

Checks that trademarked names and the name Microsoft Corporation remain unlocalized, as per the list of Microsoft trademarks (updated on June 15th, 2011) available here.

o NB CUSTOM Microsoft Style Guide EN-NB.rul

Checks compliance with the Microsoft Style Guide Requirements for Norwegian Bokmal (Updated on March 31st, 2011).

o SV CUSTOM Microsoft Style Guide Fictitious Information EN-SV.rul

Checks for compliance with the Microsoft Style Guide regarding Sev. 1 - Fictitious Information

o SV CUSTOM Microsoft Style Guide Genitive EN-SV.rul

Checks for compliance with the Microsoft Style Guide regarding Sev. 1 - Genitive.

o SV CUSTOM Microsoft Style Guide Negative Affirmative EN-SV.rul

Checks the Swedish translation for compliance to Microsoft Style Guide regarding Sev. 1 - Negative and affirmative sentences.

· Updated rules (19):

o IT STANDARD Common Errors ALL-IT.rul

Specific checks for Grammar issues have been removed from this list and can be found now in the IT STANDARD Grammar ALL-IT.rul. Additional checks for common spelling mistakes have been added.

o ES STANDARD Common Errors ALL-ES.rul

o ES STANDARD Detect Old Spelling ALL-ES.rul (previously named: ES STANDARD Spanish Spelling Reform ALL-ES.rul)

o ES STANDARD Grammar ALL-ES.rul

o ES STANDARD Mistranslations EN-ES.rul

o ES STANDARD Monolingual Detect Old Spelling.rul (previously named: ES STANDARD Monolingual Spanish Spelling Reform.rul)

o ES STANDARD Negative-Affirmative Sentences EN-ES.rul

o ES STANDARD Rude Words and Vulgarisms ALL-ES.rul

These seven rules for Spanish have been updated with feedback from users to remove false positives and new checks have been added.

o FI STANDARD Rude_words_and_vulgarisms ALL-FI.rul

o FI STANDARD Additional_grammar_and_punctuation_check ALL-FI.rul

o EN STANDARD Detect Corrupt Chars or Wrong Lang ALL-EN.rul

o ES STANDARD Detect Corrupt Chars or Wrong Lang EN-ES.rul

o FI STANDARD Detect Corrupt Chars or Wrong Lang EN-FI.rul

These thee rules now check for sequences of corrupt characters and they exclude false positives related to the degree sign or to Greek letters.

o Core EN STANDARD Number Format 1,000.0 to 1.000,0.rul

Updated to remove German from the list of languages for this rule.

o Core EN STANDARD Number Format 1,000.0 to 1 000,0.rul

Updated to remove French from the list of languages for this rule.

· Microsoft Rules

o JA CUSTOM Microsoft MacUI (MS Style Guide ver.6).rul

Detects the Windows UI strings that are different from Mac UI strings according to the Microsoft Style Guide ver. 6.

o JA CUSTOM Microsoft Style Guide ver.6.rul

Checks compliance with the Microsoft Style Guide Requirements (Style Guide 6). Note that most unchanged rules are still based on Style Guide 5.

o JA CUSTOM Microsoft Character Spacing (MS Style Guide ver.6).rul

Updated to remove false positives when LTB detects editorial symbol and delimiter.

o JA CUSTOM Microsoft Katakana (MS Style Guide ver.6).rul

Updated to revise the incorrect description in error log written out.

· Deleted rules (1):

o JA_CUSTOM_MS_TermStudio_EN_JA.rul

Rule deleted due to large volume of false positives. Alternative rule will be provided in the near future to check for key Microsoft Terminology for Japanese.

Dictionaries

· New dictionaries (1):

o EN(UK)_Travel_&_Leisure.xpl

· Updated dictionaries (6):

o ES_Life Sciences.xpl

o Finnish.xpl

o French (Canada).xpl

o Galician.xpl

o Italian.xpl

o Spanish.xpl

Documentation

· Help file has been updated with changes related to this release.

· Information about the functionality and usage of the rules installed with the Term and Punctuation is available but has not been updated with changes related to this version: http://autoupdate.lionbridge.com/ltb/_LTB_Installation_Rules_Description.html

· Previous Release Notes are available at: http://autoupdate.lionbridge.com/ltb/PreviousReleaseNotes.htm

Known Issues

There are no updates for Known Issues related to this release: http://autoupdate.lionbridge.com/ltb/KnownIssues.htm

___________________________________________________________________________________________________________________________________________

Lionbridge Linguistic ToolBox ver. 2.42 Update 5- Release Notes

June 2nd, 2011

Contents

Enhancements. 1

Defects fixed. 1

Support files Updates. 1

Core Configuration. 1

Dictionaries. 2

Documentation. 2

Known Issues. 2

We are pleased to announce a new release of Linguistic ToolBox ver. 2.42 Update 5. In this version we have fixed important defects in relation to the parsing of LTB, especially for XLIFF file formats and have also released a large number of new and updated Term and Punctuation rules and dictionaries.

If you have any technical questions or in case you identify any bugs, please contact us once you have checked with your Site Expert through Service Desk.

Enhancements

· XHTM and XHTML file extensions are now automatically identified in the Add Input files tab, under Type.

Defects fixed

· Issue with LTB not processing XLIFF files when the group <group id=“x”> appears before <trans-unit>.

· Issue with LTB not parsing correctly XLIFF from Idiom containing merged segments under certain particular conditions.

· Issue with LTB parser not working correctly for the Change Report component when input files contains Tracked Changes.

· Issue in the Segment Checker, the option Ignore CaMelWords was not working correctly when used in conjunction with the option Check if source equals target.

· Issue with LTB producing an unhandled exception when processing files that contain segments in the header or footer.

Support files Updates

Core Configuration

· Updated: The file LTB_Core_Config.zip has been updated with these changes:

o Term and Punctuation:

§ CORE TH STANDARD Detect Redundant Punctuation.rul (new rule)

§ Core ALL STANDARD Tags Generic.rul (updated)

o Spelling: New dictionaries have been added for these three languages: Albanian, Malay and Galician.

Term and Punctuation Rules

· New rules (11):

o CORE TH STANDARD Detect Redundant Punctuation.rul

Detects unnecessary punctuation in Thai including instances of a full stop at the end of sentence.

o ES CUSTOM Microsoft Country Names EN-ES.rul

Checks that country names have been correctly translated from English into Spanish, as per the country names approved by Microsoft in TermStudio (May 3rd, 2011).

o DE STANDARD Formal Style ALL-DE.rul

Detects instances of usage of formal style in German. This rule is applicable for those cases where the guideline is to use the "personal" you (du) in German rather than the "formal" you (Sie).

o DE STANDARD STRICT Formal Style.rul

Detects instances of usage of formal style in German. This rule is applicable for those cases where the guideline is to use the "personal" you (du) in German rather than the "formal" you (Sie). This rule is stricter than the DE STANDARD Formal Style version.

o DE STANDARD Grammar.rul

Detects common grammatical issues in German.

o BG STANDARD Grammar.rul

Detects common grammatical issues in Bulgarian.

o ZH-CN STANDARD Space Between Single Byte and Double Byte.rul

Detects instances of space between single byte character and double byte characters. Some accounts requires that there should be NO space between English character and Chinese character.

o ZH-HK STANDARD TW terms appear in HK translation ALL-ZHHK.rul

Detects instances of terms in Chinese (Traditional) in Chinese (Hong Kong) content.

o ZH-TW STANDARD HK terms appear in TW translation ALL-ZHTW.rul

Detects instances of Chinese (Hong Kong) terms in Chinese (Traditional) content.

o ZH-TW STANDARD Forbidden CHS Terms All-ZHTW.rul

Checks for forbidden Chinese (Simplified) Terms in Chinese (Traditional) content.

o ZH-TW STANDARD Punctuation EN-ZHTW.rul

Checks for common punctuation errors for Chinese (Traditional).

· Updated rules (12):

o Core ALL STANDARD Tags Generic.rul

Updated to remove false positives when the order of the tags has been altered.

o ALL STANDARD Software Checks.rul

Updated to remove false positives related to ampersands not used as hotkeys.

o ES CUSTOM Microsoft Style Guide EN-ES.rul

Updated according to the latest changes in the Microsoft Style Guide in March 2011.

o ES CUSTOM Microsoft Geopolitical Issues EN-ES.rul

Updated as per the latest Policheck output received from Microsoft.

o ES STANDARD Monolingual Spanish Spelling Reform.rul

o ES STANDARD Spelling Reform ALL-ES.rul

Updated to add more exhaustive checks for the Spanish Spelling Reform.

o ES Standard Spelling Errors ALL-ES.rul

Updated to remove the check for typos related to the usage of “se/sé”.

o ES STANDARD Negative-Affirmative Sentences EN-ES.rul

Small update to deal also with mistranslations related to cannot / cannot / can’t.

o ES STANDARD Neutral Spanish ALL-ES.rul

Updated to eliminate false positives related to variations of the verb “coger”.

o ES STANDARD Rude Words and Vulgarisms ALL-ES

Rule related to the term "cas" has been removed.

o ES STANDARD Common Errors ALL-ES.rul

Updated with new entries.

o ZH-TW STANDARD Common Typos ALL-ZHTW.rul

Updated with new entries.

Dictionaries

· New dictionaries (3):

o Albanian.xpl

o Malay.xpl (Brunei Darussalam)

o Galician.xpl

· Updated dictionaries (3):

o Spanish.xpl

o Hindi.xpl

o DE_LifeSciences.xpl

Documentation

· Help file has not been updated with changes related to this release.

· Previous Release Notes are available at: http://autoupdate.lionbridge.com/ltb/PreviousReleaseNotes.htm

Known Issues

There are no updates for Known Issues related to this release: http://autoupdate.lionbridge.com/ltb/KnownIssues.htm

___________________________________________________________________________________________________________________________________________

Lionbridge Linguistic ToolBox ver. 2.42 Update 4- Release Notes

March 24th, 2011

Contents

Changes

___________________________________________________________________________________________________________________________________________

We are pleased to announce a new release of Linguistic ToolBox ver. 2.42 Update 4. In this version we have added four new languages to the list of languages for Linguistic ToolBox (Bosnian (Latin), Bosnian (Cyrillic), Lingala and Malagasy). In addition, we have fixed important defects in relation to the XLIFF Parser and we have improved the tokenization process for the spelling component to make the Spelling component more efficient and prevent false positives related to parsing issues.

If you have any technical questions or in case you identify any bugs, please contact us once you have checked with your Site Expert.

· For Lionbridge users, please use Service Desk.

· For non Lionbridge users, you can contact us at GTLTBSupport@lionbridge.com.

Changes

· New Languages. Four new languages have been added to the list of languages of Linguistic ToolBox: Lingala, Malagasy, Bosnian (Latin) and Bosnian (Cyrillic).

Defects fixed

· Issue with LTB incorrectly merging segments in the LTB Output reports when processing XLIFF files. This issue happened when groups of segments contain a “merge-trans” value.

· Issue with LTB not being able to parse particular types of XLIFF files with split/merged segments. When trying to process these files, LTB reported this error message: “Object reference not set to an instance of the object”.

· Issue with LTB XLIFF parser not parsing correctly Xliff files without header and nested groups. In this situation LTB produced this error message: “Sequence contains no elements”.

· Issue with LTB parsing for XLIFF files not displaying TAG marks to replace internal XLIFF formatting tags after the parsing has been completed.

· Issue with LTB not processing specific XLIFF files. In these situations, LTB produced this error message: “Unexpected end tag. Line 1, position 3".

· Issue with LTB parser for RTF incorrectly removing hyperlinks.

· Issue with LTB parsers merging incorrectly words when there was no space in between tags. Now the LTB tokenization process for spelling has been changed to follow a double tokenization pass to address this issue and make the spell-check more efficient.

· Issue in the Input tab, when clicking on the Add Folder button some users got an unhandled exception and were not able to use this functionality.

· Issue in the Input files tab, when adding a folder containing Microsoft LocStudio files and selecting under the Type column: LCX, LTB did not process any of the files.

· Issue with LTB rules that contained reserved “XML” characters in the Description field. Whenever Entity Extractor or Term and Punctuation rules contained any of the reserved XML characters in the Rule Description field such as: &, <, >, etc. whenever the rule was added the user would get an error messaging: “Invalid rule or rule not well formed”.

· Issue in the Source Analysis component, when the path to the exceptions or known cases lists was incorrect, the error message displayed was not correct.

Support files updates

There are no updates to support files with this release.

Documentation

· Help file has not been updated with changes related to this release.

· Information about the functionality and usage of the rules installed with the Term and Punctuation is available at: http://autoupdate.lionbridge.com/ltb/_LTB_Installation_Rules_Description.html

· Previous Release Notes are available at: http://autoupdate.lionbridge.com/ltb/PreviousReleaseNotes.htm

Known Issues

The Known issues have been updated: http://autoupdate.lionbridge.com/ltb/KnownIssues.htm

Lionbridge Linguistic ToolBox ver. 2.42 - Release Notes

January 20th, 2011

Contents

New Features

Enhancements

Entity Extractor Rules

Term and Punctuation Rules

We are pleased to announce a new release of Linguistic ToolBox ver. 2.42. In this version we have implemented a workaround to be able to ignore Idiom ICE Matches and have introduced a new field to filter by date when using Microsoft LocStudio files as input. LTB is now able to deal correctly with hotkeys for Asian languages that follow this format (&H) or (&H), this change will reduce greatly the number of false positives related to hotkeys. We have also made a number of important enhancements to the LTB parsers for these file formats (Idiom, XLIFF, tab-separated file formats, XML file formats and DITA) and also, to the Change Report.

If you have any technical questions or in case you identify any bugs, please contact us once you have checked with your Site Expert.

· For Lionbridge users, please use Service Desk.

· For non Lionbridge users, you can contact us at GTLTBSupport@lionbridge.com.

New Features

· Idiom ICE Matches are automatically assigned a 200% match in the LTB output reports. Idiom has an equivalent to our “Context Matches” called ICE (which stands for In-Context Exact match). In some cases, these are set to Locked when exported from Idiom World Server, but that isn’t technically necessary and isn’t always the customer’s preference. Sometimes, there are thousands of these ICE segments that are NOT locked but should be ignored for LTB checks. These ICE Matches are automatically assigned by LTB a 200% match, you can ignore them by using the option Ignore matches equal or above to 200%.

· LocStudio Files – Filter Settings now include a new option to Filter by Date: Modified After.

Enhancements

· Hotkeys. LTB now also identifies hotkeys also when they follow this format (&H;) or (&H) for these components QUICK, Segment Checker (Ignore hotkeys) and Term and Punctuation (Ignore hotkeys (unformatted segments) and Speller.

· The items on the LocStudio Files Filter Setting now appear ordered alphabetically.

· Filter using previous report functionality has been enhanced to also work for situations where the order of the columns Source, Translation, Issue and Ignore? may have been altered.

· The issues reported by the QUICK component have been renamed as follows:

o "Target term not found in Glossary" has been renamed as "Target Term not found in reference"

o "Multiple Targets found in glossary" has been renamed as "Multiple Targets found in reference"

o "Source not found in glossary" has been renamed as "Source not found in reference"

· The <menucascade> element from XML DITA files is parsed by LTB in the same way as DITA parsers.

· When processing XLIFF files from Idiom, LTB output used to display the Idiom placeholders, for example {11}, {12}, etc. Now we have enhanced the parsing of LTB to ensure that these placeholders going forward are displayed as tags following the same behavior of standard XLZ or TMX file formats.

· Change Report functionality has been enhanced to automatically ignore differences related to leading and trailing spaces in source and target segments.

Defects fixed

· Issue with LTB displaying this warning message each time that LTB was run without using one or more of the Quality Control Components.

· The warning message "This workbook contains links to other data sources" each time LTB runs without using one or more of the Quality Control Components, does not appear any longer.

· Issue with Lionbridge internal users of Windows 7 (64 bits) not being able to use the Linguistic Editor from the Term & Punctuation component.

· Issue in QUICK when using the option Report unmatched together with a Custom Tag Pattern. When these two options were used together QUICK did not report any unmatched entries.

· Issue in QUICK when using the option Custom Tag Pattern, in the LTB Output Report the Formatted Source and Formatted Translation columns did not show any format.

· Issue with over segmentation in tab separated file formats (.xls, .csv, .txt) due to abbreviations using a period at the end. This issue produced a number of false positives in different components. This change only affects Excel file formats.

· Issue with LTB not parsing correctly separator tags. Previously LTB did not manage correctly separator tags (for example, , <cite>, <code> or <div>) if these tags contained attributes.

· Issue with LTB not parsing correctly <ph> tags for XLIFF files, as a consequence some internal text was incorrectly processed by LTB. Now both the LTB XLIFF Parser and the TMX parser substitute <ph> tags with ^TAG^.

· Issue with the RTF Parser when dealing with extended characters. When extended characters were found in unsegmented text, the LTB Parser for RTF did not convert these extended characters into their equivalent Unicode character.

· Issue with LTB not processing segments included in between <tu> tags that don’t have any attributes (for example, <tu id:XX> or <tu srclang:en>)

· Issue with LTB not parsing correctly a Trados file.

· Issue with LTB not ignoring segments that appear "crossed out" in the .XLIFF Editor. These "crossed out" segments are segments that have been expanded or shrunk, and should be ignored.

· When parsing several tags without spaces in between LTB generates some false positives due to concatenations in certain situations.

· Issue with LTB not ignoring   entities when parsing Idiom XLZ files.

· Issues in Change Report:

o Align file names functionality has been restored.

o Error messages related to added or removed segments in relation to the original file set have been rewritten for clarity purposes.

o When selecting the option Ignore matches equal or above to: 101%, Change Report only applied this ignorability option to the reviewed files and not to the original files.

· In the XML to TMX Converter, the tag <nbsp /> was incorrectly removed by LTB when converting Helium files into TMX. With this fix, LTB will replace this tag with a space in the TMX.

· Issue with LTB falsely reporting some entries as inconsistent with the Clean for MT (Beta) tool.

Support files updates

Core Configuration

· Updated: The file LTB_Core_Config.zip has been updated with these changes:

o In the Term and Punctuation:

o CORE ALL STANDARD Punctuation.rul has been updated to remove these two checks below to reduce the output:

§ Punctuation: Extra or missing space at start of segment (Rule ID: 24)

§ Punctuation: Extra or missing space at end of segment (Rule ID: 25)

These two checks (Rule ID: 24 and 25) are still available in the ALL STANDARD Strict Punctuation.rul.

o Core FR STANDARD Punctuation space before ALL-FR.rul

We have added a new check to ensure that there is always a space before the % sign for French. Previously named: Core FR STANDARD Punctuation ALL-FR.rul

o Core FR-CA STANDARD Punctuation space before ALL-FRCA.rul

Rule ID: 2 has been modified as it reported incorrectly as issues situations when there was no space before semi colon (;). Previously named: Core FR-CA STANDARD Punctuation ALL-FRCA.rul

o In the Segment Checker, the options below have been enabled:

§ Ignore case and punctuation

§ Ignore end punctuation

§ Ignore alphanumeric only segments

· New rules:

o ALL STANDARD Common English words left in target EN-ALL.rul

Detects instances of common English words left in the translation.

o ES STANDARD Negative-Affirmative Sentences EN-ES.rul

o NL STANDARD Negative-Affirmative Sentences EN-NL.rul

Both rules above, detect instances where affirmative sentences may have been translated as negative and vice versa. For example, prevents situations when "yes" may have been translated as "no".

o ES STANDARD Spanish Spelling Reform ALL-ES.rul

o ES STANDARD Monolingual Spanish Spelling Reform ALL-ES.rul

Checks for adherence to the changes in the Spanish Spelling Reform in bilingual and monolingual files. The Spanish Spelling Reform was approved by the 22 Academies of the Spanish Language on 28th November 2010.

o ES STANDARD Passive Voice ALL-ES.rul

Extracts passive verb forms from target segments.

o JA CUSTOM Microsoft Style Guide ver. 6.rul

Japanese custom list for Microsoft, containing the style rules adherent to Japanese Style Guide 6. Note that most unchanged rules are still based on SG5.

o JA CUSTOM Microsoft MAC UI (Microsoft Style Guider ver. 6).rul

Detects the Windows UI strings that are different from Mac UI strings.

o JA CUSTOM Microsoft Katakana (Microsoft Style Guide ver. 6).rul

Japanese custom list for Microsoft, containing rules of the elongation mark usage and the spaces within a compound noun for Katakana letters adherent to Japanese Style Guide 6. Note that most rules have not been changed since SG5 and this newly includes the new cho-on rules.

o JA CUSTOM Microsoft Character Spacing (MS Style Guide ver. 6).rul

Japanese custom list for Microsoft, containing the character spacing rules adherent to Japanese Style Guide 6.Fully compatible with Style Guide 5.Note that in most case you cannot apply this rule against software strings containing such as placeholders and tagged RTF files, unless you turn on "Use Formatted Segments" option in the properties window of the rule. This rule replaces JA_CUSTOM_MS_CharSpacing_SG5.rul.

o RU STANDARD DateTime EN-RU.rul

Checks that dates/times in RU target segment correspond to EN source and that they follow the correct format. Please note: If date format should not match Russian date format, exclude this rule (i.e. if 11/9/07, acc. to style guide, should be 9 ноября 2007 года, not 09/11/2007). 1-го октября and suchlike, ranges like 5 или 6 июня are not accounted for. Jan 18 should be 18 января, else an error is added to LTB report. 'May' in source should be capitalized to match (to avoid false positives with the modal verb 'may').

o Core FR STANDARD Punctuation space before ALL-FR.rul

We have added a new check to ensure that there is always a space before the % sign for French. Previously named: Core FR STANDARD Punctuation ALL-FR.rul

o Core FR-CA STANDARD Punctuation space before ALL-FRCA.rul

Rule ID: 2 has been modified as it reported incorrectly as issues situations when there was no space before semi colon (;). Previously named: Core FR-CA STANDARD Punctuation ALL-FRCA.rul

o DE CUSTOM Microsoft Common Errors EN-DE.rul

Renamed rule. Previously named: DE_Microsoft_Errors_en-de.rul

· Updated rules:

o ALL STANDARD Strict Punctuation.rul

These two new checks have been introduced as they have been removed from the rule CORE ALL STANDARD Punctuation.rul:

§ Punctuation: Extra or missing space at start of segment (Rule ID: 24)

§ Punctuation: Extra or missing space at end of segment (Rule ID: 25)

o CORE ALL STANDARD Punctuation.rul

These two checks have been removed in order to reduce the output produced by the Core configuration:

§ Punctuation: Extra or missing space at start of segment (Rule ID: 24)

§ Punctuation: Extra or missing space at end of segment (Rule ID: 25)

These two checks (Rule ID: 24 and 25) are still available in the ALL STANDARD Strict Punctuation.rul.

o IT STANDARD Common Errors ALL-IT.rul

o IT STANDARD False Friends EN-IT.rul

These two rules have been updated with a view to reduce false positives.

o RO STANDARD Detect Corrupt Chars or Wrong Lang EN-RO.rul

o RO STANDARD Monolingual Detect Corrupt Chars or Wrong Lang.rul

These two rules have been modified to add Romanian (Romania) target language.

o SV STANDARD Detect Corrupt Chars or Wrong Lang EN-SV.rul

o SV STANDARD Monolingual Detect Corrupt Chars or Wrong Lang.rul

These two rules have been modified to accept the character é as a valid Swedish character.

· Deleted rules:

o Core FR STANDARD Punctuation ALL-FR.rul

o Core FR-CA STANDARD Punctuation ALL-FRCA.rul

o DE_Microsoft_Errors_en-de.rul

The three rules above have been deleted as they have been renamed for clarity purposes.

o JA_CUSTOM_MS_Katakana.rul

o JA_CUSTOM_MS_StyleGuide5.rul

The three rules above have been deleted as they have been updated to comply with the Microsoft Style Guide for Japanese ver. 6.

Entity Extractor Rules

· New rules:

o EN STANDARD Cross References.rul

Detects instances of inconsistent cross references.

o EN STANDARD Procedural Sentences.rul

Detects instances of procedural sentences.

o ES STANDARD Passive Voice.rul

Extracts passive verbs from source segments.

Dictionaries

· New dictionaries:

o EN(US)_Life Sciences.xpl

· Updated dictionaries:

o ES_Life Sciences.xpl

o Finnish.xpl

o French (Canada).xpl

o FR_Life_Sciences_Medical_devices_&_specialities.xpl

Documentation

· Help file has been updated with changes related to this release.

· The document with information about the functionality and usage of the rules installed with the Term and Punctuation component have been updated: http://autoupdate.lionbridge.com/ltb/_LTB_Installation_Rules_Description.html

· Previous Release Notes are available at: http://autoupdate.lionbridge.com/ltb/PreviousReleaseNotes.htm

Known Issues

The Known issues have been updated: http://autoupdate.lionbridge.com/ltb/KnownIssues.htm

___________________________________________________________________________________________________________________________________________

Lionbridge Linguistic ToolBox ver. 2.40 Update 1 – Release Notes

October 21, 2010

Contents

Enhancements

Term & Punctuation Rules

Entity Extractor Rules

We are pleased to announce a new release of Linguistic ToolBox ver. 2.40 Update 1. In this version we have implemented fixes for several defects and we have added new and updated rules for both the Term & Punctuation component and the Entity Extractor.

If you have any technical questions or in case you identify any bugs, please contact us once you have checked with your Site Expert.

· For Lionbridge users, please use Service Desk.

· For non Lionbridge users, you can contact us at GTLTBSupport@lionbridge.com.

Enhancements

· In the LTB output report there has been some changes in the QUICK component and in the Spelling Component. In the QUICK tab the column “Comments” has been renamed to “Issues” and in the Spelling tab, there have been two changes, the column “Misspelled word” has been renamed to “Match” and a new column has been created called “Issue” to contain Spelling errors and Grammar Errors.

· LTB Helper has been updated with changes related to the above enhancement.

Defects fixed

· Issue with some specific LocStudio filters not appearing in the Settings file.

· Issue with non-Latin characters not displaying correctly in LocStudio filters in the Settings file.

· Issue with .Lspkg files when the first string was empty an unhandled exception used to occur

· Issue with the data from the formulas in the LTB Statistics tab not displaying correctly for Office 2003 users.

· Issue with LocStudio locked strings being incorrectly reported as Segments with empty target.

· Issue with the Segment Checker option: Ignore Camel Words incorrectly identifying some words that were not CaMel words. This was a consequence of mixing up LogoportMarkup styles with normal text within a translation unit.

· Issue with LTB incorrectly processing a type of locked segments in Idiom XLIFF files when the Segment Checker option: Ignore locked segments or marked as non translatable was enabled. This issue only happened for files that used the attribute node: “lock_status” for each unit.

· Issue with LTB incorrectly considering legacy segments for the Segment Checker checks when the option Ignore matches equal or above to was enabled.

Support files updates

Term and Punctuation Rules

· New rules:

o ALL STANDARD Detect Wrong Variable Order.rul

Checks that the variables/placeholders in the translation follow the original order in the source. This rule works for these types of variables: %s1, %(w)d and %1.

o RU STANDARD Country Names EN-RU.rul

Checks that country names have been correctly translated from English into Russian. PLEASE NOTE: Use the option: Ignore untranslated segments in the Term and Punctuation Checker to use in documents with addresses where country names could have been left in English.

· Updated rules:

o NB CUSTOM Microsoft EN-NB.rul

Entity Extractor Rules

· New rules:

o EN STANDARD Chat and Text Abbreviations.rul

Detects instances of common chat and text abbreviations, such as: LOL, TTYL, FYI, etc.

o EN STANDARD Rude Words.rul

Detects instances of rude words and vulgarisms in English.

o ALL STANDARD Monolingual Duplicated Words.rul

Checks for duplicated words in monolingual files or in the source for bilingual files.

· Updated rules:

o ALL STANDARD Expanded Acronyms.rul

Dictionaries

· Updated dictionaries:

o Norwegian (Bokmål).xpl

Documentation

· Help file has not been updated with changes related to this release.

· Previous Release Notes are available at: http://autoupdate.lionbridge.com/ltb/PreviousReleaseNotes.htm

Known Issues

The most up-to-date information on Known issues can be found at: http://autoupdate.lionbridge.com/ltb/KnownIssues.htm

___________________________________________________________________________________________________________________________________________

Lionbridge Linguistic ToolBox ver. 2.40 – Release Notes

September 21, 2010

We are pleased to announce a new release of Linguistic ToolBox ver. 2.40. In this version we have implemented support for the new Microsoft® Localization Studio file formats. We have also included new ignorability options and functionality with a view to reduce the number of false positives. And in relation to our efforts to adapt LTB even more for Machine Translation tasks, we have created two brand new tools to assist with MT preparation tasks.

In addition, as usual, there are many other enhancements and bug fixes as part of this release; see below for more details.

IMPORTANT NOTE: The installation requirements have changed and LTB users must install .Net Framework 4 prior to installing/updating to ver. 2.40. This is a mandatory requirement. Please note that .Net Framework 4.0 has not been tested internally yet to ensure compatibility with other applications and this may cause unexpected issues.

If you have any technical questions or in case you identify any bugs, please contact us once you have checked with your Site Expert.

· For Lionbridge users, please use Service Desk.

· For non Lionbridge users, you can contact us at GTLTBSupport@lionbridge.com.

New Features

· Support for the new Microsoft LocStudio file formats (LCL, LCX and Lspkg). Thanks to this development, there is no need to export to.CSV file format to use the new LocStudio file formats with LTB. As part of this new release, we have also included a new feature to enable users to apply filters to the LocStudio files (Input files tab>Settings). Please note that you can also use LocStudio new file formats as QUICK glossaries for ensuring consistency between UI and UA and in the Change Report to compare two versions of the same LocStudio files.

· New Ignorability options in the Quality Control components:

o Ignore untranslated segments (option added to the QUICK component and Term & Punctuation)

o Ignore segments with empty target (option added to the Term & Punctuation component)

o Ignore hotkeys (option added to the Segment Checker and Term & Punctuation component). This option only deals with the standard type of hotkeys, indicated with &, such as, for example: &Organizer. This option does not deal with the new LocStudio hotkeys indicated with an underscore, for example: Move Dow_n.

o Ignore end punctuation (option added to the Segment Checker). The overall performance of this option has been improved.

Please note that the previous Segment Checker option>Ignore hotkeys and end punctuation has now been replaced with two separated options: Ignore hotkeys and Ignore end punctuation. Both of these options only affect the inconsistency checks.

· Dictionaries for multiple language variants included within multilingual configuration files now will behave as follows: For example if you have a multilingual configuration file containing dictionaries for Spanish and Spanish (Mexico), the behavior will be as follows:

o If you select Spanish (Argentina) as your Target Language under Project options, the dictionary loaded by default in the Spelling tab would be Spanish.xpl (as there is no matching dictionary for the Spanish (Honduras) language variant.

o If you select Spanish (Mexico) as your Target Language under Project options, the dictionary loaded by default in the Spelling tab would be Spanish (Mexico).xpl (as there is a match with the language variant of the dictionary).

· Clean for MT Tool (Beta). This tool cleans-up and prepares bilingual translation memories with a view to use these resources to train Statistical Machine Translation Systems (SMTS). This tool automatically performs the most common type of checks required to prepare legacy TMs for Machine Translation, for example: segment length, direct and reverse consistency, tag checks, etc. With the Clean for MT tool, we obtain two different types of output:

o "correct" output (correct.tmx): this is the output with potentially correct bilingual material for its direct use for SMTS.

o "incorrect" output (inconsistent.tmx, revinconsistent.tmx and rule_name.tmx ): this is the output with wrong alignments or potentially wrong segments, so these can be reviewed, edited or discarded if necessary.

· Extract TMX Tags Tool (Beta). This tool extracts from translation memories in TMX 1.1 and TMX 1.4b file formats internal tags and internal group tags, reporting the following information for each tag: Tag name, Count, Type of Tag, Content surrounded by the tag and Examples. In addition, the report provides a summary of the total number of tags and the total number of unique tags in both source and target segments.

Changes

· Installation requirements have changed: LTB users must install .Net Framework 4 prior to installing/updating to this new version. This is a mandatory requirement.

· User Interface of LTB has been made larger in order to support fonts in different languages. This new UI should be used in conjunction with a DPI Setting of 96.

· In the LTB Installer references to the Logoport Word Client have been modified with references to Translation Workspace Microsoft Word plug-in.

· Languages.xml installation file has been updated to ensure consistency with the ISO Language codes used by the LTB Glossary Converter script.

· Two new input languages have been added to LTB: English (Singapore) and English (India).

Enhancements

· In the LTB output report now you can identify under the Status column, segments locked or marked as non-translatable. In the LTB output report these segments are identified following this convention: Blocked – match percentage, for example: “Blocked-100%”.

· LTB Statistics tab is now available by default in the generated LTB output report. Previously this tab was only visible in the LTB output report once the LTB Helper had been activated. Now, this tab is available by default and the statistical information is automatically populated by either using the LTB Helper or by entering manually Ignore or Mark under the Ignore column in the LTB output report.

· Show additional Source/Translation columns in the report. This new option under File>Preferences>Output displays in the LTB output the Formatted Source and Formatted Translations columns for all the Linguistic ToolBox quality control components, independently on whether the option Use formatted segments is enabled or not.

· The LTB Helper’s overall performance in relation to Excel and other add-ins has been improved. To work with the LTB Helper, once you have opened the LTB output report in Excel, click Start/Stop LTB Helper button and when you have finished, click Start/Stop LTB Helper.

· LTB now does not report inconsistent translations when the segments that produce the inconsistency are segments with empty target. Please note that going forward the only way to detect these issues are by using the Segment Checker option, Check if target is empty.

· The overall performance of the Segment Checker options: Ignore alphanumeric only segments and Ignore case and punctuation have been improved.

· In the Input files tab, when you click on Add Folder, now you can also copy and paste to the folder path. This enhancement is particularly useful for Windows 7 users, as the option to drag and drop folders is not available.

· New option in the XLS Properties window: Use these settings on all workbooks: This option applies the same settings to all the Excel files in the Input Files tab, QUICK tab and Change Report tab

Defects fixed

· Issue with LTB not processing Idiom .xlz files containing a .tbx glossary file within. Now LTB processes these files correctly without producing the error message "Data descriptor signature not found".

· Issue with LTB producing sometimes noise when carrying out spell check using the option Ignore Internet and file addresses.

· Issue when working with multilingual configuration files in Windows 7. When working with very large configuration files not all the relevant support files were loaded according to the languages selected.

· Issue with the QUICK component causing noise entries when dealing with entries in the QUICK glossary that contains brackets that are not in Latin encoding.

· Issue in the XLS Properties dialog, when scrolling up and down the files producing an unhandled exception error.

· Issue with the clean-up of the Source and Translation columns in the LTB output report not being done consistently for the Segment Checker.

· Issue with LTB output report not showing for some components the columns Formatted Source and Formatted Translation.

· Issue with the LTB Helper automatically saving LTB output reports under My Documents folder. After using the LTB Helper, if you selected Save in Excel (instead of Save As), the LTB output report saved under My Documents instead of being saved at the default location.

Support files updates

Core Configuration

· LTB_Core_Config.zip

The Core Configuration file has been updated to include this change: under Term & Punctuation, the new options Ignore segments with empty target and Ignore untranslated segments are enabled by default.

Rules

· New rules:

o ALL STANDARD Capitalization at the beginning of the segment or string EN-ALL.rul

Checks for capitalization mismatches between source and target at the beginning of the segment or string. This rule is valid for Latin script and Cyrillic script languages. Please note that this rule is not applicable for those languages for which capitalization does not exist.

o ALL STANDARD Check Trade and Registered Marks.rul

Checks that the number of registered marks ®, trademarks ™, copyright marks ©, service marks℠ and sound recording copyright marks ℗ found in the source and target match. It also checks if there are any of these marks found in source and not in the target and the opposite.

o DA STANDARD Spanish-Danish Translation Errors ES-DA.rul

Detects common translation errors including many false friends from Spanish into Danish. Applicable to the Travel and Tourism domain.

o DA STANDARD Common Errors ALL-DA.rul

Checks for common errors such as use of one/two words, use of uppercase, general style in texts with Danish target.

o FR CUSTOM Microsoft Style Guide EN-FR.rul

Checks for common Microsoft stylistic guidelines for French, according to the Microsoft Style Guide ver. 1.

· Updated rules:

o ES CUSTOM Microsoft EN-ES.rul (Previously named: ES STANDARD MICROSOFT EN-ES.rul)

o ES STANDARD Grammar Errors ALL-ES.rul

o ES STANDARD Common Errors ALL-ES.rul

o ES STANDARD Spelling Errors ALL-ES.rul

o NB CUSTOM Microsoft EN-NB.rul (Previously named: NB_CUSTOM_Microsoft_EN-NB.rul)

o NB STANDARD Common Errors EN-NB.rul (Previously named: NB_STANDARD_General_EN-NB.rul)

o NN STANDARD Common Errors EN-NN.rul (Previously named: NN_STANDARD_General_EN-NN.rul)

Dictionaries

· Updated dictionaries:

o French (Canada).xpl

o Norwegian (Bokmål).xpl

o Slovak.xpl

Documentation

· Help file has been updated with changes related to this release.

· Previous Release Notes are available at: http://autoupdate.lionbridge.com/ltb/PreviousReleaseNotes.htm

Known Issues

The most up-to-date information on Known issues can be found at: http://autoupdate.lionbridge.com/ltb/KnownIssues.htm

___________________________________________________________________________________________________________________________________________

Lionbridge Linguistic ToolBox ver. 2.37 Update 1 - Release Notes

April 22nd, 2010