Allow Translation Kit merge from Kit Creation "skeleton" instead of original file

[Former user]

Original issue 310 created by @fliden on 2013-01-31T20:31:46.000Z:

Cases below where there are steps prior to the Kit Creation Step can introduce synchronization issues (deleting inline codes or translation units) causing the Merge to fail. This is because the Kit Merge uses the original file but do not perform the same intermediary steps. The solution would be to record the skeleton resulting from the intermediary steps and then use that skeleton for the merge instead of the original file. However, this could cause other side effects.

Input file ->

***EXTRACTION***
RawDocument to Filter Events
Inline Codes Simplifier
.........
Rainbow Translation Kit Creation

***MERGE**
RawDocument to Filter Events
Rainbow Translation Kit Merge

[Former user]

Comment 1. originally posted by @ysavourel on 2013-09-04T06:37:21.000Z:

Related to issue comment 19.3

[Jim Hargrave (OLD)]

This is still an issue. We need a way to replay merge with the same steps done during extraction. Could the pipeline be stored in the xliff? External file? Custom tkit? Maybe this is a TMS issue and should be solved by okapi?