Hi Adams, thanks for your comment. What we want to do is to be able to bypass having to create a new memory, whether anyTM or otherwise. Obviously, we can live with the workaround, but seeing as you can change the language variant (from en-US to en-GB, for instance, by editing the xliff in Wordpad or some other tool, for PM purposes, it would be convenient to be able to do the same thing to reverse the language direction.

The idea would be to produce a Studio TM from the original German-English XLIFF file, using the batch processing tool. Next, it is possible to use an existing TM the other way round, namely English to German: (prefixed "anyTM"), The Studio documentation exists for this. I presume you are seeking to "vet" the client's English translation for concordance with your original XLIFF and hence the TM that you would derive from it. You could then inject any variants or new material into the other-way-round TM, and hence into the XLIFF file, again using batch processing in Studio. You would obviously have to check the right options before running the batch processing: overwrite existing segments, or add new segments to the existing TM segments. HTH