Usually, this error doesn’t prevent you from translating. Nevertheless, you can get rid of it.
First, let’s figure out what causes this error.
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.
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. Thus, a file with the name, for instance, Text_to_translate_asap.docx is transformed into the file Text_to_translate_asap.docx.sdlxliff.
By 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. Apparently, a Trados Studio file with the name Translate_right_now!.xlsx.sdlxliff is created from the Excel fileTranslate_right_now!.xlsx.
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. To perform this operation, Trados Studio has to store the source file somewhere.
If the source file is small, it is stored right inside the SDLXLIFF file. If it is big, Trados Studio remembers its location to return to it when needed later.
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:
It equals 20 MB by default. Looking ahead, we need to say that it’s worth increasing this value.
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. 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 Trados Studio gives out the “Dependency file not found” message, it means that it needs the original files, but it has “lost” them. That’s why it will wonder, “Would you like to browse for this file?”—i.e., ask for specifying the path to them.
It will be great if you have the original files. Then you say “Yes” to the question and just specify the path to them. The error disappears, Trados Studio calms down and proceeds with operation as usual.
If you don’t have the original files or if you decided not to specify the path to them, answer “No” as there is no other option actually. You’ll be able to keep working on the text, but some operations with files won’t be available (in particular, Save Target As, Preview, Generate Target Translations, etc.). In most cases, you won’t need them anyway.
Generally, this error doesn’t prevent you from continuing translating: you’ll be able to finish the translation, create the return package, and send the translation to the customer. Since the package was created on their computer, such a problem is not going to puzzle them.
But there are situations when Trados Studio refuses to work because of this error. In this case, the most important is to save the translation memory you’ve been using. It keeps all the segments you’ve translated if you had been confirming them while translating. You’ll be able to use them in the fixed Trados Studio package.
While opening certain packages, Trados Studio gives you a mysterious unsupported culture message, something like this:
In this case, there is only one thing clear about this message—it says that Trados Studio package can’t work with the Norwegian language (NO-NO is the code for Norwegian). But what does this language have to do with the package if it is English-Ukrainian translation?
This message appears because of the conflict between language identifiers of SDLXLIFF files and in the termbase connected to the package.
The only way to get rid of this error we know is to remove the ill-fated termbase. To do this, choose Project Settings > on the left panel choose Language Pairs > choose All Language Pairs > Termbases > unmark the term base check box > press ОК:
There is a simple way to extract .sdlxliff from Trados Studio package
Recently, we already discussed how to extract .xlf file from memoQ XLIFF File (.mqxlz). Users of Trados Studio often encounter the similar challenge: how to extract .sdlxliff bilingual file from Trados Studio package. The procedure is described below; it is even more simple.
1. Like .mqxlz, an .sdlxliff file is actually the renamed .zip archive. Add the .zip extension to it.
Inside, there are several folders. Two of them (if your package is bilingual) correspond to the source and target languages and are named according to the language codes. For example, if you translate from English into Ukrainian, your folders are named en-US and uk-UA. The .sdlxliff files you need are in the folder of your target language.
Note: This procedure is the same both for incoming and return Trados Studio packages. The only difference is in the fact that there is no translated text in the incoming package.