File type settings
RWS engineers will provide customers an options XML file to support the XML standard received from Sitecore. This file has been built using standard files available in the Sitecore installation. In certain cases, customers may have custom XML content that requires the options XML file to be modified.
The file type settings should be Custom XML with Embedded Content, using the options XML file provided and edited per customer requirements. The source and target encoding should be UTF-8.
All fields, including non-standard, non-shared fields are sent for translation. Non-text based fields are flagged with an XML attribute (DoNotTranslate) which tells Trados to leave them untranslated.
<?xml version="1.0" encoding="UTF-8"?>
<project projectid="{FF178ADF-9B77-4D12-A7C1-BE550437A68E}" name="">
<item id="{698E5FAB-CE59-4FFC-88A0-A55489EEC172}" path="/sitecore/content/Content/Article Test Chain/Article1" name="Article 1">
<field name="Title" id="{ED69E97A-0AE4-4118-8E17-9AE746D54542}" type="Single-Line Text"><![CDATA[Article1]]></field>
<field name="Description" id="{2BE2B87E-61AB-451E-8F6A-FC6DFE6A21A4}" type="Single-Line Text" DoNotTranslate="true"><![CDATA[Ignore the content of this field]]></field>
</item>
</project>
Logic is included in the XML generation to allow for code blocks and XML within the translation content. Internal CDATA tags are now replaced for the translation process and put back when the new item is created.
<field name="Description" id="{23129CE7-E767-471C-BC79-619B917DED1B}" type="Single-Line Text" DoNotTranslate="true" cdataguid="2McsM3IlWEKJEyhEh22FEQ==">
<![CDATA[The first article in a chain of test articles, <2McsM3IlWEKJEyhEh22FEQ==>to check</2McsM3IlWEKJEyhEh22FEQ==> related item depth]]>
</field>