New Features, Improvements, and Changes
Use DeepL Translator with Memsource
Memsource users can choose from an even wider range of machine translation (MT) engines. Memsource now supports DeepL Translator, a neural machine translation engine which provides high-quality machine translation matches.
DeepL Translator currently supports 42 language combinations between English, German, French, Spanish, Italian, Polish, and Dutch. The neural networks are already training to master more languages like Mandarin, Japanese, and Russian.
Find out more about DeepL Translator.
To set up DeepL in Memsource and learn about the other machine translation engines we support, see our Machine Translation help center article.
Memsource + Jukkou MT Engine
Memsource users will now be able to attach the Jukkou machine translation (MT) engine to translation projects. When setting up this MT engine in Memsource, it is possible to choose from industry-specific versions of the engine: legal, medical, and financial.
This engine is only available for real-time translation in the Memsource Editor and batch pre-translation is not supported.
To set up this engine and find out about the other machine translation engines we support, see our Machine Translation help center article.
New Supported Languages
Memsource now supports 82 new languages/language locales.
Users will be able to select these languages when creating projects, translation memories, and term bases.
An updated list of all supported languages is available in this article.
New Job Owner Notification Option
An option to Notify the job owner when the job status is changed has been added to the Access and Security settings both in the main Setup and the Project Template settings. Previously, it was only possible to select this option manually, on a project level.
Support for COTI
Memsource now supports the Common Translation Interface (COTI) as a premium feature for Memsource Enterprise users. Find out more about the Memsource Enterprise edition.
COTI is an interface developed by DERCOM (The Association of German Manufacturers of Authoring and Content Management Systems) for data exchange between authoring systems and translation systems.
COTI was developed as part of an effort to improve CMS/TMS system integration and make it more flexible. This standardized interface creates translation projects from content management systems and then exports the final translations from the CAT tool. COTI can reduce translation costs as well as errors that result from manual translation management. Before the support for COTI was developed, PMs and Localization managers needed to do a lot of manual work: extracting the files from the packages, creating a project based on the configuration information, exporting the translated files and putting them in the correct folder.
COTI has three levels and Memsource supports level 2. The difference between this and level 1 is that the data exchange is automated via exchange folders in level 2 instead of simply being provided in the specified package structure. In level 3, the data exchange is via web services (API).
In COTI level 2, the content management system places a data package, including the content to be translated and any reference materials, into an exchange folder. This folder is monitored by Memsource and the package is converted into a Memsource project when new content is added.
Once the translation project is completed, Memsource places the finished COTI package into a second exchange folder, which is monitored by the content management system. As soon as the CMS detects the COTI package, including the translation, the CMS automatically imports the translation.
You can integrate Memsource with various online repositories and CMSs, including Typo3, using our connectors and plugins. See our integrations page.
Change to File Import Settings
This is a very important change to the default settings.
Previously, when importing a new file with customized file import settings, these settings would be saved into the project and all additional files added to the project later would also use these settings.
With the latest release, the customized file import settings will no longer overwrite the settings of the project. This means that when adding a new file into a project, the default file import settings of the project (or project template) will be used. If the file needs to be imported in the same way the previous file was imported (with customized import settings), you either need to set these up for this specific file, or you can re-use any previously created import settings via the “Create a new job with the same file import settings” option on the Project's page.
- When the email login option was selected in Memsource, the window that appeared was too small. This has been fixed.
- The Job Create API will now return the correct language locale.
- If you view the details for an existing connector and click the Select remote folder button, the dialog box that appears will only display 1 connector and the list of folders.
Have you come across any other bugs?
Thank you for letting our Support team know.