A “Package”, sometimes referred to as a “Kit”, is the name given to a file produced by some Translation Tools that comprises of some or all of the following:
- Bilingual files for translation (SDLXLIFF, XLIFF, ITD, TTX for example)
- Any files as reference material (source files as PDF documents, image files, native versions of the source files, reference material etc.)
- Translation Memories (SDLTM, TMX for example)
- Termbases (SDLTB, TBX for example)
- AutoSuggest Dictionaries
- Analysis information and wordcounts
- Project metadata (due date, QA settings, filetype settings, custom quick inserts, etc.)
SDL Trados Studio 2011 can work with packages from many sources, but irrespective of where they come from the process for working with packages is the same. So this article is going to deal with a simple workflow to explain how best to handle a package in Studio. But first let’s look at where the packages could have come from:
You may have noticed I left SDL Trados Synergy off this list. Synergy uses the same package extensions as SDL TMS but Studio does not support them… so if you do get a package that has the extension *.stppk and you can’t open it then this may be the reason why. You’ll need SDL Trados Synergy to open that one. You can read more details on this subject here in the Studio online help.
If you are sent one of these supported packages to work with then the process is simple. First, you open the package up using “Open Package” which you can find in several locations in Studio. First of all it’s in the “Home View”:
It’s also in the Projects View:
And you can always open the Package from the File menu pretty much anywhere you like:
Once you have done this all the packages behave pretty much the same way… Studio extracts the contents and takes you into the Open Package dialogue like this (this one came from SDL TMS):
I can click on “Finish” here and I’m directed to a window where I decide where to put the Project. I’d recommend placing this into the default folder you use for all your Projects and then you’ll always know where they are… and you won’t have to remember to change the location every time you get a new package. You should then see this:
Now your Project is created and added to the Projects list. To see the files for translation you make sure the Project is active in the Projects View… so this means it should be bold. If it isn’t then right click it and set it as the active project:
Now all you do is select the Files View and the files in there will be the ones that were included in the Package and are part of the active project (double clicking a project in the Projects View will make it active and take you to the Files View at the same time):
In this view you can see the task came from Peter ProjectManager and you can also see the files for translation. In this case the native format was ITD as the package came from SDL TMS. To translate these files I simply double click them and they will open up in the Editor View. What I DO NOT DO, is use the Open Document command to select any of these files for translation. You can find an article here that explains what the Open Document command is for.
You may have been given these files for Review, or for Sign-Off as part of a controlled workflow, so in this case you can open the files in the appropriate mode by right-clicking on them and selecting the way you would like to work:
Opening in one of these modes and pressing Ctrl+Enter will confirm the segment with the appropriate status to each segment as you work. Once you have completed the tasks and are ready to hand the package back you need to create a return package. You can only create a return package based around the package you have received. So if you find that the command “Create Return Package” is greyed out it is because you either do not have the correct active project set, or you worked on the project files without using the project package as I described here. The most common mistake being the use of “Open Document” when translating the files resulting in several new projects within a project.
You can create the return package in a number of places… first of all from the Files View where you can select all, a few, or just one file for inclusion in the package. In this screenshot I have selected the two files that are 100% complete so I can send a partial delivery:
This allows the Project Manager to update the main project whilst I complete work on the rest of the files. I can still create more return packages later. I can also create the return package from the Project menu in all of the views and this will base the return package on all the files within the Project:
If you didn’t want all the files in the Return Package you can still deselect them at this stage:
You then follow the wizard clicking on next to specify the location for the Project Return Package and finally you are presented with the opportunity to open the target folder or send the package by email. So you choose the appropriate step to locate the package and return it to the Project Manager in the manner requested.
One interesting thing to note at this stage is that if you are handling WorldServer Packages then the creation of a Return Package will take you to this window where it looks as though the incorrect extension is being used… it says ….sdlrpx which is the Studio Return Package:
This is not a problem… the correct extension will be added when the package is created. So in this example if I look in the folder containing the return package I can see this:
It’s also worth noting that as long as Studio is installed then the Type column above will also help to identify the type of package. The WorldServer Package doesn’t distinguish between the original Package and the Return Package however there is a difference. If you add a .zip to the end of the filename and unzip the package you will find there are only the translated sdlxliff files in the return package. So if you find a TMX, settings files and a filetypes folder then this is the original WorldServer Package. If you find xlf files instead of sdlxliff then it’s just an old version of WorldServer.
On a final note… if you are handling Studio Packages you’ll find an excellent application on the OpenExchange called the Package Reader. This allows you to right-click on a Package and see what’s in there without having to open the package in Studio… in fact it shows you much more and is well worth taking a look. You can download the application from here and you can read about it in this article as I demonstrated the application as part of a tips and tricks session at the ATA this year… scroll down a little towards the end and you’ll find it.