Author - Globalese Team

What's new

Building on functionality introduced in Globalese 4.3 and Globalese 4.4, users can now choose to select an inactive engine version to be used for document translation. This feature has been added to support users who want to test a newly trained version of an engine before activating it.

Fixes

• If a segment in a corpus only contained a quotation mark, the exported TMX file contained invalid XML.
• Fixed health indicator for the active version of stock+ engines.
• The Engines page now consistently displays the correct deprecation status of stock+ engines.

Improvements

• Some issues with the Bulgarian ↔ English stock corpora have been fixed.
• The English → Bulgarian stock engine has been retrained to reflect the improvements in the underlying stock corpus.
• Very large segments (are usually the result of incorrect segmentation in the source) are handled better.
• When training an engine that has Romanian on either side, T-cedilla and S-cedilla are always converted to t-comma and s-comma as a pre-processing step.
• When translating from Romanian, T-cedilla and S-cedilla are always converted to t-comma and s-comma as a pre-processing step.

Fixes

• When trying to quick train an engine that was quick trained on the previous occasion, an error occurred.
• Existing corpora could not be updated from the GUI.
• Fixed an issue with tag translation where two consecutive tags in the source sometimes ended up within a word in the translation.
• The list of corpora was loaded twice when arriving at the Corpora page.

Changes

• An inactive engine version cannot be activated while the engine is being re-trained.

New stock corpora

• Finnish ↔ Swedish
• Norwegian ↔ Swedish

What's new

• A new System settings page enables system administrators to decide whether or not Globalese should store one active plus one inactive version of engines. If this settings is turned on, it is also possible to configure whether or not the latest version of an engine should always become the active version.
• If there is an active and an inactive version of an engine, clicking the new Activate button on the inactive engine version's tab will make the currently inactive engine version the currently active one.
• The new Compare to active version toggle on the Next version tab of an engine displays the changes that have been made (corpora removed, added or updated) to the currently active engine version.
• The new Revert to active version button on the Next version tab of an engine does what it says on the tin: it reverts the next version back to the currently active engine version. (Note that it doesn't trigger re-training of the engine, just reverts all the changes made to the active version.)

Other changes and improvements

• When editing an existing engine, there is now an optional text field for leaving notes related to the engine version. Any information saved here will be displayed on the engine's Log tab, next to the "Engine updated" event.
• Text translation statistics can now be filtered by dates as well as users or API keys for text translation.
• If the stock corpora or engine used in an engine has been updated, there is now an indicator of that update next to the stock corpus/engine version.
• If an engine has more than 10 versions, earlier versions can be loaded in groups of 10.

Improvements

We have improved the transparency around the engine lifecycle.

• The Engines page now has a new column to show how long each engine has left before they get deprecated (which means they cannot be used until retrained).
• E-mail notifications received after successful file translation events now also contain a reminder about the engine that was used.

Fixes

• Quick training an engine would fail under certain circumstances.
• When authenticated with an API key for text translation, the GET /v3/engines endpoint incorrectly returned a 401 response.
• API keys could not be loaded on the Authorized users tab of an engine.

Changes

• The "Deployment for document translation" column on the Engines page has been renamed to "Published". Since it always has a binary value (published/unpublished) and there is no status to track, this is now represented by a simple tick/cross instead of a status badge.
• The Master corpora and Auxiliary corpora columns on the Engines page have been removed to make way for the more important Days until deprecation column.
• References to Memsource have been changed to Phrase.

Fixes

• Fixed a regression where fewer segments from the auxiliary corpora were used for translation than the optimal volume.
• Corpora could not be merged.
• Duplication of engine versions in the relevant API response.
• When translating into French, the â character caused words to split.

Improvements

• Engines having a long history of versions are now much faster to navigate around.

New stock corpora

• Danish ↔ Swedish
• Danish ↔ Norwegian

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

Fixes

• A bug introduced in v4.2.2 caused SDLXLIFF files to be unparseable after translation.

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

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

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