XLIFF Splitting and Merging

Created by: Anonymous

Original issue 146 created by micah... on 2010-10-14T21:07:43.000Z:

What steps will reproduce the problem?

1. This functionality was present (buggy) in .net OKAPI, not yet present in Java Okapi (?)
   2.
   3.

What is the expected output? What do you see instead?
Under .net version of Okapi (latest version), you could split a single xliff into multiple xliffs, based on the element. Each component xliff written out had all the header information, and then one file element. The problem was that it added line returns to the source and target: whenever there was an inline element directly following or , it added a line return. If or was followed first by a text string, it didn't do this. Same for inline elements directly before the closing or . This behavior made it destructive to use the tool.

Example of it after split:

{1}Caution:{2} To prevent catheter damage or dislodgement during introducer needle and guide wire removal:

Same data, before split:
{1}Caution:{2} To prevent catheter damage or dislodgement during introducer needle and guide wire removal:

What version of the product are you using? On what operating system?
winXP, final .net version. Tested Java version on OS X 10.6, but it doesn't seem to have that utility built in yet.

Please provide any additional information below.
Split/merge can be really useful, I hope it gets added back soon (with tweak for the white space handling)!