Issues resolved in Trados Studio 2015 SR1
A list of issues that were resolved in SDL Trados Studio 2015 Service Release 1.
- Fixed several AutoSuggest issues
-
There were several issues with AutoSuggest:
- Using AutoSuggest, if you deleted a target segment while holding the Backspace key pressed, the Parameter name: StartIndex error was thrown. This is now fixed.
- Fast typing the second letter of a word was stalling AutoSuggest meaning it would stop giving suggestions. This is now fixed, which also means that AutoSuggest no longer interferes with third-party products such as dictation software.
- Fixed several AutoCorrect issues
-
There were several issues with AutoCorrect:
- Pressing the End, Home, Page Up and Page Down keys was unexpectedly triggering AutoCorrect quotes. This is now fixed.
- The cursor jumped unexpectedly when deleting characters behind an apostrophe or when using AutoSuggest suggestions. This is now fixed.
- Using the Copy Source to Target option, straight quotes were changed to smart quotes. This is now fixed.
- Fixed several TQA issues
-
There were several issues with Translation Quality Assessment:
- When all Penalties values were set to 0 the Object Reference not set to an instance of an object error was thrown. This issue was fixed.
- TQA reports used to calculate incorrect total penalty points when text replacements (additions/deletions) existed in the file. The penalty point are now correctly calculated.
- Working with terminology issues
-
There were several issues with terminology in Trados Studio that are now fixed:
- Terms are now added to corresponding sub-language in termbase.
- Using the Quick Add New Term option no longer goes into a loop when mandatory fields are not filled.
- Auto-propageted segments lead to duplicate TUs when updating TMs
- Editing and confirming auto-propagated segments was creating duplicate translation units. This is now fixed.
- Addressed XLIFF File Type issue
- If the source XLIFF contained empty source tags, Studio generated an invalid target language XLIFF. This is now fixed.
- Addressed several Bilingual Excel File Type issues
-
There were several issues with the Bilingual Excel file type:
- Empty cells in the source column cause the translation in the target to move a row higher.
- Segment status is no longer confirmed when the cell in the translation column is empty.
- Addressed Microsoft PowerPoint 2007-2013 File Type issue
- Microsoft PowerPoint PPTX files are no longer saved out with all text formatted in the source language, making it impossible to run spell check on the target file.
- Addressed Microsoft Word File Type issue
- Fixed the No context information exists error when opening specific files.
- Addressed HTML File Type issue
- All the attribute values following lang are no longer changed to match the target language rather than keeping the attribute value.
- Addressed XML File Type issue
- Extra spaces are no longer added unexpectedly at the end of paragraphs in the target file if the source language is Japanese or Chinese.
- Miscellaneous fixed issues
-
These issues were also fixed with SR1:
- Fixed several issues related to Retrofit.
- Files could not be checked into GroupShare after splitting segments. Fixing this also eliminated the related Confirmation statistics word count is greater than the total number of words error.
- Formatting added with QuickPlace included whitespace after the word selected by double-click. This no longer happens.
- After activating the option to use regular expressions, the Find function for plain text was not working correctly. This is now fixed.
- Fixed the Multiple placeholder tags with the same ID having different tag properties error.
- When trying to change the password of a GS account from Studio an error was thrown. This is now fixed.
- When the content of custom text fields exceeded 1680 values, the generic error occurred in GDI+ error was thrown. This is no longer happening.
- Several project translation memories were not populated in multilingual projects. This is now fixed.
- Tag colors are not saved.
- You could not select the last word properly in certain cases for mixed BiDi / English text. This is now fixed.