Releases

Globalese 3.7 released

The major update in this release is the switch of the underlying neural network model from RNN (Recurrent Neural Network) to TNN (Transformer Neural Network). The result is simply better translations obtained from engines trained from this release onward.

Further improvements

  • CAT tool plugins now also have access to generic stock engines.
  • Faster file transfers through the XTM connector.
  • Faster loading of projects connected to remote CAT tool projects.

Fixes

  • Delivering remote CAT tool files after pretranslation failed in certain cases.
  • User authentication via the API failed.
  • URLs truncated in translations.
  • Missing special characters in translations.

Globalese 3.6 released

Starting with version 3.6, Globalese cloud users can quickly take advantage of ready-to-use generic stock engines for the most common language combinations. This addition aims to provide a quick solution in scenarios where a custom engine cannot yet be trained because there is not enough in-domain training material. At the time of writing, stock engines are available:
  • English <> French
  • English <> German
  • English <> Hungarian
  • English <> Italian
  • English <> Polish
  • English <> Portuguese
  • English <> Spanish
  • German <> Polish
Please contact Support for queries about further language combinations.

Changes

  • New projects can no longer be created without an engine.
  • Projects can be created using generic stock engines. API users should first query the list of engines for the specific language combination to find out if a stock engine is available or not.
  • Engine segment pair counts reflect the real count after training.

Improvements

  • A range of new API endpoints to help manage engines.
  • Boolean "ready" property in engine API responses to indicate whether an engine can be immediately used for translation.
  • Generic training and translation quality improvements.
  • More helpful API error messages.

Fixes

  • No API warnings if deleted groups were specified in the request payload.
  • Engine cloning not working in specific circumstances.
  • New users not receiving welcome e-mails.
  • Better handling of tags adjacent to numbers.
  • A sentence-last tag would always be followed by an underscore in the translation.
  • If a sentence starts with a tag, the first word gets lowercased.
  • Translate button enabled in situations where the file cannnot actually be translated.

Globalese 3.5 released

The major addition in this release is the ability to use stock corpora as the foundation for training engines in the cloud. Read more about stock corpora in this blog post.

Changes

  • Core corpora have been renamed to master corpora.
  • It is now mandatory for engines to have a certain volume of master corpora as well as a certain number of segment pairs in total.

Improvements

  • Better handling of dates and numerical information
  • Ability to train engines with no locale (e.g. 'en') even if all corpora are marked with a certain locale (e.g. 'en-us')
  • Terms and Conditions are always available
  • Better error messages for failing file uploads
  • An engine being edited can now only be saved (and marked as Changed) if there are actual changes

Fixes

  • Training progress went over 100% (had too many GPUs working for us... now we're using them to mine Bitcoin instead (just kidding!))
  • Translations containing a redundant tag at the end of some segments

Globalese 3.4 released

In the past months, we have been working hard on improving the two core processes in Globalese: training and translation. Globalese 3.4 brings overall improvements in both departments. Training an engine is now 20% to 60% faster. Translation is 20% to 40% faster overall, and we conducted extensive tests to ensure that automated metrics show at least as good a score as before retraining an engine (as always, this depends on the language combination). Since this a significant change, you will notice that certain engines will be marked for retraining. This makes use of the engine health feature introduced in Globalese 3.3. Note that while you can continue using your engines as they are, retraining them will give you the advantage of faster translation and higher quality. Bugfixes:
  • SDLXLIFF parsing errors for rare segment statuses.
  • Pulling MXLIFF files from a connected Memsource server failed in certain cases.
  • Various tokenisation-related issues in training and translation.

Globalese 3.3 released

Globalese 3.3 introduces the concept of engine health. The idea behind it is to prevent cases where you have old engines hanging around, when you could increase their output quality simply by retraining them on the same corpora. As always, we are trying to keep it simple. Whenever we release a new Globalese version in the future that adds a significant (read: measurable) increase in engine quality, Globalese will prompt users gently to retrain engines that are going "stale" (starting with the oldest ones). If a major change is introduced that affects engine quality more dramatically, users will see a firm warning. In both cases, old engines can still be used to translate files. Other improvements:
  • SDLXLIFF files with segment comments supported.
  • Safer password hashing algorithm implemented.
Bugs fixed:
  • File names starting with a non-ASCII character will no longer generate translation errors.
  • Groups could not be deleted.
  • Smartcat files could not be delivered after translating them on the Globalese instance.
  • Segment count mismatch after merging two or more corpora.
  • New engines could not be saved if all available corpora were selected.
  • Various training and translation-related issues.

Globalese 3.2 released

Globalese 3.2 is all about version 2.1 of the Globalese API. The new API endpoints introduced in v2.1 let users automate corpus management and engine creation and training. Paginated results are also available for listing queries. Other improvements include:
  • Improved corpus pre-processing guarantees better engine training results.
  • UI improvements.

Globalese 3.1 released

Globalese 3.1 introduces the concept of augmented in-domain engines trained from core and auxiliary corpora. Minor improvements:
  • Better feedback for misconfigured SmartCAT and Memsource connectors.
  • Improved user guidance when training small engines.
  • Users can now see engine IDs and group IDs directly on an engine page to help set up pretranslation in Memsource.
  • Improved 404 pages for non-existing or removed resources.
  • A lot of minor issues have been fixed since the release of Globalese 3.0.

Globalese 3.0 released

Globalese 3 We are very happy to announce the release of Globalese 3, which uses neural machine learning technology to deliver MT quality unseen before. Corpora management and the engine creation process have both been simplified. Upload, pick, train! CAT tool integration options now include a connector to memoQ 8 servers, and a translate5 plugin. The updated SDL Trados Studio plugin is currently available upon request, but it will soon appear in the App Store as well. As always, we invite everyone to try out Globalese 3 for 30 days.

Globalese 2.13.1 released

Globalese 2.13.1 fixes the following issues:
  • Files previously translated with errors could not be selected for translation in bulk.
  • Error when using the Memsource plugin.
  • Duplicated files in projects.
  • Issues with the SmartCAT connector.
  • Engine training issues.