- attached parts.zip
XLIFF Joiner does not properly merge <file> elements that were split up
Issue #724
resolved
- In Rainbow, add the attached XLIFF to a project. Note that this XLIFF contains only a single
<file>
element. Create a pipeline consisting of the "XLIFF Word-Count Splitter" step. Set the max word count param to 100. Execute the pipeline. - This will generate a large set of PART XLIFF files. (Also attached as a zip, for reference.)
- Clear (or restart) rainbow, and add the PARTs as input files. Create a pipeline containing "XLIFF Joiner". Execute the pipeline.
Examine the resulting CONCAT XLIFF file. It contains multiple <file> elements, each with original="400.html"
.
This is XLIFF corruption. If the original XLIFF was produced by extraction from another source format (as in this case), the CONCAT XLIFF will not merge correctly.
Comments (5)
-
reporter -
reporter - changed status to resolved
Fix
#724- Correctly join XLIFF parts split by word countBetter handling of cases where a single <file> element in the original XLIFF was split across multiple `PART` files by the splitter. Improved unittest coverage.
→ <<cset 3ee9dceb5087>>
-
reporter - changed status to open
Reopening because the code isn't merged yet
-
reporter - changed status to resolved
Fix
#724- Correctly join XLIFF parts split by word countBetter handling of cases where a single <file> element in the original XLIFF was split across multiple `PART` files by the splitter. Improved unittest coverage.
→ <<cset 833562f3a719>>
-
reporter Merged in issue724 (pull request #266)
Fix
#724- Correctly join XLIFF parts split by word countApproved-by: YvesS yves@opentag.com
→ <<cset 77315b9e08a4>>
- Log in to comment