About Embedded Content Processors

Embedded content is content that uses a different syntax than the syntax specific to a certain type of file. For example, some complex XML file may contain chunks of HTML content included inside a CDATA section.

SDL Trados Studio can use separate processors for handling content embedded inside XML, XHTML, Java and Excel documents. This enables Studio to process embedded content as different file within the XML document and allows you to set different settings for extracting and displaying main and embedded content.

Available Embedded Content Processors

The Embedded Content page containing the settings for configuring embedded content processing is available for the following file types:

File Type	Embedded Content Processor Used	Description
XML: Microsoft .NET Resources	New Embedded Content Processors	Extracts content embedded with a dedicated processor, specific to the type of embedded content found inside the XML document. Processes the extracted embedded content as a separate, individual file. Enables you to specify which parts of the embedded content should be processed and to define custom settings for processing the extracted embedded content.
XML: OASIS DITA 1.2 Compliant	New Embedded Content Processors
XML: OASIS DocBook 4.5 Compliant	New Embedded Content Processors
New XML (Embedded Content) file types	New Embedded Content Processors

XML: Any XML	Legacy embedded content processor	Extracts embedded content with the file type parser, then processes extracted content with a generic embedded content processor. Does not differentiate between the type of embedded content extracted from the document. As a result, this restricts you from specifying custom extraction and display settings for different types of embedded content.
Microsoft Excel	Legacy embedded content processor
Java Resources	Legacy embedded content processor
New XML (Legacy Embedded Content) file types	Legacy embedded content processor

Why use embedded content processors?

Studio 2014 SP1 and later include separate embedded content processors, dedicated to handling HTML 5, HTML 4 content and Plain Text inside XML documents. These dedicated processors enable Studio to handle such sub-content as a separate file within the XML document. This means that you have all the settings to:

configure what information Studio extracts from the embedded content.
tag embedded content as translatable or untranslatable when opened in the Editor view.
use custom formatting for each embedded content element.
segment HTML content correctly before converting it to a translatable format.
add additional context information to structure HTML elements to make this reference information available in the Document Structure column.
display HTML character entities in the Editor view.
control HTML whitespace characters in embedded content.