Author - Greg Horváth

Globalese 4.2 released

What's new

  • Billing administrators can now set a budget to help monitor monthly spending. When a budget is set, e-mail notifications are automatically sent to the billing contact e-mail address whenever the current monthly spending reaches 50, 90 and 100 per cent of the budget threshold. Read more here.
  • Engines whose version has been superseded more than 9 months ago cannot be used to translate documents or text until fully re-trained. Read more here.

Minor changes and improvements

  • A new text translation service is now available in the Asia region. Engines can now be deployed in Asia, which ensures shorter roundtrips for data if users are in Asia.

Fixes

  • Some issues have been fixed around tagged content with the same strings appearing in the source and the translated side between tags.

New stock corpora

  • English ↔ Ukrainian
  • German ↔ Ukrainian

Globalese 4.1.2 released

Minor improvements

  • 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.

Globalese 4.1 released

What's new

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.

Fixes

  • 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.

Globalese 4.0.3 released

Fixes

  • When importing corpora from a CAT tool connection, all groups were available for selection, not just the ones the user had the relevant permission in.
  • Small fixes in the navigation on the GUI.
  • Visiting the /logout page did not log out a logged in user.
  • The page didn't automatically refresh after a training or document translation was started.
  • When re-importing a previously existing corpus from a CAT tool connection, no new event was created in the corpus log.

Minor improvements

  • The Billing page provides details about the upcoming (open) invoice.
  • Users receive a confirmation e-mail on starting a subscription.
  • The Billing page indicates if the default card is about to expire or has expired.

Changes

  • A default limit of 100 has been introduced in the v2.1 API for listing corpora, projects and project files. See the updated API specification for details. This limit works the same way as the upcoming v3 API will: if no limit is specified, it will automatically be set to 100. (Version 3 of the API will add meta information about the filtered and total number of records.)
  • The File translation and Segment translation tabs on the Usage statistics page have been renamed to Document translation and Text translation, respectively.

Globalese 4.0.2 released

Fixes

  • Non-administrators can see the Log tabs of corpora, engines and project files.
  • When importing TMs or TBs from a CAT tool, not all previously imported corpora were detected.

Minor improvements

  • TMX versions 1.3 and 1.4 are checked for invalid tags when uploaded.

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 page.
  • Users were forced to accept the new Terms and Conditions applying to the new post-paid subscription model even if they were still on legacy subscriptions.

Minor improvements

  • Additional information is available to help decide when a stock+ engine built on an older stock engine should be re-trained.

Globalese 4.0 released

What’s new

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.

Usage-based subscription

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.

Fixes

  • 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.

Globalese 3.13.1 released

Fixes

  • Modifying an engine didn't work if a corpus was promoted from auxiliary to master or demoted the other way round.
  • When cloning an engine, the browser would get stuck on the original engine instead of jumping to the clone.
  • Fixed the translation of formatting tags wrapping URLs.
  • Fixed the filters on the Statistics pages.
  • Displaying a group would show all users in the system, not just the ones in the group.

Minor improvements

  • If a user's browser gets stuck in a session, they can now force logout by visiting the /logout URL.
  • If the translation of a file fails, users will get an extra heads-up in the notification email in case the engine used has a deprecated version and needs to be retrained.
  • Minor quality improvements in the training process.

Changes

  • Version 2.1 of the API now mandates that a valid extension be provided when creating a new corpus entity using POST /v2.1/corpora.

New stock corpora

  • English ↔ Hebrew

Globalese 3.13 released

What’s new

  • Support for Across XLIFF files exported using crossConnect: exported XLIFF 1.2 files can be translated in Globalese and reimported into Across when using crossConnect for External Editing.

Changes

  • Files that only include new segments that are locked for translation can no longer be uploaded to projects. Previously these appeared as translatable, whereas they were never processed by Globalese.
  • Engines that used to be called "healthy" are now called "up-to-date".
  • The indicator showing that an engine includes corpora that have been updated has been changed from "Update available" to "Corpus updated". (See also the 3.12 release notes.)

Minor improvements

  • Translation quality improvements across all language combinations. Retrain your engines for improved quality.
  • When clicking on a link to a certain corpus, engine etc. requires the user to log in, the browser is now redirected to the original destination after a successful login.
  • Pagination numbers only take up a certain amount of space on a page, regardless of how many pages there are. At the same time, any page can be directly displayed with the new Jump to page input.
  • Master and auxiliary corpora are now paginated when displaying an engine that includes a large number of corpora.
  • Overview, Preview, Log, Versions etc. tabs now have their own URLs so they are easier to jump to directly.

Fixes

  • Various issues related to tags and punctuation marks have been fixed.
  • Line break characters within segments were incorrectly changed.
  • Multiple project files inside a folder and uploaded in a single zip file had the folder name(s) as part of the filenames, which caused issues when downloading the translated files.
  • When creating or editing engines, only 100 corpora were visible for selection.
  • The Status filter on the Engines page did not show all engines with Trained status.
  • New but locked segment/word/character numbers were included in the translation statistics.
  • Engines could not be quick trained if a master corpus was updated (as opposed to uploading the new version as a new corpus).

New stock corpora

  • Italian ↔︎ Slovenian