Forum: SDL Trados support
Topic: Problems working with opened Project Package Trados 2011
Poster: Rossana Triaca
Post title: One of the most common issues with packages...
is that you and your client don't have the same Studio version (Service Packs included).
You won't be able to work with the package as is and deliver a return package, but you certainly can work directly with the .sdlxliff files and use all the termbases and TMs included. If your client is OK with receiving just the .sdlxliff files, you can:
1) Rename the package to .zip and extract it to access its contents.
2) Open the .sdlxliff files for the correct target language in Studio (take into account there are 2 sets of .sdlixliff files, and if you choose the incorrect one the next step won't work).
3) Link the Tms/Termbases.
4) Work as usual.
5) Save each file using the "Save as" option and choosing .sdlxliff.
For some packages, you will still get the "reference not set to an instance of an object" error when pressing enter to go to the next row, but you can circumvent this by simply using the down arrow (not sending to TM, etc.) and then globally changing the rows status to "Translated". Not ideal, but it works.
Check first if the client agrees with receiving just .sdlxliff files though...
p.s. Edited to add that it's a good idea to copy all the source segments to target, save the files and send the client these "test" .sdlxliff files to ensure they are able to open and process them on their end before beginning the translation.
[Edited at 2013-07-31 17:48 GMT]
Topic: Problems working with opened Project Package Trados 2011
Poster: Rossana Triaca
Post title: One of the most common issues with packages...
is that you and your client don't have the same Studio version (Service Packs included).
You won't be able to work with the package as is and deliver a return package, but you certainly can work directly with the .sdlxliff files and use all the termbases and TMs included. If your client is OK with receiving just the .sdlxliff files, you can:
1) Rename the package to .zip and extract it to access its contents.
2) Open the .sdlxliff files for the correct target language in Studio (take into account there are 2 sets of .sdlixliff files, and if you choose the incorrect one the next step won't work).
3) Link the Tms/Termbases.
4) Work as usual.
5) Save each file using the "Save as" option and choosing .sdlxliff.
For some packages, you will still get the "reference not set to an instance of an object" error when pressing enter to go to the next row, but you can circumvent this by simply using the down arrow (not sending to TM, etc.) and then globally changing the rows status to "Translated". Not ideal, but it works.
Check first if the client agrees with receiving just .sdlxliff files though...
p.s. Edited to add that it's a good idea to copy all the source segments to target, save the files and send the client these "test" .sdlxliff files to ensure they are able to open and process them on their end before beginning the translation.
[Edited at 2013-07-31 17:48 GMT]