Releases

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

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