Globalese 3.8.3 released

Globalese 3.8.3 fixes the following issues:

  • Some term bases could not be retrieved from Memsource
  • XTM term bases could not be filtered by target language
  • URL translation issues
  • Stock corpora were automatically added when creating a new engines even if there were no stock corpora for the language pair

Related Posts

Globalese 3.7 released

The major update in this release is the switch of the underlying neural network model from RNN (Recurrent Neural Network)... read more

Globalese 4.1.1 released

Minor improvements Tag pairs surrounding entities that remain untranslated after machine translation are checked and corrected if necessary. read more

Globalese 3.10 released

What's new Aggregated usage statistics per month and per engine are now available to administrators. Read more here.Corpora and project listings... read more

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... read more

Globalese 1.0.2 released

Globalese 1.0.2 comes with a couple of enhancement for groups: Better overview Statistics for groups Groups may only be deleted if no resource... read more

Globalese 3.12.1 released

Fixes Notification e-mails were not sent when an engine training finished.When changing the selection of corpora in an engine, corpora involved... read more

Globalese 2.3.1 released

Globalese 2.3.1 fixes the following issues: If a segment contains capital letters only, it was converted into lowercase in the translation. The... read more

Globalese 1.7.3 released

Globalese 1.7.3 fixes the following issues: Tokenization error during translation. If engine tuning is stopped, the engine will now remain usable even... read more

Globalese 3.11.2 released

Minor improvements Improved user experience when importing project files from a CAT tool server.Projects that are linked to a project on... read more

Globalese 1.8.2 released

Globalese 1.8.2 fixes the following issues: Special characters in the output were displayed as HTML entities on the Quick translation page. When... read more