IDML filter issues: Hard returns are inline

[Former user]

Original issue 245 created by benjamin.t.m... on 2012-06-20T00:00:58.000Z:

What steps will reproduce the problem?
1. Open Rainbow, add IDML file to input list
2. Utilities > Translation Kit Creation
3. Package Format > XLIFF with RTF
4. Execute

What is the expected output? What do you see instead?
Should see an RTF file with soft returns represented as inline tags and hard returns represented as external tags. Currently both are represented as inline tags which causes segmentation issues when punctuation is not used at the end of a paragraph. Without punctuation or the hard return represented as an external tag the segment does not end where it should.

Additionally, when the Translation Kit Creation utility is used, the RTF is created with the text pre-segmented and the source text copied to the target. Can we modify the utility so this does not happen?

What version of the product are you using? On what operating system?
Rainbow 6.0.16 on Windows 7
IDML generated from InDesign CS5 for PC.

[Former user]

Comment [1.](https://code.google.com/p/okapi/issues/detail?id=245#c1) originally posted by @ysavourel on 2012-08-02T04:11:58.000Z:

[Former user]

Comment [2.](https://code.google.com/p/okapi/issues/detail?id=245#c2) originally posted by @ysavourel on 2012-08-02T04:49:53.000Z:

The part about not pre-segmenting and not pre-filling the target will be addressed in issue comment 26\.2.

[Former user]

Comment [3.](https://code.google.com/p/okapi/issues/detail?id=245#c3) originally posted by @ysavourel on 2012-08-09T15:19:38.000Z:

Status on Aug-09-2012: Work is under way to add an option to create a new text unit for each <Br/>. The modification is complicated and the merging back does not work properly in several test cases.

[Former user]

Comment [4.](https://code.google.com/p/okapi/issues/detail?id=245#c4) originally posted by @ysavourel on 2012-08-09T15:20:41.000Z:

[Former user]

Comment 5. originally posted by @ysavourel on 2013-02-27T18:59:04.000Z:

The option was made accessible today in the snapshot.
This is not finsihed yet and in quite a few cases using the option will result in the inhability to merge back the document. For production work, one must do a round-trip first to make sure the extracted document can be merged back.

[Chase Tingley]

Fixed in M34

The option, which never worked terribly well, has been removed -- the filter will now generally split TUs based on BRs as appropriate.