Protecting Translation Units
Important Information on Protecting Translation Units
- Before you use the function to protect translation units, check the current use of the Released status in your crossTank database entries. For example, you can create a crossTank summary and use Status as the selected field. If you also select the Language field, the language combinations in which crossTank entries are available will also be shown for each crossTank status.
You can also search exclusively for released crossTank entries by using the quick filter Status with the search option Released in the crossTank Manager.
- To check how any released crossTank entries have come about, you can check whether the option Automatically set crossTank entries to released, which is deactivated by default, has been activated in the task properties of the workflows. If possible, this should be done in all tasks of the various workflows.
If the option is activated, we recommend contacting our Consulting team in view of the possible implications.
- In addition, you need to consider which user groups should have the right to process released entries.
- We recommend using the protection of translations in combination with sentence splitting of paragraphs. In this way, you can ensure that pre-translations are inserted and protected even if a paragraph consists of more than one sentence and a released 100% match does not exist for all sentences.
A possible procedure to introduce the function to protect translation units could be as follows: Set all previously released crossTank entries to Newly inserted and successively set the crossTank entries that you would like to protect (i.e. entries that are suitable for virtually all contexts) to Released. For example, you can do this with the crossTank Maintenance Wizard: Select the action Change attributes and define a filter with the field Status, condition equal to, and value Released. In the next wizard step, activate the option Set new status value and select Newly inserted as the new status.
Before you modify your crossTank data with the crossTank Maintenance Wizard, we recommend backing up the crossTank database. Moreover, carefully review the possible consequences before applying the changes, e.g. by making the changes on a test system first.
Depending on the size of the crossTank database, mass operations may take up to several hours. Therefore, mass operations should, if possible, take place at times when Across is not subject to a high workload and should be performed directly on the computer on which the Across Server is installed.
To execute the action, you need to add at least one action in the top area. You can use an attribute value that you do not use otherwise in Across (e.g. a value of a structure attribute), which you can add and immediately delete.
Subsequently, execute the action Change attributes.
For further information, please consult your contact at Across Systems GmbH.
General information on Across services is available at www.across.net/en/services/.