Versions Compared

Old Version 2

changes.mady.by.user Aaron Sakievich (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Aaron Sakievich (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

Project Management

Projects and Project Templates

Projects are more than a way to organize and group content. They include complex settings that control how content interacts with the system and how users interact with content. We created Project Templates to make it easy to create perfectly configured projects with a click of a button. Your project managers or community admins can create a project template with settings configured to meet your organization's specific needs. Then, project managers can use those templates to create a new project without giving it a second thought.

  • You can find Project Templates under the Template menu in the sidebar. Here you will create and manage your community’s project templates.

  • The interface for creating projects has changed. Instead of creating a project with a workflow template, you will use a project template. Or you can manually create a new project and configure your project settings before you actually create the project.

Resolved Issues

  • Display issues with dates on the Targets page have been resolved.

  • The user’s timezone preferences are now respected on the Targets page and when setting due dates in bulk.

  • The Global Find and Replace tool works as expected for linguists.

  • Downloaded Xbench packages can now be loaded into Xbench without any problems.

Workbench

In-Context Translation

  • Users can interact with buttons and animations on the webpage inside the Context Viewer. Users can also click on links using ctrl + click.

  • We have improved the user experience of checking out tasks while the Context Viewer is open.

  • Segments with inline tagged words match the source text as expected.

API5

  • We have added the an optional community_id parameter  parameter to the GET /document call. If you make the GET /document call without specifying the project_id parameter, the community_id parameter is requiredthe GET /document call.

  • PATCH /document/{id}

    • We resolved an issue with the call that prevented certain metadata fields from being set correctly.

    • Users can control which locales are added to the new document version.

      • If the API call specifies one or more translation_locale_code parameters in the PATCH call, only those locales will be included in the document's new version.

      • If the call does not specify a translation_locale_code parameter, the new version of the document will include all the previous document's targets.