Documentation Center

XML 2: W3C ITS Compliant settings

The XML 2: W3C ITS Compliant file type has the *.xml and *.its extensions.

Detection

Setting
The file detection settings for this XML file type are pre-defined and cannot be changed.

Writer settings

SettingInstruction
Unicode UTF-8 byte order mark (BOM)From the list, choose an option to determine how BOM is handled during translation: Preserve; don't add if not originally present, Preserve: add if not originally present, Remove if present.
Values of xml:lang and lang attributeFrom the list, choose an option to determine how 'lang' is handled during translation: Change matching source language to target language, Always change to target language, Do not change.

Whitespace settings

SettingInstruction
Whitespace in contentDecide how whitespace is treated during translation: Normalize unless xml:space='preserve' ; Always preserve; Always normalize.
Normalize whitespace in tagsSelect the check box to ensure that whitespace is normalized in tags.

Namespace settings

SettingInstruction
The namespace mappings for this XML File Type are auto-generated and cannot be changed. If you require manual control over the namespace mappings, create a new XML file type.

Validation

SettingInstruction
Perform schema and DTD validation during file detectionDecide how schemas and DTD files are validated:
  • Treat all validation warnings as file parsing errors
  • Report warning if no DTD/schema can be found
Perform schema validation when verifying translation
Manually specify schemaEnable this option to specify schemas manually. Decide how the schemas are used:
  • Use for all XML documents
  • Use only for documents which do not specify DTD/schema
Master SchemasKeep the default values or add more files.
Dependency Schemas and DTDsKeep the default values or add more files.

Entity settings

SettingInstruction
Enable entity conversionEntity settings specify whether special characters are converted to their corresponding HTML entity. Select or clear the check box depending on whether you want to have entity conversion enabled or not.
Convert numeric entity references to inline placeholder tagsSelect or clear the check box depending on whether you want to have the numeric entity conversion enabled or not.
Skip conversion inside locked contentSelect or clear the check box depending on whether you want conversion skipped for locked content.
Add an entitySelect plus sign, add the character, and decide whether you need the following check boxes enabled or not:
  • READ AS CHARACTER - When enabled, this setting specifies which entities are converted to their respective characters during parsing.
  • WRITE AS ENTITY - When enabled, this setting specifies which characters are converted to their respective entities during writing.
Edit an entityAdjust the given values.

Embedded Content

SettingInstruction
Process embedded content Select the check box to enable the processing of embedded content. Then, specify one processing method: Inside CDATA element with; Defined by parser rules; Defined by document structure information.
Inside CDATA element withCDATA stands for character data and refers to a portion of element content that is marked to be interpreted literally, as textual data, instead of marked up content. If you enable this option, specify which entity interprets the element: Embedded Content Plain Text v 1.0.0.0; Embedded Content SpreadsheetML v.1; Html Embedded Content 5 2.0.0.0; Html Embedded Content 4 2.0.0.0.
If you select this option, the content is sent directly to the embedded content processor of your choice, which parses the resulting paragraph units. There are several limitations:
  • Context information (e.g. comment, length limitation) can be defined on the parent element enclosing the content. This context information, when sent to an embedded content processor, is not be propagated and shown in the editor. In other words, context information cannot be applied over the paragraph units parsed by the XML2 filter, regardless of what was specified at the level of parser rules.
  • XPath-based comments cannot be extracted for the paragraph units parsed by the XML2 filter.
To overcome these limitations, do one of the following:
  • Use the Document Structure Information option.
  • Configure the XML2 filter in Trados Studio, export the configuration file, and import it in your cloud environment.
Defined by parser rulesTo add a parser rule:
  1. From the PARSER RULE and EMBEDDED PROCESSOR ID lists, select one of the available values.
  2. Select plus sign.
If you select this option, the content is sent directly to the embedded content processor of your choice, which parses the resulting paragraph units. There are several limitations:
  • Context information (e.g. comment, length limitation) can be defined on the parent element enclosing the content. This context information, when sent to an embedded content processor, is not be propagated and shown in the editor. In other words, context information cannot be applied over the paragraph units parsed by the XML2 filter, regardless of what was specified at the level of parser rules.
  • XPath-based comments cannot be extracted for the paragraph units parsed by the XML2 filter.
To overcome these limitations, do one of the following:
  • Use the Document Structure Information option.
  • Configure the XML2 filter in Trados Studio, export the configuration file, and import it in your cloud environment.
Defined by document structure information - Document Structure InformationFrom the Document Structure Information list, select one of the available values and then select plus sign.
Defined by document structure information - Tag definition rulesEnable this option to set the selected embedded content processors to extract embedded content from specific context. Create extraction rules based on the document structure information. Make sure that the document structure information you specify here is covered by a parser rule in the Parser settings section for your file type. Trados Studio and Trados Online Editor can only extract embedded content that is recognized by the file type parser.
  1. Select Add New Rule.
  2. From the Tag Type list, choose a value: Placeholder or Tag Pair.
  3. In the Regular expression field, enter the regular expression.
  4. Select the Ignore Case check box to ignore the case of the identified content. Otherwise, keep the default value (clear check box).
  5. From the Segmentation Hint list, choose a value from the list to determine how segmentation is performed: May Exclude (default), Include, Include With Text, Exclude. The value you specify here is available when you configure a parser rule under Parser > Add New Rule > Properties > Advanced Settings > Segmentation Hint. Check this topic to learn what each segmentation hint does.
  6. Select Save.

Preview settings

SettingInstruction
XML node-tree preview

When previewing your XML file in Trados Online Editor, you can use the built-in node-tree preview to view the general structure and components of your XML.

This preview displays the target XML file as a tree of XML elements which you can navigate. The preview displays all segment updates except:

  • Auto-cloned tag pairs (i.e. the segment starts outside of a tag pair and ends within it or vice versa)
  • Segments containing tags with attributes that are extracted in a sub-paragraph
Add preview type > Preview type based on XSLTIf you need preview capabilities not covered by the built-in XML node-tree preview, but rather by an XSLT, select Add preview type, and then select Preview type based on XSLT:
  1. Edit the name and description of your preview type, if necessary.
  2. Next to XSLT file, select Browse and upload the XSLT file for your transformation.
Add preview type > Preview type based on preview packageIf you need preview capabilities not covered by the built-in XML node-tree preview, but rather by a preview package emulating HTML display, select Add preview type, and then select Preview type based on preview package:
  1. Edit the name and description of your preview type, if necessary.
  2. Next to Preview package (.zip) , select Browse and upload a package containing the content and dependencies for your XML. The package should consist of several folders emulating a structure.
  3. Next to Selected output folder inside the package for the generated HTML file, select Browse. A pane emulating your folder structure opens. Select the appropriate location where the translated file will be saved once generated.