Supporting XML with standard HTML embedded content
You first need to configure support for your XML content in SDL Trados Studio:
- From the menu File > Options, in the File Types dialog click New and select XML (Embedded Content) as below:
- Continue through the steps of the XML file type configuration dialog.
- Once you have completed the definition of the XML elements, click Finish and expand the newly added node for your new file type in the File Types tree on the left.
- Select Embedded content in the expanded list, check the box for Process embedded content using the following processor and select one of the default processor, namely Embedded Content Plain Text v 1.0.0.0, Html Embedded Content 5 2.0.0.0 or Html Embedded Content 4 2.0.0.0
- Click OK:
Now follow the usual steps to export your content type settings:
- Select the File Types parent node on the left side.
- In the list of file types that appears, select your newly configured XML file type.
- Click Export Settings... at the bottom of the screen.
- Save the .sdlftsettings file.
- To add support for such content to SDL TMS, proceed as described in the section Adding these settings to an SDL TMS Content Type below.
Supporting XML with custom embedded content
The example given below will demonstrate these steps for a source file that contains custom embedded content that will be identified by the use of regular expressions to delimit the text for extraction.
You first need to configure support for your Embedded Content Processor:
- From the menu File > Options, select Embedded Content Processors and unfold the navigation tree on the left-hand side of the dialog to see the list of processors
- Select one of the default processor, Plain Text (for this example), and customize this processor's settings as you wish. Note: It is important to use one of the three default processors and NOT use the Copy... button from this dialog as SDL TMS only support the three default embedded content processors ID. Copies are not supported.
- From the navigation tree on the left-hand side of the dialog, select the File Types
- Click New and select XML (Embedded Content) as below:
- Continue through the steps of the XML file type configuration dialog.
- Once you have completed the definition of the XML elements, click Finish and expand the newly added node for your new file type in the File Types tree on the left.
- Select Embedded content in the expanded list, check the box for Process embedded content using the following processor and select the Embedded Content Processor that you have customized.
Now follow these steps to export and manipulate your content type settings:
- From the menu File > Options, select the File Types parent node on the left-hand side.
- In the list of file types that appears, select your newly configured XML content type.
- Click Export Settings... at the bottom of the screen.
- Save the .sdlftsettings file.
- From the navigation tree on the left-hand side, select the Embedded Content Processors node.
- On the right-hand side, select the Embedded Content Processor that you have customized.
- Click Export Settings... at the bottom of the screen.
- Save the .sdlecsettings file.
- In an XML editor of your choice, open the .sdlftsettings and .sdlecsettings files.
- Copy the content of the .sdlecsettings into the .sdlftsettings file so that the root node SettingsBundle now has two SettingsGroup subnodes, one each for holding the settings of the XML filter and those of the Embedded Content Processor, as shown in the below screenshot:
- Save the file being sure to retain the .sdlftsettings extension.
- To add support for such content to SDL TMS, proceed as described in the section Adding these settings to a SDL TMS Content Type below.
Adding these settings to a SDL TMS Content Type
- Add a new Pre-processing Resource of Type Options XML File and upload the .sdlftsettings file to this new resource.
- Add a new Content Type based on the Custom XML (Embedded Content) Pre-processing tool and associate the new Option XML file that you have just created.
- Add it to your Configuration and since it is XML content, be sure to include Scan in the supported Workflows and configure the Encoding tab of your Configuration settings according to the content to be processed