Documentation Center

Issues resolved in Trados Studio 2017 SR1

A list of issues that were resolved in SDL Trados Studio 2017 SR1.

Fragment Matches window now displays whitespace characters
Unlike the Concordance Search window, the Fragment Matches window did not display whitespace characters. This is now fixed.
Corrected segment numbers for the GDF and Excel filters
Segment numbers were not displayed in a consecutive order in *GDF and *Excel files. This is now fixed.
Improved hyperlink handling inside hidden text
When processing hyperlink inside hidden text style, the segmentation hint was pushed into the segment by default, for * DOCX files. This is now fixed.
Fixed Analyze batch task for segment merge scenarios
When merging two segments across paragraphs and performing an Analyze batch task, "Object reference not set to an instance of an object" error occurred. This is now fixed.
Fixed Analyze Files report for segment merge scenarios
When merging two segments across paragraphs and running the Analyze Files report, "Object reference not set to an instance of an object" error occurred. This is now fixed.
Fragment matches beginning with a number are returned by AutoSuggest
Fragment matches beginning with a numerical value could not be retrieved via AutoSuggest when typing the numerical value during translation. This is now fixed.
File-based TM for every project package
When creating a project package, the option Create new file-based project translation memory for every package failed to create and include any project translation memories (TMs) in the project package. This is now fixed.
Reduced false positives for various tag combinations
Tags and placeholders were not treated as regular characters or separators. Segments of the type Space<Tag>Space were incorrectly reported as double spaces when running a Find and replace command.
Auto-substitution for dates and times
The changes performed on auto-substituted dates and times, in a project template, were not preserved, and the default settings were used. Therefore, translators who created projects or received a package had to notify their peers to double-check the project settings, so that date/time settings could be applied correctly. This is now fixed. The changes from the project template are reflected in the project settings.
Fixed File Types issues
  • Fixed issues with nested insets in FrameMaker file type.
  • Addressed issue with whitespace normalization for specific use case in XML filter
  • Auto-localization for currencies is now handled in same way as measurements
  • User can configure Writer settings for HTML embedded content processor
  • Specific placeholders were not placed inside segments in FrameMaker file type
  • State-qualifier attribute was not handled correctly in XLIFF 1.2 file type
  • Addressed issues with segment numbering for GDF and Bilingual Excel
Language resource template showing up multiple times
A language resource template would show up multiple times, if it was linked to different TMs. This is now fixed.
Duplicate language resource template names
Fixed issue with creating duplicate names for Trados GroupShare language resource templates.
Incorrect checkout time for Trados GroupShare project files
Checking out a file from a server project displayed a checkout time in a different time zone than that of the user's. This is now fixed.
Error with virtually merged files
Fixed Trados Studio throwing an error after editing two virtually merged MemoQ XLIFF files that have source comments and then trying to reopen them.
Improved TU filtering performance
Performance for filtering translation units in Trados GroupShare TMs was dramatically improved. This is mostly visible when using the export or filtering features in TM maintenance mode. Based on test with real-life data, improvement is over 90%.
Using a read-only TM caused performance issues
When adding a read-only TM to a project, some actions performed during translation would cause Trados Studio to freeze. This is now fixed.
Date and time format from application not from OS
Date and time format in Trados Studio is no longer taken from the system locale, but from Trados Studio.
Duplicate project names when publishing to Trados GroupShare
It is no longer possible to publish a project on a Trados GroupShare server if the organization you want to do so contains a project with the same name.
Fixed error for files with edited source in Trados GroupShare projects
The Confirmation statistics word count is greater than the total number of words error was displayed when checking in Trados GroupShare project files that had their source edited.
Capitalization persists in AutoCorrect replacements
If the first letter of a word to be replaced by AutoCorrect is capitalized, then the first letter of the word that replaces is capitalized as well.
Fixed issue with creating projects based on other projects
An Object reference is not set to an instance of an object error was thrown when creating a new project with the Create a project based on a previous project option. This is now fixed.
SDL Language Cloud connection issue
For customers with custom Language Cloud subscriptions that have the Billing Period option set to Infinite, connection to SDL Language Cloud stalls. This is now fixed.
Fixed issue with importing TQA project settings
Importing Translation Quality Assessment (TQA) project settings profile into the general settings did not always work if, after importing the profile, you selected OK without going through the Categories, Severities or Document type nodes. This is now fixed.
Fixed Analysis statistics not showing latest updates
When checking in a file from a Trados GroupShare project, the data from the Analysis Statistics window in Files view could change. This is now fixed.
Fixed incorrect encoding for HTML files
When opening certain HTML files inside a project for translation, it was possible that the encoding was determined incorrectly. This is now fixed.
Trados Studio now saves field values added when importing files in TM
When importing a bilingual SDLXLIFF or a TMX file into a server-based translation memory, field values that you add from General Import Options are not saved in the TM. This is now fixed.
Custom file types are now properly removed
There was an issue where trying to remove a previously added custom file type would not remove the file type entry completely and the file type could be restored just like a default file type. This is now fixed and custom file types are completely removed and new ones can be added with the same name.
Incorrect file-based project TM included in package if project has more than one language pair
When you created a project with several target languages using a server-based TM, included a file-based TM for each language direction and then created several project packages using the Create a package for every project language option, the Translation Provider is disabled... message was displayed.
This was due to the fact that the project packages created for each language did not include the individual project TMs for each language, but only the project TM with the language direction first listed within the Project Settings > Language Pairs > All Language Pairs > Translation Memory and Automated Translation of the original project. This is now fixed and each project package includes the individual project TM.
Pre-translate batch process uses LC characters even if translations from TM are found
If the SDL Language Cloud provider sits before a translation memory in the translation providers list, the Pre-translate batch process with Apply automated translation option selected used Language Cloud characters even if TM matches were found. This is now fixed and no Language Cloud characters are consumed.
Project Settings dialog could not be accessed for project packages with server-based resources
When opening project packages that originated from a project with a server-based resource and navigating to Project Settings > Language Pairs > All Language Pairs > Batch Processing > Project Translation Memories, the No identity information found for server '[server name]' error was displayed and the Project Settings dialog could not be accessed. This is now fixed.
Incorrect info on Analysis Statistics tab for No Match results when segments are locked
After running the Analyse Files batch task and when the Report locked segments as a separate category option is selected in the Analyse files settings, the No match result in the Files view is different then the No match result in the Analysis Statistics tab. This is now fixed.