Globalese 1.3.2 released

Globalese 1.3.2 delivers the following fixes:

  • Improved handling of multilingual TMX and TBX files.
  • memoQ file parser bug fixed.
  • Handling of invalid language codes in TMX or TBX files (invalid language codes won’t appear as a new language code any more).
  • Improved tokenization rules.

Related Posts

26Nov

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... read more
27Jan

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... read more
02Feb

Globalese 2.1.2 released

Globalese 2.1.2 fixes the following issues: When recycling a project, all segment pairs were taken from the evaluation files. Now only... read more
28May

Globalese 3.6 released

Starting with version 3.6, Globalese cloud users can quickly take advantage of ready-to-use generic stock engines for the most common... read more
08Apr

Globalese 1.7.3 released

Globalese 1.7.3 fixes the following issues: Tokenization error during translation. If engine tuning is stopped, the engine will now remain usable even... read more
31Jan

Globalese 5.2.1 released

Globalese 5.2.1 released read more
23Feb

Globalese 2.3.1 released

Globalese 2.3.1 fixes the following issues: If a segment contains capital letters only, it was converted into lowercase in the translation. The... read more
17Mar

Globalese 2.3.4 released

Globalese 2.3.4 fixes the following issues: Not getting a result after testing an engine. Problems when testing an engine with a TMX... read more
14Sep

Globalese 1.8 released

New features in Globalese 1.8: Non-translatable lists can be added to engines. These are simple monolingual files with one entry per... read more
28May

Globalese 1.7.7 released

Globalese 1.7.7 fixes the following issues: Japanese character conversions broke URLs in translatable text Lookup issues with glossary entries with mixed casing Globalese... read more