This can be done by using a task template in the import. It is possible to
- protect tags in segments, that contain a valid xml string
- protect HTML5-tags in segments, even if the segment is no valid HTML5 or xml.
- protect arbitary strings via PHP-PCRE-regular expressions (it is chooseable, if the regex is executed before tag-protection, after tag-protection or both). The user can define as many regex as he needs to.
The order of protection in CSV-files is as follows:
- Protect MQM tags within the CSVs to ensure that they are imported and destroyed by one of the next steps
- Protect everything per REGEX, that is marked in the task-template as to be protected by REGEX BEFORE tag-parsing
- if tag protection in the task template is enabled
- If a segment is valid XML, protect all Tags
- If segment is not valid XML: Protect all known HTML5 tags
- Protect everything per REGEX, that is marked in the task-template as to be protected by REGEX AFTER tag-parsing
- Protect Whitespace (linebreaks and multiple spaces
- Protect all XML-special-chars that are left by encoding them as entities
Please see task templates for more information.