Globalese 2.3.4 fixes the following issues:
- Not getting a result after testing an engine.
- Problems when testing an engine with a TMX file.
- Engine calibration issues.
- Wrong tokenization of Japanese brackets.
Related Posts
Globalese 2.12.1 released
Globalese 2.12.1 fixes the following issues:
DELETE API calls failed.
When using the SAP Translation Hub for a project, global settings did not... read more
Globalese 1.7.5 released
Globalese 1.7.5 fixes the following issues:
Wrong before and after-tuning scores displayed for engines involving Japanese
Missing language codes for Norwegian
Normalization of... read more
Globalese 1.6.8 released
Globalese 1.6.8 fixes the following issues:
Inconsistent capitalization.
Segments containing only capitalized words were not translated.
The 404 page didn't display the page... read more
Globalese 2.0 released
Globalese 2.0 is all about composite engines. You can read the short summary or a blog article about them.
Important notes:
Since... 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 1.8.4 released
Globalese 1.8.4 fixes training errors related to phrase tables. read more
Globalese 2.10 released
Globalese 2.10 brings the following new features and improvements:
Bilingual resources can now be exported as TMX files
MT analysis scores can... 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.1 released
Improvements
Some issues with the Bulgarian ↔ English stock corpora have been fixed.The English → Bulgarian stock engine has been retrained... 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