- Release Notes v7.0
- 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
- System Management
- Project Management
- Projects
- Documents
- Reports
- Quality management
- The Filter Editor
- Partitioning
- 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
- Modes
- Customizing crossDesk
- Tasks in Across
- Comments
- Bookmarks
- Paragraph Numbering
- Sorting Paragraphs
- Context View/Source View
- crossTerm Window in crossDesk
- crossView
- Fuzzy search
- Concordance search
- crossSearch
- Spell-check and User Dictionary
- Pre-translations
- Store Translations Wizard
- The Target Editor
- Preview
- QM Check in crossDesk
- Search and Replace
- Correction
- Reviews
- Redelegation to the Translator
- Quick Translate
- Local Data in the Offline Client
- crossWAN
- TM Management
- Terminology Management
- Concept-Oriented Terminology System
- Definitions
- 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
- crossMining
- crossSearch
- Browser-based Work
- Editing of Special Formats
- Menus, Icons, and Keyboard Shortcuts
QM Check with Regular Expressions
Creation and Overview of Regex-Based Criteria
To create your own regex QM criteria, open the system settings, go to General > Quality Management v7.0 and click Configure Regex-based Criteria.
The following options are available:
Option | Description |
Add | Adds a new rule. |
Delete | Deletes the selected rule. |
Load Rules from QM Template | Enables the loading of rules contained in a QM template. During the import, it is checked whether identical rules or rules with identical names already exist You can decide whether to update rules with identical names or create separate rules. |
OK | Saves all changes and closes the window. |
Cancel | Discards all changes and closes the window. |
Help | Opens the context-sensitive Across help topic. |
RegEx Rules
The regex-based QM criteria are defined in the form of rules. A regex rule consists of at least one regular expression and a condition that determines where matches are to be searched for and what is to be reported.
The following conditions are available:
Option | Example (excerpt) |
Report if both source and target patterns match | To check URLs with a language-specific path (e.g. www.page.com/en), which is to be adapted in the target text |
Report if source matches, but target has a different number of matches | For no-break spaces in connection with measurement units, for version numbers |
Report if source matches, but target has fewer matches | For product names, company-specific IDs |
Report if target matches but not the source | For wrongly inserted placeholders and hotkeys in software localization |
Report if source matches but not the target | For placeholders and hotkeys that have been forgotten in software localization |
Report if source matches | To check paragraphs that contain certain IDs |
Report if target matches | To check unwanted number or date formats |
The name and error description of the rule will be displayed in crossDesk if there is a match for the criterion.
Example: No-break space in connection with measurement units
A rule that checks whether no-break spaces have been set in connection with measurement units in the target text (as in the source text) could look as follows:
Option | Details |
Condition | Report if source matches, but target has fewer matches |
Error description | Missing no-break space between number and unit symbol |
Source regex | (\d{1,3}[., ])*\d+[ ]?([mdchk]?[glmAWV][²³]?\b|[€$£元%°]) Activate the Case-sensitive option |
Target regex | (\d{1,3}[., ])*\d+[ ]([mdchk]?[glmAWV][²³]?\b|[€$£元%°]) Activate the Case-sensitive option |