Problem

Currently, when exporting a task (especially via translator package), content protection is removed and exported as normal text.

This means:

Protected content is no longer protected outside of translate5 and translators can accidentally change or break this content. With this the purpose of content protection is lost.

Solution

Ensure that protected content stays protected when exporting XLIFF files.

Proposed way to go:

Export protected content using XLIFF <x/> (single) tags
Store the original protected content in the equiv-text attribute

We can use the ctype attribute to identify content protection tags

Example:

<x id="1" equiv-text="ORIGINAL_CONTENT" ctype="x-translate5-protected" />

Reimport Requirement

On import, detect these tags via the custom attribute
Restore them back into translate5 as content protection

In my opinion this behavior should be configurable.

Enabled: Export protected content as tags (new behavior)
Disabled(default): Export unprotected content as plain text (current behavior)

The config should apply to both: package and regular export.

Technical Notes

Implementation will be done in editor_Models_Export
Change affects:
Package export
Regular export (shared logic)
Validate if it works with: (e.g. Trados, Across)

config: runtimeOptions.editor.export.keepContentProtected
export will end in a file "parallel" to the normal xliff. So we will have:
<filename>.xlf (with xliff as before, un-protected)
<filename>.protected.xlf (which contains the protected content)