Memsource Cloud 5.4: API & Analytics for All, Clone Jobs, INDD
Memsource Cloud 5.4 is scheduled for release on Sunday, 28 February 2016, at 11:00 AM GMT. This release is literally packed with new features including some major improvements. We are extending Memsource API support to all of our customers. And the recently introduced business analytics features will now also be available for our translation agency customers.
API for All Customers
We are extending our API to all of our customers.
Memsource API is necessary to integrate Memsource with any 3rd-party software. Previously, API was only available to our Ultimate and BIZ Ultimate editions customers. We are now extending the API to all paying customers (this excludes the free Personal edition).
The Ultimate and BIZ Ultimate editions will continue to offer unlimited API calls to its subscribers. All other editions will enjoy full API functionality but with a daily limit on API calls which we will start enforcing during March 2016:
|Edition||Max. API Calls Daily|
|Ultimate & BIZ Ultimate||Unlimited|
|Team & BIZ Team||2000|
|Team Start & BIZ Start||1000|
Cloning jobs can prove extremely useful for multilingual projects.
Typically for large projects with multiple target languages, it may make a lot of sense to prep the translation jobs before they are assigned to linguists. This may include modifications that will be identical in all target languages. It is quite tedious for project managers to have to apply the same modifications job by job for all the target languages. For instance, copy source to target for segments with non-translatable content. Or, lock some segments because they should not be touched, etc.
With the new clone feature, jobs can be prepped in just a single target language and then cloned to any number of the project’s target languages.
Native Adobe InDesign files (INDD) are now supported.
We have supported IDML, the translation-friendly Adobe InDesign file format, for a long time. However, not the Adobe InDesign’s native INDD format. It is always possible to convert INDD into IDML or ask your customer to provide IDML. However, it adds an extra step.
We have started supporting INDD directly in Memsource. Thanks to our partnership with Frontlab, this feature is available for everyone in Memsource.
How it works exactly: Simply select the INDD file when creating a new translation job, it will be converted into IDML in the background and the new job will be created using the IDML file. When you are done with the translation, you will receive IDML as the output target file (not INDD - as this would be unnecessary). The translated IDML can then be directly imported into Adobe InDesign.
Business Analytics for Translation Agencies
We have recently completely redesigned our business analytics component and introduced the first set of analytics features in our previous release, Memsource Cloud 5.3 (and just for our enterprise customers). We are now extending business analytics also to our translation agency customers on the Team and Ultimate editions.
Home Page for Translation Agencies
The Home page is a new dashboard-like page with customizable widgets. It has been introduced in our previous release, Memsource Cloud 5.3, just for our enterprise customers. We are now making it available also to our translation agency customers.
Currently, analytics and automation widgets can be added to the page. The Home page is available in our Team and Ultimate editions and all enterprise editions.
Pre-translate on job creation.
The project’s pre-translate settings have received a new option: _Pre-translate on job creation. _When enabled, every new job will be pre-translated automatically, based on the project’s pre-translate settings.
This new option can be very well used also in project templates and automation widgets, associated with those templates.
Entering a pool of linguists and/or vendors into a project template.
In one of our previous releases, Memsource Cloud 5.0, we made it possible for project managers to assign jobs to a pool of linguists or vendors, order them by priority and let them be notified automatically by Memsource in the selected time interval. The first linguist available would be able to claim the job.
We are now bringing this exact same feature also to project templates which opens up a number of additional automation scenarios. For instance, creating an automation widget, associating a project template with a pool of linguists/vendors and letting the translation automation flow…
Linguist relevancy data.
Relevancy data for linguists can be entered already in the user creation page.
Original file extension added to MXLIFF.
Our MXLIFF files now include the file extension of the original source file which should help project managers for better orientation, especially when dealing with lots of files.
Set net rate schemes by workflow steps.
It is now possible to set specific net rate schemes for each workflow step. For instance, a different net rate scheme for translation and revision.
New language added.
We have added Russian (Estonia) to our list of supported languages.
New Memsource Cloud default url.
Memsource Cloud has a new default url: cloud.memsource.com (previously cloud1.memsource.com).
Multiple columns for translation in multilingual MS Excel.
It is now possible to enter multiple columns for translation, e.g.
Source - A,B,C
Target(de) - G,H,I
Target(cs) - J,K,L
There is also a new file import option that makes it possible to import specific rows only. Entering _2- _will import all rows except the first row:
A new file import setting allowing to specify a context key.
It is now possible to select the location of a key in a file for translation which will then be displayed to linguists during translation in order to provide more context information. Newly available for these file types:
Improved handling of index markers in FrameMaker.
We have started placing index markers following the paragraph where they were used in order to separate them better from the translatable text. This should be more translator-friendly.
New HTML file import option: Translatable meta tags.
We have introduced a new file import option for HTML files which relates to translatable content in the meta section of HTML files. Previously, Memsource would only import _description _and _keywords _for translation. Now it is possible to specify (using a regular expression) what content should be imported from the HTML meta section.
Identify translatable text in text files using a regular expression.
We have introduced a new option, Translatable text, that makes it possible to extract just translatable text in plain text files using a regular expression.
Maximum target segment length for JSON.
A new file import option, Max. target length, makes it possible to restrict maximum target length for JSON files.
XLIFF 2.0 improvements.
We have introduced a number of improvements to our XLIFF 2.0 handling:
Standalone file import settings for XLIFF 2.0 (previously the settings were shared with XLIFF 1.2).
srcLang and trgLang attribute support.
Better handling of translatable content in nested elements.
Better file-validation check when exporting a completed target file (to check whether the XLIFF file conforms to the XLIFF standard).
Chaining context note parameters for XML files.
Multiple parameters can be chained and entered into the _context note _field in XPath file import settings for XML files. For instance:
New file import settings for Multilingual XML files.
We have added new XPath file import settings for multilingual XML files:
Max. target length.
Conditional text from Adobe InDesign files extracted.
Conditional text is now extracted for translation from Adobe InDesign files.
Segments can now be saved to two translation memories in a project.
Previously, we only supported a single translation memory to be set up in the “write” mode in a project (the TM into which segments are saved when they are confirmed). From now on, it is possible to select the write mode for up to two translation memories in a project.
This means that we now support up to 2 TMs in the write mode and up to 10 TMs in the read mode.
Navigating search results from TMs with multiple languages got much easier.
Viewing TM search results from within Memsource Cloud got a bit more user-friendly, especially for TMs with multiple target languages thanks to a few UI tweaks we have deployed. And by the way, it is possible to drag-and-drop each language column in the TM results page to re-order the languages for better viewing.
New API call to list users by email address.
New API call to clone projects.
New API call to clear all translation memory segments.
- api/v4/transMemory/clear (be careful, this action cannot be reverted!)