- Installation and Administration
- About Across Translator Edition
- Installation of the Across Translator Edition
- Connection to Across Account
- Activation of the Across Translator Edition
- Functions of the Across Translator Edition
- Data Synchronization/Migration of the Across Translator Edition
- Backing up Data of the Translator Edition
- Restoring Translator Edition Backups
- Uninstalling the Across Translator Edition
- Getting Started
- Structure and Architecture
- Basic Decisions
- Logging in
- Change username/password
- Confirming and Opening Tasks
- Internal Communication
- Rights System: Default Settings
- System Management
- User settings
- System settings
- System attributes
- Project Management
- Quality management
- QM Criteria
- SGML, XML, and XLIFF (QM v6.3)
- Windows Resources (QM v6.3)
- .NET Resources (QM v6.3)
- Display Text (QM v6.3)
- QM Templates (v7.0)
- Date/Time/Numbers (QM v7.0)
- Display Text (QM v7.0)
- Formatting (QM v7.0)
- Spacing and Whitespaces (QM v7.0)
- Placeables (QM v7.0)
- Private Use Area Characters (QM v7.0)
- Spell-Check (QM v7.0)
- Punctuation (QM v7.0)
- Use of Terminology (QM v7.0)
- Use of TM (QM v7.0)
- Translation Consistency (QM v7.0)
- XML (QM v7.0)
- QM criterion for .NET resources (QM v7.0)
- QM criterion for Windows resources (QM v7.0)
- QM Criteria
- The Filter Editor
- Relay Translations
- Document preparation
- Term Extraction and Term Translation
- External Editing of Documents
- The EN 15038 Standard Workflow
- The ISO 17100 Standard Workflow
- Cost Estimates
- Task Processing
- Working in crossDesk
- Paragraph States
- Empty Paragraphs
- Customizing crossDesk
- Tasks in Across
- Paragraph Numbering
- Sorting Paragraphs
- Context View/Source View
- crossTerm Window in crossDesk
- Fuzzy search
- Concordance search
- Spell-check and User Dictionary
- Store Translations Wizard
- The Target Editor
- QM Check in crossDesk
- Search and Replace
- Redelegation to the Translator
- Quick Translate
- Local Data in the Offline Client
- TM Management
- The crossTank Manager
- Adding Translations
- Editing Translations
- Changing the Status of Translations
- Merging Translations
- Deleting Translations
- Protecting Translations
- Searching for Translations
- Generating a crossTank Summary
- crossTank Import
- crossTank Export
- crossTank Maintenance
- Terminology Management
- Concept-Oriented Terminology System
- The crossTerm Manager
- crossTerm settings
- crossTerm Manager User Interface
- Searching for Entries/Terms
- Entry and term elements
- Editing Entries/Terms
- Delete Entries/Term(s)
- Merging Entries
- Duplicating Entries
- Manual correction
- crossTerm Reports
- crossTerm Import
- crossTerm Export
- crossTerm Data Maintenance
- crossTerm Web
- Browser-based Work
- Editing of Special Formats
- HTML Documents
- XML Documents
- SGML Documents
- FrameMaker Documents
- Word Documents
- TXT Documents
- Excel Documents
- PowerPoint documents
- InDesign and InCopy Documents
- QuickSilver documents
- PO Documents
- MC Documents
- XLIFF Documents
- Software Localization
- Localization of mobile apps
- Localizing Display Texts
- Menus, Icons, and Keyboard Shortcuts
Project Settings Templates: crossTank > Pre-Translation
In the Pre-Translation section, you can now determine the match rate for pre-translations. You therefore specify the percentage of matches from which matches are taken into account for pre-translations and displayed accordingly in the pre-translation overview. Regardless of the selected match rate, only 100% matches will be inserted in the target text during pre-translation.
Please note that the selected match rate will also affect the reporting. Only matches above the selected match rate will be displayed in the Across reports.
Additionally, you can grant bonus points for the prioritization of 100% matches.
- You can grant bonus points for the following types of 100% matches:
- For perfect matches (100% matches that correspond to the current segment without any auto-adjustments by Across)
- For 100% matches with the Released status
- For context matches
- For structure matches
- For matches with length restriction
The bonus points serve the prioritization of matches in case several 100% matches exist for one segment. During pre-translation, the match with the highest number of bonus points will be inserted in the translation.
If there are several 100% matches, the bonus points will also be displayed in the fuzzy search of the Search Center. The 100% match with the highest number of bonus points will always be displayed first.
The bonus points are added up. For example, for a match with the Released status (e.g. 1 bonus point) that is also a context match (e.g. 2 bonus points), the bonus points are added up (in this case: 1 + 2 = 3 bonus points).
For pre-translations, you can also determine that 100% matches are to be inserted even if there are several 100% matches (without bonus points) for a sentence or if there are several 100% matches with the same number of bonus points. In this case, the 100% match that was last modified will be inserted automatically.
Normally, existing 100% matches are not inserted in paragraphs containing more than one sentence if the crossTank does not contain 100% matches for all sentences. If you want the 100% matches to be inserted in the translation nevertheless, activate the option Insert placeholders when not all segments can be pre-translated. The placeholder ##NO_MATCH## will thus be inserted in the translation for every segment for which there is no 100% match. Thus, you can ensure that all 100% matches available for a document are inserted without additional user interaction.
All paragraphs in which at least one placeholder was inserted are systematically recorded by the QM criterion No match placeholder and displayed separately in the QM tab in crossView. In this way, you can systematically process all affected paragraphs.
Skip QM check for pre-translated paragraphs
If you activate the checkbox, the QM criteria will not be checked for pre-translated paragraphs. Among other things, this accelerates the document check-in.
In addition to the normal matching of a segment with crossTank with respect to the content and style during pre-translation, this feature also takes the preceding sentence and the subsequent sentence into consideration. For this purpose, Across stores the context for each translation unit on the basis of the IDs of the preceding sentence and the subsequent segment.
During pre-translation, structure matches also take structure attributes into consideration, in addition to the normal matching of a segment with crossTank with respect to the content and style. Structure attributes indicate which area of a document a segment comes from. A structure match is a match for which not only the properties of a normal 100% match but also the structure attribute corresponds.
Context & structure
If a match is a context match as well as a structure match, it is referred to as context and structure match.
Protecting Pre-translated Paragraphs
Another option also allows paragraphs pre-translated with released crossTank entries to be locked, thereby preventing them from being edited.
Before you use the option to protect pre-translated paragraphs, check the current use of the Released status in your crossTank database. Search exclusively for released crossTank entries by using the quick filter Status with the search option Released in the crossTank Manager.
During pre-translation, the pre-translated paragraphs are automatically set to the final paragraph state of the underlying workflow. For example, this would be the Corrected editing state for the Translation and Correction workflow.
Final Paragraph State for Pre-Translated Paragraphs
You can choose whether and in which case pre-translated paragraphs should be assigned the final paragraph state (e.g. Translated).
- You can choose:
- You can determine that pre-translated paragraphs should never be set to the final paragraph state. In this case, the pre-translated paragraphs will be set to the editing state (e.g. Touched).
- You can determine that pre-translated paragraphs should always be set to the final paragraph state.
- You can determine that pre-translated paragraphs should be set to the final paragraph state depending on the type of 100% match available for the pre-translation. In this case, you can determine that the final paragraph state is to be set if
- a structure match,
- a context match,
- a context match or a structure match, or
- a context and structure match is on hand.
If you use the option for protecting paragraphs pre-translated with released crossTank entries (see above), this option does not have effect on the released crossTank entries. Paragraphs pre-translated with released crossTank entries are automatically set to the final paragraph state of the underlying workflow.
For pre-translations performed from within crossDesk, the final paragraph state of the task currently opened in crossDesk will be set.
In contrast, for pre-translations performed from within the Projects or Tasks module, the final paragraph state of the underlying workflow will be set (not the editing state of the current task of the workflow). For the Translation and Correction workflow, the pre-translated paragraphs will be set to Corrected. These pre-translated paragraphs will be locked for processing for upstream tasks (e.g. translation).
If you determine that the final paragraph state of the task is to be set, you should activate the option for saving the translations to crossTank when finishing the respective task. In this way, the attributes of the current task (e.g. Subject and Relation) will be added to the translations (if the options for saving the attributes are activated under Tools > System Settings > General > Project Settings Templates > General > Project Settings Templates > crossTank > Storing Settings).