Author Archives: Karol Moran

Release Version: 8.7.3

GlobalSight 8.7.3 is the latest release that includes such features as Dynamic Quality Framework fields (DQF), JBoss/WildFly Upgrade, API updates, Wildcards in TM search, Ability to Identify MT Matches in Reports, Comprehensive Pending Job Information, Popup Editor Supports Viewing and Replace image Files, Plugin for Adobe Experience Manager 6.2, Addition of Secondary JSON filter to XML filter, Microsoft Translator API change, Restart Globalsight from the GUI, Perplexity score MT segments, Import / export configurations, Show MT segments in editor, UI and usability improvements and many others.

Full release notes

Expert Insights into Latest GlobalSight TMS Connectors

By Andrew Gibbons

To meet today’s multilingual content requirements, global organizations require “publish fast” language technology solutions. Translation Management Systems (TMS) like Welocalize’s open-source GlobalSight TMS automate the content collection and delivery process to increase the overall efficiency of the localization workflow. Welocalize works with clients to develop connectors to automatically match files for translation and integrate the TMS with client’s content management systems (CMS). This increases speed and agility and facilitates continuous translation. Andrew Gibbons, Senior Software Engineer on the Welocalize GlobalSight team, shares his insights on the various push and pull connectors that have been developed for Welocalize clients using GlobalSight.

In the world of localization and translation automation, interconnectivity is key. But how to make the interconnectivity theory turn into reality in the real commercial world of different approaches, processes, files types and systems can be a challenge.

While there are standards such as TMX 1.4b, TBX and XLIFF 1.2 and 2.0 for translators, there are no widely accepted industry interoperability standards between Content Management Systems (CMS) and Translation Management Systems (TMS). The way forward for increased connectivity is to develop bespoke connectors and application programming interfaces (APIs) to enable integration of the various processes and files within the TMS and CMS.

The Welocalize GlobalSight team continues to develop a number of connectors to fuel our vision of interconnectivity for clients. We have a number of approaches:

  1. Third party connects to GlobalSight (“push”)
  2. GlobalSight connects to a third party (“pull”)
  3. Watched folders (“push/pull”)
  4. COTI standard (not yet widely adopted)
  1. Third party connect to GlobalSight (“push”): So far, connectors that have been developed under the “push” approach, include Drupal, WordPress, Adobe Experience Manager and Clay Tablet. The work of connecting to GlobalSight is carried out using GlobalSight's public API's. You can access these APIs on the GlobalSight website here.

Some of this “push” connector work is not included in the GlobalSight open source code and therefore not yet publicly available. Anyone wishing to use certain third party connects is given access when partnering with Welocalize. Welocalize has contributed the code for WordPress and Drupal connectors, and we are undergoing a process to make them publicly available on the Drupal and WordPress websites.

  1. GlobalSight connects to a third party (“pull”): The connectors that have been developed under the “pull” approach, include Git, CVS, Eloqua Marketing Content and Blaise. For these connectors, GlobalSight has exercised the API's of each system, creating each connector. The connector is included in the core code and may be turned on by accessing permissions within GlobalSight.
  1. Watched folders (“push/pull”): A “halfway house” of a watched folders solution has been created for clients using a standalone application called “Smart Box.” Essentially, a zip file on an ftp or folder that is accessible by stakeholders. Once a format has been accepted, either a naming format or particular file or an element inside an xml file, Welocalize’s watched folder solution can pull in the file and make sense of it, exercising GlobalSight API's to create a job within GlobalSight. There is a similar path for exporting. Smart Box is not part of the open source GlobalSight code.
  1. Common Translation Interface, COTI. COTI is an initiative to try to standardize the connection between CMS and TMS but has not yet been widely adopted by the localization community. You can read more about this project on the Association of German Manufacturers of Authoring and Content Management Systems website. COTI comprises of three levels, one, two and three. Level one has the ability to import a basic COTI package. Level two is a watched folder scenario. Level three is exchange by API. A COTI package consists of source files, a manifest, and optional reference files. For a COTI package, the source and target is a one to one language mapping. There is no one to many languages COTI mapping as yet. GlobalSight implements Level one and can import a COTI package. We have some elements of Level two in place, and more elements of Level three in place. More information can be obtained by speaking directly with your Welocalize GlobalSight team.

One of the key challenges with bespoke connectors is the time and resource needed to produce them. To create a connector, you need the API documentation, a test system to work with and test files. Some users have chosen to connect to GlobalSight in a “push” configuration using GlobalSight API's to create their own bespoke solutions with their own in-house systems and resources.

