Skip to main content

Currently to import a translated engagement one must pause the engagement and then import it. It is very painful especially when translations take longer times and English/source language do not want to wait for the translation to come back. Also, it is painful for import bug fixing on translated engagement.

 

Forgot to add one thing, that lot of times we cannot even pause the source/English live engagement, so we cannot even export the translated engagements.


No StatusAcknowledged

@aharkut Would draft mode solve this now? 


Yes it will. From UI we will be able to do this. But on API side, we will need the draft engagement’s ID which is not available. We will work on that separately.


@aharkut / @broghanzwack , please let us know when the draft mode is available via API.

Here is my current process via API (completed automated)

  1. Export the English engagement (XLIFF file)
  2. Convert XLIFF to JSON file as XLIFF strings are incorrectly segmented. So I am further breaking down multi sentence segment into single translatable unit.
  3. Send for translation
  4. Once the translation is received, convert the JSON back to XLIFF
  5. Pause the engagement if it’s active
  6. Import the localized XLIFF files
  7. Un-pause the engagement

After the draft mode API is available, I can update step 5 and 7


Reply