Releases

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

Globalese 3.12.2 released

Fixes

  • Fixed a regression affecting the translation of URLs and email addresses.
  • Auxiliary corpora were not included when an engine was cloned.
  • No new corpus version or log event was created when a new version of an existing corpus was uploaded using the API.
  • Added a few missing language codes.
  • Issues with setting a new password after forgetting it and requesting a new one to be generated have been fixed.

Minor improvements

  • We have been making continuous improvements for the Globalese GUI to be faster for a long time now. You will notice that navigation between pages is now a lot quicker.
  • When an engine is being trained, the progress now appears on the engine's own page as well as the Dashboard.

Changes

  • Engines with a trained version below 3.8.3 are now deprecated and need retraining.
  • The maximum allowed length of file names has been increased from 128 to 255 characters.

Globalese 3.12.1 released

Fixes

  • Notification e-mails were not sent when an engine training finished.
  • When changing the selection of corpora in an engine, corpora involved were also removed from all other engines containing the same corpora.
  • The timeout for uploading corpora has been increased to allow for longer processing times in case of large corpora.
  • White space issues were fixed in translation.

Globalese 3.12 released

What's new

The focus in the latest release of Globalese is on corpus lifecycle management.

Corpora in Globalese are maintained centrally, meaning you only have to upload a corpus once and then you can re-use it in as many engines as you wish, in either language direction. Needless to say, some corpora change more frequently than others, and if an engine is centred around a translation memory that gets updated every day, the engine might quickly become obsolete. The way this can be tackled is to first update the corpus, and then re-train the engine so it can reflect the changes.

Up to now, updating and re-training existing engines meant taking the following steps:

  1. Upload the most up-to-date version a corpus.
  2. Edit all the engines that were trained on said corpus, removing its old version and adding the new one.
  3. Re-train all affected engines.
  4. Delete the old, no longer used version of the corpus from Globalese.

The new process looks like this:

  1. Go to the corpus that needs updating.
  2. Click the Update button and upload the most up-to-date version.
  3. Re-train all affected engines.

It's even simpler if you are used to pulling your corpora from your CAT tool(s). When importing a corpus for the second time and onward, Globalese will not create a new entity, but update the existing one.

All the engines affected by a corpus update will display an indication next to the updated corpora, so when looking at an engine, you can immediately see what has changed since the last update.

When viewing a corpus, you can now see its version history on the new Versions tab to give you an idea about the volume changes across versions.

New stock corpora

  • Danish ↔︎ French
  • French ↔ Swedish

New stock engines

  • French → Swedish
  • French → Danish

Globalese 3.11.3 released

Fixes

  • An auxiliary corpus in an engine could not be changed into a master corpus, or vice versa.
  • Certain types of TBX files could not be uploaded.
  • Fixed recasing issues.
  • Fixed the parsing of heavily tagged TMX translation units.
  • The Corpus > Preview tab only showed the first tag in a segment with a symbol.
  • The password reset page didn't work.
  • Empty source segments could cause the translation of a file to fail.
  • The parsing of delimited corpora would stop if there was a line in the corpus containing nothing or only white space.
  • When previewing corpora or project files, RTL languages are now justified correctly.

Minor improvements

  • More efficient way of assigning permissions when a system administrator is editing a user account.
  • The Dashboard shows training and translation jobs in two separate tables.
  • When uploading corpora, newly uploaded corpora will have a link that enables users to conveniently go to the new corpus directly.
  • Toast messages have been introduced to confirm executed actions, also enabling us to transition slightly quicker between pages.
  • Specific error messages are now visible if uploading a corpus fails.
  • When a user is changing their password, they get instant feedback on password strength.

Changes

  • Dedicated translator instances are not available any more. Engines cannot be manually deployed for translation at this time, but expect this feature to start a new life in Globalese 4!

New stock corpora

  • English ↔︎ Korean
  • French ↔︎ Russian
  • Russian ↔︎ Spanish

New stock engines

  • French ↔︎ Russian
  • Russian ↔︎ Spanish

Globalese 3.11.2 released

Minor improvements

  • Improved user experience when importing project files from a CAT tool server.
  • Projects that are linked to a project on a CAT tool server and project files imported from a CAT tool server will have an icon to indicate the association.
  • Faster navigation between the tabs when looking at the details of a project file.
  • Improved user experience when displaying a preview (now with the actual segment IDs) of a project file.

Fixes

  • Error if two translation jobs using the same engine were started at the same time.
  • Unexpected control characters in project files could cause the translation to fail.
  • Locked tags in Memsource files were sometimes reinserted in the translations the wrong place.

New stock corpora

  • English ↔︎ Turkish

Globalese 3.11.1 released

Fixes

  • Training jobs could get stuck in "finishing" status on the dispatcher.
  • Language filters not working when importing corpora from Memsource.

Minor improvements

  • The Dashboard now displays training and translation jobs in starting order.
  • Tab-/comma-/semicolon-separated corpora containing not exactly 2 columns are rejected on upload.
  • More specific error messages when importing corpora from Memsource and the Memsource connector is missing certain permissions.

New stock corpora

  • German ↔︎ Russian

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.