Whether the issue comes up as Note, Warning or Error, once the verification report is complete, it usually gives us a good idea about the gravity, but not always. Luckily, not only can you define what Studio should be checking the translation for, but you can also set different levels of severity to the errors picked up (Project Settings > Verification > Tag Verifier > Common). Let’s look at a few examples where you might find some fine-tuning useful to differentiate between serious errors and potential issues in the files you work with.
- Ghost tags: When either the opening or the closing part of the tag pair is missing, the missing tag will appear as a ghost tag, half-transparent. In the default verification profile ghost tags only come up as Notes, but since they can lead to structural issues in the target file, they must be corrected – and one way to make sure that you notice them is to set the level to Error.
- Tag order: As languages construct sentences differently, tags might be placed in a different order in the translation compared to the source. By default these changes appears as Warnings, even if the modified order is justified. With this in mind it might sound reasonable to lower the severity level to Note, but doing so can also lead to overlooking genuine issues. So please be cautious.
- Spacing: Studio also checks for changes in the spacing around the tags and reports them even if they are justified or have no effect at all on the structure of the final translation. Imagine a space change after or before a bold tag – it does not really matter. The default level is Note, and in most cases should be kept this way.
- Formatting tags: Here the change is not about the level, but about whether Studio should check them in the first place. By default they are not picked up during verification, but I would argue in favor of checking for them, if you would like to make sure that the formatting of the target document indeed matches that of the source file.