Very often, the translated text should follow the formatting of the source. The text formatting is defined by tags in bilingual files. That is why it is so important to check whether the target and source text contain the same tags.
This check detects:
- If the target segment contains tags different from the source ones.
- If the number of tags in source and target is not the same.
This check searches only in a translated text and reports incorrect spacing around opening and closing tags. It produces four types of errors:
- No space after end tag (a space after the closing tag is missing)
- No space before start tag (a space before the opening tag is missing)
- Spaces after start tag (a space after the opening tag is not needed)
- Spaces before end tag (a space before the closing tag is not needed)
This check compares spacing before and after a tag in source and target, and reports if it does not match.
|NB! The Spaces around tags and Inconsistent spaces around tags in source and target checks may report the same errors. Please keep this in mind when selecting both of them. You may find useful to check first spaces around tags in target are consistent with the source ones, and then check the correctness of spaces around opening and closing tags.|
Entities are fragments of code (e.g. &) that are not tags and are often found as special characters in browsers.
The check detects:
- If the target segment contains entities different from the source ones.
- If the number of entities in source and target is not the same.
This check detects segments where the order of tags in a source text and a translation is different.
|NB! Verifika highlights only the first error in the segment. A user must review all tags in a segment with one highlighted inconsistent tag.|