Create Rainbow TransKit for XLIFF2 results in tab-delimited files

[Former user]

It seems we don't get the right selection in Rainbow when selection XLIFF2 for the output format of the Rainbow TransKit creation. Probably some issue with index mapping.

[Chase Tingley]

Oh, wild. To clarify: if you use the Rainbow Translation Kit Creation step and set the output type to XLIFF v2 (Beta), the step does not execute persist correctly. It selects Translation Table (Beta)instead and writes out the translation table .txt file in the package.

I’ve verified this on the current dev branch (1.40.0-SNAPSHOT).

[YvesS]

I think that was introduced when we removed the “versified text” output format. It should be a quick fix.

[YvesS]

Fixed issue #944 (Create Rainbow TransKit for XLIFF2 results in tab-delimited files).

→ <<cset 36da12bbe57e>>

[Chase Tingley]

Thanks @YvesS !