7 reasons to create XML file types in SDL Trados Studio

Even though a default file type for the translation of XML documents (AnyXML) is available in  SDL Trados Studio , there are several good reasons to create a custom XML file type:

Example: An XML file in SDL Trados Studio without a custom XML file type

1. The default XML file type makes all elements in an XML file translatable. That means that there can be cases where more content is shown in the translation editor than actually has to be translated.
2. The default XML file type does not process attribute values. This means that there are cases were certain contents are not translated. This is often only discovered after the re-import of the translation into the originating system. The additional translation of the missing contents costs extra time.
3. The default XML file type does not process information about length restrictions, e.g. in the form of attributes. This means translations have to be edited later and translation memories have to be updated. These additional workflow steps can be avoided using a custom file type.
4. The default XML file type provides no contextual information such as formatting or information in the document structure column in the translation editor. I.e. during the translation process, headlines, paragraphs, list items, etc. cannot be distinguished. This complicates the work of the translator.  In addition, the context cannot be saved in the translation memory, which makes the automatic reuse of correct translations in follow-up projects very difficult.
5. The default XML file type does not allow optimal processing of embedded contents, such as HTML in XML or CDATA sections. This means Tags in CDATA sections are processed as text and are counted (as well as paid) as such and cannot be locked and checked. As a result CDATA sections are often not properly segmented.
6. The default XML file type does not allow the validation of the XML file with a DTD or a schema. I.e. the validity of the translated XML file cannot be guaranteed, which can lead to errors when the XML file is processed.
7. The default XML file type offers no preview of the document in the original layout during translation or review of the file in SDL Trados Studio. This results in an increase of review work in the processes.

Example: XML files with a custom XML file type in SDL Trados Studio 

Conclusion

Without a custom file types for XML, the work of translators and reviewers is made more difficult. In addition, the translation process as a whole is often prone to errors. As a result, the time and the costs for translation and review are often significantly higher than with the use of a custom XML file type. The creation of a custom XML file type is an investment that will quickly pay off.

Do you have any questions?

Do you have question about the translation of XML files in SDL Trados Studio? Do you want to learn how to create an XML file type in SDL Trados Studio? Or do you want us to create or adjust an XML file type for you? Send an email to  info(at)loctimize.com  or call us at + 49 (681) 91038365.

XML workshop

Loctimize offers a special workshop on the translation and localization of XML files in SDL Trados Studio. You can find more information about the workshop on our website under the section Training and workshops.