- removed milestone
- changed title to Create Rainbow TransKit for XLIFF2 results in tab-delimited files
Create Rainbow TransKit for XLIFF2 results in tab-delimited files
Issue #944
resolved
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.
Comments (5)
-
-
I think that was introduced when we removed the “versified text” output format. It should be a quick fix.
-
- changed status to resolved
Fixed issue
#944(Create Rainbow TransKit for XLIFF2 results in tab-delimited files).→ <<cset 36da12bbe57e>>
-
Thanks @ysavourel !
-
- changed milestone to 1.40.0
- Log in to comment
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 selectsTranslation 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).