| |
Import with user interaction | All translation units will be imported. In the case of translation units that are not clear, you as the user can decide what is to be done. |
Import without user interaction | All ambiguous translation units that would require interaction (e.g., translation units with different numbers of segments) are saved to a separate TMX file. This file can later be imported separately. This mode is especially recommended for extensive TMX imports. |
| Across will try to adjust crossTank entries with respect to placeables, formatting, and tags, in which e.g. only a placeable is different. These entries will not be stored as two crossTank entries but only as one crossTank entry. |
Import crossTank entries with sentence segmentation | - For translation units containing the same number of sentences in the source and target segments (e.g., 2 sentences each in the source and target segments), you can determine that:
- The sentences should be treated as a perfect match, meaning that the individual sentences from the source and target segment are put together as sentence pairs (e.g., sentence 1 of the source segment with sentence 1 of the target segment, sentence 2 of the source segment with sentence 2 of the target segment, etc.) and saved as separate translation units.
- during the import process a dialog box will appear in which manual corrections can be made to the respective translation unit.
- the sentences are merged to one segment.
- the translation unit is discarded and is not transferred to crossTank.
- For translation units containing a different number of sentences in the source and target segments (e.g., 2 sentences in the source segment and 1 sentence in the target segment), you can determine that:
- during the import process a dialog box will appear in which manual corrections can be made to the respective translation unit.
- the sentences are merged to one segment.
- the translation unit is discarded and is not transferred to crossTank.
|