Connectors are an integral part of our overall GlobalSight strategy, to continue to deliver interconnectivity and value-add within all Welocalize language technology and TMS solutions delivered to our clients. The Welocalize GlobalSight team continues to develop the latest innovative connector solutions to meet client’s evolving localization and translation needs.

GlobalSight release notes are available online at and the latest version of GlobalSight is available to download at If you have any queries or questions about GlobalSight and GlobalSight connectors, please contact me,


Based in Dublin, Andrew Gibbons is a Senior Software Engineer at Welocalize, specializing in GlobalSight.

Release Version: 8.6.7

GlobalSight 8.6.7 is the latest release that includes such features as In Context Review Tool for InDesign and Office 2010, Support InDesign CC for In Context Review; Drupal 8, Stash, Blaise and AEM (CQ5) connectors; Eloqua Dynamic Contents Support, XLIFF 2.0 Specification Support, Upgrade JBoss and JDK version, API enhancements, Recreate ready jobs, Added re-try MT option, Add Multi-select to My Jobs - Job ID filter, Ability to Batch Download QA Reports, New Translation Verification Report, Support Special characters (emojis), UI and usability improvements and many others.

Full release notes

What’s new in GlobalSight 8.6

The latest version of Welocalize’s open-source translation management system (TMS), GlobalSight 8.6, was launched at the Localization World Conference 2015 in Berlin.  Senior Solutions Architect at Welocalize, Vincent Swan, shared the latest features and updates at the special GlobalSight Boot Camp conference session. This latest version brings even more functionality, enabling users to manage, translate and deliver global content. Andrew Gibbons details the new features in the following post.

There are a number of new features on the latest version, GlobalSight 8.6 that add benefit and significant value to GlobalSight users.

IMPORT PROCESS: The big item on the agenda for GlobalSight 8.6 was the improvements to the import process. We noticed that large jobs would be memory hungry and we tracked that down to usage of the JMS queuing system. To improve the memory usage, we created our own queue. This enabled us to have a more granular control over how many threads were available to do work for each file type. This function is turned on by default in the 8.6 version of GlobalSight and the configuration file is called In the 8.6 version, there is also a new import management console, so large jobs in progress can be cancelled by the admin. In later releases, we will review the usage for the JMS queue for export as well. We also noticed high memory usage for a large number of files for kit upload and thus made some improvements in this area too. The configuration file is called

MT CONTROL: Another key feature of GlobalSight 8.6 is machine translation (MT) control. For each MT type, you can increase the logging for debugging of connection to the MT systems or adjust the timeouts for how long GlobalSight will wait for an answer from the chosen MT system. Supported MT systems are now MS translator, Asia Online, DoMT, IP Translator, ProMT, Safaba, and Google Translate. The configuration file is called

REVIEWER SCORECARD: For reviewers, we give the opportunity to score an overall impression of the translation, under four categories and provide an overall comment. The scorecard categories are adjustable. These comments and scores can be reported via the usual reporting feature. To turn this feature on, check the radio button in the workflow, and in the project, select the scorecard option.

NEW LOG FOR AUDITING: We now log any changes, addition, modification and deletion in the Workflow, Translation Memory (TM), Translation Memory (TM) profile, Projects, Location Profiles, Filter Configuration, File Profiles, Segmentation Rules and Users. This is useful tracking down accidental and deliberate changes to critical settings that may affect leverage and word counts.

DOWNLOADABLE TRANSLATION KITS BY WORD COUNT: GlobalSight 8.6 can now split a file based on word count, or combine all files together. You can keep the original source folder structure or flatten it and also have the option to download a repetitions-only file.

NEW CONTEXT REVIEW TOOL: Reviewers do not need to log into GlobalSight 8.6. They can obtain an encrypted link from GlobalSight via an API that will take the user directly to the online review tool, with the ability to generate a preview pdf. Other Welocalize systems can request a reviewer link from GlobalSight and can the encrypted link out via email.

The path to the configuration files of interest is <GLOBALSIGHT_HOME>/<SERVER_HOME>/jboss/server/standalone/deployments/globalsight.ear/lib/classes/properties/.

GlobalSight 8.6 release notes, including product documentation, bug trackers and forums are available online at The new version of GlobalSight is available to download at  If you would like a demonstration of GlobalSight or to discuss any of the features, please let contact us today.