Engines can be cloned. Cloning an engine recreates the engine with the same list of components, except for the quality estimation model (which means the new engine will have to be calibrated before it can be used).
Users can now test an engine with an asset.
Testing an engine with an asset means the asset will be translated blindly, then evaluated against the original (existing) translations. The results are shown on the Assets tab of the engine, as well as on the asset page.
Currently works with assets retrieved from the repository, .mqxliff and .sdlxliff files.
Globalese 2.12 comes with the following improvements:
Duplicates are removed when uploading resources. Filtering out duplicate segments increases system speed while... read more
Globalese 1.3.3 is out with the following fixes and enhancements:
Improved tokenization for English, Italian and Swedish.
Segments that were not translated... read more
Globalese 2.12.3 fixes the following issues:
Error when translating Memsource XLIFF files.
All models were showing as deletable, even the ones belonging... read more
Globalese 1.3.2 delivers the following fixes:
Improved handling of multilingual TMX and TBX files.
memoQ file parser bug fixed.
Handling of invalid language... read more
Globalese 1.7.2 fixes the following issues:
Memory issues when training large phrase tables
Errors when retraining previously trained phrase tables
Javascript issues when... read more
Globalese 2.4.1 fixes the following issues:
Issues when translating an individual file within a project.
Problems when testing an engine with an... read more
Globalese 1.2 includes a couple of important new features and various fixes.
memoQ server integration
Globalese now offers integration with memoQ server... read more
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.OkPrivacy policy
