I have to agree with Neil about the irritation of false positives and how it makes you annoyed with Studio.
I have had problems with false positives from date recognition in Austrian for years.
I reported it years ago and, since other people commented about other languages with date recognition problems in the same thread, I naively thought it would be corrected "soon".
For example "1. Januar 2018" is NOT recognised as a date in Austrian, but its translation into English as "1 January 2018" IS recognised as a date.
So I get 3 errors, two errors because the numbers "1." and "2018" are missing in the target segment ("1. Januar 2018" is recognised as 2 numbers separated by a word in Austrian) and then I get a third error because Studio thinks there is an extra date in the English target segment.
I have been thinking about converting the Austrian TMs and termbases to German (which does not have this problem) to get rid of the annoyance, but that means convincing the clients and then actually spending the time to do the conversion, so I will probably let it slide another few years before I finally lose my patience. If I had known this in advance I definitely would not have used Austrian.
Yes, it is technically possible to use regex when I happen to get another Austrian job that happens to have a lot of dates in it, but I don't have the patience for using a separate workflow in these cases. I just grit my teeth and spend the few additional minutes needed in that occasional job to check the list of "missing" numbers.
It does, however, leave a bad taste in my mouth every time. (Customer satisfaction?)
ASAP Language Services