Studio QA can compare the number of brackets on source and target sides. However, when bilingual translation is applied across a project (extra measurements, references to untranslated UI, etc.), this check can generate dozens of False Positives, making it difficult to identify true issues. It would be helpful to have an optional setting for the brackets check that only analyzes the target, and reports when the number of opening and closing brackets of each type is not even. Example:

Source:
English text

Target:
English text (Translation)

---No error, because "("=1 and ")"=1.

Source:
English text and [placeholder].

Target:
English text and [placeholder] (Translation and [placeholder).

---1 error, because "["=2 but "]"=1.