Hi everyone,

we noticed a few issues with the Number Verifier plugin related to separators.
Regardless of the language combination, the issues described below produce a lot of unwanted error messages or false positives,
which in turn creates additional work for our translators during the QA check.

1. Whenever there is a smaller sequence of numbers separated by a hyphen, the Number Verifier (NV) claims that the separator (-) is not recognized.
When we add the hyphen as a custom separator in the NV settings, the "Separator is not recognized" error message disappears, but is replaced by the
"The group value is out of range" message. Based on the NV documentation, this is due to the fact that the hyphen must be preceded by at least
3 digits for the string to be properly recognized. In our case, the customer has a lot of product names that contain sequences like the own shown below (i.e. 13-2)

This is not a customer-specific issue, though.The same happens with segments that have ranges (like "keep pressure between 2-5 hpa") in them.
Working with regular expressions to exclude these strings doesn't cut it for us, as we would risk to miss erratic changes of these strings (i.e. when working with fuzzy matches).

Is there an easier way to tag these kind of strings as being a range?

2. We also noticed that the NV does not always adhere to the thousands and decimal separators specified in the NV settings.

In the example below we should not get an error message according to our settings. We allow commas as thousands separators in the source and spaces in the target.

The message even pops up when we allow every single default separator in both source and target.

Again, this produces a lot of false positives.

Any idea why this is happening?

Thanks in advance for your support!

KR,
Julian