As part of our ongoing efforts to improve the accuracy of our international translations, I am pleased to announce a new process that will assist with getting translation recommendations into the product much quicker.   Specifically, we revamped this process with the following objectives in mind:

 

  • it confirms that the problem is very quick to fix
  • it assigns it to an engineer that is responsible for translation fixes
  • it provides internal accountability for the improved translation
  • it keeps Jive's translation company in-the-loop in order to ensure the fix makes it into future versions

 

In general, the process is invisible to the customer, who files bugs to the supportal as before.  As always, the more detail supplied the better, including the language the problem is in, a suggested fix to the problem and the language bundle key it affects, if known.  It is also useful to indicate in the issue that it should be filed using the ‘fast-track’ method for getting language fixes into core.

 

Once a customer submits a ticket to Jive Support, the following happens:

 

  • the support engineer files an issue with a special flag for translations into our bug-tracking system.  This automatically assigns the bug to the engineer responsible for language issues
  • the language engineer passes the issue to a Jive employee responsible for confirming or creating the proper translation
  • once confirmed, the language engineer sends the fix to our external translation service for confirmation and inclusion in their “translation memory” for future translations
  • the fix is then checked into the core code for the next release 

 

We have already tested this process out, and this new process completes in only a few days!  Note, however, that there is no guarantee that fast-tracked translation bugs will get into core.  It is ultimately up to the language engineer and Jive employee responsible for the language to make this decision, based on appropriateness for all customers and difficulty in getting it fixed.