Embedded Content (Legacy) vs Embedded Content Processors

SDL Trados Studio 2014 and earlier used the XML/Java/Excel parser for extracting any type of content found inside the XML/Java/Excel file. The extracted content that met the rules defined on the Embedded Content page was then processed with a generic embedded content processor. This generic processor could not differentiate between the type of embedded content extracted from the XML, Java or the Excel document.

For XML files, SDL Trados Studio 2014 SP1 and later can extract content embedded with a dedicated processor, specific to the type of embedded content found inside the XML document.

The embedded content processor that you assign to handle the embedded content in your XML document processes the embedded content as a separate, individual file. This enables you to specify which parts of the embedded content should be processed and to define custom settings for processing the extracted embedded content.

For Java and Excel files, Studio 2014 SP1 and later use the same processing behavior as Studio 2014 and earlier.

The table below compares the way Studio 2014 and Studio 2014 SP1 and later process embedded content.

	Embedded Content (Legacy) - Studio 2014 and earlier	Embedded Content - Studio 2014 SP1 and later
XML files	Any type of content embedded in an XML document extracted with the XML parser and processed with a generic embedded content processor.	HTML 5 content processed with the dedicated HTML 5 embedded content processor. HTML 4 content processed with the dedicated HTML 4 embedded content processor. Plain text embedded inside the XML document processed with the dedicated Plain Text embedded content processor. Any other type of XML embedded content processed with a custom copy of one of the existing embedded content processors.
Java and Excel files	Any type of content embedded in a Java or Excel document is extracted with the Java/Excel parser and processed with a generic embedded content processor.	Any type of content embedded in a Java or Excel document is extracted with the Java/Excel parser and processed with a generic embedded content processor.
	Cannot customize extraction settings for embedded content.	Can customize extraction settings for embedded content.
	Cannot differentiate between embedded content and main content in the Editor view.	Clearly marks embedded content sections and mentions the embedded content processor used for processing the chunk of embedded content.

Embedded Content (Legacy) vs Embedded Content Processors

Embedded Content (Legacy) - Studio 2014 and earlier

Embedded Content - Studio 2014 SP1 and later