Author - Greg Horváth

Globalese 4.3 released

What's new

We wanted to make the lifecycle of an engine easier to keep track of and more transparent to our users. A new Versions tab that does just that has been added to every engine. This is similar to the existing Versions tab for corpora: it shows the properties of the engine over time -- or rather, over various trained versions (since a new engine version is created every time a training finishes.). You can see the composition of corpora, the version of stock corpora or engines used, as well as which Globalese version the various engine versions were trained on. (Note that historical data may not be always accurate, but it is going to be going forward.)

Above all versions, you will also find a version named Next. (In fact, this is the only "version" displayed for new engines that have not been trained yet.) This is a special one that always shows the current state of the engine, i.e. after the last edit. This is how the engine's next version will look like when you hit the Train button after making changes to the engine.

You will also notice a badge labelled Active. Currently this always indicates the last trained engine version, which is the one used for translation. There has been some ambiguity over what was previously displayed in the Master corpora and Auxiliary corpora tables, because once you edited an engine, it was no longer obvious what corpora were used in the active version. From version 4.3 on, we no longer have to make compromises about that.

Making clearer which version of an engine was trained how and when also enables us to introduce more new functionality related to engine versions in upcoming releases.

Where have the Train/Edit/Clone buttons gone?

We thought it makes sense to move the Train/Cancel training, Edit and Clone buttons from the header of the engine page to the Versions tab. Since it is always the next version that gets trained, edited or cloned, we believe it is the best user experience if you find these buttons together with the pertaining information.

Important changes

  • If you have been using the Quick training functionality, you probably know that in order to be able to quick train a (previously trained) engine, you had to update some of the master corpora in the engine. From version 4.3, removing one master corpus and adding another will not qualify the engine for quick training. Instead, you should be updating corpora using the existing corpus update functionality, so Globalese understands that the engine is using the same corpus, only a more recent version of it. (Note that you can still add new master corpora to engines and quick train them, as before.)
  • The API endpoint /v3/engines/{engineId}/resources has changed. Please check out the updated specification.

Minor changes and improvements

  • As more and more v3 API endpoints become publicly available, we continue to deprecate v2.1 API endpoints. They will still be around for a while, but it's best to familiarise yourself with version 3 of the API, if you haven't already done so.
  • Improved the speed of displaying tabular data on statistics pages.

Fixes

  • A 400 status code is returned alongside a meaningful message in case of an error uploading corpora using the v2.1 API. (Previously, a 500 status code was returned.)

Globalese 4.2.2 released

Fixes

  • Stock engines could not be selected to for a project, even if the engine actually did exist.
  • Empty and locked translation segments were counted as billable in Trados Studio files when translated through the file-based plugin.
  • Large Trados Studio files could not be uploaded for translation.

Changes

  • Apostrophes will be converted into right single quotation marks in certain cases when translating into French.
  • Removed the X-Powered-By header from API responses.
  • Removed nginx version from API responses.

New stock corpora

  • Bulgarian ↔ German

New stock engines

  • Bulgarian → German
  • German → Bulgarian

Globalese 4.2.1 released

Fixes

  • The wrong stock engine was loaded for translating files in some cases.
  • Newly trained engines could not be deployed for text translation.
  • Corpora could not be imported from Memsource.
  • Uploaded corpora or XLIFF files whose name starts with a non-ASCII character had the special character trimmed in the name after uploading.

New stock corpora

  • English ↔ Vietnamese

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.