Skip to content

v16.1.0 - Machine Translation Memory Release

Latest
Compare
Choose a tag to compare
@KevinJump KevinJump released this 12 Aug 14:13

This is a minor release of Translation Manager for Umbraco v16 - it contains some fixes and updates to make translating even more streamlined.

What's new ?

  • Machine translation memory (see below)
  • Improved update messages on Machine translators
  • Background Job creation
  • Improved Set management UI
  • add support for translation of the data-caption attribute on embedded images

Fixed

  • ensure contents of <a> tags is always re-inserted
  • fix licence validation issues

Feature : Machine translation memory

This release contains a new feature called 'Translation Memory' that allows supporting connectors to add and retrevie phrases from a local translation memory before they choose to send information over to a translation service.

principally this has been written to support the machine (e.g microsoft, google) translation connectors and reduce the amount of re-translation requests for any given site.

before content is translated it is broken down into phrases and chunks and these are then sent to translation, with Translation memory these chuncks are first checked against a list of 'approved' translations for that exact phrase.

if the exact phrase has been translated before and subsequently approved onto the site, it will be matched and the translation connector will not send that phrase to the translation service for translation. this should reduce the cost of re-translation via machine translation quite significantly as only changes are sent to any service.

If you are using a machine translation connector, then turning on Translation Memory should have no impact on your translations other than incrasing speeds and reducing costs!.

Notes :

  • Translations will only be used if they have been part of an approved job previously
  • If content is sent to translation and then subsequently edited as part of the translation job prior to approval that content will not make it into approved translation memory
  • Translation memory is per connector, (e.g microsoft connectors memory is not shared with the google connector).

Machine Only.

Local Tranlation memory is currenytly only implimented on machine connectors, more complex connectors with Human translators will often/always want all of the text to form a context around the translation and these services often have their own Translation Memory tools that fit within their workflow.

Feature: Background Job Creation

This release includes the ability to have translation jobs created on a background thread, freeing up your browser and UI on large translation jobs (also reducing the likelyhood of timeouts during operation).

With background creation enabled, when you send to translation the process of Submission will be ran in the background.

You can still see the progress of the job in your browser, but you are free to close the page or go do something else while the job is processed. upon compleation the job is placed in the relavent submitted or recevied location for further processing.