![]() Thus, for example, if you plan to translate an SDLXLIFF file using TagEditor in SDL Trados 2007, you must ensure that the source has been copied to the target text, because the INI supplied for XLF files in the old version of Trados only reads the tags for the target segments. Some other environments, such as Trados TagEditor (a tool in older versions of Trados) cannot successfully process an XLIFF file unless the source text is copied to the target segments. Your customer with SDL Trados Studio must do that. Please note that you cannot generate a target file ("cleaned file") from environments other than SDL Trados Studio if you are working with SDLXLIFF files. Your deliverable file will be the translated SDLXLIFF upon export from your translation tool. Then import these into your working environment using an XLIFF filter. If you are using a tool other than a version of Trados and your customer requires full compatibility with SDL Trados Studio 2009 or SDL Trados Studio 2011, request the files to translate in SDLXLIFF format. However, SDLXLIFF can be processed by tool capable of working correctly with XLIFF, which includes the later versions of Atril's DVX and the current DVX2 as well as Kilgray's memoQ, the Open Source tool OmegaT (be careful - tags must be checked carefully and possibly repaired afterward!) and many others. The latest versions of SDL Trados (SDL Trados Studio 20) use an underlying data format which is a version of the XLIFF standard, for which SDL uses its own extension (SDLXLIFF) rather than the usual *.xlf extension. This is not difficult, but it does require attention to detail and proper methods for the specific case involved. Or which are not unless the right techniques are used to prepare and exchange the data. There are many tools which claim to be "compatible" with Trados but which are in fact not to a full extent. This post focuses on satisfying the requirements for "Trados jobs", due to the widespread use of this tool in various version over the past two decades among corporate clients and translation agencies. In other words if you as a translator work with an agency or a direct client who uses a common tool such as a current or older version of SDL Trados, WordFast, memoQ or most other professional tools, it is possible to translate the data safely in the format your customer desires even if you use a different translation environment or in some cases none at all. With the current exception of most server-based projects, it is very seldom true that translations must be done with the same tools used to prepare the data for translation or manage the translated data resources. Other great websites include, , and .For many years, there have been frequent, unnecessary misunderstandings between outsourcers and translators regarding the tools necessary to translate jobs for which particular data formats are required. ![]() Some answers simply cannot be given without these factors in mind. Nota bene: When creating a post, please consider whether following information might be relevant for others: your language pair(s), your location, and your specialisation. To ask for help with a translation even if you are a professional translator. To debate the quality of a translation, or compare different translations, literary or not. To talk about translating as a job, problems with clients etc To discuss anything translation-related, such as CAT, MT, theory, subtitling and so on To share interesting links, blogs and articles about translation Links to commercial websites and personal information (agencies, your curriculum.) will be removed. For translation requests please go to: /r/translator.
0 Comments
Leave a Reply. |