XLIFF export should be with empty targets

As far as i know we prefill the translation with the source.
Adding the translation to the output if available would be a feature in tmgmt.

The system is designed to deal with a lot improvements. However, processes like creating a review only job or asking to apply changes from origin is not implemented yet. Only the process of new content with request to translation, review, and flagging as outdated works. Placing another job (of the same source item) is a full cycle to ask for full retranslation of the document.

We are currently improving the XLIFF support and adding paired tags.
The problem is that CAT tools check if the source structure is identical to the target structure and things like paired tags are all there. It's integrity.

If we add a new chapter, new HTML elements, new paired tags and they are missing in the outdated translation provided, the validation will fail.

With translation memory based systems, it's easy to reapply the translation memory to the target again.
However, in case a user changed the translation in Drupal during the review / accept phase, the translation memory might be outdated.

This issue needs intelligent merging in the translation domain in case the structure / translation meta tags changed.

This requires testing with tools like Trados.

The idea is to have the translation field EMPTY instead of the duplicated source.
Adding the (previously) translated source to the translation side doesn't work as tools will not accept the xliff this way.

Yes, can confirm this is no go. Tried this out with Trados and the import might fail due to source and target not having same semantic structure. Moreover this should not be our responsibility. Translation tools have translation memory that should do exactly this job. So I suggest to close this issue as "won't fix".

Looks like not passing the source text into the target element is enough.

I assume you did test this with trados?

Can we add an assert for this? We already parse it to add the translation, should be a one line change to add an assertEqual((string) $transunit->target, '', 'Target text is empty') there?

yes, tested with trados.

provided test.

yes, forgot the dot.

OK, tested this. Works fine this way.

Ok, that was fun.

This exposed a bug in the actual implementation of the mask patch, and flaws in the test coverage.

Improved and fixed that.

Last minute argument change was a bad idea.

cannot get dreditor working...

Looks good, found only one typo:

Creates a translated XLIFF file basd on the replacement definition.

basd -> based

Committed and pushed.

This is way worse than it was for manual translation!

If I had the target prefilled I could replace text with a text editor quickly and easly, now I don't know how to do it (since there is nothing in documentation on how to translate manually, the format the file html or xif file should have etc.)

Can you please create an option in the module to choose whether to have target prefilled or not?

This is XLIFF specification. Perfectly documented:
http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html

It is a machine readable format. We follow semantics (as it is semantically wrong to prefill translation).
I recommend you to use a tool that can deal with XLIFF.

Plain text editor experience is no valid reason to change this behavior.
Please open a support request in case you need to discuss this situation.