Project Settings Templates: crossTank > crossTank Storing Settings
The crossTank Storing settings section comprises settings that determine the behavior of Across when storing translation units in crossTank.
Please note that the storing settings affect every kind of storing of translation units in crossTank. For example, they affect the storing of translation units both in crossDesk and in the crossTank Manager (e.g. when importing a TMX file).
Translation Units Saving Mode Section
Here you configure when translations are transmitted to crossTank for storage. The following options are available:
Option | Description |
Not enabled | No storing action is performed when a paragraph is set to the final paragraph state (e.g. Translated). You need to store the translation units manually with the Store Translations Wizard, which you can open as follows:
|
Semi-automatic storing | The Sentence Alignment dialog is displayed when a paragraph is set to the final paragraph state (e.g. Translated). Align the sentences and click Save Paragraph in order to save the translation unit to crossTank. |
Automatic storing | When a paragraph is set to the final paragraph state (e.g. Translated), the translation unit is stored to crossTank under consideration of the following two options:
|
Store only at target state | If this checkbox is not activated, translations will be stored to crossTank even if they have not reached the final paragraph state, namely when you go to another paragraph. If the checkbox is activated, the storing will take place as soon as the paragraph is set to the final paragraph state. |
Automatic Storing of Attributes Section
You can specify whether while storing crossTank entries, the information on the project, relation, subject, and user-defined attributes is added to the entries, or whether the entries should remain free of this information, rendering them "neutral" and thus independent of project, relation, subject, and other user-defined attributes.
Storing Settings Section
By means of the option Multi-attribute update mode, you can determine the behavior when adding new attribute values to existing crossTank entries. For example, this may be the case when importing identical crossTank entries with different attribute values or when using a crossTank entry whose attributes differ from those of the project in a translation in crossDesk.
The new and old attribute values can be merged, the old values can be overwritten with the new attribute values, or the new attribute values can be discarded.
The option will only be effective if all attributes are defined as multiple-value attributes, i.e. attributes, for which several attribute values can be determined. The option requires that the underlying option for avoiding multiple translations is activated.
Example
The following example explains how this option works:
If, for example, a crossTank entry belongs to the subject "Business" and the current translation belongs to the subject "Finance", the different settings of the option will result in the following behavior when transferring the crossTank entry to the translation (and when subsequently storing it):
Setting | Effect |
Merge multi-attribute values | The new subject "Finance" is added to the subject "Business". Thus, the crossTank entry will henceforth belong to the "Business" and "Finance" subjects. |
Overwrite multi-attribute values | The subject "Business" is overwritten with the new subject "Finance". Thus, the crossTank entry will henceforth belong to the "Finance" subject. |
Skip multi-attribute values | The new subject "Finance" is discarded. Thus, the crossTank entry will still belong to the "Business" subject. |
Multiple translations
The multiple storage of translation units, e.g. through successive translation and correction of a text or through TMX import of translation units, can lead to unwanted redundancies in crossTank. To prevent this from happening, you can select how to proceed when new translations are added to existing ones. Enable the Prevent multiple translations by overwriting existing entries with new ones checkbox to prevent multiple translations from being stored for one source segment. The existing translation is then overwritten and replaced by the new one. Disabling this option allows the storage of multiple translations: Theoretically, an unlimited number of translations can be stored for each source segment.
When you enable the checkbox, you can also select how to proceed when adding a new translation to one that is already stored in crossTank. You can specify which entries of the existing translations should be overwritten and be replaced by your new translations.
Option | Description |
Overwrite all entries | For all entries, replace the existing translations with your own new translations. |
Overwrite all my own entries | Replace existing translations only if these translations are your own translations. |
Overwrite all unreleased entries | For all unreleased entries, replace the existing translations with your own new translations. |
Overwrite only my own unreleased entries | Replace existing translations only if these translations are your own non-approved translations. |
Skip all entries | Storing should always be skipped. The previous translation should never be overwritten by the new translation. |
Skip released entries | Skip storage only for released entries. |
Skip released entries with identical translation | Skip storage only for released entries with identical translation. In this case, a released translation can overwrite another released translation. |
Please note that if you decide not to store multiple translations, multiple translations will also be prevented when importing TMX files or crossWAN and crossGrid packages – even if these files or packages contain multiple translations.
Rich Translation Memory Section
You can define how rich content is to be stored in crossTank. You can define the storing method separately for formatting, inline objects, and special characters.
- Special characters in Across are all characters that do not belong to the following characters:
- Language characters (alphabetic characters, ideographic characters, and syllabic characters)
- Punctuation Marks
- Decimal or hexadecimal digits
Special characters include white spaces (e.g. normal and no-break spaces), control characters (e.g. line feed, horizontal and vertical tab), arrow symbols, Braille characters, and mathematical operators. A list of all special characters is available at Across special characters.