Forum: SDL Trados support
Topic: Exception has been thrown by the target of an invocation
Poster: John Fossey
Post title: Workflow
Well, I agree the workflow may not be the best one. Unfortunately it was set by my client and the end user. If I had my 'druthers I'd skip the TTX altogether.
My agency client is one of the larger agencies, with offices worldwide, and they have to supply their client - the linguists branch of a national government department - with the DOCX and the TTX. Being government, the end user no doubt has no budget to upgrade to Studio. The agency pretranslated the TTX for me and provided both files. This is the workflow they use for a very substantial number of documents. And apparently it works for "everyone else" (as it worked for me the last time).
Of course, in Studio I am working in the SDLXLIFF file - the TTX is the interim target and the DOCX is the final target. But next time I will try your suggestion of attempting to produce a target DOCX from the pretranslated TTX before starting translation.
Actually, the main beef I have is the incomprehensible and meaningless (to me) error message. Software tends to "throw" errors, but most software catches error messages and displays them in some way that is meaningful to the user. I think Studio just displays the raw Java error message, which doesn't mean anything to anyone but a Java programmer (which I am not).
[Edited at 2013-07-31 22:33 GMT]
Topic: Exception has been thrown by the target of an invocation
Poster: John Fossey
Post title: Workflow
Well, I agree the workflow may not be the best one. Unfortunately it was set by my client and the end user. If I had my 'druthers I'd skip the TTX altogether.
My agency client is one of the larger agencies, with offices worldwide, and they have to supply their client - the linguists branch of a national government department - with the DOCX and the TTX. Being government, the end user no doubt has no budget to upgrade to Studio. The agency pretranslated the TTX for me and provided both files. This is the workflow they use for a very substantial number of documents. And apparently it works for "everyone else" (as it worked for me the last time).
Of course, in Studio I am working in the SDLXLIFF file - the TTX is the interim target and the DOCX is the final target. But next time I will try your suggestion of attempting to produce a target DOCX from the pretranslated TTX before starting translation.
Actually, the main beef I have is the incomprehensible and meaningless (to me) error message. Software tends to "throw" errors, but most software catches error messages and displays them in some way that is meaningful to the user. I think Studio just displays the raw Java error message, which doesn't mean anything to anyone but a Java programmer (which I am not).
[Edited at 2013-07-31 22:33 GMT]