Instant translation using custom engines
For us, the single most important new feature in Globalese 4 is the ability to deploy custom engines in the cloud for instant translation. This has been due for a while now, and opens up possibilities for a deeper and more natural integration between Globalese Cloud and CAT tools — or any custom integration leveraging the Globalese API — than ever before.
You can turn on any custom Globalese engine in the cloud and send segments in plain text or XLIFF format to be translated instantly. This means you are no longer restricted to using Globalese as a pre-translation tool, but can offer instant lookup to translators/post-editors. XLIFF-compliant input is processed as usual, as we continue to aim to provide the best tool around for tagged content.
Read more about this new feature here (or here if you are a developer). New CAT tool plugins are expected to be released in the coming weeks, but you can already start your own integration. Just let us know if you need help.
The engine-based subscription model is getting retired, which means you will no longer have to specify how many engines you want to have upfront. Just train and translate what you need, and pay accordingly.
Existing subscriptions will remain valid and in place until their end date, or can be converted any time into usage-based subscriptions upon request. New subscriptions will exclusively be usage-based.
You can find our new price list here.
Streamlined billing and payment
With the new usage-based cloud subscription, payments are made and invoices issued automatically, while your sensitive data is handled safely, all thanks to the new Stripe integration. Invoices are automatically generated at the start of each month, or when the due amount reaches EUR 1,000 — whichever comes first. The new Billing page provides an overview of the balance and your details.
What does all of this mean to you?
First of all, these new features are available for Globalese Cloud users.
Secondly, there is no immediate impact for Cloud users either. All of our Cloud users will be continuously migrated to the new usage-based subscription scheme if they want to renew their current subscriptions once they expire. If you want that to happen today, just let us know!
Once you start a usage-based (or post-paid as we call it) subscription, you can opt in for the text translation feature. This means that by default the features available to you will be as before: engine training and document translation.
All users can continue using the existing CAT tool plugins to translate files. However, if you are eligible, we encourage you start using the new ones (as soon as they become available) for a more natural experience.
Minor changes and improvements
- A new “billing administrator” user role and a new “translate text” permission have been introduced. Read more about user roles and permissions here.
- The attribute previously known as engine health now reflects whether or not an engine is still supported or has been deprecated and needs retraining. This is determined by the Globalese version the engine was trained on. Read more here.
- All users in post-paid systems will see a prompt when first starting a new training or file translation, as it now generates costs almost instantly.
- To make it easier to grant access to deployed engines, we introduce API keys for text translation.
- When sorting tables, a new sort completely cancels the previous one (whereas previously they would have been aggregated).
- A handy Copy button for copying user API keys.
- System administrators can now see an Authorized users tab on engine pages to see who has access to an engine.
- Users can get system status information by visiting, and get updates by subscribing to, our Statuspage.
- The statistics for Studio files showed incorrect numbers if a segment, as represented by a
<trans-unit>, was split by Studio and its subsegments had different statuses.
- In Studio files, new segments were counted towards the translatable amount even if they were locked (in which case Globalese never touches them).
- If a translation job could not be started, in certain cases it would block all subsequent queued jobs waiting for the same engine.
- Studio files using the language “Spanish (Latin American)” could not be uploaded to Globalese, or sent by the Studio plugin.