Blog

Systran and Microsoft Translator Hub Integrations, Additional APIs - Memsource Cloud 2.6 Release

Memsource Cloud 2.6 has just been released. This version includes over 120 improvements and bug fixes.

New Machine Translation Option

  • We have added new machine translation engines to which Memsource users can connect out of the box as well as new features
    • Systran is now supported out of the box in MemSource
    • Microsoft Translator Hub is also supported out of the box in MemSource, including the “feedback” option (see below)
    • We have also redesigned the user interface to handle MT; it is much easier now “create” new machine translation engines, configure specific MT domains, etc.
    • We have also introduced an optional “feedback” feature for MT engines that support this (e.g. Microsoft Translator Hub). When feedback is enabled, post-edited translations are sent to the MT engine to improve it

  • A new quality assurance check: ”No text between tags”
    • When there is no text between paired tags in the target but there is some in the source, a warning will get triggered in quality assurance
  • MXLIFF files can now be directly imported into Memsource translation memory, as if it was a TMX file
    • In fact the “Import TMX” button is used for this
    • This feature can be useful in many ways, e.g. in an emergency, when recovering a translation job gone wrong if you only have the MXLIFF file you are not able to generate a TMX file directly from Memsource Cloud
  • New API calls have been added, for instance:
    • Set Translation Memories
    • Get Translation Memories
    • Create Analysis (and get results)
    • Set Term Bases
    • Get Term Bases
    • Delete Project
    • Memsource wiki lists all Memsource APIs, including the related documentation
    • With the latest API additions, Memsource translation projects, jobs, translation memories and term bases can be efficiently managed from 3rd party applications
  • New configuration options have been added for HTML file imports
    • Break tags create a new segment
    • Non-HTML tags convert to Memsource tags
  • Text files (TXT, CSV, PROPERTIES…) are now always exported (after translation) in UTF8 character set
  • 101% matches can now be locked during pre-translation
    • When locked, segments may not be edited by a linguist user
    • A project manager or administrator may also manually lock/unlock segments in Memsource Editor
  • Memsource Cloud UI localization
    • Besides the existing Japanese, also Russian localization is now available (branded as “community translation”)
  • Memsource Web Editor
    • A completely web-based editor, an alternative to Memsource Editor, is now available to selected organizations
    • A public launch is not far away
  •  Launching and resolving QA warnings can be enforced
    • A new option is available under the Quality Assurance settings in a project: “Linguists may not set jobs with QA warnings to Completed”
    • When this option is selected, linguist users will not be able to set a job to the Completed status if QA was not launched or QA warnings have not been resolved or ignored
  • A linguist may set a job to the Completed status only if all segments are confirmed
  • ZIP file import improvement
    • When files get imported from a zip file, the path for each file is included (it is part of its name in the list of jobs, e.g. “…/dir/filename”)
  • New macros for email templates has been introduced
    • {jobs.count}
    • {jobs.newStatus}
    • Project managers can now get automated notification emails, such as “Project SomeName: 4 Jobs Completed
  • Clone
    • Projects can now be cloned via the new Clone button