Leveraging PO files: Source is always inserted into target

[Former user]

Original issue 308 created by [e-mail] on 2013-01-16T17:51:12.000Z:

What steps will reproduce the problem?
1. Load PO files in Input List 1
2. Load OmegaT TMX file in Input List 2
3. Create Pipeline: Raw Document to Filter Events, Diff Leverage, Filter Events to document

In Diff Leverage I set the treshold to 100

What is the expected output? What do you see instead?
I would expect that if a match is found in the TMX file, the translation will be inserted in the newly created PO files (and there are definetely matches). If not, the target should remain empty (indicating that not translation has been done).
Instead the source content of the PO files is copied to the target of the PO files. The same happens if I use leveraging by Piensive TM.

What version of the product are you using? On what operating system?
Windows 7, 64bit; Version 6.0.19

Please provide any additional information below.
Source is EN-GB, target is DE-DE

Am I only handling this wrong? Or is it a bug?

[Former user]

Comment 1. originally posted by @fliden on 2013-03-15T20:21:24.000Z:

It's not really a bug. I believe this is how the multilingual format are designed currently. The intended use case is:

Raw Document to Filter Events,
Diff Leverage,
Rainbow Translation Kit Creation (For example xliff package)

The leveraged items are placed in the pre-translated tmx as well as alt-translations inside the xliff file. The previously emtpy targets are to be translated from scratch. But maybe for this specific case we could consider having an option to keep the empty targets.

[Jim Hargrave (OLD)]

There are many components that seem to default to copying the source (segmenter!!??). I don’t believe any component should copy the source to the target except for the final writer.