This check group detects incorrect use of punctuation marks and spaces.
This check detects segments that contain several consecutive spaces and produces two groups of errors:
- Multiple spaces in succession. It recognizes all types of spaces (regular, non-breaking, etc.).
- Multiple spaces with tags between them. It reports segments where multiple spaces are separated by tags. However, be careful, as sometimes such spaces may be necessary before and after the tag.
The check has the following option:
- Ignore source formatting. To keep the source formatting, the translator puts spaces in the translation just as they are in the source text. However, such an approach sometimes can transfer errors from source to target. Therefore, you can enable this option to detect such errors. When this option is off, multiple spaces found in both source and target will not produce an error.
This check looks for segments with different punctuation marks at the end of the source and target segments. It produces four groups of errors:
- No end punctuation in source. When a translation contains a punctuation missing in a source text.
- No end punctuation in target. When a translation is missing a punctuation found in a source text.
- Inconsistent end punctuation in source and target. When punctuation marks in a source and a translation are different.
- Wrong end punctuation. As you know, such languages as Chinese, Armenian, etc. have their own punctuation marks (e.g. in the Thai language, use of punctuation is not recommended at all). So, this error group contains segments where punctuation marks do not belong to a target language.
This check has the following option:
- Ignore quotation marks and brackets. With this checkbox enabled, Verifika checks a text as if it does not contain any quotation marks and/or brackets. It allows the exclusion of cases where a full stop in the source text is located within the brackets but is outside of them in the translation.
This check detects double consecutive punctuation marks. The report will include errors such as repetitive colons, commas, full stops, etc. However, Verifika does not consider different consecutive punctuation marks to be an error, nor the three dots which are often used instead of an ellipsis.
There are situations when two punctuation marks follow each other according to the source text and are not an error. To exclude these cases from the report, enable the As in source setting.
The check detects incorrect spacing around punctuation marks. Spacing rules can be quite different for some languages (e.g. French). You can specify rules under Punctuation by adding the punctuation mark you want to the respective fields. For example, to check spaces around a full stop, add its symbol to:
- Space after
- No space before
You do not need to separate other punctuation marks in a field, just enter them one by one.
|NB! The setting is language-specific. If you have more than one translation language in your project, do not forget to set up these rules for each one of them.|
Verifika will check the spacing of all punctuation marks that you specify in the table and produce the following groups of errors:
- Invalid spacing after punctuation
- Invalid spacing before punctuation
- No space after punctuation
- No space before punctuation
- Non-breaking space required after punctuation
- Non-breaking space required before punctuation
This check works the same as the previous one, producing similar groups of errors. The difference is that it checks spaces around signs as trademarks, copyrights, percentage sign, etc. The rules for the spaces are set up under Special signs on the right.
|NB! At the moment, the check detects spacing errors only between special signs and text (digits excluded). However, we are working on a solution to check combination of any characters and hope that soon we will come up with one. Meanwhile, if you need to check spacing between special signs and digits, you can use Search or create a User-defined check as a temporary substitution for the missing part of this check.|
This check detects segments that start or end with a space. It reports an error even if the source has spaces at the end or at the beginning of a segment, i.e. the translation follows the source spacing. It produces two groups of errors respectively:
- Start spaces
- End spaces
The check has the following setting:
- As in source. Enable this to detect only segments with inconsistent spacing in source and target and exclude segments where the leading and trailing spaces are located exactly as in the source text.
This check detects segments that contain an opening bracket but do not contain a closing one, and vice versa. It respects nesting rules, i.e. the first closing bracket in a sequence has to match the last opening one. So, if a bracket has its pair but is incorrectly nested (e.g. “([)]”), it will also be reported as an error in the Unmatched bracket error group.
The check has the following settings:
- Ignore “more than” and “less than” signs. If there are inequality signs in your project, check this box to avoid reporting them as a non-matching bracket. Please note that all these signs will be ignored, even if they are used as brackets.
- Ignore if brackets are unmatched in source. Sometimes text in brackets can be split into several segments, and an unmatched bracket is not an error in this case. So, you can enable this option to avoid reporting segments where both source and target contain an unmatched bracket.
To get a visual overview of how the check works, please watch the Punctuation ans spacing video.