Dear SDL Community,

As I read elsewhere, this topic has been discussed over and over, but my question is more specific. Obviously there are ways to solve this issue, provided you have either the source file or an SDLXLIFF file in which the issue does not occur. In any case the client will be wondering at the very least why this pop-up occurs when he opens the delivered SDLXLIFF files, but I would like to know how the WorldServer deals with SDLXLIFF files featuring missing dependency files. If there are no error messages or any other negative consequences, we need no longer solve the issue in WorldServer packages, as long as you don't need to generate the target files yourself.

Kind regards,

Bart Van Maele