September 25, 2018: Memsource Release v6.81

New Features and Improvements

Continuous Job Launched 

We are very pleased to announce the launch of Continuous Job, our latest continuous localization feature.

Up until now, we offered a more project-centric approach to continuous localization with our automated project creation feature; new projects and jobs within those projects were created every time new content was added to a repository. Now, with Continuous Job, when a file in a repository is updated, the corresponding job in Memsource will be updated within the existing project.

This is particularly useful for software localization. When new strings are added to a file in a repository, the modified source strings are updated, and any deleted source strings are removed. Unchanged strings that are already translated are copied to the updated version of the job.

This feature is powered by our connectors. See a full list of the connectors we offer.

This feature is available for our Team, Ultimate, and Enterprise edition users.

Fixed Bugs

There are lots this week as we've just finished a bug-fixing sprint. 

  • Incorrectly displayed dates in the Japanese UI have been fixed in this version. 

  • TM matches were not correctly displayed for segments containing < and > in combination with numbers. These segments will now correctly show TM results.

  • The progress bar on certain mobile devices caused the Memsource UI to become distorted. The issue has now been fixed.

  • When importing MS Excel files, some texts were not properly extracted for translation. This behavior has been fixed.

  • If a ZIP file containing a folder structure was imported for translation, the MXLIFFs (if downloaded not as joined, but in a ZIP) did not follow the folder structure, and therefore files may have been overwritten. This issue is now fixed.

  • Certain SDLXLIFF files could not be opened in SDL Trados after new lines were converted to spaces when processed in Memsource. This issue has now been resolved.

  • It was sometimes not possible to deselect a provider that was assigned from a template, but this problem was resolved in this release.

  • Pre-translation from TMs was sometimes not available if projects contained multiple languages while the TMs matched only some of them. This has now been fixed.
  • A processed subfolder was not correctly created in a Dropbox repository if Automated Project Creation had the root folder selected. The issue was resolved in this version, and the subfolder will now be correctly created.

  • Deleted projects remained available in the Linguist's view despite the fact that they were no longer accessible. They will no longer be displayed. 

  • Documents containing XML inline elements or XML entities in HTML elements will now be rejected when imported as multilingual XML files with the HTML subfilter enabled. 

  • It was not possible to download certain Excel files if Data validation for table names was specified. The names will now be checked to prevent similar issues in the future.

  • PSD files containing a forward slash (/) in specific places were not correctly imported due to the processing of special codes. These will now be correctly imported.

  • The Identify inline elements automatically option will now be enabled even if users insert some elements into the respective fields.

  • For a temporary period of time, some of the Git repositories could not be initialized. This issue has been resolved and connectors to Git repositories should be initialized correctly.

  • During job creation, incorrect email templates were sometimes selected, thus sending the wrong email messages to assigned Linguists or Vendors. This has now been fixed.

  • Due to limitations of the Google APIs, importing Docs, Sheets, and Slides via the Google Drive connector can result in an internal error. Such documents should be downloaded as DOCX, XLSX or PPTX and imported outside of the Connector feature.

  • When processing DOCX Templates, background motifs were sometimes lost when exported. This has now been fixed. 


Have you come across any other bugs?

Thank you for letting our Support team know.

Was this article helpful?

Sorry about that! In what way was it not helpful?

The article didn’t address my problem.
I couldn’t understand the article.
The feature doesn’t do what I need.
Other reason.

Note that feedback is provided anonymously so we aren't able to reply to questions.
If you'd like to ask a question you can leave a public comment below or Submit a request to our Support team.
Thank you for your feedback.



Article is closed for comments.