Known issues
This section lists the limitations associated with the 2021 release of Trados Studio.
General known issues
- Trados Essential: Tasks not auto-accepted after revert
-
Trados Live Essential subscriptions offer a simple translation workflow for working with cloud projects. This workflow does not include a Review task, but enables you to revert any Completed tasks back to the Translation stage. Revert Translation tasks to make further changes to a completed translation, similarly to how you would update a translated file following a Review task.
With Trados Essential, Translation tasks are always assigned to you, and automatically accepted for you because you are the only user working on your project tasks. However, with this initial release you need to manually accept the new Translation task created automatically following the task reversal. To accept reverted tasks:
- from Trados Studio: double-click on a Completed task from the Files view and confirm that you want to revert the status and continue with the translation.
- from a browser: go to the Inbox tab > New, select the completed target file and click Accept. Accepted tasks show up in the Active tab from where you can open them in Studio or in the Online Editor.
- Placeables containing formatting tags are not identified correctly
-
Trados Studio detects any formatting differences inside numbers, dates and other placeables in the source text. These differences introduce formatting tags that split up the token, thus affecting match recognition and auto-localization.
Formatting differences inside placeables can occur especially with non-alphabetic languages, like Japanese. For these languages, text editors may apply mixed formatting to strings made up of language-specific character sets and alphanumeric letters.To work around this issue, check your source document for formatting differences inside the elements that Studio treats as placeables:
- Dates
- Times
- Numbers (in numerals)
- Measurements
- Acronyms and URLs
- Email addresses
- Alphanumeric strings
- Variables
- Currencies
- Previous Trados Studio versions do not fully support the new TQA category during TQA batch task
- Trados Studio 2021 introduces a new TQA category: Not Categorized. This default category in 2021 is not recognized in previous Trados Studio versions and is automatically converted to CategoryNotSet.
- Some UI elements not localized after switching language
- When choosing a different user interface language and restarting Trados Studio, some of the user interface elements may not show the new language as expected. When this happens, click to refresh the user interface and show all elements localized.
- The TQA window stays open the Editor view
- The TQA window reopens automatically after restarting the Editor view. Close the window manually until this issue will be fixed in a future release.
- Cannot select project templates while another project is being prepared
- You cannot select a new project template for your projects while Trados Studio prepares another project.
Save to Cloud limitations
- Save to Cloud does not support all project and package formats
- You cannot save the following to cloud:
- Saving project packages to cloud requires the native files to work correctly
-
To correctly save packages to the cloud, Trados Studio requires the native files of each target bilingual file. However, the native files may not be available if the package was created in Trados Studio 2021 SR1 and earlier, when source files that were too large to be included in the package were embedded in the .SDLXLIFF files or added as separate dependency files.
If the project package you are trying to save to cloud includes:Embedded files - you can save to cloud, preview and generate the target files. This is because Trados Studio 2021 SR2 automatically extracts the native files from embedded files.
Linked dependency files - you cannot preview or generate target files. The package can be saved to cloud only if the linked files are .docx, .pptx, .xlsx or .PDF 3.0.0.0 documents.
- Return packages must be created from the same instance of Trados Studio that saved the package to cloud
- When working with project packages saved to cloud, you can only create a return package from the same instance of Trados Studio that saved the package to cloud.
- Packages saved to cloud lose their attributes if they are removed from the project list
- If you remove a project package saved to cloud from the list, and then download it again, it will lose its project package attributes and become a cloud project instead.
- Cloud project settings take priority over local project settings
- When saving projects to cloud, cloud project settings take precedence over your local project settings. This means that your cloud project will use default cloud project settings. Support for specifying a cloud project template or saving your local project settings to cloud will become available in future updates. After the project has been saved to cloud, you can change project settings in the browser at any time and they will also be synchronized back to the Studio project.
- Translation Engine matches may overwrite existing confirmed segments
-
When you save a project to cloud that includes confirmed translations, the matches coming from your translation engine may overwrite any unlocked segments. To avoid this, lock translated segments that you want to keep before saving local projects or packages to cloud. For instance, if you use PerfectMatch, segments will be locked by default, and segment content will remain unchanged.
Alternatively, Trados Live Team and Trados Enterprise users can adjust the workflows used for saving projects to cloud, to exclude automated translation and translation memory matching as desired.
A future update to Trados Studio will give you more fine-grained control over this behavior.
- Reference files not imported with the cloud project package
- Any reference files included in offline cloud project packages are not visible when opening the package in Trados Studio.
Known issues for cloud projects
- Cannot run local batch tasks on remote cloud files
- You only run batch tasks on cloud files that are downloaded in Trados Studio and available on your computer. Open cloud files in the Editor view to bring them in Trados Studio where you can then run batch tasks locally.
- Local batch tasks do not check cloud translation engines
-
By design, running batch tasks on local projects will not do any lookups in cloud-based translation engines. Cloud engines are already applied during pre-processing and are not used again in any subsequent batch task that you run in Trados Studio.
This means, for instance, that the Analyze Files batch task will not reflect correct numbers if you run it from Trados Studio. Nor will the Pre-translate batch task apply any results from cloud-based translation memories, as this already happened in pre-processing.
As best practice, we recommend the following:
Use the new Save to Cloud functionality for local projects. This combines the best of both worlds: you can prepare the files locally and then move them easily to the cloud for running batch processing against translation engines and sharing all resources with your team.
For any projects that you wish to keep local, use the WIP Report, Translation or Word Count batch tasks in Trados Studio. These batch tasks can always be run locally and give you an accurate overview of the work required for your current file or the project as a whole.