Details
-
New Feature
-
Resolution: Fixed
-
None
-
High
-
For CSV file importers: the protection of HTML tags in the CSV content is now configurable (tag protection config) and is disabled by default.
-
XLF and CSV files can now contain HTML content (CSV: plain, XLF: encoded), the HTML tags are protected as internal tags. This must be enabled in the config for the affected tasks.
-
Empty show more show less
Description
The currently available import config "CSV import: Protect tags" must be generalized, that it protects HTML/XML tags within the CSV parser and as well tags inside XLIFF or SDLXLIFF files (regardless if they come form Okapi or from a direct import).
In xliff or sdlxliff the HTML/XML is assumed to be encoded as entities like so:
<source xml:lang="de">Dies <strong>ist ein</strong> Test.</source>
In our CSV parser the tags will be assumend as plain tags, like it currently is the case. So the CSV cell content would look like this:
Dies <strong>ist ein</strong>Test.
The description of the config must change to this (also the code id and the default changed):
INSERT INTO `Zf_configuration` (`name`, `confirmed`, `module`, `category`, `value`, `default`, `defaults`, `type`, `description`, `level`, `guiName`, `guiGroup`, `comment`)
VALUES ('runtimeOptions.import.fileparser.options.protectTags', '0', 'editor', 'system', '', '', '', 'boolean', 'If set to active, the content of the file is treated as HTML/XML (regardless of its format). Tags inside the imported file are protected as tags in translate5 segments. This is done for all HTML5 tags and in addition for all tags that look like a valid XML snippet.', '8', 'Protect tags', 'File formats', '');