trados studio 2017 how to close container quick insert window

But if the files have been moved or if the package is being sent to another computer, Trados Studio will have no access to them. If the work on the project is performed at the same computer where it has been created, no problems usually occur as Trados Studio knows where all original files are stored. Looking ahead, we need to say that it’s worth increasing this value. What file’s size is considered small and what is recognized as big is determined by the parameter in Trados Studio that is hidden here:įiles > Options > File Types > SDLXLIFF > General: If it is big, Trados Studio remembers its location to return to it when needed later. If the source file is small, it is stored right inside the SDLXLIFF file. To perform this operation, Trados Studio has to store the source file somewhere.

Once the translation is completed, you face a reverse task: you need to recreate the original file replacing the source text there with the translated one. This operation is called “Clean” and stands for cleaning the source text off the file. Apparently, a Trados Studio file with the name Translate_right_now!.xlsx.sdlxliff is created from the Excel file Translate_right_now!.xlsx. Thus, a file with the name, for instance, Text_to_translate_asap.docx is transformed into the file Text_to_translate_.īy the way, it means that with the file’s name you can reconstruct the name and type of the source file used for its creation very easily.

The name of the SDLXLIFF file is generated in the simplest way possible: by adding the SDLXLIFF extension to the name of the original file. When you create a package for translation in Trados Studio, each file you add to it gets converted into the SDLXLIFF format, and the translation is performed in this new file. First, let’s figure out what causes this error.

Trados studio 2017 how to close container quick insert window