Releases

Globalese 3.11 released

What's new

Changes

  • CAT tool connectors are now all managed in one place.
  • Projects are now sorted by creation date by default.

New stock corpora

  • Czech ↔︎ Slovak

New stock engines

  • Czech ↔︎ Slovak
  • English ↔︎ Norwegian Bokmål

Globalese 3.10.2 released

Fixes

  • Translation failed if a source segment contained three pipe characters in succession.
  • Casing errors when translating to/from Japanese.
  • Uploading a TSV file as corpus threw an error.

Minor improvements

  • Corpora imported from CAT tool servers using one of our connectors are marked with the icon of the CAT tool on engine pages and when editing an engine.

New stock corpora

  • English ↔︎ Norwegian Bokmål

Globalese 3.10.1 released

Fixes

  • Wordbee files were pre-translated incorrectly: two <target> elements were inserted into each translated segment.
  • The PUT /v2.1/corpora/{id} API endpoint failed if the uploaded corpus had already been uploaded once.
  • When importing translation memories from Smartcat, all TMs are now listed instead of only a maximum of 100.

Globalese 3.10 released

What's new

  • Aggregated usage statistics per month and per engine are now available to administrators. Read more here.
  • Corpora and project listings are now paginated.

Changes

  • Corpora imported from CAT tool servers using one of our connectors will be marked with the icon of the CAT tool going forward. Stay tuned for further improvements in this area!
  • Corpora added to an engine are now sorted alphabetically.

New stock corpora

  • Danish ↔︎ German
  • English ↔︎ Estonian
  • English ↔︎ Irish
  • English ↔︎ Latvian
  • English ↔︎ Lithuanian
  • English ↔︎ Maltese
  • English ↔︎ Norwegian
  • English ↔︎ Swedish
  • German ↔︎ Romanian
  • Italian ↔︎ Spanish

New stock engines

  • Danish ↔︎ German
  • German ↔ Czech
  • German ↔︎ French
  • German ↔︎ Italian
  • German ↔︎ Portuguese
  • German ↔︎ Spanish
  • English ↔︎ Norwegian

Fixes

  • Groups could not be updated.
  • Error creating a new project using a stock engine.

Globalese 3.9.2 released

New functionality

  • Stock engine language combinations can now be queried through the API.

Fixes

  • URL parsing and translating issues.
  • Not all Memsource translation memories were displayed when retrieving them as corpora.
  • Users with only engine managing permissions could not display the names of projects used by an engine.

Improvements

  • Longer sentences are now translated more accurately.

Globalese 3.9.1 released

Fixes

  • Users with only project access in a group could not see the group a project belongs to.
  • Not all Memsource TMs were listed when retrieving translation memories from Memsource.
  • Project creator user missing from project Log page.
  • When editing an engine, corpora were not sorted alphabetically (this was a regression).

Minor improvements

  • 4 to 8 per cent increase on average in training speeds.

Globalese 3.9 released

What's new

We've introduced a quick training option to save training time where engines receive minor updates, and therefore don’t need to be fully retrained.

Read more about this new functionality here.

Notable fixes

  • Spacing issues after tags followed by punctuation marks.
  • Unicode characters were sometimes replaced by text in the translation.
  • Project log could not be displayed.
  • Translate button active for projects without an engine.

Globalese 3.8.4 released

New functionality

Minor improvements

  • Groups on the Corpora, Engines and Projects pages are now listed alphabetically.
  • The total number of currently existing engines is always displayed on the About page.
  • Project files can be sorted by status and last translation date & time.
  • Memsource connector updated so support changes in the Memsource API affecting filtering for TMs when retrieving them from Memsource.

Fixes

  • When editing a project that had a stock engine chosen, no selected engine was displayed.
  • Non-admin users could not edit projects.
  • Spaces left after translation in Japanese target texts.
  • Conversion of colons to double-byte characters fixed for Japanese.
  • URLs inside tags were truncated.
  • When deleting an engine, corpora that were not deletable were offered for deletion, causing an error.
  • Stock+ engines with a non-green health indicator didn't become healthy even after retraining.

Globalese 3.8.3 released

Globalese 3.8.3 fixes the following issues:

  • Some term bases could not be retrieved from Memsource
  • XTM term bases could not be filtered by target language
  • URL translation issues
  • Stock corpora were automatically added when creating a new engines even if there were no stock corpora for the language pair

Globalese 3.8 released

The major highlight of Globalese 3.8 is stock+ engines. Stock+ engines are customised stock engines, i.e. pre-trained stock engines extended with the user's own corpora. Note: stock+ engines are only available in the cloud environment.

Improvements

  • A Select all/Deselect all option has been added to the Corpora and Engines listing pages.
  • It is now possible to filter engines by status on the Engines page.
  • Better experience on smaller screens (i.e. mobile devices).

Further changes

  • The number of individual corpora that an engine may contain has been limited to 500.
  • The Engines page now shows master and auxiliary corpora segment counts in two distinct columns.
  • The Engines page now shows whether an engine has been built using stock corpora or a stock engine.
  • An Engine page now shows whether the particular engine uses stock corpora or a stock engine.
  • Master and auxiliary corpora now appear in two distinct tables on Engine pages.
  • The last trained version is shown on Engine pages.

Notable fixes

  • TBX parsing issues.
  • Not being able to create new users.
  • Could not delete resources containing apostrophes in their names.
  • Engines' Log pages not showing any entries.
  • Translation files' Log pages not displaying.
  • Authentication via the API not working.
  • System administrators unable to change their passwords.
  • Projects using XTM connector could not be created.
  • XML parsing errors during translation.