Yes. Thanks. It's no great hassle, of course, but I wonded if CT did it automatically as Metatexis does.
I just had a look at the xml part of a translated Word file, and it does show the target language:
<w:lang w:val="nl-NL"/></w:rPr><w:t xml:space="preserve">De nieuwe op cadmiumselenide gebaseerde kwantumpuntmonitoren van Philips vormen een belangrijke doorbraak voor de EU voor concurrentievermogen, milieubescherming en energie-efficiëntie
So my remark above - As far as I know, the target language code is not embedded in the document - is utter nonsense (again). Don't know what's going on here.
The source language in the source document has to be set in order to let CafeTran set the target language in the target document.
If by that you mean was the source and target languages set when I imported the original files then they were indeed set.
I had no problem with the long file I did a week ago, but these short ones all failed to transfer the change of language to the target text exported from CT.
I'm not sure I understand completely what you mean, but what happens is this:
Does CT not define the exported file as now being in the target language?
When I recently exported three short texts to Word to finally review before submitting, I had to reconfigure the documents to tell Word they were in English. I would have thought CafeTran would have already done that as part of the exporting process. Doesn't it?