Globalese 2.2.2 checks all engines, and resets the status for those that haven’t been retrained as composite. This ensures there will be no unnecessary errors when using engines that have not been retrained in Globalese 2.
Related Posts
Globalese 2.2.4 released
Globalese 2.2.4 fixes the following issues:
The wordcount of files with tags separating words without spaces was incorrect.
Translating Memsource .mxliff files... 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 1.4.5 released
Globalese 1.4.5 is out with some improvements and fixes:
It is now possible to start tuning an engine from the Recycle... 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 3.10.1 released
Fixes
Wordbee files were pre-translated incorrectly: two <target> elements were inserted into each translated segment.The PUT /v2.1/corpora/{id} API endpoint failed if... read more
Globalese 4.4 released
What's new
A new System settings page enables system administrators to decide whether or not Globalese should store one active plus... read more
Globalese 4.0.1 released
Fixes
Fixed target language filter when importing translation memories or term bases from Memsource.Billing administrators could not see the Usage statistics... read more
Globalese 4.2.3 released
Fixes
A bug introduced in v4.2.2 caused SDLXLIFF files to be unparseable after translation.
read more
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... read more
Globalese 1.0.3 released
Globalese 1.0.3 focuses on XLIFF files:
Improved handling of XLIFF files
Improved handling of <group> tags in the XLIFF filter
read more