04-30-2020
- Aaron Sakievich (Unlicensed)
Owned by Aaron Sakievich (Unlicensed)
We are pleased to announce that version 15.17.0 of the Lingotek Translation Management System was released today.
Project Management
- We have added the following generic locales (the language code is in parenthesis):
- Danish: (da)
- German: (de)
- English: (en)
- Spanish: (es)
- French: (fr)
- Italian: (it)
- Japanese: (ja)
- Dutch: (nl)
- Norwegian: (no)
- Portuguese: (pt)
- Turkish: (tr)
- Chinese: (zh)
- The Arabic (standard) locale has been changed to Arabic.
Targets
- We added the name and UUID of the save-to-vault on the Edit Target modal.
Document List
- The Assigned To option on the smart selector works as expected.
Workbench
Standard Workbench
- The new Workbench is no longer in Beta status. When users launch a task, they will be taken to the new Workbench by default unless they choose to use what is now the Legacy Workbench using the View menu.
- We have resolved an issue that prevented users from using the context viewer for webpages if they did not have the extension installed. Now the webpage will load as expected; however, the following features are not available for web content without the extension:
- Source segments will not link to the text on the webpage.
- Translations will not replace the source content in the context viewer.
- Edits will not be reflected in the context viewer.
Marketplace
- We have improved the performance of downloading attachments to the translated page.
API
- We have added a translation_vault_id parameter on the POST /document call that allows you to set the save-to-vault for each target uploaded using the translation_locale_code parameter. You have the following options when using the translation_vault_id:
- Leave the parameter blank - the document's save-to-vault will be used for the target.
- Use the parameter once - the specified vault will be used for all targets added to the document and will override the document's save-to-vault.
- Use the parameter as many times as you used the translation_locale_code parameter - this option is used when different vaults should be used for different targets. If the translation_vault_id parameter is used more than once but does not equal the number of translation_locale_code parameters, your API request will fail.
