Forum: SDL Trados support
Topic: Exception has been thrown by the target of an invocation
Poster: Rossana Triaca
Post title: Don't shoot the messenger...
Please bear in mind that I'm not a fan of Trados (in any of its incarnations), but I have to concede that a lot of these issues spring from misuse. I know this can rub you in the wrong way considering the tool has just failed you in a moment of need, but please believe me when I say that the following is meant with the best of intentions to help you in the long run:
[quote]I am just wrapping up a long project translating a TTX file, from a DOCX original. I have been translating the TTX and have to return the translated TTX and the target DOCX.[/quote]
If you're using Studio 2011, where did the .ttx file come from? Was it generated by the client? If this is the case, then it's really the wrong workflow to expect you to be able to clean it up, since this is many times completely impossible (even if you both use the exact same Trados version, including service packs and patches, and the exact same Word version, even then you cannot be certain this will work at all).
If it was you that generated the .ttx, how was it generated and why did you chose this format? With 2011 you should be using sldxliff files for all your projects, and if the client requests a .ttx you can generate one *after* completion and not to work with (also, this .ttx is mostly a reference file, an abstruse way to send a TM, and not a file that will actually clean up on their end).
Regardless of the format, the correct workflow should have been to create workfiles/import the files provided by the client, copy the source to the target, and export/clean-up the resulting files *prior* to begin translating, to ensure you were going to be able to deliver what they asked in the first place. This workflow would have detected any issues right away.
Mind you, I agree Trados is one of the most unfriendly pieces of software ever, and this catch-all generic message is so liberally used as to be rendered meaningless (if it was not obscurely worded already), but I think the issue here is that they cannot pinpoint the exact reason for the failure due to the workflow used.
We can of course debate on the reasonable assumption that with Trados you should be able to work with .ttx files seamlessly and that no compatibility issues should be expected, but... alas, that's marketing for you!
Topic: Exception has been thrown by the target of an invocation
Poster: Rossana Triaca
Post title: Don't shoot the messenger...
Please bear in mind that I'm not a fan of Trados (in any of its incarnations), but I have to concede that a lot of these issues spring from misuse. I know this can rub you in the wrong way considering the tool has just failed you in a moment of need, but please believe me when I say that the following is meant with the best of intentions to help you in the long run:
[quote]I am just wrapping up a long project translating a TTX file, from a DOCX original. I have been translating the TTX and have to return the translated TTX and the target DOCX.[/quote]
If you're using Studio 2011, where did the .ttx file come from? Was it generated by the client? If this is the case, then it's really the wrong workflow to expect you to be able to clean it up, since this is many times completely impossible (even if you both use the exact same Trados version, including service packs and patches, and the exact same Word version, even then you cannot be certain this will work at all).
If it was you that generated the .ttx, how was it generated and why did you chose this format? With 2011 you should be using sldxliff files for all your projects, and if the client requests a .ttx you can generate one *after* completion and not to work with (also, this .ttx is mostly a reference file, an abstruse way to send a TM, and not a file that will actually clean up on their end).
Regardless of the format, the correct workflow should have been to create workfiles/import the files provided by the client, copy the source to the target, and export/clean-up the resulting files *prior* to begin translating, to ensure you were going to be able to deliver what they asked in the first place. This workflow would have detected any issues right away.
Mind you, I agree Trados is one of the most unfriendly pieces of software ever, and this catch-all generic message is so liberally used as to be rendered meaningless (if it was not obscurely worded already), but I think the issue here is that they cannot pinpoint the exact reason for the failure due to the workflow used.
We can of course debate on the reasonable assumption that with Trados you should be able to work with .ttx files seamlessly and that no compatibility issues should be expected, but... alas, that's marketing for you!