The new version of the manual expanded from pages for Studio , to pages for Studio , and now to pages has been updated to reflect the changes from Studio to Studio As previously, it comes in two version: a clean one and one in which the changes from the previous version are highlighted; this is very useful for those who want to skim through the manual to see what has been changed and added to the program.
The manual is sold for USD 49 Euro 38 to new users, and at a discounted price of USD 24 Euro 19 to those that are upgrading after buying a previous version of the manual. In any case, a reasonable price for a very useful resource. A suggestion I have for Mats is to consider publish future editions as a true e-book: this would be useful to the increasing number of people who use e-book readers and tablets, as it would then permit such features as increasing the font size as necessary.
You can purchase the full-price version of the manual from www. If you already purchased a previous version, you upgrade it from the Upgrade to page. The reason is that translators tend to download the package and then process its content while not connected to the Internet, which means that they cannot use any online resources.
You may decide to recompute the analysis statistics, if a translator only receives part of the files for a particular target language. Example: Your project contains 10 files to translate. There are repeated segments between files 1 and 7. However, the translator who receives this package will only get files 1 to 5, i. This means that for this package the cross-file repetition analysis for the whole set of 10 files will not be correct.
In this case, it makes sense to re-compute the analysis statistics, so that only the cross-file repetitions of the 5 package files are taken into account. Usually, the package contains the relevant project TM s , i.
You may want to re-create the project TM s when creating the package for similar reasons as the re-computation of the analysis statistics. Example: Let us assume again that your project contains 10 files to translate. When setting up the project you created a project TM that applies to those 10 files. However, the recipient of your package will only get the first 5 files, as you need to split up the job among two translators.
If you decide to re-create the project TM s , these will contain only the TUs that are relevant for the 5 files that are going to be included in your package. Through the ProjectTranslationMemoryPackageOptions class, you can select among the following options: CreateNew : Re-create the project TM s for the files of this particular package UseExisting : Simply include the project TM s that were created during the project set-up i. It may happen that the package creation fails for some reason e.
This is why you should check for any events during the project package creation, and output a message to the user if required. The following sample code leverages the PackageStatus class to check the project package status. Cancelling: case PackageStatus. InProgress: case PackageStatus. Scheduled: case PackageStatus.
Cancelled: case PackageStatus. Completed: case PackageStatus. Failed: case PackageStatus. Working With Projects. Code Examples. Creating a New Project. Creating a Project Package. Creating a Return Package. Importing a Return Package. Creating a Project Package When assigning tasks to e.
GetIds ;. Note After creating a package, the manual task will be shown in SDL Trados Studio as sent and assigned as illustrated in the screenshot below:. Configure the Project Package Options. Check the Project Package Creation Status. It throws an error message if in the end the package status is not Completed : C.
Putting it All Together. The complete functions should now look as shown below: C. See Also. Other Resources Creating a Return Package. Be the first to Edit the community content of this topic.
0コメント