Server-based Project Translation Memories were not being populated correctly in some scenarios.Custom fields were not propagated when creating additional language directions.Increased the robustness when deleting server termbases.Full Text Search was not working when working with server termbases.Hard filter for the filter condition "contains" did not apply correctly for server termbases.In some scenarios the default entry class was not respected when adding new terms to server termbase.Improved robustness of the Cumulative Update installer when IIS and some services are not installed.Newly created translation units during interactive translations now correctly store the GroupShare login.Fields are no longer replaced in translation unit in translation memory when confirming a segment populated from TM during interactive translation. ![]() When working with GroupShare and selecting TM User ID, we use the GroupShare login unless the TM User ID was changed and does not match the currently logged on user on the local windows machine. Users can now decide if to use the SDLXLIFF user metadata, the GroupShare login or the TM User ID to update Created by and Changed by system fields.Fixes in the TM update batch task settings:.The Translation Memory list could not be retrieved from within Studio if a user had access to multiple thousands of TMs in GroupShare.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |