09-12-2019

We are pleased to announce that version 14.30.0 of the Lingotek Translation Management System was released today.

Project Manager

Edit Distance Report

• We resolved an issue that prevented the user from running an Edit Distance Report across multiple documents. 

InDesign Files

• InDesign packages must be uploaded in a specific way or they will fail upon upload or download. See here for more information. We have updated error messages to clearly explain why the InDesign file failed upon upload or download. 
  
  
  
  
• An issue preventing users from downloading translated InDesign content via API 5 has been resolved.

TM Units Page

• We resolved an issue that prevented the user from editing the first search result on the TM Units page. 

Project Callbacks

• We have added a new Failed Import project callback that will be triggered each time a document fails to upload. You can choose whether or not your application will receive this callback in the Project Settings. 
  
  

New Workbench (Beta)

Resolved Issues:

• Segment Status
  • The segment status was not displaying as expected after saving a translation or using the Approve All action.  
  • Exact matches were showing the user that they were already saved when they were still unsaved.
  • Users were unable to save segments properly after changing the size of their page. 
  • The count of unsaved translations was displaying incorrectly.
• Issues with the Check Spelling & Grammar When Saving feature
  • The setting could not be disabled after it was enabled. 
  • The feature was still enabled even when users attempted to use it for unsupported languages. 
• Users could not paste text from outside the Workbench into the Find and Replace tool. 
• Scrolling would cause unexpected behaviors when translating "Right to Left" languages.
• The merge segments feature was causing unexpected results when users attempted to select a segment after merging. 
• Splitting a segment while displaying whitespace would cause unexpected issues. 
• The new Workbench would not open as expected when users selected the WorkbechLink variable in Workflow generated emails.
• Keyboard shortcuts that require the user to specify a number with the shortcut were not working properly. 
• Using the Approve while Navigating feature was occasionally approving locked segments. 
• When in a review type phase, the Next navigation options displayed Next Untranslated instead of Next Unreviewed. 
• Users were able to edit and save translations without checking out the task. 
• Entering a segment or page number in the navigation sections would take users to that segment/page without the user pressing the enter key. 
• Users were unable to sort by severity in Quality Checks. 
• Users were unable to scroll in their dictionary. 
• IDML files would not open if they didn't have an InDesign preview. This occurred for files that were uploaded before In-Context Translation was supported for IDML files. 
• Right to Left languages were being shown as Left to Right languages in the Context Viewer. 

Xbench Integration

• We have fixed an issue where selecting the Edit Segment option from an Xbench package would not open the new Workbench properly. 

Find and Replace

• The Find and Replace tool has been improved to work across large documents.
  
  
  
  
  • The Find and Replace tool pops out as a moveable box which can be collapsed for later use. 
  • You can use the Find and Replace tool across multiple pages.  
  • The matching text is highlighted in the returned segments. 
  • The search results will display tags. 
  • If you try to Replace in bulk on segments that include tags, you will be warned that your edit will remove tags from those segments. 

Marketplace

Marketplace Extension

• Marketplace integrations will be notified whenever a document fails to import. The source tile will be updated to the failed status. 
• We have removed the 30 target language limit when setting up integrations. 
• When a document is selected for upload to the TMS, integrations will pull from the original source of the document, rather than the cached document. 
• Our Marketplace integrations are now aware of the URL that is being used when the extension is opened. This will help users that have multiple integrations for the same third party tool. (EX: A sandbox and production environment of Eloqua.)
  • If all of your environments share the same URL, then you can manually change which integration is being used. 
• We have changed the color of the "Downloading" status in order to differentiate it from the "Pending" status.

Eloqua

• Users can choose to exclude dynamic content from being available for translation in the Eloqua integration. When this setting is enabled, Dynamic content will be prevented from being sent for translation when associated content is sent to the TMS.
• The following issues have been resolved:
  • When a filter was set up in the project settings, it would override the selected filter set up in Eloqua's translation profile. 
  • Translated hover text was being incorrectly imported into Eloqua and was showing English in translated content. 
  • The Request Translations option would disappear from the drop-down after requesting a translation. 
  • Opening the integration as a separate window would cause documents to show incorrect statuses. 

Zendesk

• The following issues have been resolved:
  • Changes made to articles would not update the status in the extension to "Edited."

Marketo

• The following issues have been resolved:
  • Translated forms were not being downloaded correctly back into Marketo. This resulted in the "translated" page displaying English. 
  • Any document referencing forms would also fail to translate since forms were also being downloaded incorrectly. 
  • Call to action fields (buttons) in emails were not being downloaded as expected into Marketo, causing them to be displayed in English.

Confluence

• When setting up the Confluence settings in Marketplace, users will need to set up a unique space per target language. 
• The following issues have been resolved:
  • Selecting a target language in order to view the translated page returned an error. 

API 4

• The listTMVaults and listProjects calls were not performant and were preventing some users from adjusting settings in our Drupal 7. This has been resolved.