Currently, after you upload XLIFF files to an engagement to provide translations, you are not allowed to modify the engagement. This means that to modify an engagement after a translation has been put in it, you have to take the following steps:
- Store the original XLIFF file
- Remove the translations from the engagement
- Update the engagement with the changes
- Re-export a blank XLIFF file
- Add the translations back into that blank, new XLIFF (likely using a 3rd-party diffing tool like Winmerge or Kdiff3 to facilitate)
- Re-import the translations.
This is a pretty painful process, and means that we can only really upload translations and validate the engagement in other languages once the engagement is really, really done.
It would be nice if Gainsight would:
- Allow editing the engagement after translations have been uploaded.
- Highlight engagements on the Engagements page that have been updated after they have translations, but that haven’t yet had their XLIFFs updated in one or more languages. This would remind them that they need to get the engagement translations updated to get the translations up-to-date with the base engagement.
- Other notifications within Gainsight reminding users of this might be useful.
- When an engagement has been edited in English but hasn’t yet had updated XLIFFs uploaded, show users the old version of the engagement for the other languages of the engagement, so they still see a coherent, fully-translated engagement in their native language.
