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

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

Original issue reported on code.google.com by fli...@enlaso.com on 31 Jan 2013 at 8:31

Blocked on: #193

computerline1z / okapi

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