Engines trained with version 4.1.2 and above deployed for text translation now accept xml as a format.
In the rare event of a subscription getting suspended due to non-payment, all users are made aware of this as soon as they log in.
Changes
The format parameter is no longer required when making API requests to engines deployed for text translation. Although it is still strongly recommended to specify the format whenever it is known, Globalese will attempt auto-detecting the format of the segments sent for translation if the format parameter is not present in the payload.
Enhancements in Globalese 1.1.1 include:
Through the new Recycle feature, it is possible to send all human-translated files in a translation... read more
Globalese 2.5.3 fixes the following issues:
Uploaded resources and assets contained unnecessary HTML entities.
Memsource files with composite language codes could not... read more
Globalese 1.7.6 fixes the following issues:
Segments that are covered entirely by glossary entries got a low QE score.
Translation error on... read more
Globalese 1.7.9 fixes the following issues:
Unknown word report only worked case sensitively
Added subscript and superscript support to detokenizer
Corrected segment statistics... read more
Engines can be cloned. Cloning an engine recreates the engine with the same list of components, except for the... 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