- Release Notes v7.0
- Getting Started
- System Management
- General Information
- Users
- Groups & User Crowds
- Softkeys
- Reports for User and Group Information
- User Settings Templates
- Workflows
- Relations
- Languages
- Fonts
- User settings
- System settings
- Editing States
- User Dictionary
- crossGrid
- crossGrid Packaging Templates
- crossTank
- crossWAN Packaging Templates
- Subjects
- Information
- Machine Translation
- Project Settings Templates
- Quality Management v6.3
- Quality Management v7.0
- Reporting
- Segmentation
- Language Settings
- Structure Attributes
- System Attributes
- Search Center
- Concordance Search Results
- Stopwords
- Term Extraction
- Document Settings
- Document Associations
- Display Text
- .NET Resources
- Excel 2000-2003
- Excel 2007-2016
- IDML
- MIF 7
- MIF 8-2019
- PowerPoint 2000-2003
- PowerPoint 2007-2016
- QuickSilver
- Tagged HTML
- Tagged SGML
- Tagged XML
- Tagged XML v2
- Visual XML
- Windows Resources
- Word 2000-2003
- Word 2007-2016
- XLIFF
- Regular expressions
- System attributes
- Project Management
- Projects
- Project View
- Project settings
- Functions of the Module
- Project Search
- Project creation
- Adding attachements
- Releasing Projects
- Document and Project Updates
- Project status
- Exporting projects
- Importing projects
- Activating/Deactivating Projects
- Duplicating Projects
- Archiving Projects
- Change workflow
- Changing Workflows (Several Documents)
- Documents
- Reports
- Tasks
- Quality management
- Formats
- The Project Archive
- crossGrid
- Project Management Cockpit
- The Filter Editor
- crossAnalytics
- Linguistic Supply Chain Management (LSCM)
- crossWAN Project Management
- Partitioning
- Relay Translations
- Document preparation
- Term Extraction and Term Translation
- External Editing of Documents
- The EN 15038 Standard Workflow
- The ISO 17100 Standard Workflow
- crossConnect for External Editing
- Finishing pre-translated tasks automatically
- Projects
- 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
General QM Criteria (QM v6.3)
Date, Time, and Number Format
Checks whether the date, time and number formats have been translated correctly and adapted to the target language (according to the settings under Tools > System Settings > General > Language Settings).
Example
In this example, the date "2016-12-24" has been identified as a valid English date format. However, the translation "24/12/2016" does not correspond to the settings for the German date format (see below). Therefore, the QM criterion indicates an error:
For German, the language settings require the date format DD.MM.YYYY, e.g. "30.04.2014":
The criterion can only identify errors in the translation if Across recognizes the particular date, time, or number in the source text as such. For these data to be recognized, they must have a valid format in the source text.
For example, a date correctly recognized by Across is evident from the blue overline.
The following example shows an English source text containing a date.
Example
The date was recognized as a valid date format, as it corresponds to one of the specifications for English dates (YYYY-MM-DD) in the language settings. | In contrast, the following date was not recognized as a valid date format, as it does not correspond to any of the two specifications for English dates (YYYY-MM-DD or MM/DD/YYYY) in the language settings. |
The tooltip of a data, time, or number shows what format the information was recognized as and what the corresponding information looks like in the target language:
Formatting Order
Compares whether all formatting (such as boldface and italics) used in the source document has been used in the translation in the same order.
Example
In this example, the boldface and italics formatting was not used in the same order in the source text and in the translation. Therefore, the QM criterion indicates an error:
Formatting Usage
Compares whether all formatting (such as boldface and italics) used in the source document has been used in the translation. Only the existence of all format styles is checked, not the order of use. This is checked via the QM criterion Formatting Order (see above).
Example
In this example, the italic formatting of the address has not been used in the translation. Therefore, the QM criterion indicates an error:
To quickly and easily identify various formatting settings in the source text, you can use the contrast formatting function. To enable the contrasting formatting, click the icon in the crossDesk toolbar. This will highlight different formatting settings in the active source and target-language paragraph in color. In this way, you can easily identify any formatting errors and correct them.
Same Source – Different Translation
Checks whether identical source-text segments have been translated differently.
If you click an error reported by this QM criterion, Across will filter the paragraph view so that only the affected paragraphs are displayed. The filter will be reset e.g. when you click another QM criterion.
Identical Segments
Checks whether the segments are identical in the source and target documents. Discrepancies often indicate that one or several segments have not been translated. The criterion only takes paragraphs containing text to be translated into consideration. For example, paragraphs only containing placeables are not checked.
Example
In this example, the source-language paragraph was mistakenly inserted in the translation. Therefore, the QM criterion indicates an error:
No Match Placeholder
Comprises all paragraphs containing the pre-translation placeholder ##NO_MATCH##. at least once. Thus, this criterion prevents the translator from forgetting to replace the placeholder with the respective translation.
- The placeholder is inserted in a paragraph
- if the option Insert placeholders when not all segments can be pre-translated is activated under Tools > System Settings > General > crossTank >Pre-translation and
- if crossTank does not contain 100% matches for every sentence of the paragraph.
Example
In this example, the pre-translation placeholder is contained in the current paragraph. Therefore, the QM criterion indicates an error:
Consistent Capitalization
Checks whether the uppercase/lowercase spelling of the first word of a translated paragraph corresponds to that of the first word of the source paragraph. If, for example, the first word in a source paragraph starts with a lowercase letter, but the first word in the translated paragraph starts with an uppercase letter, the QM criterion will indicate an error in the QM tab of crossView.
Example
"Https" was capitalized in the translation but not in the source text. Therefore, the QM criterion indicates an error:
Identical brackets
Checks whether the number and type of brackets used are identical in the source and target documents. The criterion takes into consideration the following brackets: (), [], {}, and <>. The sequence of the brackets in the translation is not checked, as it may differ from the source text.
Empty Translation
Checks target paragraphs for missing translations. If an empty paragraph has been set to touched or translated, the QM criterion will indicate an error.
Any target paragraphs that are left empty will also remain empty in the checked-out document. A paragraph reported as an error might have been left empty on purpose. Check whether the reported errors need to be corrected or can be ignored.
Placeables Formatting
In crossDesk, parts of XML documents that are processed with Visual XML can be displayed as placeables, i.e. gray fields that are not translated but only inserted in the target text. This is helpful to prevent elements like product names that must not be changed in the target text from being changed in the first place. Some placeables may be assigned a style (e.g. bold type). The QM criterion Placeables formatting verifies whether all placeables are formatted correctly.
Example
The following excerpt of an XML file contains the <code> tag whose content (the word Across) is to be displayed as a placeable in crossDesk. Additionally, the <b> tag formats the word "Across" in bold type:
In crossDesk, the content of the tag <code> is presented as placeable ("code") according to the specifications. Additionally, the placeable is formatted in bold type. In the translation, however, the placeable is formatted in normal type, not in bold type. Therefore, the QM criterion indicates an error:
Placeables Order
Checks whether the number and the sequence of utilized (green and gray) field and/or tag types correspond in the source and target documents.
The criterion merely checks the number and order of the fields used and does not consider factors such as the position of text that may exist between the fields.
Example 1
In this example, the number of fields is identical in the source and target-text paragraphs, but two fields have been switched. Therefore, the QM criterion indicates an error:
Example 2
In the following example, the number and order of the tags are correct in the source and target texts – only the text is located in different places. Therefore, the criterion does not report any error:
Placeables Usage
Checks whether the number of (green and gray) fields and/or tags used in the source and target documents is identical.
Example
In this case, the source-language paragraph contains three gray fields, but the target-language paragraph contains only two. Therefore, the QM criterion indicates an error:
Segments Count
Check whether the number of segments (sentences) is the same in source and target text.
Example 1
In this first example, the source-text paragraph consists of two segments, but the translated paragraph consists of only one segment, as the translation of the second source segment has obviously been forgotten. Therefore, the QM criterion indicates an error:
Example 2
In the second example, the source-text paragraph again consists of two segments, but the translated paragraph consists of only one segment. Thus, the QM criterion indicates an error. However, this is not justified in this case, as the translation is complete and the two segments of the source text are rendered in only one segment in the translation:
To correct the error, expand the first source-text segment by an additional segment by clicking the icon in the toolbar of the Source View.
Terminology
The Terminology QM criterion verifies whether the source-language terms (source terms) in the source text have been duly translated with the corresponding target-language terms (target terms).
The function of the crossTerm check can be customized as needed. By default, the crossTerm check verifies whether any existing target-language terms in crossTerm were used to translate the terms in the source paragraph. If a target-language term was not used, the criterion reports an error for the respective paragraph.
However, the crossTerm check can also be customized for more specific checks. For example, the translation can be checked for the use of forbidden terms. The crossTerm check can be configured under Tools > System Settings > General > Quality Management v6.3.
Example 1
This first example assumes that the crossTerm check is used with the default settings:
The source paragraph contains the expression "terminology system", which is stored as a term in crossTerm. At the same time, three target-language translations ("Terminologiesystem", "Terminologie-System", and "Term-System") have been set up in crossTerm for the term. However, none of these entries has been used in the translation. Therefore, the crossTerm check indicates an error:
Example 2
In the second example below, the settings for the crossTerm check have been customized. All source-language terms except the do-not-use terms are to be checked. Moreover, only "recommended" terms (i.e. terms with the attribute Standard) are to be accepted as target-language translations:
The source paragraph again contains the expression "terminology system", which is stored as a term in crossTerm and is labeled as "recommended" (). Thus, the crossTerm check takes this term into consideration. At the same time, crossTerm contains a target-language translation labeled as "recommended" ("Terminologiesystem"). However, the translation contains a target-language term ("Term-System") not labeled as "recommended". Therefore, the crossTerm check indicates an error:
Example 3
The third example assumes the same settings and conditions as in example 2. However, the recommended target-language term "Terminologiesystem" has been used instead of "Term-System". Therefore, the crossTerm check does not indicate any error:
Different Source – Same Translation
Checks whether different source-text segments have the same translation. If you click an error reported by this QM criterion, Across will filter the paragraph view so that only the affected paragraphs are displayed. The filter will be reset e.g. when you click another QM criterion.