Globalese 4.1 releasedGreg Horváth
Engines can be published and unpublished to allow or deny a wider group of users the use of individual engines for document translation.
Breaking change: from Globalese 4.1 onwards, all new engines need to be explicitly published after their first training.
Read more about this new feature here.
Minor changes and improvements
- Better tag reinsertion after machine translation in Japanese through improvements in word alignment. Requires retraining of engines.
- When TMs or TBs that have already been imported before from a CAT tool are updated from their origin, changed resource names are updated in Globalese to reflect the new name of a resource in the CAT tool.
- While an engine was being turned on/off for text translation, changes in associated API keys for translation were not reflected in the system. From Globalese 4.1 onwards, engines that have an instance that is being turned on or off are temporarily locked into all API keys for translation until the transition is over.
- While being turned on or off for text translation, the status of an engine instance was not refreshing when the Refresh button was clicked.
- The Statistics > Engines page did not display all engines if there are more than 100 engines in a system.
- Fixed the display of checkboxes on the Preview tab of project file pages.