The Embedded content (Legacy) page is available for file types that still use the legacy embedded content processor. This is a generic processor that relies on the file type parser to extract embedded content and does not differentiate between the type of embedded content. As a result, this restricts you from specifying custom extraction and display settings for different types of embedded content.
The legacy embedded content is available for the following file types:
Microsoft Excel (all versions)
Java Resources
XML: Any XML
New XML (Legacy Embedded Content) file types
To configure the legacy embedded content processor, use the following options on the Embedded Content page of one of the file types above. These options control how SDL Trados Studio converts the extracted content into tags and whether these tags show up as translatable or non-translatable in the Editor view.
Use the Add... button to create extraction rules based on document structure information. Make sure that the document structure information you specify here is covered by a parser rule on the Parser page of your file type. Studio can only extract embedded content that is recognized by the file type parser.
Add tag definition rules to specify how to treat the embedded content defined in Document structure information box.
The processor will try to match the tag pair before tries to match each tag expression. That is, it looks for any section of text that starts with the Start Tag expression and ends with the End Tag expression before it tries to match individual start and end tags.
For example, to identify all HTML <tr>...</tr> (table row) tag pairs, enter:The Advanced Settings specify how tags are displayed.
When selected, the editor treats the tag as a word for the purposes of navigation. For example, in the editor, pressing Ctrl+Left Arrow will move the cursor to the beginning of the tag and Ctrl+Right Arrow will move the cursor to the end of the tag.
Gather ye rosebuds while ye may,<br>
Old Time is still a-flying: <br>
And this same flower that smiles to-day <br>
To-morrow will be dying.
Selecting this option does not mean that the tag is always hidden; the user can change the editor settings to force the tag to be displayed.
A tag can have a text equivalent. For example, the entity tag " has the text equivalent ".
Example: the tag specifies a footnote marker. Where this is the case, the translator needs the ability to move the marker to another word in the same sentence, so the tag should be included with the text.
Legacy Embedded Content vs Embedded Content Processors
Creating a New Embedded Content Processor
Topic: Published: November 10, 2014