| Source segments | Target segments | Error | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Select an error to inspect it here.
|
|||||||||||||||||||||||||||||||||||
| issueId: | accuracy |
| Description: | The target text does not accurately reflect the source text, allowing for any differences authorized by specifications. |
| Note: | Most cases of accuracy are addressed by one of the children subtypes listed above. In Machine Translation literature, this category is typically referred to as “Adequacy”. |
| Examples: | None |
| issueId: | mistranslation |
| Description: | The target content does not accurately represent the source content. |
| Note: | None |
| Examples: | A source text states that a medicine should not be administered in doses greater than 200 mg, but the translation states that it should be administered in doses greater than 200 mg (i.e., negation has been omitted). |
| issueId: | addition |
| Description: | The target text includes text not present in the source. |
| Note: | None |
| Examples: | A translation includes portions of another translation that were inadvertently pasted into the document. |
| issueId: | omission |
| Description: | Content is missing from the translation that is present in the source. |
| Note: | None |
| Examples: | A paragraph present in the source is missing in the translation. |
| issueId: | fluency |
| Description: | Errors related to the form or content of a text, irrespective of whether it is a translation or not |
| Note: | If an error can be detected only by comparing the source and target, it MUST NOT be categorized as fluency or any of its children. |
| Examples: | A text has errors in it that prevent it from being understood. |
| issueId: | grammar |
| Description: | Errors related to the grammar or syntax of the text, other than spelling and orthography |
| Note: | None |
| Examples: | An English text reads “The man was seeing the his wife.” |
| issueId: | punctuation |
| Description: | Punctuation is used incorrectly (for the locale or style). |
| Note: | In most cases it is not necessary to distinguish this error type from typography. |
| Examples: | An English text uses a semicolon where a comma should be used. A two-digit year reference begins with an open single quote instead of a close single quote (apostrophe). |
| issueId: | whitespace |
| Description: | Whitespace is used incorrectly. |
| Note: | None |
| Examples: | A document uses a string of space characters instead of tabs. Extra spaces are added at the start of a string. |
| issueId: | spelling |
| Description: | Errors related to spelling of words |
| Note: | None |
| Examples: | The German word Zustellung is spelled Zustetlugn. |
| issueId: | style |
| Description: | The text has stylistic problems. |
| Note: | None |
| Examples: | The translation of a light-hearted and humorous advertising campaign is in a serious and “heavy” style even though specifications said it should match the style of the source text. |
| issueId: | unidiomatic |
| Description: | The content is grammatical, but not idiomatic. |
| Note: | None |
| Examples: | The following text appears in an English translation of a German letter: “We thanked him with heart” where “with heart” is an understandable, but non-idiomatic rendering, better stated as “heartily”. |
| issueId: | awkward |
| Description: | A text is written with an awkward style. |
| Note: | None |
| Examples: | A text is written with many embedded clauses and an excessively wordy style. While the meaning can be understood, the text is very awkward and difficult to follow. |
| issueId: | company-style |
| Description: | The text violates company/organization-specific style guidelines. |
| Note: | None |
| Examples: | Company style states that passive sentences may not be used, but the text uses passive sentences. |